Search every question across sub-FAQs

Articles 10 and 11 treat suspension or termination as last-resort measures, not the first response. For potential impacts that cannot be prevented or adequately mitigated, an enhanced prevention action plan may use or increase leverage through temporary suspension if there is a reasonable expectation that the effort will succeed. If there is no such expectation, or if the enhanced plan fails and the potential adverse impact is severe, termination may be required where the law governing the relationship allows it.

For actual impacts, the parallel last-resort route is an enhanced corrective action plan and, where necessary, termination if the actual adverse impact is severe. Before suspension or termination, the company must assess whether the adverse impacts of doing so can reasonably be expected to be manifestly more severe than the impact that could not be addressed.

The useful record is an impact file, not a generic memo. It should let a reviewer see the identified impact, the Article 10 or Article 11 classification, the prioritisation basis, stakeholder input, measures selected, implementation status, and monitoring result.

Article 15 requires periodic assessments of operations and measures, including subsidiaries and relevant business partners, to monitor the adequacy and effectiveness of identification, prevention, mitigation, bringing to an end, and minimisation. Those assessments should be based where appropriate on qualitative and quantitative indicators and be updated after significant changes, at least every 12 months, and when reasonable grounds indicate new risks may arise.

The mandatory remediation trigger is narrow: the company must provide remediation when it has caused or jointly caused an actual adverse impact. The directive describes remediation as restoring affected persons, communities, or the environment to a situation equivalent or as close as possible to the one that would have existed without the impact, proportionate to the company's implication.

Do not treat every supplier incident as an automatic company-funded remedy. If the actual adverse impact was caused only by a business partner, the company may provide voluntary remediation and may use its influence over that business partner to enable remediation.

Start with the factual link between the company's own operations, its subsidiaries, and business partners in the chain of activities. The remediation file should explain what happened, who was affected, which activity or omission created the harm, and whether the company was one of the causes.

For a jointly caused impact, the remedy should be proportionate to the company's implication. For a business-partner-only impact, the file should explain what leverage is available, what the company asked the partner to do, and whether voluntary support is appropriate.

Complaints are a remediation input, not just a mailbox. Article 14 requires companies to enable complaints from affected persons, people with reasonable grounds to believe they may be affected, their legitimate representatives, relevant trade unions or workers' representatives, and experienced civil-society organisations for environmental impacts.

If a complaint is well founded, the adverse impact is treated as identified and the company must take the relevant measures under the directive, including remediation where Article 12 applies. Complainants can request follow-up, meet company representatives about severe impacts and potential remediation, and receive reasons for a founded or unfounded decision.

The evidence should let a later reviewer see why remediation was required, what was done, and what was left outside the remedy. Recital 61 says compliance documentation should include remediation measures, periodic assessments, notifications, and complaints where relevant.

Keep enough detail to support the causation view and the remedy design without turning the file into unsupported legal conclusions. The most useful record is a compact remediation log tied to the underlying impact assessment, complaint file, stakeholder consultation, and implementation proof.

Remediation under Article 12 does not supersede every other route to remedy. Affected stakeholders do not have to seek company remediation before bringing claims in court, and a company complaint procedure does not block access to supervisory-authority, judicial, or other non-judicial mechanisms.

Civil liability is a separate question. Article 29 says a company cannot be held liable if damage was caused only by its business partners in its chain of activities, and full compensation under the directive must not lead to punitive, multiple, or other overcompensation.

Article 9 applies after Article 8 identification and assessment. If it is not feasible to prevent, mitigate, bring to an end, or minimise all identified adverse impacts at the same time and to their full extent, the company must prioritise the impacts so it can fulfil the prevention and mitigation duties in Articles 10 and 11.

The priority order must be based on the severity and likelihood of the adverse impacts. After the most severe and most likely impacts have been addressed within a reasonable time, the company must move on to less severe and less likely impacts.

Severity should focus on the impact on people or the environment. The CSDDD definition points to scale, scope, and irremediable character, including gravity, number of affected people, environmental extent, irreversibility, and limits on restoring affected people or the environment within a reasonable period.

Likelihood should capture credible indicators that the impact has occurred or may occur, such as prior assessments, notifications, complaints, high-risk geographies, product or service risks, sector risks, business-model risks, or changed operating conditions. For human rights impacts, the rationale should not let low estimated probability bury an impact that would be severe or hard to remedy.

Stakeholder evidence should help test the company's view of severity and likelihood. Article 13 requires stakeholder consultation when gathering information to identify, assess, and prioritise adverse impacts, and again for prevention or corrective action plans, suspension or termination decisions, remediation, and monitoring indicators.

The file should distinguish direct stakeholder evidence from expert input. If effective stakeholder engagement is not reasonably possible, the company should consult experts who can provide credible insight into actual or potential impacts.

