Spray records: what a defensible application log contains

Every time a tank is filled and a boom goes down, two obligations begin at once. The first is agronomic: hit the target pest, at the right rate, on the right crop. The second is a promise to everyone the crop and the field touch afterwards — the worker who walks the rows next morning, the crew that harvests, the neighbour downwind. That second obligation is discharged not by the spray but by the record of it.

A spray record is not a diary entry. It is the document you hand to an auditor or an investigator long after the crop has been sold, and the only thing standing between an honest application and a drift complaint you cannot answer. This page is about what belongs in it, why each field earns its place, and why the version most farms keep fails when it is needed.

The active ingredient is the fact; the product name is a label on a jug

The instinct is to write down what you poured from — the brand. That is necessary, but it is not the part that has to survive. The residue tolerance and the intervals that protect people and the crop are written against the active ingredient, not the name on the container. The chemistry is what the rule attaches to; the name is what marketing attaches to.

This matters because product names are the least stable thing in the chemical supply. A product gets reformulated and keeps its name, or renamed and keeps its formulation; it is discontinued, re-registered under a new owner, sold as a generic under three labels. A record that names only the product can become an orphan the year the catalogue changes. One that names the active ingredient stays legible, because that is what a certifier cross-checks against an approved-inputs list and what an investigator matches to a residue result.

So write both: the product, its concentration, and its registration or EPA number where one applies, so the record points back to a specific label; and the active ingredient, because that is what the rest of the world reasons about. When the two seem to disagree, the active ingredient is the fact and the name is the packaging.

A defensible application record carries all of this

The list is longer than a treatment log because a spray touches more people and more downstream product. Every field earns its place by being something an auditor, an insurer, or your own future self will ask for.

• The product and its active ingredient, with the concentration and the registration or EPA number where one applies. The name points to the label; the active ingredient is what the tolerance is written against.
• The rate actually applied, and the total quantity mixed. Not the label’s maximum, not the rate you meant to use — what went through the boom, over what area.
• The lot or batch number, the thread that connects your field to a recall you have not received yet.
• The target crop and the target pest, enough to show the application was on-label for what you were treating.
• The field or block, identified precisely enough that the re-entry and harvest constraints attach to one piece of ground and nothing else.
• The date, with a start and an end time. A re-entry clock starts at a moment, and a large block sprayed across an afternoon has a real spread you may need to reconstruct.
• Who applied it, and under what licence — part of whether the application was lawful, not a formality bolted on afterwards.
• The equipment — the sprayer, the nozzles, the calibration behind the rate that lets you stand behind the rate.
• The weather at application — wind speed and direction, temperature, humidity. The field everyone skips, and the one a drift complaint turns on.
• Both intervals, and the calendar date each one ends. The re-entry and pre-harvest intervals from the label, and the two dates they resolve to for this application.

Notice how much of this a livestock treatment record shares: active ingredient, lot number, who did it, and an interval before the thing treated is safe to touch or to sell. The structure repeats because the problem repeats — a substance was applied, and time has to pass before the consequences clear.

Two clocks start when the tank empties, and they protect different people

A completed application starts two separate clocks, and they are not the same clock told twice.

The re-entry interval, or REI, is a constraint on people: the time that has to pass before anyone may go back into the treated area without specified protection. Its victim, when it is ignored, is a human being — a worker sent to scout, weed, or irrigate a block that is not yet safe to walk. The pre-harvest interval, or PHI, is a constraint on the crop: the time before the treated crop may be harvested. Its victim is the produce itself, and everyone who eats it — a residue that has not fallen below tolerance leaves the farm on the truck.

Two clocks, two people at the wrong end of a mistake. They can be different lengths, are set independently by the label, and honouring one does not honour the other. A record that blurs them into a single number will eventually let a crew into a block safe to harvest but not yet safe to enter, or the reverse. Carry them as two fields — which is why worker safety recordkeeping and spray records are the same discipline seen from two sides.

The interval is the justification; the end date is the constraint

