Reviewing Whether Mitigation Reduced Risk to Negligible

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 3, 4(5), 9, 10, 11 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

Return to the unanswered question

Mitigation is successful only when the resulting evidence supports the required no or negligible risk conclusion for the relevant products. Completing the action plan is not the same as establishing that outcome. An audit can finish, training can occur and a supplier can submit every requested file while an important origin or legality concern remains unresolved.

Start the review with the original assessment. State the concern in factual terms, the affected products and why the concern prevented release. Then compare the new evidence with the question the measure was designed to answer. If the issue was unknown-origin mixing, ask whether the actual covered goods can now be connected to assessed origins, not whether the supplier has generally improved its procedures.

The risk assessment and mitigation framework requires reassessment before placement or export where mitigation was necessary. A favourable progress report cannot substitute for that reassessment. Nor does an internal completion deadline allow an unresolved issue to expire into acceptance.

Test evidence quality and product coverage separately

First evaluate whether the new evidence is reliable. Examine its source, date, method, internal consistency and links to other records. A corrected permit needs a credible explanation of the correction; a revised farm list needs an account of additions and removals. Repeatedly replacing inconsistent files without investigating their cause can conceal a deeper reliability problem.

Then ask whether the evidence covers the goods under decision. A strong audit of current receiving controls may not establish the origin of stock accumulated before those controls existed. An accurate map of one farm does not cover deliveries from another farm carrying the same local name. Quality and coverage are separate conditions, and strength in one does not compensate for absence in the other.

Examine whether the mitigation created new dependencies. A segregated stream may rely on a shared tank remaining closed to other inputs. A direct-source arrangement may depend on a processor not using emergency purchases. Record those conditions and establish evidence that they actually hold for the proposed product set.

Use a concern-by-concern closure test

For each open concern, identify the finding that would support closure and compare it with what the investigation actually established. Classify the result as resolved, partly resolved, unresolved or contradicted by further evidence. These are useful workflow labels, not legal thresholds. The final conclusion still needs reasoned consideration of all relevant information and criteria.

Do not close an issue because its score has fallen below an internal number. The EUDR does not prescribe a numerical percentage of acceptable non-compliance risk. Explain what changed in the facts. For example, the previously unexplained delivery is now linked to a specific plot through verified receiving records, and the plot's compliance evidence has been assessed.

Check the interaction between concerns. Reliable segregation may remove an affected source from the covered lot, but the revised quantity and route must remain consistent with records. Resolving an origin gap can reveal a new legality issue at the identified plot. The review should reopen that new issue rather than treating identification itself as a complete compliance result.

A supplier improvement that covers only future supply

An operator commissions work after a cocoa cooperative cannot separate member deliveries from spot purchases. The cooperative installs separate storage, trains receiving staff and demonstrates a new lot-identification process. A follow-up audit confirms that the controls operate for deliveries received after a specified date. Management proposes closing the original issue for all remaining warehouse stock.

The reviewer compares the audit period with the goods. Some stock predates the new controls and was already mixed. The new procedure demonstrates a credible improvement for future assessed supply, but the report does not establish origins for that earlier stock. The reviewer records partial success, keeps the earlier stock outside the proposed release and defines a new assessment boundary for later identifiable production.

This conclusion recognises the value of mitigation without overstating its reach. If further evidence can establish the older goods' origins, they may be assessed on that evidence. If not, improved future practice cannot retrospectively repair the gap. The same principle applies when known post-cutoff deforestation exists: a better control system does not change the production history of the affected goods.

Approve a bounded conclusion and keep it under review

The closing note should summarise what changed, which evidence supports the conclusion, which goods are covered and any conditions for continuing reliance. Identify exclusions clearly. A decision that supports one production period or controlled route should not silently become approval for new plots, intermediaries or warehouses. Give operations an instruction tied to the revised product identifiers and quantities.

Consider a challenge by someone who did not perform the mitigation. Can they identify the original concern and follow the reasoning to the release conclusion? Where appropriate, use the non-SME operator's independent audit function to examine whether internal policies, controls and procedures support reliable decisions. That system assurance remains distinct from evidence establishing a particular lot's compliance.

Document mitigation decisions and review them at least annually under Article 11(3). New relevant information can require earlier reassessment and applicable notifications, including Article 4(5) or Article 13(2). Keep unresolved issues visible and record further action. The risk assessment and mitigation checklist provides a final structured challenge before closing the dossier and releasing the defined goods.

Primary sources on the record

Articles 3, 4(5), 9, 10, 11 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.