The organic system plan reads like paperwork — a document you write once, submit, and file. Treated that way, it becomes the single biggest liability in a certified operation, because a plan is not a record of anything that happened. It is a statement about what will happen, made before any of it does, and a statement made in advance is worth exactly as much as the evidence that follows it.
This distinction sounds academic until an inspection turns on it. An inspector does not certify the plan; a certifier already did that when they approved it. What the inspection tests is the gap between the plan and the season — whether what you wrote you would do lines up with what your records show you actually did. The plan sets the terms. The records are the only thing that can meet them.
Your certifier is the authority. What an organic system plan must contain, how it is amended, and what your certifier expects your records to demonstrate are set by your certifier and your jurisdiction’s regulator, and they differ and change. This page describes the general shape of the plan-and-record relationship, not a specific standard. Confirm every actual requirement with your certifier.
A plan is a promise, not a description
Most farm documents describe something that already exists — a field map, a herd inventory, a list of equipment. The organic system plan is different in kind: it describes an operation that does not exist yet, written in the future tense and agreed to before the first seed goes in the ground. You are telling your certifier what will be true, not what is true.
That reversal is why the plan cannot be self-certifying. A promise is not evidence that it was kept. Something else has to carry that weight, and that something is the ordinary, dated, specific record of what actually happened on the farm across the season the plan covers.
Every clause needs a record that could contradict it
A useful test for any organic system plan is to read each clause and ask what record, if it existed, would prove the clause was followed — and what record, if it existed instead, would prove it was not. If neither record could exist because nothing is written down, the clause is unverifiable, which for certification purposes is close to unwritten.
Take a clause about keeping organic seed stock separate from conventional stock in storage. The plan states the intention. The record that tests it is a storage log or a labelled-bin photo taken over the season — something dated, something that could not have been produced after the fact without it being obvious. This is the same discipline covered in organic certification recordkeeping more broadly: a claim about a period needs evidence spread across that period, not gathered at its end.
The plan you filed is not the plan in force if it is stale
Farms change mid-season more often than the plan gets updated to match. A field gets added, a new input gets used because the first choice was out of stock, a practice shifts because last year’s did not work. Each of those is a small, reasonable decision. Each one also creates a gap between the plan an inspector reads and the operation they are standing in.
The record that closes that gap is not a rewritten plan — it is a note, made at the time of the change, of what changed and why, filed alongside the plan rather than folded silently into it. An inspector who finds a documented divergence reads a farm that is managing its plan honestly. An inspector who finds an undocumented one has to wonder what else does not match.
The plan and the input approval have to point at each other
A thin plan lists what will be grown or raised and stops there. A working one goes further: it names the fields, the rotation, the fertility sources, the pest and weed management approach, and the buffer arrangements with adjoining land, because each of those is a place where the season could quietly diverge from the promise. The more specifically the plan describes what will happen, the more precisely the records can later show whether it did — a vague plan cannot be contradicted by anything, which sounds safe but is actually the opposite of safe. A plan too general to fail is also too general to prove you kept it.
A plan typically names the categories of input you expect to use. Individual materials still have to clear approval before they are applied, and the record of that approval should reference back to the plan it falls under. A plan that lists “approved fertility inputs” in the abstract and an approval log that never mentions the plan are two documents that happen to sit near each other, not one system. A reader — your certifier, an inspector, or you a year from now — should be able to move from one to the other without a translation step.
Write the plan for the record it will require, not just the season
A plan written to satisfy a certifier’s form and a plan written to be checkable against records over a season are not automatically the same document. The second version anticipates its own evidence: for every practice it commits to, it implicitly names the record that will later prove the commitment was kept. A plan that says “equipment shared with the conventional side will be cleaned between uses” is only as good as the cleaning log that record generates every time the equipment is used — the subject covered in split-operation recordkeeping for farms running both sides at once.
This is where Farm40 fits without pretending to replace the plan itself. Input applications, harvest lots, and the documents behind them are entered once and stay attached to the field and the planting they belong to, so the record a season generates is already organised the way an inspector reads it — by field, by date, by input. Its limit: it has no notion of your organic system plan and cannot tell you whether a given record satisfies a given clause of it. It stores what you enter and keeps it retrievable; matching that record against your plan and your standard is still a judgment for you and your certifier.
The inspection reads the relationship, not either document alone
By the time an inspector arrives, the plan and the records are being read together, as one argument. The plan says what should be true; the records say what was; the inspection is the comparison. A farm that treats the plan as a filing exercise and the records as an afterthought has usually written two documents that were never meant to meet, and it shows the moment someone tries to line them up — the same reading an inspector does during the annual inspection. Keeping the plan current and the records contemporaneous the whole season through is what makes that comparison uneventful instead of a scramble.