How to Document EUDR Risk-Mitigation Decisions

Filed under EUDR Risk Assessment and Mitigation Explained

Plot record: legal status and review details

Jurisdiction: European Union
Status: Current consolidated Regulation (EU) 2023/1115, including the 2025 amendment and September 2026 consolidation. Main obligations are not yet generally applicable on the verification date.
Application: Generally 30 December 2026; 30 June 2027 for qualifying micro and small operators established by 31 December 2024 under Article 38(3), except products covered by the EUTR Annex; some newly added products apply from 30 December 2027. Check the product and actor-specific rules.
Relevant provisions: Articles 4(5), 9, 10, 11, 12 and 13(2)

Review this page when:

Amendments to Articles 9 to 13
New Commission due diligence or certification guidance
Changes in country benchmarking, supply routes or relevant adverse information
Product-scope and application-date amendments

Document the reasoning, not only the activity

Article 11(3) requires decisions on mitigation procedures and measures to be documented, reviewed at least annually and made available to competent authorities on request. Operators must be able to demonstrate how those decisions were taken. A purchase order for an audit proves that work was commissioned; it does not explain why that work was appropriate or what the operator concluded from its findings.

A useful record connects four things: the concern, the selected response, the evidence obtained and the resulting product decision. Another reviewer should be able to follow that chain without attending the original meetings. The record can be concise, provided it links to accessible underlying evidence and preserves enough detail to understand limitations and judgments.

Within the risk assessment and mitigation framework, this record is the bridge between an adverse assessment and a subsequent release or continued hold. It should be started when the concern arises, then updated as facts emerge, rather than reconstructed after a shipment has already departed.

Define the concern and affected product boundary

Begin with a unique issue identifier and a factual statement of the concern. Instead of writing supplier risky, state that delivery records contain unidentified purchases entering a shared store during the proposed lot's production period. Identify the product, quantity, dates, suppliers, locations and shipments that may be affected, distinguishing confirmed facts from assumptions under investigation.

Link the concern to the relevant information requirement or assessment criterion. This shows whether the issue concerns origins, deforestation-free evidence, lawful production, document reliability, mixing or another applicable factor. Several concerns can arise from one event and may require separate responses. A missing land record and a volume mismatch should not disappear together merely because one new document arrives.

Record the immediate operational instruction, including holds and responsible teams. If the affected scope is uncertain, explain the temporary boundary and what evidence would permit narrowing it. Preserve the original warning, source and date. An overwritten spreadsheet cell can obscure when the operator learned a relevant fact and how promptly it responded.

Explain the selected response and alternatives

Describe the measure in enough detail to show its connection to the concern. Identify the information requested, survey or audit scope, segregation control or sourcing change. Record who will perform the work, relevant competence and independence, expected evidence and the acceptance test. Completion should mean the evidential question has been answered, not simply that a supplier has replied.

Where a choice matters, explain why alternatives were rejected or combined. A remote document check may be adequate to resolve an obvious transcription error but insufficient where records appear fabricated. A site audit may need additional geospatial work to address historical land cover. Recording this reasoning helps demonstrate proportionality without suggesting that every issue requires the most expensive investigation.

Keep commercial considerations visible but distinct from the compliance conclusion. A costly delay may explain why an alternative source was evaluated urgently. It does not explain why incomplete evidence is sufficient. If a deadline changes the procurement plan, record the changed plan and assess the new goods rather than weakening the acceptance test.

Record results, limitations and a usable decision

Summarise the evidence received and its version, date, source and coverage. Separate an investigator's observation from a supplier's explanation and from the operator's judgment. Link to the report and underlying accessible records. Explain contradictions and remaining limitations, including missing sites, incomplete periods or information that could not be independently corroborated.

For example, an audit may establish that an unexplained supplier code refers to a warehouse, while leaving its incoming origins unresolved. The record should close the code-identification question and retain the origin concern. A broad statement that the audit passed would conceal the distinction and could cause an unjustified release.

State the final outcome for the identified goods: release supported by no or negligible risk, continued hold pending specified work, exclusion of reliably segregated goods or refusal. Identify the authorised decision maker and date. Translate the decision into batch or order instructions that operations can implement. A well-reasoned memo is ineffective if a separate purchasing system still displays the lot as freely available.

Maintain a record that survives change and review

Preserve the sequence of decisions and evidence rather than replacing earlier versions. This is especially important when mitigation changes the assessed product set. If an uncertain portion is removed through reliable segregation, show the original scope, excluded goods, separation evidence and revised covered quantity. Do not imply that the excluded material became compliant through the change.

Article 11 requires at least annual review of mitigation decisions, while Article 10 and Article 12 have related assessment and system review requirements. Set review responsibilities and change triggers, including new origins, altered processing routes, adverse claims, certificate changes and control failures. Relevant new information may require immediate action under Article 4(5) or Article 13(2), rather than waiting for a scheduled review.

Maintain accessible records for the applicable five-year retention period and ensure the evidence remains retrievable when staff or systems change. Test a closed file by asking a colleague to reconstruct the decision. Then use a structured effectiveness review to check whether the recorded measures actually resolved the concern, rather than merely producing a complete administrative file.

Primary sources on the record

Articles 4(5), 9, 10, 11, 12 and 13(2). This entry was checked against the consolidated text dated 18 September 2026. Consolidated texts are documentation tools; the authentic acts are those published in the Official Journal.

Check the current sources and the guidance of the relevant competent authority for your situation. This page is not legal advice or a compliance determination.