For most of the past decade, traceability in agricultural supply chains has meant provenance: which farmer, which plot, which polygon. The industry has invested heavily in answering that question, and rightly so. Without reliable data on where commodities come from, nothing downstream holds up.
But provenance is becoming the entry ticket, not the finish line. The question buyers, auditors and regulators are starting to ask is different: show us what you did.
Due diligence is a claim about actions
A polygon proves where a commodity came from. It says nothing about what happened when that polygon flagged a deforestation risk, or when a household survey surfaced a child labour case. Who reviewed it? When? What was the remediation step, and who signed off on closing it?
Due diligence, in the regulatory sense, is not a data point. It is a process claim. And process claims can only be verified one way: through a record of actions, each one attributable to a person, a time and a decision.
This is where much of the sector’s current tooling falls short. Plot and farmer data is captured carefully; the actions taken on that data often live in email threads, spreadsheets and institutional memory. When an auditor asks how a case was handled eighteen months ago, the answer is reconstructed rather than retrieved.
The regulatory direction is unambiguous
The EU Deforestation Regulation makes the shift explicit. The due diligence statement is the visible artefact, but the obligation behind it is a system: due diligence must be exercised, documented and retrievable, and competent authorities can ask to see the records that prove it was. A statement without an inspectable trail behind it is an assertion, not compliance.
The same logic runs through human rights due diligence frameworks. Child labour monitoring and remediation systems (CLMRS) are judged not on whether risks were identified but on whether identified cases were followed through. A monitoring system without a verifiable follow-up trail is, from an assurance perspective, incomplete.
In both cases, the unit of proof is the action, not the record.
What an action-level audit trail looks like
In practice, three capabilities matter, and the latest release of Orbit, our platform for first-mile field operations, delivers on each of them.
Every data-changing case action is logged and reviewable. When a case moves through a workflow, from identification to remediation to closure, every action that alters its data should be visible after the fact. Orbit’s new Case Management Audit View does exactly this, recording the case, the task, the rule evaluated, the action executed, who performed it and when. It turns a compliance narrative into an inspectable sequence, so “walk us through this case” is answered by opening the record, not reconstructing it.
Imports, bulk updates and exports are recorded, not invisible. Supply chain data is managed at scale through imports, bulk updates and exports: one operation can touch thousands of rows, and these are exactly the moments where audit trails traditionally go dark. Orbit’s Web Activity Log now records these operations alongside individual actions, restoring the chain: this operation, by this user, on this date, affecting these records.
Consent is captured, signed and exportable. Farmer data underpins the entire system, and the legitimacy of that data rests on consent that can be evidenced, not assumed. In Orbit, consent is captured digitally and signed by the farmer at registration, and the signed record can be exported on request. That is the difference between asserting compliance and demonstrating it.
Together these reflect a deliberate product direction: treat the audit trail as a first-class output of the system, not a byproduct. Whether the action is a single case decision or an import touching thousands of records, it becomes part of the record the moment it happens.
The first mile complicates everything, and that’s the point
There is a reason action-level traceability is hard in agricultural supply chains specifically. The actions happen in the field. A household survey is conducted on a farm visit. A remediation step is agreed in a village, often without connectivity. Consent is given in person.
If the audit trail can only be created back at the office, it will always be a reconstruction, with everything that implies for accuracy and credibility. The record has to be generated at the point of work, offline if necessary, and synchronised intact. This is why Orbit’s mobile tools are built offline-first, and why the same release brings deforestation risk mapping fully offline: a field agent standing on a remote plot can now see the risk picture around the farm, and act on it, with no connectivity at all. First-mile tooling is not an operational nicety here; it is what determines whether the evidence exists at all.
Provenance was chapter one
None of this diminishes the work the industry has done on knowing where commodities come from. Polygons, farmer registries and plot mapping remain the foundation. But the next audit, whether it comes from a competent authority, a certification body or a customer’s own assurance team, will ask a harder question: not where did this come from, but what did you do, and can you prove it?
The organisations that can answer from a system of record, rather than a folder of reconstructions, will find that conversation considerably shorter.
Farmforce provides digital solutions for managing the first mile of agricultural supply chains, from farmer registration and GPS plot mapping to harvest purchasing, deforestation monitoring, and EUDR compliance. To see how Farmforce can support your traceability and sourcing operations, request a demo.