An audit-ready rationale should let a reviewer trace the decision from identified impact to priority ranking to action. It should explain why the selected impacts were treated first, which evidence was used, which stakeholders or experts informed the assessment, and when lower-ranked impacts will be addressed.

The rationale should also separate prioritisation from response design. Articles 10 and 11 ask different questions after prioritisation, including whether the company caused, jointly caused, or is linked to the impact, where the impact occurs in the chain of activities, and what influence the company can exercise.

The current CSDDD phase-in is no longer the original 26 July 2027, 26 July 2028, and 26 July 2029 sequence. Directive (EU) 2025/794 amended Article 37 so Member States must transpose by 26 July 2027 and apply the national measures from 26 July 2028 for the larger wave and from 26 July 2029 for all other in-scope companies.

For the 26 July 2028 wave, Article 37 covers EU companies and EU-parent groups in Article 2(1), points (a) and (b), that had more than 3,000 employees on average and more than EUR 900 million net worldwide turnover in the relevant financial year. It also covers third-country companies and groups in Article 2(2), points (a) and (b), that generated more than EUR 900 million net turnover in the Union.

The 26 July 2029 wave is the catch-up wave for companies that are in Article 2 scope but are not in the larger 26 July 2028 EUR 900 million cohorts. For EU companies, the main Article 2(1)(a) threshold remains more than 1,000 employees on average and more than EUR 450 million net worldwide turnover. Ultimate parent companies of groups meeting those thresholds are also covered.

The 2029 wave also includes the CSDDD franchise and licensing categories. For EU companies or groups, Article 2(1)(c) uses royalties above EUR 22.5 million and net worldwide turnover above EUR 80 million where the arrangements involve a common identity, business concept, and uniform business methods. For third-country companies or groups, Article 2(2)(c) uses the same royalty amount in the Union and an EU net turnover threshold above EUR 80 million.

Start with Article 2 scope, then apply Article 37 timing. A company outside Article 2 is not pulled in merely because a business partner asks for CSDDD information. A company inside Article 2 still needs the amended Article 37 test to identify whether its first application date is 26 July 2028 or 26 July 2029.

Keep the EU and third-country tests separate. EU companies use employee and net worldwide turnover thresholds. Third-country companies use net turnover generated in the Union, and no employee threshold is listed for the main Article 2(2)(a) test.

Retain evidence that lets a reviewer reconstruct both parts of the analysis: why the company is or is not within Article 2, and why the selected application date follows from the amended Article 37 text. The record should not rely on the superseded 26 July 2027 first-wave date from the original directive text.

The evidence file should be refreshed when consolidated group numbers, EU turnover, franchise or licensing royalties, or national transposition rules change.

The main mistake is using the original Directive (EU) 2024/1760 phase-in schedule as if it were still current. That can incorrectly leave a 26 July 2027 first wave in calendars and supplier requests. Current planning should use the Article 37 wording amended by Directive (EU) 2025/794.

A second mistake is blending CSDDD scope with CSRD reporting waves or supplier due diligence requests. CSDDD scope waves are based on Article 2 CSDDD categories and Article 37 CSDDD application dates. A smaller supplier may still receive information requests from an in-scope customer, but that is not the same as being directly in CSDDD scope.

Article 22 requires covered companies to adopt and put into effect a transition plan for climate change mitigation. The plan must aim, through best efforts, to make the company's business model and strategy compatible with the transition to a sustainable economy, the 1.5 C Paris Agreement pathway, and the EU climate-neutrality objective under the European Climate Law.

The plan is not only a disclosure label. Its design must include targets, the actions and levers for reaching those targets, the investments and funding that support implementation, and the role of the company's administrative, management, and supervisory bodies.

The plan should include time-bound climate targets for 2030 and then in five-year steps up to 2050. Article 22 says these targets must be based on conclusive scientific evidence.

Where appropriate, the plan should include absolute greenhouse-gas emission reduction targets for Scope 1, Scope 2, and Scope 3 emissions for each significant category. Teams should therefore avoid targets that cannot be traced to a baseline, emissions boundary, target year, and significant emissions category.

Article 22 requires a description of the decarbonisation levers identified and the key actions planned to reach the climate targets. In practice, that means the plan should identify how emissions are expected to fall, who owns each lever, and which operational decision makes the lever real.

The Directive gives examples rather than an exhaustive list: changes in the company's product and service portfolio and adoption of new technologies may be relevant. Other levers should still be documented only where the company's evidence supports them.

Article 22 requires an explanation and quantification of the investments and funding supporting the transition plan. A useful plan should therefore link each material lever to the capital, operating spend, financing, or budget line that makes implementation credible.

The plan also needs to describe the role of administrative, management, and supervisory bodies. That should cover who approves the plan, who monitors progress, who receives escalation when targets or levers are off track, and how updates are reviewed before publication or reporting.