EU TaxonomyEvidence

EU Taxonomy Regulation (EU) 2020/852 DNSH and minimum safeguards

These are the parts of Taxonomy alignment that fail most often under review.

Treat them as control systems with evidence, testing, remediation, and perimeter coverage.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 21, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 21, 2026

Overview

Most undertakings can list eligible activities. Far fewer can prove Taxonomy alignment. The gap is usually in DNSH and minimum safeguards. DNSH requires activity-specific evidence against the delegated-act criteria. Minimum safeguards require enterprise-level due diligence processes that actually operate in practice across the relevant perimeter. Both must be strong enough to support an Article 8 alignment claim.

Section 1

DNSH is activity-specific and evidence-heavy

DNSH is not a narrative statement that the business is generally responsible. It is a set of negative-condition tests that sit inside the technical screening criteria for the activity you are claiming as aligned.

That means the evidence must sit at activity level, site level, or asset level, depending on how the criteria are written. The more generic the claim, the weaker the file usually becomes.

Map each DNSH criterion to a pass or fail decision, the evidence item, the owner, and the review date
Keep boundary notes so the evidence clearly matches the exact activity, asset, site, or project in the KPI numerator
Where criteria require continued performance, define a monitoring cadence instead of treating the test as one-and-done
If one DNSH condition fails or cannot be evidenced, the activity stays out of aligned KPI numerators

Section 2

Minimum safeguards are not just a policy pack

Article 18 and the 2023 Commission Notice make the standard clearer than many teams assume. Minimum safeguards are procedures implemented by the undertaking. That means the review needs to look at how the undertaking identifies, prevents, mitigates, tracks, communicates, and remediates adverse impacts.

The safeguards baseline points to the OECD Guidelines for Multinational Enterprises on Responsible Business Conduct, the UN Guiding Principles on Business and Human Rights, the ILO fundamental principles and rights at work, and the International Bill of Human Rights.

OECD 2023: due diligence across business relationships, complaints channels, remediation, disclosure, and governance
UNGP: policy commitment, human-rights due diligence, leverage, tracking, and access to remedy
ILO 1998 Declaration as amended in 2022: forced labour, child labour, discrimination, freedom of association, collective bargaining, and safe and healthy working environment
The 2023 minimum-safeguards notice also links Article 18(2) to the SFDR DNSH principle through the social and governance principal adverse impact indicators

Section 3

What a reviewable safeguards file looks like

A reviewable safeguards file is cross-functional. It is not owned by sustainability alone. Legal, procurement, HR, compliance, and internal audit usually each hold part of the evidence.

The file must also show coverage. Reviewers will ask which entities, business relationships, and risk areas are actually captured by the procedures you say are in place.

Governance documents: policies, board or committee oversight, escalation routes, and management responsibilities
Due-diligence operation: risk assessments, supplier and partner screening, contract controls, training, and remediation workflows
Remedy and complaints: grievance mechanisms, case logs, investigations, corrective actions, and closure evidence
Coverage map: which entities, geographies, value-chain tiers, and activity owners are inside the procedures
Testing record: internal review, external assurance questions, and how open findings were resolved

Section 4

Common failure modes

The same weaknesses appear in most failed files. The undertaking may have serious policies, but the evidence chain does not show whether those policies were implemented for the actual reporting perimeter or the reporting year.

You should treat the red flags below as automatic triggers for deeper review before making any alignment claim.

DNSH reduced to a generic ESG statement rather than criterion-level evidence
Minimum safeguards shown through policies only, with no operating proof or remediation record
No linkage from aligned numerator to the exact DNSH and safeguards file used for that activity
Perimeter mismatch, where group disclosures cover more entities than the due-diligence procedures actually reach
Open severe incidents or unresolved remediation without clear treatment in the alignment decision

Recommended next step

Use EU Taxonomy Regulation (EU) 2020/852 DNSH and minimum safeguards as a cited research workflow

Research Copilot can take EU Taxonomy Regulation (EU) 2020/852 DNSH and minimum safeguards from clarifying scope and applicability with cited answers to a reusable workflow inside Sorena. Teams working on EU Taxonomy Regulation (EU) 2020/852 can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Research workflow

Open Research Copilot for EU Taxonomy Regulation (EU) 2020/852 DNSH and minimum safeguards

Start from EU Taxonomy Regulation (EU) 2020/852 DNSH and minimum safeguards and answer scope, timing, and interpretation questions with cited outputs.

Explore next step

Talk to Sorena

Talk through EU Taxonomy Regulation (EU) 2020/852

Review your current process, evidence gaps, and next steps for EU Taxonomy Regulation (EU) 2020/852 DNSH and minimum safeguards.

Explore next step

Primary sources