A custom applicator drives onto your ground, sprays a field you did not walk with your own hands on the boom, and drives off again. The spray happened. The obligation that follows it — a re-entry window on your field, a harvest window on your crop, a line in your records that has to survive an audit years from now — did not happen to the applicator. It happened to you.
This is the part that catches operations off guard: hiring the work out does not hire out the recordkeeping. The applicator may keep excellent records of their own, tied to their license and their own regulatory obligations, and those records can be genuinely comprehensive — and still not be the record your farm needs, sitting in your files, attached to your field, available to your certifier without a phone call to someone else's office. Getting that record is less a recordkeeping problem than a contract problem, and this page is about treating it as one.
The label is the authority. Nothing here states a re-entry interval or pre-harvest interval for any product, and you should be wary of anything that does. Those intervals are set by the product label and by the regulator and certifier who govern your operation, and they apply to your field regardless of whose hands were on the sprayer. What follows describes the process of obtaining and keeping a custom applicator's record. For the intervals themselves, the label the applicator used is the source, not this page.
The obligation follows the field, not the boom
Regulators, certifiers, and buyers generally do not care who owned the sprayer. They care what happened on the ground that is on your farm, under your name, growing the crop you are about to sell. An audit that asks "what was applied to this block, and when is it clear" does not accept "a contractor did that part" as an answer — it wants the record, and the record's location is supposed to be with the operation whose field it describes.
This is exactly the same standard described for any application in what belongs in a spray record. A custom-applied pass does not get a lighter version of that list because someone else did the work. It gets the same list, obtained through one extra step: asking for it.
Treat the handoff as a contract term, not an afterthought
The moment to solve this problem is before the applicator arrives, not after they leave. Make the record a stated condition of the job — in the same conversation as the price and the timing, not a favor asked for afterward. Specify what you need in writing: the product and active ingredient, the rate applied, the lot number, the exact date and start and end time, the field or block identifier you use (which may not match theirs — reconcile that up front), the weather at application, and both intervals from the label with the resulting end dates.
Applicators who do this work regularly already generate most of this as part of their own compliance, so the ask is rarely a burden — it is usually a copy of a document they were going to produce anyway. The failure mode is not that the record doesn't exist. It's that it exists in a filing cabinet or a database that belongs to someone else, and nobody made getting a copy of it a condition of the job.
A verbal handoff is a bridge, not a record
What you can usually get on the day of the spray is a verbal summary — the applicator telling you what went down and roughly when things clear. That is genuinely useful: it tells a crew whether to stay out of a block tomorrow. It is not a record, because it has no lot number, no exact rate, nothing an auditor can check against the product's registration, and no permanence past whoever remembers the conversation.
Use the verbal summary to make today's decisions safely, and treat it as a placeholder for the written record that has to follow within days, not weeks. The gap between the two is where these obligations tend to be lost — the verbal version feels sufficient in the moment, and the written one never gets chased down because the moment has passed.
What to do when the paperwork doesn't show up
Sometimes it doesn't arrive — the applicator is busy, the invoice shows up without the detail attached, and weeks later nobody can say exactly what the rate was. The field does not care that the paperwork is missing. It carries whatever constraint the actual application created, whether or not a document describing it exists yet.
The safe default is to treat the block as inside the most conservative reasonable window — closed to entry, closed to harvest — until the applicator's record confirms otherwise, and to follow up before, not after, anyone is scheduled to go near the field. This is the same logic that governs a drift complaint investigation: the absence of a record is not evidence that nothing needs recording. It's evidence that the record hasn't been obtained yet.
Building the applicator's record into your own
Once the record arrives, it becomes part of your field's history in exactly the same way a pass you sprayed yourself would — it belongs in the same log, next to the applications you made in-house, so that anyone reviewing the block's history sees one continuous record rather than a gap where the custom work happened. This is the same principle behind spray and input records generally: the record belongs to the field, and it should not matter to a reader a year later whose hands did the spraying.
Farm40 lets you enter an application record for a pass you did not personally make — the active ingredient, rate, lot number, and intervals are the same fields whether you sprayed it or a contractor did — so a custom-applied pass sits in the same field history as every other application. Its limit is the obvious one: it can only record what you type in from the applicator's paperwork, and it has no way to reach into the contractor's own files and pull the record for you. Getting the paperwork in the first place is still yours to do.
The rule that makes this manageable is simple: ask for the record before the truck leaves, in writing, with the specific fields you need named up front — and treat "I'll send it over" as an invitation to follow up, not a completed step.