Most of a farm's input records describe things done on the farm, by someone on the farm, to a field the farm can walk. A seed treatment breaks that pattern before the first seed even reaches the ground — it was applied at a facility, by a company the farm may never deal with directly, weeks or months before the bag arrived. And yet it is every bit as much an input as anything sprayed from a boom, and it still has to appear in the record of what that field, and that crop, actually received.
The gap this creates is not that the treatment doesn't matter. It's that nobody on the farm is naturally positioned to write it down, because nobody on the farm did it. This page is about closing that gap — treating the seed tag and the supplier's documentation as the record, rather than assuming an input applied somewhere else is somehow not part of the chain.
The treatment label is the authority. This page does not state which active ingredients are used in any seed treatment, what pests they target, or any handling interval for treated seed. Those are set by the treatment's own label, by the seed supplier's documentation, and by your regulator, and they vary by product and crop. What follows describes the process of recording a seed treatment as part of your field's input history — not the specifics of any treatment itself.
An input applied off-farm is still an input
It's easy to draw the boundary of "what we recorded" around the things that happened on the farm's own ground, by the farm's own hands. A seed treatment sits outside that boundary by construction — it happened at a seed conditioning facility, under a different company's process, before the seed ever reached the farm. But the boundary that actually matters isn't where the input was applied. It's what ended up in the field, and a treated seed puts an active ingredient into that field just as certainly as a boom pass does.
A traceability packet, a certifier's audit, or a buyer's question about what was applied to a crop doesn't stop at the farm gate. It asks about everything the crop received, and a seed treatment is chronologically the first thing it received — before the planter even started. Omitting it isn't a small gap. It's a missing first chapter.
This matters most for organic and residue-sensitive markets, where a buyer or certifier reconstructing what touched a crop needs the full list, not the list of what happened after the farm took over. A crop grown from untreated seed and one grown from treated seed can look identical in the field and answer very differently to that question — and the only place the difference is visible is in a record most farms never think to keep past planting day.
The seed tag is the record, if you keep it
The supplier's own documentation — the seed tag, an accompanying data sheet, or an invoice line describing the treatment — is generally where the treatment's details actually live: the active ingredients used, the pest or disease each targets, and any handling guidance for the treated seed itself. The farm's job is not to reconstruct this information. It's to keep what the supplier already provides, attached to the planting record for the field that seed went into, rather than letting it get discarded with the bag it came in.
This is a smaller task than most input recordkeeping, and it fails for a correspondingly small reason: the tag gets thrown out before anyone thinks to photograph or file it. Treat the seed tag the way you'd treat a spray record's product label — the thing to keep, not the thing to discard once the job it labels is done.
Treated seed can carry its own handling rules
Because a seed treatment concentrates an active ingredient onto a small, easily dispersed product, treated seed is frequently subject to handling, storage, and disposal guidance separate from both the seed itself and from an equivalent field-applied spray. Leftover treated seed, dust generated during planting, and spillage can all be subject to specific instructions from the treatment's label, and those instructions are not always the same as the ones that would apply if the same active ingredient had been sprayed on the field directly.
Recording that these precautions were followed — and keeping the documentation of what they were — belongs in the same place as the rest of the treatment record. It's a smaller and more specific version of the same discipline described in input inventory tracking: know what you're holding, in what quantity, and what its own label requires of you while it's in your possession.
Farm-applied treatments follow the ordinary rules
Some operations apply their own seed treatment on-farm, rather than buying pre-treated seed — a slurry mixed and applied at planting time, using a treater or a simple auger setup. In that case, the off-farm documentation problem disappears, but the underlying obligation doesn't: the active ingredient, rate, lot number, and date of the treatment still need to be recorded, exactly as they would for any other input applied that day. The only thing that changes is who's holding the pen — the responsibility for capturing the treatment at the time it's made moves from the seed supplier's documentation to the farm's own records, following the same discipline described generally in what belongs in a spray record.
Building the seed treatment into the field's chain
Once the treatment's details are captured from the seed tag, they belong in the same record as everything else applied to that field — filed with the planting date, the variety, and the in-season sprays that followed, so that a season's full input history reads as one continuous chain rather than starting the story after the seed was already in the ground. This is the same principle behind spray and input records generally: the record belongs to the field and the season, not to whoever happened to apply the input.
Farm40 lets you log a seed treatment as an input record tied to a planting, with the active ingredient and lot detail as first-class fields alongside anything sprayed later in the season — so the field's history includes its first input, not just the ones applied after emergence. Its limit is the same one that applies to every input record here: it stores what you enter from the seed tag or supplier documentation, and it has no way to independently verify what treatment a seed lot actually received. Keeping the tag, and transcribing it accurately, is still the step that makes the record true.
