A food safety inspector can ask to see your records with no appointment, and federal rule requires you to make them available promptly, right then, for review and copying (21 CFR 117.320). What they check: whether your batch, CCP, and monitoring records are complete, current, signed, and tied to the right product and lot (21 CFR 117.305). The records also have to be created as the work happens, not filled in later from memory (21 CFR 117.305(d)). The producers who stay calm are not the ones with the fattest binder. They are the ones who can pull the right record for a product, a date, or a product group without scrolling.
What a food safety inspection is, and how it differs from an audit
An inspection is a regulatory visit. A government authority, FDA or a state agency acting under its own food-safety law, checks that you are following the rules that apply to what you make. It can be routine, or it can be triggered by a complaint or an outbreak, and it is often unannounced.
That is different from an audit. An audit is usually voluntary or required by a customer, run by a third party against a certification standard like SQF or BRCGS, and scheduled in advance with a defined scope. Fail an audit and you miss a certificate. Fail an inspection and the consequences are heavier: mandated corrections, a hold on product, or a recall.
The two words get used interchangeably on the floor, but for this piece the line matters. This is about the regulator who can show up without warning, not the certifier you booked six weeks out.
One note on scope: which rule applies depends on your product and your size. Most human-food facilities that register with FDA fall under the Preventive Controls rule (21 CFR Part 117). Acidified foods, seafood, and juice have their own HACCP records under separate parts. Smaller operations can qualify for modified requirements, but even then you keep records. The citations here are to Part 117 because it is the most common case. Confirm the part that governs your product.
The inspection you didn't schedule: someone else's visit becomes yours
If you run out of a shared or commissary kitchen, the walk-in often is not even about you. An inspector is on site for another tenant, sees your operation running, and asks a couple of questions in passing. Where do you log your temperatures? Can you show me the last batch you ran?
If you are organized and your answers are quick, that is the whole interaction. A few questions, a nod, back to work. If you fumble, if the answer is "it's in a binder somewhere" or "I'd have to check with the owner," a casual question can become a real inspection fast. What decides it is whether the record is there when someone asks, not how clean the floor looks that morning.
That is the scenario worth preparing for, because you do not get to pick the day.
What an inspector can actually ask to see: and the rule behind it
Under 21 CFR 117.320, an inspector can request your records out loud and you have to make them available promptly, on the spot, for review and copying. There is no "let me send that over next week." So the practical question is not whether the records exist. It is whether you can put your hands on the right ones while someone is standing there.
Here is what they are checking, and what each record has to carry.
- Your monitoring and CCP logs. The entries showing you actually checked the things your plan says you check: temperatures, pH, times, whatever your control points are. The rule requires them to hold the real values you observed, not a tidy summary written afterward (21 CFR 117.305(b)).
- That each record is complete and attributable. Every entry needs the date, and where it matters the time, the initials of the person who did the check, and where appropriate the product and its lot code (21 CFR 117.305(f)). A log with blank initials or a missing lot code is a finding waiting to happen.
- Your corrective actions and verification. When a check came back out of range, what you did about it, and who confirmed the control was back in line.
- How far back it goes. Records have to be kept at the facility for at least two years from the date they were made (21 CFR 117.315(a)(1)). "We only keep the current month" is not an answer.
The through-line: an inspector is not grading your handwriting. They are checking whether the record exists, whether it is complete, and whether it ties to a specific product and lot. Miss any one of those and the size of the binder does not save you.
The moment you sweat: proving it from a spreadsheet you haven't finished
Ask a producer who has been at it more than a year or two where their records live, and a lot of them will say a spreadsheet. It works fine at first. Then it grows. Tabs multiply, rows run into the thousands, and finding one batch from four months ago means scrolling and squinting while someone waits.
That scroll is the moment you sweat. Not because you did anything wrong, but because proving you did it right is suddenly slow, and it is happening in front of an inspector.
There is a worse version. You are mid-shift, mid-batch, and the sheet is not current, because you have not stopped to update it yet. The checks happened. The record did not. That gap is exactly what the rule is written against: records are supposed to be created as the work happens, not reconstructed later from memory (21 CFR 117.305(d)). A spreadsheet you fill in at the end of the day, or the end of the week, is a record the regulation already treats as suspect.
This is the real risk of end-of-shift logging, and it is not about being lazy: the system makes real-time entry too clunky to keep up with, so the record drifts behind the work, and the gap only surfaces when someone asks to see it.
How to be ready before they ask: records you can surface in a couple of taps
Being ready comes down to two things: capturing the record when the work happens, and pulling it back up without a hunt.
That is what FourFoxes is built to do. Logging is low friction, so a CCP check or calibration gets recorded in the moment, at the equipment, instead of piling up for later. Surfacing is just as fast: pull every record for a specific product, a specific date range, or a whole product group, and hand it over. The minutes of scrolling turn into a couple of taps.
None of that changes what the rules require. It changes whether you can answer for them on demand. Every entry already carries its date, its initials, and its lot code, because the system captures them as you go, which is what 117.305(f) asks for. Records stay put through the retention window without you babysitting a pile of old tabs. And because electronic records count as onsite when they are accessible from an onsite location (21 CFR 117.315(c)), a system you can open right there on the floor meets the "available for review" bar by design.
A two-minute readiness check
- Can you pull every batch that used a specific ingredient lot, right now, without asking anyone?
- Can you show today's checks as of this moment, not as of last night?
- Does every entry have a date, an initial, and a lot code, with no blanks?
- Can you produce a record from eighteen months ago as fast as one from this morning?
If any answer is "not really," that is the gap an inspector would find first.
FourFoxes is HACCP logging and compliance for small food and beverage producers. Log every check as it happens, then pull the records for any product, date, or product group the moment someone asks. The same readiness that clears a scheduled audit turns an unannounced inspection into a few questions and a nod.
Explore audit readinessFAQ
Can a food safety inspector show up without an appointment?
Yes. Regulatory inspections are often unannounced, and for-cause visits triggered by a complaint or outbreak almost always are. Under 21 CFR 117.320, when an inspector asks for your records, you have to make them available promptly, on the spot.
What records does a food safety inspector look at?
The records that show your food safety plan is running: monitoring and CCP logs with the real observed values, corrective actions, and verification. Each needs a date, the initials of who performed the check, and where appropriate the product and lot code (21 CFR 117.305).
What happens if you can't produce records during an inspection?
A check you cannot prove is treated as a check that did not happen. Incomplete, unsigned, or missing records become inspection findings, and depending on severity the outcome ranges from a required corrective action within a set period to a product hold or a recall. The record existing is not enough: you have to be able to produce it on request (21 CFR 117.320).
How long do I have to keep food production records?
Under the Preventive Controls rule for human food, at least two years from the date the record was made, kept at the facility (21 CFR 117.315(a)(1)). Retention windows differ under other rules, so confirm the part that governs your product.
Do digital records count, or do inspectors want paper?
Digital counts. Electronic records are considered onsite as long as they are accessible from an onsite location (21 CFR 117.315(c)), so a system you can open on the production floor satisfies the requirement to have records available for review.
Is a food safety inspection the same as an audit?
No. An inspection is a regulatory visit by FDA or a state agency, often unannounced, with legal consequences. An audit is usually voluntary or customer-required, run by a third party against a certification standard, and scheduled in advance. This post is about the inspection.