Why does calibration matter if I already write down the rate I sprayed?

Because the rate you write down is only true if the sprayer actually delivered it, and a sprayer's actual output drifts over time — worn nozzles, changed pressure, a different ground speed than the last calibration assumed. Recording a rate is a claim; calibration is the check that makes the claim something you can stand behind rather than something you're assuming.

How often should a sprayer be calibrated?

Often enough that the rate you write down stays true — many operations calibrate at the start of a season, after any nozzle change or repair, and periodically through a heavy-use season, but the right interval for a specific machine and its wear pattern is a question for the equipment manufacturer, an extension service, or your own operational experience, not a fixed number this page can supply.

What should a calibration record contain?

The date of the calibration, which sprayer and which nozzle set was tested, the method used (a catch test, a timed distance test, or another standard method), the resulting output rate, and who performed it. Keep it alongside the spray records for the applications that relied on that calibration, since it's the evidence behind every rate those records claim.

Should recordkeeping software track sprayer equipment or calibration schedules?

That depends on the software, but it's worth knowing what it can and can't do before relying on it. A rate field on an application record stores whatever number you type in — it has no way to verify that a sprayer was recently calibrated or that the rate it delivered matches what's written down. Calibration itself — testing the machine, computing its actual output, and deciding when the next check is due — happens on the equipment, and the record of it belongs wherever your operation keeps maintenance history, software or otherwise.

Calibration Records for Sprayers

Every spray record has a rate field, and the rate field is treated as a fact — a number someone can read later and trust. It isn't a fact on its own. It's a claim about what a machine actually delivered, and that claim is only as good as the last time anyone checked that the machine was telling the truth.

A sprayer's real output drifts. Nozzles wear unevenly and deliver less, or more, than they did new. Pressure gauges lose accuracy. Ground speed varies with terrain and operator habit in ways that change the effective rate even when every setting on the sprayer looks the same as last time. None of this shows up by looking at the machine. It shows up only when someone tests what actually comes out of the nozzles and compares it to what the label calls for. This page is about why that test, and the record of it, is what makes the rate written on every application record actually true.

The label and the manufacturer are the authority. This page does not state a calibration interval, a target output rate for any product, or a required testing method — and it does not state a re-entry interval, pre-harvest interval, or any other regulated figure for any product either. Those come from the product label, the sprayer manufacturer, and your extension service or regulator, and they vary by equipment, product, and jurisdiction. What follows describes the process of recording a calibration and connecting it to your application records — not a calibration procedure, an interval, or a schedule of its own.

The rate you recorded is a claim about a machine

Write "22 gallons per acre" on an application record and it reads as settled fact. It isn't. It's a claim that the sprayer, on that day, with those nozzles, at that pressure and that ground speed, delivered 22 gallons over an acre — and every one of those conditions can drift without anyone noticing until a residue result, an efficacy failure, or an off-target injury claim asks whether the rate was really what the record says.

This is the quiet assumption behind every field in a spray application record: that the numbers written down are what actually happened, not what the operator intended. Calibration is the step that closes that gap — it's the only way to know the machine's actual output rather than its designed one.

Calibration turns an intention into a measurement

A sprayer's nominal settings — nozzle size, pressure, ground speed — imply a rate on paper. Calibration measures what the machine actually puts out under those settings, typically by catching output from individual nozzles over a fixed time or distance and comparing it to the target. The gap between the implied rate and the measured one is often small. It is sometimes not, and the only way to know which is true on a given day is to have actually measured it, recently, on the equipment actually in use.

Once measured, the calibration becomes the basis for trusting every rate recorded afterward, until the next check. It's the difference between "we set it to deliver 22 gallons an acre" and "we confirmed it delivers 22 gallons an acre" — the second is what a rate field on an application record is implicitly claiming, and only a calibration record can back that claim up.

An uncalibrated machine makes every downstream record uncertain

The consequences of a rate that's quietly wrong don't stay contained to the rate field. An actual rate lower than recorded can mean a pest wasn't controlled at the level the record implies, undermining a resistance-management decision made on the assumption the label rate was hit. An actual rate higher than recorded can mean a residue level, or a drift volume, greater than the record — and everyone who reads that record later — believes. The rate field is upstream of almost every other judgment a spray record supports, which is why an error there is quiet and consequential rather than loud and obvious.

This is also why calibration deserves its own record, separate from the application log it supports. A calibration test performed once and never written down is a fact that exists for exactly as long as someone remembers it happened.

What the calibration record needs to contain

The date of the test and which sprayer and nozzle set it applies to.
The method used — a catch test, a timed-distance test, or whatever standard method your equipment and extension service recommend.
The measured output rate, not the nominal setting.
Who performed it, and any adjustment made afterward — a nozzle replaced, a pressure changed — as a result.

Kept alongside the application records the calibration supports, this becomes the evidence that connects a written rate to a measured, verified one, rather than an assumption that the sprayer did what its dial said.

Calibration and the tank matter together in a mixed pass

A calibration error compounds in exactly the situations where precision matters most. In a tank mix, an uncalibrated sprayer delivers the wrong rate of every product in the tank at once, not just one — the error isn't isolated to whichever product happens to be most sensitive to over- or under-application. And on a crop taking many passes across a season, such as tree fruit or a vineyard, a calibration drift that goes unnoticed after one pass carries forward into every pass that follows until the next check, quietly multiplying a single error across a whole season's worth of recorded rates.

This is why calibration is worth checking on a schedule rather than only when something seems obviously wrong. A sprayer rarely fails all at once in a way that's visible from the seat. It drifts, a little at a time, in ways that only a measurement — not an impression — will catch.

Where this fits, and where it doesn't

Calibration is equipment maintenance, not an application event, andFarm40 does not track equipment or maintenance schedules as their own module — there is no equipment registry to log a calibration test against. What Farm40 does hold is the rate field on the application record itself, as a first-class value alongside the active ingredient, lot number, and both intervals; its limit is that it takes that rate at face value, exactly as entered, with no way to know whether the sprayer that produced it was recently calibrated or not. The application record only reflects what you tell it. Whether the number is true is a question that gets answered at the sprayer, on a test bench, before the season's first pass — not inside any software.

Frequently asked questions

Why does calibration matter if I already write down the rate I sprayed?: Because the rate you write down is only true if the sprayer actually delivered it, and a sprayer's actual output drifts over time — worn nozzles, changed pressure, a different ground speed than the last calibration assumed. Recording a rate is a claim; calibration is the check that makes the claim something you can stand behind rather than something you're assuming.
How often should a sprayer be calibrated?: Often enough that the rate you write down stays true — many operations calibrate at the start of a season, after any nozzle change or repair, and periodically through a heavy-use season, but the right interval for a specific machine and its wear pattern is a question for the equipment manufacturer, an extension service, or your own operational experience, not a fixed number this page can supply.
What should a calibration record contain?: The date of the calibration, which sprayer and which nozzle set was tested, the method used (a catch test, a timed distance test, or another standard method), the resulting output rate, and who performed it. Keep it alongside the spray records for the applications that relied on that calibration, since it's the evidence behind every rate those records claim.
Should recordkeeping software track sprayer equipment or calibration schedules?: That depends on the software, but it's worth knowing what it can and can't do before relying on it. A rate field on an application record stores whatever number you type in — it has no way to verify that a sprayer was recently calibrated or that the rate it delivered matches what's written down. Calibration itself — testing the machine, computing its actual output, and deciding when the next check is due — happens on the equipment, and the record of it belongs wherever your operation keeps maintenance history, software or otherwise.