Here is the field farms most often get half-right: they write down the interval and stop, and an interval is not actionable. Say, hypothetically, the label hands you a window measured in days — a person at the edge of the block cannot act on “a window of some days.” They have to know the calendar date it ends, and to get there they do arithmetic, from the application time, under whatever pressure the day is applying. Sums done at the edge of a field are how a crop gets harvested a day early or a worker walks in a morning too soon.

So write the interval and the date it resolves to. Both. The interval is the justification — how you show the date was not invented — and the calendar date is the constraint the person on the ground can obey without doing sums. Do it for the re-entry date and the pre-harvest date separately. A record with two intervals and two end dates turns a label into something a tired person can act on correctly; one with two intervals and no dates has delegated the most dangerous step to the least equipped moment.

Weather is the field everyone skips, and drift claims turn on it

Ask a farm to show you a spray record and the gap is almost always the same one: the weather line is blank. Product, rate, date — filled in. Wind speed and direction, temperature, humidity at the moment the boom was down — empty, because the crop needed spraying and nobody stopped to write the sky down.

That blank is where a drift complaint lives. When a neighbour’s crop shows injury, nobody disputes that you sprayed; the question is whether the conditions were within the label’s limits when you did. A weather line recorded at the sprayer answers that with evidence; one reconstructed a week later from memory answers it with a guess a hostile party will treat as one.

The label itself usually constrains the conditions you may spray in — wind ceilings, temperature limits, buffer requirements — and the weather field is how you show you stayed inside them. It is also how you defend against a claim you did nothing to cause: the record of a light breeze from the safe direction ends the conversation. It costs seconds and is unrecoverable after the fact. Write it down while the wind is still blowing.

The applicator’s memory is not a record

The most common recordkeeping system on a real farm is a person who remembers. They know what they sprayed, roughly when and where, and will tell you the intervals are “fine, plenty of time.” For a day or two, that person is a better record than most software. The problem is everything after that.

A memory does not survive a second person: when the applicator is not the one who sends the scout in or calls the harvest, the constraint in their head never reaches the person about to violate it. It does not survive time — three weeks on, with forty applications since, the details blur and the confidence does not, which is worse. And it produces nothing an auditor or an insurer can read. When the question arrives — backwards, from a test result or a complaint, weeks later — “I remember it was fine” is not a record. It is the absence of one, delivered confidently.

A written application record is written for a stranger reading it a year from now, with no memory to lean on and no benefit of the doubt. That stranger might be an audit reviewer, a certification inspector, or the buyer who asks for your traceability records before signing — the same document, only the reader changes.

Record at the sprayer, not at the desk that evening

Nearly every failure in a spray record is a failure of latency — the gap between the application and the writing-down. A record made at the sprayer is made by the person who mixed the tank, read the lot number off the jug, calibrated the boom, and can see the wind. One made at the desk that evening is a reconstruction, and the fields reconstructed worst are the ones that matter most: the weather, the true rate, the times.

This is the honest place for software, and its limit. Farm40gives you an input application record where the active ingredient, the rate, the lot number, the re-entry interval, and the pre-harvest interval are first-class fields on the form where you log the spray, and it computes the end date from the interval and the application date you enter, so the calendar constraint is written down, not left as arithmetic for later. The limit belongs in the same breath: it records what you enter and nothing more. It cannot know the correct interval for your product, and it does not read labels — type the wrong interval and it will faithfully compute the wrong end date. It does the sums so a tired person doesn’t; it does not replace the label as the source of the number. That part stays yours.

Where the spray record connects to the rest of the farm

An application record does not live alone. Upstream, it is part of the crop story — the plan, the plantings, the scouting that decided the spray was needed — the subject of crop management. Downstream, it is part of the packet a buyer or certifier asks for, and part of being able to say, about any lot that left your farm, exactly what was applied to it and when the field and the crop became safe — the whole subject of farm recordkeeping.

None of this requires software. It requires that the active ingredient, the true rate, the lot number, the weather, and both interval end dates be written down at the sprayer, where the person entering the field and the person calling the harvest will actually look. Everything else is an implementation detail — but that is where farms fail: not in understanding that a re-entry interval protects a person and a pre-harvest interval the crop, but in surviving the ordinary Tuesday when the person who knew is somewhere else and the record has to speak for itself.