Assemble the evidence a scheme's checklist calls for, walk the lot links from input to shipment and flag what is missing or expiring — the certification body decides whether the scheme is met.
Take the scheme, the checklist version the audit is booked against and the findings the last audit left open.
02
Pull the records that checklist points at — farm system, packhouse, lab, training file and the paper folder.
Reason
03
Match each record to the clause it is offered for, and check it covers the period and version the scheme asks for.
04
Walk the lot links from input and field through harvest, cooling, packing and commingling to the shipment that left.
05
Read certificate, training, calibration and test dates against the season ahead rather than against today.
Decide
06
Separate a record that is missing from one that is present but stale, unsigned or out of period.
07
Route a broken lot link, a contested finding or a clause that turns on judgement to the food-safety lead.
Out
08
Assemble the audit pack in the checklist's order, showing for each clause what supports it and what does not.
09
Keep every open finding on the list with the evidence filed against it, and re-check what expires before the audit.
→Product statement
The agent assembles, checks and flags. Compliance is the operation's responsibility, and whether a scheme is met is the certification body's decision.
Example workflow
One checklist, end to end
AgentHuman
1Scope setThe scheme, the checklist version the audit is booked against, and the sites, crops and lots in scope
2Records gatheredFarm system, packhouse records, lab results, training files, calibration certificates and the paper folder
3Clauses matchedEach record read against the clause it is offered for, the period it must cover and the version in force
4Lot links walkedInput and field through harvest, cooling, packing and commingling to every shipment that left
No human action required
Stages 1 to 4 run without a person in the loop — gathering, matching and link-walking finish before the food-safety lead is asked to read anything. A lot link that will not resolve is raised the moment it is found.
5DecisionSplits on whether a clause is evidenced and whether the lot resolves both ways
Clause evidenced, links resolve
Reaches the pack with the record attached.
Gap or broken link
Goes to a person before the pack is filed.
Food-safety or certification lead
Reads the clause, the record that was found and the link that breaks, then decides what the operation does about it.
Accept · Supply the record · Raise a corrective action
Decided — handed back▼
6Pack drafted, gaps listedWritten to the audit pack only where write access and policy allow; nothing is marked closed or met
7Outcome evaluatedGap-detection recall against the auditor's findings, trace completeness under mock recall and expiry lead time
Corrections
A gap the lead 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
Deciding that an operation meets a scheme.
Closing a non-conformance or a corrective action.
Signing or dating a record for someone else.
Calling a lot traceable when a link is missing.
Automation boundaryAgent acts unaided
✓Gather the records the checklist points at and match each one to its clause.
✓Walk the lot links from input and field through packing to the shipment that left.
✓Flag records that are missing, stale or out of period, and dates that are about to lapse.
✓Assemble the audit pack and keep each open finding beside the evidence filed against it.
Write actions run only inside the approval boundaries agreed in implementation. The pack is drafted; nothing is closed.
Releasing, holding or withdrawing product.
Deciding a recall or withdrawal is unnecessary.
Deciding an expired certificate still counts.
Changing the checklist, scheme version or thresholds.
Example output
One clause and one lot, annotated
Everything the agent returns is attached to the clause it came from and the lot it was tested against.
Gap output · single checklist clauseIllustrative example
Clause
Checklist
Lot tested
Check result
Confidence
Closure
Traceability, one step each way
Version the audit is booked against
3 June, one run
Link breaks at packing
93%
Not the agent's to make
As receivedThe clause as the checklist words it, and the lot the pack claims to cover.
Evidence usedHarvest and field recordsPacking run logShipments for that code
Why it stopped hereFour field lots went into one packing run and left under one code, unresolved to a field.
ActionAcceptSupply the recordRaise a corrective action
What the score decidesConfidence decides how hard the lead checks the link, not whether the lot is traceable.
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 clause on the checklistFrom the scheme, the audit booking and the open findings
03Scheme & records
Apply the scheme that governs it
Use the checklist in the version the audit is booked against, the operation's own records and the lot links between them.
01Approved path
Assemble it before the auditor arrives
Records are matched to clauses and lot links walked weeks before the audit, not on the morning the auditor arrives.
02Human review
Put the broken links in front of a person
A link that fails at commingling, a finding still open or a certificate about to lapse reaches the food-safety lead while there is time to act.
04Build an evidence trail
Retain the checklist version read, the records matched, the links walked, the gaps raised and what the lead 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 & field recordsOperations Center · FieldView Trimble Ag · harvest and spray records
Packhouse & traceabilityPacking and grading · lot and pallet codes Shipment records · sales invoices
A missed-gap rate that reads acceptably across a whole checklist can sit almost entirely in the lots that were commingled or reworked, and in the records that never left paper. 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
Commingled lots at packing
5.2%
3.7×
Review
Rework and repacked lots
4.4%
3.1×
Review
Paper and photographed records
2.7%
1.9×
Watch
Single-site, single-crop routine
0.7%
0.5×
Normal
Bar: missed-gap rate lift vs. single-site baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A record cannot be back-dated into existence
A gap found in August is not fixed by writing the record in August. The loop changes what gets captured at the next harvest, and who is told first.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Missed gaps, unresolved links and false flags separate out by commodity and by record type.
02Diagnose
The gap is put back on the checklist version, the record matched, the lot link or the source system.
03Improve
The mapping, link rule or source changes under food-safety sign-off, against a named scheme version.
04Verify
Old lots and closed audits are run again to see whether the findings surface this time.
05Learn
The finding turns into a check that runs at capture, and the audit runbook records why.
Learn → DetectThe return edge. A scheme version change is a checklist change — it lands before the audit window opens, not after the auditor has worked from the old one.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, records, checking logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workflow discovery and automation-boundary definition.
02Scheme, checklist and version source assessment.
03Record inventory and clause mapping.
04Lot, field and shipment data mapping.
05Link walking across commingling and rework.
06Gap detection and record-currency checks.
07Expiry tracking for certificates, training and calibration.
08Corrective-action tracking and evidence capture.
09Gap-detection evaluation against past findings.
10Mock-recall and trace-request exercises.
11Farm-system, packhouse and document 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 scheme, one siteProductionProduction system integrationAdvancedMulti-site / multi-scheme
Introduced at Pilot
Record gathering and clause matching✓✓✓
Lot links walked one step each way✓✓✓
Gap, currency and expiry flags✓✓✓
Closure left with your qualified people✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Audit-pack assembly to your checklist—✓✓
Corrective-action tracking with evidence—✓✓
Mock-recall and trace-request exercises—✓✓
Observability and evaluation—✓✓
Introduced at Advanced
Multi-scheme and multi-site checklists——✓
Grower groups and enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on schemes and checklist versions, record sources, lot and shipment systems, site count, 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
01The schemes and checklist versions you are audited against→Scheme, checklist and version source assessmentWeek 1
02Where your records actually live, including the paper→Record inventory and clause mappingWeek 1
03Lot, field and shipment data, and where product is mixed→Lot data mapping, then link walking across comminglingWeek 2
04Certificates, training files and calibration dates→Expiry tracking for certificates, training and calibrationWeek 3
05Past audit findings, including the ones you contested→Evaluation suite, regression cases and failure-mode testingWeek 4
06A withdrawal you have run, or the one you would have to→Mock-recall and trace-request exercisesWeek 5
07A named food-safety lead and the people who own findings→Review workflow, then supervised packs 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 integration work and the first mock recall run against live lots.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Workflow discovery, scheme versions and the automation boundaryW2Record inventory, clause mapping and the first lot dataW3Link walking, gap detection and expiry trackingW4Gap-detection evaluation against findings your auditor already raisedW5System integration, pack assembly and a supervised mock recallW6Your lead works from live packs, then Agent Care starts
Reading the bandGap detection is tested in week 4 against findings an auditor has already raised, before a pack is assembled in week 5.
At the end of W6Packs have been assembled alongside your existing process and read by the lead who signs 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 compliance agent around the audit you already have.
Show us the schemes you are audited against, where your records live and the findings the last audit left open. We'll take the lot that gave you the most trouble and trace it end to end, then show you which records were not there to find.
