Every input record has an order built into it, whether anyone thinks about the order or not. First a material is checked against what the standard allows and what the organic system plan describes. Then, and only then, it goes on the crop or to the animal. Reverse that order — apply first, check later — and you have not made a records mistake. You have made a decision that cannot be undone by any record written afterward.
This page is about that ordering: why it matters more than almost any other sequence in organic recordkeeping, and what a record of approval actually needs to contain to do its job.
Your certifier is the authority. Which materials are allowed, under what conditions, and what counts as adequate approval documentation are set by your certifier and your jurisdiction’s regulator, and both differ by standard and change over time. Nothing here names a specific allowed or prohibited material. Confirm any real input with your certifier before it is applied.
Approval is a decision made while you still have a choice
The reason the order matters is not procedural tidiness. It is that approval, by definition, only means something before the fact. Checking a material’s status the day after it went on the field is not approval — it is an inquiry into damage already done. The record that protects an operation is the one dated before the material touched anything: a note that this product, this formulation, this lot was reviewed against the standard and the plan and cleared to use.
Contrast this with a conventional input application record, which typically documents what happened — the rate, the field, the date. Organic recordkeeping needs that same record, but it needs a step in front of it that a conventional operation does not: the approval that preceded the application, standing on its own, independently dated.
Verbal clearance is not a record
A common failure mode is treating a phone call as approval — a supplier says a product is fine for organic use, or a neighbouring farm vouches for something they use themselves, and the material goes on the field the same afternoon. None of that is a record. A record has to exist independently of the memory of the call, dated, naming what was checked and against what standard, in a place you can point to later. If the only evidence of an approval is that someone remembers making it, the approval effectively did not happen for certification purposes.
An unapproved application is not a paperwork problem
It is tempting to think of a missed approval as an administrative gap that a good record can close retroactively — write down what was used, confirm afterward that it was fine, move on. That model works for most farm records. It does not work here, because the thing at risk is not the completeness of a log; it is the organic status of whatever the input touched.
Depending on your standard, an unapproved material applied to certified ground can cost that field, that crop, or that animal group its status for the relevant period — a consequence no subsequent record can reverse, because the material is already in the soil or in the animal. This is the sharpest way organic recordkeeping differs from most of the recordkeeping covered under farm input records generally: elsewhere, a record mainly explains a decision after the fact. Here, the record of approval is the decision, and it has to exist before the decision takes effect in the field.
It also matters who is doing the applying. On a farm with more than one person handling inputs — an owner, a family member, seasonal labour — approval that lives only in the owner’s head protects nobody but the owner’s own decisions. The record has to be somewhere the person actually standing at the sprayer can check it before they load the tank, not somewhere they would have to interrupt the work to go ask about. A gate only the owner can see is a gate everyone else can walk through by accident.
What an approval record needs to hold
A defensible approval record identifies the material precisely enough that there is no ambiguity about what was cleared — product name, formulation, supplier, and ideally the lot the operation intends to use, since formulations can change between lots from the same supplier. It states what the material was checked against: the standard, and the relevant clause of the organic system plan. And it is dated before the application record it supports, not alongside it.
What it does not need is a restatement of the standard itself. The record’s job is to show that a specific check happened for a specific material at a specific time — not to reproduce the rule being checked against. That rule belongs to your certifier, and it is worth resisting the temptation to write it into your own files as if it were fixed, since standards are revised and a copied rule can go stale silently.
New suppliers and new formulations reset the clock
An input approved once is not approved forever. A supplier can change a formulation without changing the product name on the label; a standard’s list of allowed materials is revised on its own schedule, not the farm’s. Treating last season’s approval as still current this season is the single most common way an otherwise-careful operation ends up with an unapproved application it did not intend.
The practical habit is to tie every approval to a season, a supplier, and where possible a lot — and to re-run the check whenever any of those three changes, rather than whenever the calendar suggests it might be due. This is the same seasonal discipline that governs seed and planting-stock sourcing, where a source that was fine last year still needs to be checked again this one.
Where this sits in the larger record
Input approval is one link in the longer chain covered by organic certification recordkeeping as a whole — the chain a certifier follows from a sold lot back through the harvest, the inputs, and the seed. In Farm40, an input application record carries the active ingredient, the rate, and the lot number as first-class fields, so once a material is approved and applied, the application itself is captured cleanly. Its limit is exact:Farm40 has no approved-input list and no concept of your certifier’s standard, so it cannot tell you whether a material should have been approved in the first place. That judgment, and the record of having made it before the sprayer moved, stays with you and your certifier.