Check a proposed application against the current label, the bulletin for that field and the farm's own records, then draft the record — the certified applicator decides whether to spray.
Take the proposed application from the prescription or work order — product, crop, field, rate, timing and equipment.
02
Retrieve the registered label, any supplemental or state labelling, and the bulletin for that field and month.
Reason
03
Check the proposal against the label — crop and site, growth stage, rate, timing, tank mix and adjuvant.
04
Check re-entry and pre-harvest intervals against the planned field work, the harvest date and the crop that follows.
05
Check certification, restricted-use status, buffers, bulletin limits and the forecast against the label and the permit.
Decide
06
Separate what the label prohibits outright from what it leaves to the applicator's judgement, and say which is which.
07
Route what the label does not settle — thin tank-mix data, an ambiguous stage call — to the agronomist or applicator.
Out
08
Draft the application record with the label version, the bulletin, the conditions and the clause behind every flag.
09
Re-check what can change after the plan is set — weather, harvest date, bulletin — and flag it before spraying.
→Product statement
The agent checks and records. The decision to apply, the rate and the legal responsibility stay with the certified applicator.
Example workflow
One spray plan, end to end
AgentHuman
1Application proposedPrescription, work order or spray plan — product, crop, field, rate, timing and equipment
2Label and bulletin retrievedThe registered label, supplemental and state labelling, and the bulletin for that field and month
3Restrictions checkedCrop and site, growth stage, rate, timing, tank mix, adjuvant, re-entry, pre-harvest and the following crop
4Conditions and permissions checkedCertification, restricted-use status, buffers, sensitive neighbours and the forecast against the label
No human action required
Stages 1 to 4 run without a person in the loop — retrieval and checking finish before the applicator is asked to read anything. A restriction the label states outright is raised the moment it is found.
5DecisionSplits on what the label prohibits and what it leaves to judgement
Nothing the label prohibits
Reaches the applicator with the check attached.
Prohibition or missing source
Goes to a person before the tank is filled.
Certified applicator
Reads the restriction found, the label clause it came from and the bulletin, then decides whether the application goes ahead.
Apply · Change the plan · Ask the agronomist
Decided — handed back▼
6Record draftedWritten to the farm record only where write access and policy allow; nothing is filed without a person
7Outcome evaluatedRestriction recall, bulletin currency, interval conflicts, record completeness and false blocks by crop
Corrections
A flag the applicator rejects is recorded with the reason and counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Authorising an application to go ahead.
Setting, raising or adjusting an application rate.
Clearing a crop or site the label omits.
Deciding a restricted-use product may be applied.
Automation boundaryAgent acts unaided
✓Retrieve the label, the supplemental labelling and the bulletin for that field and month.
✓Check the proposed application against every restriction those documents carry.
✓Check re-entry and pre-harvest intervals against planned field work and the harvest date.
✓Draft the application record and flag a changed condition before the sprayer runs.
Write actions run only inside the approval boundaries agreed in implementation. The record is drafted; a person files it.
Waiving a re-entry or pre-harvest interval.
Shortening a buffer or a bulletin restriction.
Approving a tank mix the label does not cover.
Changing label sources, block rules or thresholds.
Example output
One proposed application, annotated
Everything the agent returns is attached to the plan and to the clause it came from.
Check output · single proposed applicationIllustrative example
Proposed
Crop and stage
Field, date
Check result
Confidence
Decision
Post-emergence herbicide, one block
Soybean, beginning flowering
Field 7, tomorrow 06:00
Growth-stage restriction
96%
The applicator's, not the agent's
As receivedThe application as the work order states it, with the field and the intended date.
Evidence usedLabel clause and versionBulletin for this fieldGrowth-stage record
Why it stopped hereThe label carries this crop but bars application after flowering begins, and the crop is past it.
ActionApplyChange the planAsk the agronomist
What the score decidesConfidence decides how hard the applicator re-reads the clause, not what is lawful.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every proposed applicationFrom the prescription, work order or spray plan
03Label & bulletin
Apply the label that governs it
Use the registered label, the supplemental and state labelling, the bulletin for that field and month, and the farm's own field record.
01Approved path
Do the reading before the tank is filled
Label, bulletin, intervals, certification and conditions are checked while the work order is written, not after the sprayer has run.
02Human review
Put the hard cases in front of a person
A thin tank mix, an ambiguous stage call or a bulletin that changed reaches the applicator while the plan can still be changed.
04Build an evidence trail
Retain the label version read, the bulletin obtained, the conditions at the time, the clause behind each flag and what the applicator decided — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Farm records & prescriptionsOperations Center · FieldView Trimble Ag · prescriptions
Label & bulletin sourcesRegistered labels · supplemental labelling Bulletins Live! Two · state restrictions
Weather & conditionsForecast · in-field stations Wind and inversion data
Agent
Chemical-application checking
Retrieves the label Checks the plan Drafts the record
Machines & productSpray controllers · as-applied data Product inventory · certification records
Label complexity is not spread evenly across crops
A missed-restriction rate that reads acceptably across the whole spray programme can sit almost entirely in the crops and mixes whose labels carry the most conditions. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Minor and specialty crops
4.7%
3.6×
Review
Tank mixes, three or more
3.4%
2.6×
Review
Fields inside a bulletin area
2.5%
1.9×
Watch
Broadacre single-product applications
0.8%
0.6×
Normal
Bar: missed-restriction rate lift vs. broadacre baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A miss is closed out in the field before it is closed out in the agent
An application cannot be taken back. Once the sprayer has run, the work is containment, notification and the record — the loop decides the next field.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Missed restrictions, interval conflicts and false blocks break out by crop and by product.
02Diagnose
Which was it — the label version, the bulletin pulled, the clause parsed or the field record?
03Improve
The source, parser or block rule changes only on agronomy sign-off, tied to a version and a date.
04Verify
The check is proved on held-out applications from that cohort, the missed ones included.
05Learn
The application is replayed on every release, and the clause it broke joins the check set.
Learn → DetectThe return edge. A label or bulletin change is a source change — it lands in the check set before the next spray window, not after it.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, checking logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workflow discovery and automation-boundary definition.
02Label, supplemental and bulletin sources.
03Crop, product and prescription data mapping.
04Field geometry and bulletin retrieval.
05Label-restriction parsing and check logic.
06Re-entry and pre-harvest interval checks.
07Certification and restricted-use status checks.
08Weather, drift and buffer condition checks.
09Restriction-recall and false-block tests.
10Application-record drafting for the state.
11Farm-system and sprayer integration.
12Observability, deployment and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne crop and product setProductionProduction farm-system integrationAdvancedMulti-state / contractor fleets
Introduced at Pilot
Label-restriction checking✓✓✓
Bulletin retrieval for the field and date✓✓✓
Re-entry and pre-harvest interval checks✓✓✓
Application decision left with the applicator✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Certification and restricted-use checks—✓✓
Weather, drift and buffer checks—✓✓
Application-record drafting—✓✓
Observability and evaluation—✓✓
Introduced at Advanced
Multi-state and state-specific labelling——✓
Contractor fleets and enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on label and bulletin sources, farm-system integrations, crop and product range, record requirements, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your crop, product and prescription list→Crop, product and prescription data mappingWeek 1
02The label sources you already work from→Label, supplemental and bulletin source assessmentWeek 1
03Field boundaries and the geometry you trust→Field geometry and bulletin retrieval by dateWeek 2
04Your applicators, their categories and certification records→Certification and restricted-use status checksWeek 3
05Applications that went wrong, including the near misses→Evaluation suite, regression cases and failure-mode testingWeek 4
06What your state and your auditors require in the record→Application-record drafting to that requirementWeek 5
07Named certified applicators and an agronomist to review→Review workflow, then supervised checks and validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the recall evaluation and the first supervised checks.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Workflow discovery, label sources and the automation boundaryW2Field geometry, bulletin retrieval and the first product setW3Restriction parsing, interval checks and certification checksW4Restriction-recall evaluation, false-block and drift-condition testingW5Farm-system integration, record drafting and supervised checksW6Applicators work from live checks, then Agent Care starts
Reading the bandRestriction recall is tested in week 4, before a check reaches an applicator in week 5. Nothing informs a spray decision until it has.
At the end of W6Checks have run alongside your existing process and been read by the applicators who spray from them, then Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Agriculture AI agent
Build a checking agent around your spray programme.
Show us a season of applications, the label sources you work from and how a spray plan reaches an applicator today. We'll run those plans back through the check and show you which ones the label, the bulletin or an interval would have stopped.
