Implementation

Implementation should begin as a bounded programme of testing and learning, not as a complete technical or regulatory rollout. The aim is to establish whether better visibility of labour relationships can improve worker protection, accountability and assurance without creating unnecessary data collection or administrative burden.

The appropriate path is staged: establish shared expectations, test a small number of practical use cases, evaluate the results and expand only when the approach demonstrates value.

What implementation means at this stage

This project is ready for an implementation pathway, but not for a final deployment blueprint. Early implementation should define:

• the problem a pilot is intended to solve;
• the participants and relationships within scope;
• the minimum claims and evidence required;
• the safeguards governing access, correction and worker voice;
• the measures used to evaluate value and harm; and
• the conditions for expanding, changing or stopping the work.

It should remain technology-neutral and should build on existing payroll, onboarding, contractor-management, time-and-attendance and assurance processes wherever possible.

A staged pathway

1. Establish a founding coalition

Bring together industry bodies, grower representatives, employers, labour providers, workers' representatives, assurance providers, infrastructure providers and policy observers. Define the decision rights, responsibilities and boundaries of the group.

Outputs: a pilot charter, participant roles, decision process, scope and initial risk register.

Decision gate: proceed only when participants agree on the purpose of the pilot, the use of information and the protections available to workers and participating organisations.

2. Refine the Code

Translate the ten rules into implementable claims, evidence expectations, definitions, roles and a versioned change process. The Code should state what must be capable of being demonstrated without prescribing a single platform or data model.

Outputs: a minimum evidence profile, glossary, conformance questions, data-sharing principles and change-control process.

Decision gate: proceed only when the requirements are specific enough to test and proportionate enough for smaller participants to engage.

3. Pilot workforce traceability

Use a limited number of real supply-chain participants to test how worker–employer, provider and worksite relationships can be verified across existing systems. Select a bounded use case, such as onboarding, a seasonal labour event, a subcontracting relationship or an incident investigation.

Do not create a public database of workers. Test the exchange of relevant claims and evidence between authorised participants, following the principles in Federated Trust and Share Claims, Not Copies.

Outputs: a relationship map, working evidence flows, identified gaps, access records and documented user experience for participating organisations and workers.

Decision gate: continue only when the pilot produces useful evidence without unjustified access, unsafe exposure or disproportionate effort.

4. Test proportional assurance

Design assurance that uses transparent records to focus effort where risk is higher, while recognising operators that can demonstrate sound systems. Test the complete pathway from claim, to attestation, verification, assertion and decision described in From Compliance Activity to Assurance Infrastructure.

Outputs: an assurance workflow, risk signals, escalation rules, investigation protocol and examples of proportionate responses.

Decision gate: expand only when the approach improves the quality or speed of assurance while preserving human judgement, due process and worker-centred safeguards.

5. Develop the ecosystem

Create clear conformance expectations for auditors, technology providers, worker-reporting channels and investigation providers. Define what each participant contributes and what practical value they receive. Participation Needs Incentives examines why participation must create value rather than become another reporting burden.

Outputs: participation guidance, provider expectations, worker-support pathways, training materials and a public pilot report.

Decision gate: move towards wider adoption only when participation is useful, voluntary or properly authorised, and the governance arrangements can operate independently of any single participant or vendor.

How a pilot should be evaluated

The pilot should measure both value and risk. Useful measures could include:

• the proportion of in-scope labour relationships that can be attributed and verified;
• the time required to resolve a relationship or responsibility question;
• reductions in duplicate evidence requests and manual reconciliation;
• the accuracy and usefulness of assurance and investigation decisions;
• whether workers can understand, challenge and correct relevant records; and
• privacy, safety, exclusion and administrative-burden issues experienced by participants.

The evaluation should report limitations and unintended effects, not only successful demonstrations. A pilot that shows the model is unsafe, too burdensome or not useful has still produced an important implementation result.

Design principles

Principle	In practice
Worker-centred	Do not expose personal records publicly; enable trustworthy evidence and channels for worker voice.
Technology-neutral	Specify outcomes and interoperable information, rather than one mandated platform.
Proportionate	Match assurance effort to demonstrated risk and capability.
Practical	Build from existing business processes wherever possible.
Governable	Maintain clear ownership, versioning, auditability and escalation pathways.

Guardrails for implementation

Implementation must preserve the boundaries established by the project:

• personal records are not made public;
• information is exchanged for defined, legitimate purposes;
• access is limited to what the purpose requires;
• workers have safe voice, correction and remedy pathways;
• records do not determine outcomes without appropriate human review; and
• participation does not become a proxy for legal compliance or a substitute for employment rights.

These safeguards should be tested as part of the pilot, rather than added after the infrastructure has been designed.

Questions to resolve through a pilot

• What minimum data and evidence are actually necessary for attributable labour participation?
• Who can access which information, for which purpose, and under what authority?
• How should records be verified, corrected and retained?
• What interoperability profile is realistic across small and large operators?
• How can worker voice and complaint channels operate safely alongside formal records?
• Which benefits are strong enough to justify participation for each role?
• What evidence should be required before the model expands to another crop, region or supply-chain context?

Related reading

• Transparency Must Work for Workers — safeguards and participation requirements for a worker-centred pilot.
• Share Claims, Not Copies — a privacy-resilient pattern for exchanging evidence.
• Containment Is the Practical Value of Visibility — the incident-response value a pilot should be able to demonstrate.
• Workforce Traceability Is Governance Infrastructure — the maturity pathway from fragmented records to an embedded standard.