Traceability & Provenance
Traceability: How It Works
The end-to-end sequence, stage by stage, with nothing skipped.
The module is modelled as an explicit state machine with 8 stages. Every record knows which stage it is at, what has to happen to move on, and what is blocking it if it cannot. Traceability is a legal requirement and a commercial asset. This module maintains lot-level records forward and backward through every process step, supports a timed recall exercise that actually works, and turns the same underlying data into consumer-facing provenance that is substantiated rather than asserted.
End to end
How Traceability runs, start to finish
The module is modelled as a state machine, so at any point the business knows exactly which stage every record is at and what has to happen next.
-
1
Define lots at every process step
This is where the record starts, and getting it right here removes work at every later stage.
-
2
Record inputs and outputs against each lot
The platform prompts only for what this stage genuinely needs, and carries everything forward.
-
3
Code and label with the lot identity
Conflicts with scheme rules, regulatory windows and existing commitments are flagged here rather than discovered later.
-
4
Link suppliers and customers one step each way
Capture works offline, so this stage is completed in the field rather than remembered afterwards.
-
5
Carry attributes through processing
Everything recorded at this point becomes evidence automatically, in every format that will later ask for it.
-
6
Publish provenance to the consumer
This is the stage most businesses currently do twice, once for the operation and once for the paperwork.
-
7
Run mock recalls on a schedule
Results feed the whole-farm view, so the effect of this stage is visible against the rest of the business.
-
8
Execute a real recall if required
The cycle closes here, and what is learned is carried into next season's plan rather than lost.
Sequence
The order things happen in
-
Stage 1
Define lots at every process step
This is where the record starts, and getting it right here removes work at every later stage.
-
Stage 2
Record inputs and outputs against each lot
The platform prompts only for what this stage genuinely needs, and carries everything forward.
-
Stage 3
Code and label with the lot identity
Conflicts with scheme rules, regulatory windows and existing commitments are flagged here rather than discovered later.
-
Stage 4
Link suppliers and customers one step each way
Capture works offline, so this stage is completed in the field rather than remembered afterwards.
-
Stage 5
Carry attributes through processing
Everything recorded at this point becomes evidence automatically, in every format that will later ask for it.
-
Stage 6
Publish provenance to the consumer
This is the stage most businesses currently do twice, once for the operation and once for the paperwork.
Before you start
What you will need, and what the module handles for you
Most of this comes across automatically once your holding is registered. The list is here so nothing arrives as a surprise.
In practice
Six things Traceability changes on day one
None of these requires a new process. They all come from recording the work you already do, once, in a form the rest of the platform can use.
Lot creation and splitting through
Lot creation and splitting through every process step.
One-step-back and one-step-forward supplier and
One-step-back and one-step-forward supplier and customer linkage.
Field-to-pack traceability using the platform
Field-to-pack traceability using the platform production record.
Batch and lot coding with
Batch and lot coding with label generation.
Mock recall exercise with timing
Mock recall exercise with timing and completeness measurement.
Real recall execution with affected
Real recall execution with affected lot identification and notification.
Traceability
The chain behind one batch
Assurance audits ask you to prove a chain you have already lived. The record is assembled as the work happens, so the audit pack is a printout rather than a fortnight of searching.
BATCH-759F43
-
Grown
- Who
- Field parcel
- Evidence
- Cropping record, inputs applied with dates and rates
- Held in
- Field record
-
Treated
- Who
- Spray operator
- Evidence
- Spray record with product authorisation and buffer compliance
- Held in
- Spray diary
-
Harvested
- Who
- Combine or contractor
- Evidence
- Weighbridge ticket, moisture and specific weight
- Held in
- Weighbridge
-
Stored
- Who
- Farm or central store
- Evidence
- Store temperature and drying record, bin allocation
- Held in
- Store record
-
Hauled
- Who
- Haulier
- Evidence
- Consignment note and cleanliness declaration
- Held in
- Haulage
-
Delivered
- Who
- Processor
- Evidence
- Intake spec, rejection reasons if any, and settlement
- Held in
- Processor
Take the record with you
Questions answered
What people ask about Traceability
Does this replace the software I already use?
Not necessarily. Agrivencia integrates with authoritative sources and mainstream packages rather than insisting on replacing them. Where an incumbent does one job well, the platform connects to it; where the job spans several systems and nobody does it, the platform does it.
Will it work where I have no signal?
Yes. Field capture in Traceability is offline first, storing locally and synchronising when a connection returns. Only around a fifth of UK farms report reliable signal across the whole holding, so this is a design assumption rather than a feature.
What happens when the scheme rules change?
Scheme rules are held as data rather than code, so a rate change, a cap change or a window closure is a content update that takes effect the same day. The platform also alerts you to what the change does to your own position.
Who owns the data I put in?
You do. The Farm Data Charter gives you a complete export in open formats at any time, and every instance of data sharing requires an explicit, revocable consent that is visible in your account.
Does it work if I farm across a border?
Yes, and that is one of the main reasons the platform exists. A business with land in more than one nation sees one reconciled view rather than two portals, with obligations and deadlines from both administrations in a single calendar.
Can my agronomist or land agent use it too?
Yes. You grant scoped, time-limited access per holding and per module, and you can revoke it in one click. Advisers never get a shared password or a blanket view.
What is the biggest limitation of this module?
Broken linkage at a process step. Mitigated by mandatory lot capture. We would rather state that plainly than let you discover it after signing.
What we are hearing
The problems people describe to us
These are composite statements drawn from user research conversations, not attributed customer quotes. We publish named references only with written consent.
I am not short of software. I am short of one place where the same field means the same thing in all of it.
The scheme closed on a Tuesday evening. I had the application half built. Nobody told me the budget was nearly gone.
We farm on both sides of the border. Everything takes twice as long and I still cannot see the whole position on one screen.
Audit week costs me three days. Every single record they ask for is already written down somewhere on this farm.
See Traceability running on your own holding
Thirty minutes, using your parcels, your schemes and your enterprises rather than a sample farm. No obligation and no sales script — if it does not fit your business we will say so.
- Free tier available
- No card required
- Your data stays yours