Agriculture & Primary Industry /Document processing live field guide · 9 min

Spray-Diary Formatter

Turns informal field spray notes into a structured, APVMA-compliant chemical-application log — date, block, product, batch, rate, wind, operator, withholding period — quoting the source note and flagging any gap rather than inferring it.

Open the live demo

theater/demos/agri_spray-diary-formatter.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads the crew's rough spray note, extracts each application into the chemical-use record fields, checks the rate and wind against the product label, and lays it all out for the farm manager to approve before it lands in the spray diary.

Input 01

The field note, as written

A handwritten day sheet, a photo of a docket, or a dictated voice note — date, paddock, crop, product, rate, wind, operator — plus the product label restraints to check against.

Agent 02

Extracts, maps, checks

Pulls each application event into the chemical-use record fields, maps the product to its label, applies the withholding period, and checks the rate and the recorded wind speed against the label's restraints.

Output 03

A draft record, working shown

A formatted chemical-use record with the rate, withholding period and wind check laid out, and every missing or out-of-range field flagged, for the farm manager or agronomist to resolve and approve before it is added to the spray diary.

Where it works well

It catches the gap in the record at the moment it is created, not at audit time.

Done by hand it is minutes per record across a busy spraying window, and the wind and rate cross-check is the first thing skipped when the dockets pile up.
Best for an operation that sprays often and keeps its own diary — broadacre, horticulture, viticulture — where the record-keeper is not always the person who held the boom.
At dozens of applications a week in season, the recaptured time goes back into agronomy and drift planning, not transcription.

The slow, invisible cost is the re-keying — someone sits down days later with a stack of mud-stained dockets and types each one into a compliant log, by which point the operator who could explain a blank field has moved on to the next paddock.

Where it works badly

It is confidently wrong when the note is wrong — it formats a clean record around a bad number.

It reads what the note says; it cannot know the note is wrong. A misread "11" for "17" km/h passes a wind check it should have failed.
Weak on crew shorthand it has not seen — an unfamiliar paddock nickname, an abbreviated product, a brand it cannot resolve to a label. It should flag, not guess.
The wind and rate check is only as good as the label data behind it; point it at the wrong label and it clears an application it should have stopped.

The honest test

If you cannot say, looking at a finished record, which words on the original note each field came from — this tool has made your transcription faster, not your diary more correct.

A crew member writes "2.0" when they meant "0.2", or photographs a docket with the wind reading smudged, and the tool produces a tidy, professional record that reads as trustworthy precisely because it is well formatted. That is the trap.

What it doesn't do — and shouldn't

It drafts the record. A person approves it. That boundary is deliberate.

WHAT IT DOES

Quotes the words on the note each field was read from

Shows the rate against the label and the recorded wind against the label's restraint

Flags every field that is missing, ambiguous, or out of range

WHAT IT WON’T

Add anything to the spray diary on its own

Certify the application as compliant or label-legal

Decide whether a flagged drift risk was acceptable on the day

A chemical-use record is a legal document. Under each state and territory's control-of-use law a producer must make the record promptly and keep it for the required period, and the withholding period it captures is what keeps produce inside the maximum residue limits set by the APVMA and Food Standards Australia New Zealand. A wrong record can mean a residue breach, a rejected consignment, or lost export-market access — the consequence lands on the grower, so the grower stays on the decision.

What your data has to look like

Legible source notes, and a current product label to check the rate and restraints against.

Typical readiness

across orgs we see, before the first job

The field note in a form the tool can read

Needs shaping

Product label data — rate, withholding period, wind restraint

Usual weak point

A consistent paddock / block register

Usual weak point

The product trade name and APVMA approval number

Needs shaping

Operator and equipment details

Needs shaping

The real first job

The product label data is usually the weak point — held as last season's PDFs, or in someone's head. Getting the labels, withholding periods and wind restraints into a current, machine-readable form is usually the real first job — larger and more valuable than the extraction layer on top. Once the labels are right, every record checked after that is faster and right by default.

Right fit if…

You spray often and keep your own diary across a busy season

Notes are taken in the field by a crew, then written up by someone else later

You can point to the current label for each product you apply

Compliance records are a condition of export, certification, or a retailer standard you sell into

Walk away if…

You spray a handful of times a year and write it up the same day yourself

Your only product label data is whatever someone remembers

Field notes are illegible or never reach the office in a readable form

You want a tool that signs off the application as compliant for you

Open questions

The worried-buyer questions, answered straight

It can only check the recorded wind against the label restraint, and it reads whatever the note says — so if the note is wrong, the check is wrong, which is exactly why nothing is filed on its say-so. It shows the recorded wind beside the label’s restraint and flags it when it is out of range, but a person decides whether the application was acceptable and stands behind the record. The tool surfaces the breach; it does not absolve it.

It works from what it can actually read. A clear photo or a typed sheet extracts well; a faded docket or an unfamiliar paddock nickname it will flag rather than guess at. It quotes the words each field came from so you can check its reading against the original. Getting notes captured legibly in the field — and product labels into machine-readable form — is usually the first piece of work, and the piece that pays off across every record after.

No. It removes the re-keying and the line-by-line cross-check against the label, so the agronomist or farm manager spends their time on the judgement — whether a flagged drift risk was acceptable, whether the right product went on the right block, whether the withholding period clears the harvest date. The record stays theirs. The time it frees goes back into agronomy, not transcription.

Current to the label registered for the product you actually applied. Withholding periods and wind restraints are set on the APVMA-approved label and they change when a product is re-registered, so a record checked against an old label can clear a rate or a restraint that no longer holds. The honest test: do you know, today, that the label data behind the check is the one in force for that product?

Chemical-use records are your legal records — you must keep them for the period required under your state or territory’s control-of-use law, and they can be called on in a residue investigation or an export audit. Any deployment runs against your own systems and data handling, not a shared pool; we scope where the records sit and who can see them as part of the build. The demo here runs entirely on fabricated data — the paddocks, operators and dockets are invented.

It formats the record to the fields the law requires and flags what is missing or out of range, but it does not certify compliance. The record-making timeframe, the retention period, and the judgement on a flagged drift risk are obligations under your state or territory’s control-of-use law that a person confirms. The tool gets the record most of the way; the accountable person closes the gap.

What it takes to build

3–4 weeks · 4 phases

Reused from template~70%

Bespoke to this skin~30%

stack · Claude · extraction pipeline · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your operation?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where the spray-record write-up hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work