The annual organic inspection is not a test you cram for the week before, and treating it like one is the surest way to fail it. An inspector is not there to check whether your farm looks organic on the day of the visit — they are there to read a season’s worth of records and see whether the account you kept matches the promise your organic system plan made. Preparation, done honestly, is a summer’s work. What happens the week before is retrieval, not creation.
Most first-time certified operations discover this the hard way — they treat the inspection like a one-time hurdle and scramble to assemble a season’s worth of evidence in the days before, which is exactly the scramble that produces records looking like they were written for the occasion. By the second or third inspection, the same operations have usually learned that the only way to make inspection week uneventful is to make recordkeeping a habit the rest of the year, not a project that starts when the certifier calls to schedule — the same habit covered across organic certification recordkeeping as a whole.
This page is about what that retrieval actually looks like, and about the one thing no last-minute effort can fix: a record that reads like it was written for the occasion rather than at the time.
Your certifier is the authority. What an inspector reviews, how findings are handled, and what constitutes a passing inspection are set by your certifier and your standard, and they differ between certifiers and jurisdictions. This page describes the general shape of inspection preparation, not your certifier’s specific checklist. Confirm exact expectations with your certifier ahead of the visit.
The inspector is reading a season, not a snapshot
An inspection tests whether the operation, over the whole period since the last review, matched what the organic system plan committed to. That framing changes what “being prepared” means. It is not primarily about the farm looking tidy on inspection day; it is about whether the records from every week of the season, not just the recent ones, can answer the questions an inspector is likely to ask.
The practical consequence is that the most useful preparation happened months earlier, at the moment each record was written. What is left to do beforehand is mostly assembly: gathering the plan, the input approvals and applications, the harvest and sales records, and any incident notes into a form the inspector can move through without waiting on you to go find things.
An experienced inspector reads how a record was written
The clearest sign of trouble is not a missing record — it is a record that was obviously created all at once, close to the inspection date. A logbook written in one pen, one sitting, with uniform handwriting and no correction across an entire season’s entries, does not read as a season. It reads as an evening. Inspectors who have seen many operations recognise this pattern quickly, because a genuinely contemporaneous record accumulates small irregularities — different pens, the occasional correction, entries made in a hurry — that a reconstruction does not.
This is the same tell that shows up in a food safety audit: the reviewer is checking the record’s form as much as its content, because form is evidence of when the record was actually made.
Gather by question, not by document type
The most useful way to prepare a record set is to organise it around the questions an inspector will actually ask, rather than by the filing categories that happen to exist on the farm. “Show me this lot’s history” needs the harvest record, the field it came from, the inputs applied to that field, and — following the audit trail from sale to seed — the seed it started from, pulled together in one place rather than scattered across four separate logs the inspector has to reconcile themselves.
If your operation runs organic and conventional side by side, expect the questions to focus on separation — storage, equipment cleaning, and lot coding — the territory covered in split-operation recordkeeping. Have those specific records ready rather than folded into a general input file.
The walk-through tests whether the paper matches the field
Most inspections include an actual walk of the operation alongside the review of records, and the point of walking the fields, the storage, and the equipment is to check the physical layout against what the records describe — that the buffer strip shown on the map is the buffer strip actually planted, that the storage area the plan calls separate is actually kept separate, that the equipment named in a cleaning log is the equipment that was actually used. A record and a farm that quietly diverge over the course of a season are the exact thing a walk-through is designed to surface, so it is worth doing your own version of that walk before the inspector does, rather than being surprised alongside them.
A found gap is better handled than hidden
Every operation has some imperfect stretch in its records — a week nobody logged, a note that is vaguer than it should be. The instinct to quietly patch it before the inspector arrives is understandable and usually the wrong move, because a patch made under time pressure often has the same tell as a fabricated record: it reads like something written for the occasion. A short, honest, dated note explaining what happened and why the record is thin holds up far better than a suspiciously complete one produced overnight.
It also helps to raise a known gap with your certifier before the inspection rather than waiting for it to be discovered during it. A gap you disclosed yourself, with an explanation of how you are addressing it going forward, is evidence of an operation managing its own recordkeeping honestly. The same gap discovered unannounced by the inspector reads as something you either missed or hoped would not come up.
What preparation actually buys you
Done honestly, inspection preparation is not a defence against scrutiny — it is the retrieval of evidence that was already good, gathered into a form an inspector can move through quickly. In Farm40, input applications, harvest lots, and the documents behind them are entered once, tied to the field and date they belong to, and stay retrievable by field, by date, or by lot rather than needing to be reassembled from separate notebooks before a visit. Its limit is the same one that runs through this whole category: Farm40 has no notion of your certifier’s specific checklist and cannot tell you whether what it holds will satisfy your standard — it keeps the record retrievable; whether the record is sufficient is a judgment for you and your certifier.