Most of the anxiety around a food safety audit attaches to the day itself — the idea of a stranger walking the property, looking for something wrong. The actual day is more structured and less adversarial than that mental picture, and it follows a shape that repeats across most schemes even though the specific checklist differs from one to the next.
Knowing the shape in advance does not change what the auditor finds. It does change how the day feels, and for a farm that has done the recordkeeping honestly all year, that is most of what is left to manage.
The itinerary and scoring belong to your scheme. The exact sequence, duration, and pass/fail criteria for an audit are set by the standard you are being audited against and communicated by your certifier ahead of time. This page describes the shape most audits share, not a substitute for your scheme’s own instructions.
The day starts as a conversation, not an inspection
Most audits open with the auditor and the farm sitting down together — reviewing the scope, confirming which parts of the operation are being covered, and going over the general flow of the day. This opening conversation is also where any changes since the last audit, or since the application, tend to come up: new fields, a new water source, a change in crew size. It sets the terms for everything that follows and is usually the least stressful part of the day, mostly because nothing is being checked yet.
It is a reasonable moment to ask logistical questions of your own — roughly how long each portion of the day will take, whether the auditor needs anything set up in advance, who besides the owner should expect to be pulled aside later. None of that changes what gets found, but it removes a layer of uncertainty that otherwise sits over the whole day for a farm going through the process for the first time.
The document review is where most of the day actually happens
The part that surprises first-time farms most is how much of the audit happens at a table rather than in a field. The auditor works through the food safety plan and the records behind it — water tests, training records, sanitation logs, harvest and lot records — checking each against the standard and, often, tracing a specific lot through several of them at once to see whether the records connect. This is the exercise a mock audit is meant to rehearse, and a farm that has run one usually recognizes exactly what is happening here.
The pace of this part depends heavily on how the records are organized. A farm that can produce the requested document in under a minute moves through the review quickly; one that has to search for it, or reconstruct it from memory, extends the day and, more importantly, signals something about how available that record is in ordinary operation.
The walk-through checks whether the paper and the place agree
The physical tour of the farm exists to test one thing: does what the documents claim match what is actually there. A sign-off that says the cooler is monitored gets checked against a cooler that has a working thermometer. A sanitation log claiming bins are cleaned between loads gets checked against bins that look clean. The auditor is not primarily evaluating whether your practices are good in some abstract sense — the standard already set the bar — they are checking whether the practice described on paper is the practice actually happening, including on an ordinary day when no audit was scheduled.
This is also the part of the day where equipment condition and visitor or vehicle access tend to come up directly rather than through a document — a bin with visible damage, an unfamiliar truck at the dock, a gate left open near a field. None of it is a trap. It is the same test as the document review, just conducted with the auditor’s own eyes instead of a page.
The interview is the part most farms do not expect
Somewhere in the day, the auditor typically talks to someone other than the owner — a worker on the wash line, someone doing the harvest, a crew lead. This is not a formality. An owner describing a procedure is describing the plan; a worker describing the same procedure, asked independently and without being coached beforehand, is describing the practice. The auditor is testing whether those two descriptions match.
A farm whose training is real tends to do well here without any special preparation, because the worker actually knows the procedure and can describe it in their own words. A farm whose training exists mainly on paper often discovers the gap right here, in front of the auditor, which is a worse place to discover it than during a mock audit weeks earlier.
There is nothing wrong with a worker saying “let me think” or describing a procedure imperfectly in their own words — auditors expect real answers, not rehearsed ones. What tends to raise a flag is the opposite: an answer that sounds coached, or a worker visibly checking with the owner before speaking, because both suggest the practice being described may not be the practice actually followed day to day.
The closing conversation is where findings get named, not decided
At the end of the day, the auditor usually reviews what was observed — strengths, gaps, anything that will become a formal finding. This is not typically where scoring or certification decisions are finalized; that usually happens afterward, against the standard’s own criteria. What the closing conversation is good for is clarity: asking what a specific observation means, and what, if anything, needs a corrective action in response before the file is considered closed.
A farm that treats this conversation as adversarial tends to get less out of it than one that treats it as the last chance to understand exactly what was seen and why it mattered. The auditor has spent a full day forming an impression of the operation; that impression, asked about directly, is often the most useful thing said all day.
What preparation actually buys on the day itself
None of the shape above changes based on how prepared a farm is. What changes is how quickly and how calmly a farm can produce what is asked for. Farm40 exports the records a reviewer commonly requests — input applications, harvest and traceability records, treatment logs — in a form that can be handed across the table rather than assembled on the spot. The limit is the one that matters most on audit day itself: an export only reflects what was entered over the season, and it cannot answer for a record that was never made or a practice the walk-through finds does not match the paper. The day still tests the season, not the software.