We adapt the live EUDR platform to CSDDD due diligence, with 2–3 partners.
You shape what ships — and keep preferential terms for your entire contract duration.
Not ready?
- Embed
- Identify
- Prevent
- Remediate
- Monitor
- Communicate
The spine of the law
Six duties, in the order the directive lists them.
Articles 7 to 16 describe one loop: know your chain, act on what you find, check that it held, and say so publicly. Everything on this page hangs off one of these six.
- Duty 01Embed itDue diligence written into policy and management, with named owners.On the record: a programme with scope, roles and clusters, not a PDF.
- Duty 02Identify impactsActual and potential, in your own operations and your chain of activities.On the record: registered households and plots, screened and flagged.
- Duty 03Prevent the potentialAction plans and supplier assurances before harm occurs.On the record: prevention visits and assurances logged per supplier.
- Duty 04End the actualStop the harm, remediate, support the people affected.On the record: a case per household, with remediation steps and dates.
- Duty 05Check it workedMonitor effectiveness, at least once a year.On the record: return visits confirming each case stayed closed.
- Duty 06Say it publiclyReport annually on impacts, actions and outcomes.On the record: an export with counts, outcomes and method. Never names.
Two obligations run through all six: a grievance channel anyone in the chain can use, and engagement with the people actually affected — both below.
How the chain reaches a worker
Due diligence travels down, one tier at a time.
Each tier asks the one below it and answers for what it can see. The evidence comes back up the same chain.
An invitation is a request, not access. A supplier chooses what they share, a refusal is information you can act on, and workers never pay to be covered.
Risk prioritisation · duty 02
You cannot fix everything first, and the law knows it.
Where impacts cannot all be addressed at once, the directive lets you order them by severity and likelihood. What it will not accept is an order nobody can explain. Screening puts a flag and a count on every risk, so the order is explicit.
- GravityWorst forms jump the queueA hazardous-work or forced labour flag opens a case immediately, ahead of everything else in the cluster.
- LikelihoodSeasons are evidenceLast season’s findings weight this season’s screening, per village and per risk category.
- LeverageStart where you can moveVolume, relationship and programme presence decide where action is real rather than performative — and the record shows why you started there.
Supplier assurance · duty 03
Get an assurance you can check, not a clause you forward.
Cascading a code of conduct down the chain is where due diligence usually turns into paperwork. An assurance here is tied to the supplier’s actual records, so you can see whether the chain behind the signature agrees with it.
- SignedWhat the supplier attestsThe assurance names the risks it covers and the households and plots it claims to speak for.
- CheckedWhat the record showsRegistrations, visits and screening results sit next to the attestation. A gap between the two is visible before an auditor finds it.
- Last resortDisengagement, documentedIf it comes to leaving a supplier, the record shows what was tried first — which is exactly what the directive requires before you go.
Worked example · duties 02–05 on one household
Follow one case through two seasons.
The same household, the same case number, followed from the first visit to the visit that confirms it held. Two products: the Field App the facilitator carries, and the Dashboard your programme runs on.
14 Oct · Field App
The facilitator opens the case in the yard.
Offline, in her language, on a household that registration already created. The case gets a number before she leaves.
2 Nov · Dashboard
Someone decides, and signs the decision.
A remediation with an owner, a written reason and a return date. This is the record a due diligence review actually tests.
12 Mar · Field App
Four months later, the visit is on her list.
Nobody has to remember. Overdue cases surface in red, and the visit lands back on the same case number rather than opening a new one.
20 Mar · Dashboard
The case closes, with its whole history attached.
Awareness, identification, remediation and the return visit, each dated and named. Your statement is an export of this, not a reconstruction of it.
Both products are already carrying the plot boundaries and deliveries of these same households for EUDR. This is a second use of one deployment, on one plan.
Worked example · the loop
Every household gets a case, not a checkbox.
The four activities run in order, and the loop only closes when a facilitator goes back. A case identified this month is not finished until someone confirms, months later, that it stayed fixed.
- Step 01Awareness raisingCommunities are sensitised on the risks and definitions before any household is visited.In TracebudDelivered once per community, and recorded against every household that community covers.
- Step 02Active identificationA trained facilitator visits each household and asks about children’s activities and schooling.In TracebudRecorded in the Field App, household by household, offline, in the facilitator’s language.
- Step 03Remediation supportA case-specific response is agreed: a birth certificate, a school kit, a household asset.In TracebudLogged as a case, with the person who decided the remediation, a date and a reason.
- Step 04Follow-up monitoringThe same household is revisited months later to confirm the case stayed closed.In TracebudThe visit lands on the same case ID, so relapse is a fact on file, not an assumption.
The fourth step feeds the first. A relapse found on follow-up reopens the case rather than closing the file.
Caseload
See the caseload move.
One row per risk category, one column per season, and a count of the cases actually confirmed closed on a return visit. Not identified: closed.
Categories shown are typical of a cocoa or coffee origin. Definitions, thresholds and remediation menus are governed by the CLMRS standard your programme runs under, not by us.
Facilitators
Give one facilitator one cluster of villages.
A CLMRS runs on trained community facilitators, usually paid by the cooperative or the exporter, who already know these households. Tracebud is the system they carry the visit on, not a new layer above them.
- A cluster is a facilitator’s existing routeThe villages one person already covers on foot or by motorbike become the boundary a caseload is organised around.
- The cooperative or exporter pays themFacilitators are usually already funded through the union’s premium or the exporter’s programme budget, not a new line item.
- Caseload reads at both levelsA brand sees the programme’s trend; the facilitator sees exactly which households are due a follow-up this month.
- A household’s record follows the householdIf a family moves cooperative or sells to a different buyer, its case history is not left behind.
Grievance mechanism · article 9
A complaint is a case that starts itself.
The channel has to be open to workers, their families, unions and the communities around production — and “legitimate” means the person who raised it hears back. A grievance lands in the same caseload, with the same lifecycle as anything screening finds.
- RaisedBy anyone in the chainA worker, a family member, a union rep or a neighbour — by phone, through a facilitator, or anonymously.
- HandledLike any confirmed riskThe grievance opens a case, is assigned to the facilitator who knows the village, and gets a visit — not a reply template.
- ClosedWith an answerClosure needs a follow-up that confirms the situation held, and a response to the person who raised it. Retaliation protection is part of the protocol.
Grievances beyond child and forced labour — wages, land, safety — run on the same mechanism. See the human rights programme.
Sensitive data
Keep household data out of chain data.
Casework runs on the most sensitive records in the platform: children’s names, ages and school status. They are collected with consent, held for the programme, and they never travel with the commodity.
- AccessRoles see what they needFacilitators see their own cluster. Programme leads see cases and status. Buyers and auditors see counts and outcomes — never a child’s name.
- ConsentRecorded at the householdEach household’s consent names what was collected and for which programme. Withdrawing it stops future use.
- ReportingAggregates onlyEverything that leaves the platform — exports, filings, dashboards shared downstream — carries category counts, not identities.
What you file · duty 06
The annual statement writes itself from the caseload.
Reporting under the directive, and the social standards of CSRD next to it, asks four things: what you found, what you did, whether it worked, and how you know. The export answers them from the records the seasons already produced.
- Found + didRisks and actionsImpacts by category, origin and season, next to the cases opened and the remediation each one got.
- WorkedOutcomes, not activityThe number that matters: cases confirmed closed on a return visit, season over season.
- How you knowMethod travels with itVisit protocol, coverage, who verified, and where the grievance channel was open. Counts throughout — never names.
Human rights due diligence · FY 2026 extract
Annual statement
Child labour · coffee · Sidama, Ethiopia
Counts only · no household names leave the platform
The extract your CSRD and CSDDD reporting quotes. Every count traces to dated, named records underneath.
If you already collected data
Bring what you already have.
Supplier lists, household records and documents from the programmes you already run import in bulk — due diligence starts from the files you hold, and existing records are matched rather than duplicated.
CSV · 310 KB · one upload
3,120households on record
- Cases carried over — open follow-ups keep their history
- Matched to members — households tied to producers and plots
- 0 duplicates — existing records matched, not doubled
CSV, XLSX or paste a list — templates for every format. Errors show before anything is saved.
Questions we get.
Is Tracebud a CLMRS provider, or does it certify anything?+
No. Tracebud is data infrastructure: it holds household records, cases, remediation and follow-up visits in the shape a CLMRS works with. Case definitions, thresholds and remediation protocols are set by the standard your programme runs under, typically administered with a specialised NGO.
Does this replace the facilitators we already work with?+
No. It is the system of record for the visits they already make, so a visit that happened on paper or in a spreadsheet becomes a case with an ID, a status and a due date for the next one.
What happens with a worst-forms or immediate-risk case?+
It is flagged the day it is found rather than waiting for the season’s report, and routed to whoever your programme designates for urgent response, outside the normal review cycle.
Who can see household-level data?+
Access is restricted by role. A buyer or auditor sees caseload trends and closure rates, not named households; the cooperative and the programme administering remediation see the case itself. This data is never used to exclude a household from selling.
We are the buying company, not the cooperative. Who does the field work?+
The facilitators do, employed by the cooperative or exporter who knows the households, or by an agency you appoint. You fund the programme, set its scope, and see the caseload move — without holding raw household identities yourself.
How does this line up with CSRD reporting?+
The same export feeds both: impacts, actions and outcomes by category and origin map onto the CSRD social standards, and the methodology section answers how the numbers were produced. One caseload, two disclosures.
What does disengagement from a supplier look like in the record?+
As the end of a documented sequence, not a first move: the assurance, the prevention plan, the visits, the results, and then the decision. That order is what the directive expects you to be able to show before leaving.
Can we start with one origin?+
Yes, and you should. One origin, one cluster of villages, identification this season. The six duties do not require everywhere at once — they require a reasoned order and a record of it.
