Short answer
The answer, before the reasoning
C6 and C7 serve different purposes. C6 asks whether the undertaking has an own-workforce code or human-rights policy, which specified issues it covers, and whether an own-workforce complaints-handling mechanism exists.
C7 asks whether there were confirmed incidents in specified categories and whether the undertaking is aware of confirmed incidents involving value-chain workers, affected communities, consumers or end-users. A grievance, complaint or allegation should not be reported as a confirmed incident merely because it was received. The undertaking needs a documented confirmation rule, a reporting-period cut-off, separate own-workforce and value-chain populations, privacy and legal review, and evidence for any remediation statement.
A controlled case lifecycle keeps intake information separate from the conclusion reported under C7.
Why this question matters
Human-rights case data are unusually sensitive. A weak reporting process can understate serious impacts, inflate unverified allegations into confirmed facts, expose affected individuals, prejudice an investigation or create an unsupported claim that remediation has been completed.
The key control is not a more detailed public narrative. It is a restricted case register that preserves the distinction between intake, investigation, confirmation and remedy, and then produces proportionate aggregate information for the sustainability report.
Quick orientation
At a glance
- Quick orientation
- Applies to
- Undertakings applying the Comprehensive Module in full or adding C6/C7 as selected supplementary information.
- Primary decision
- What is a mechanism, what is an intake item, and what qualifies as a confirmed incident for reporting.
- Key source
- C(2026) 5011 Annex I, paragraphs 61-62; historical Recommendation (EU) 2025/1710, Annex II paragraph 174.
- Common confusion
- Treating every hotline report as confirmed, or requiring a final court judgment before anything can be confirmed.
What C6 and C7 actually ask
MICRO RELIEF / C6(a), C6(c), C7(a) and C7(c) are marked voluntary for undertakings with 10 employees or fewer in the Commission-adopted text. The reporting team should record the relief deliberately; it should not silently treat a non-reported datapoint as “not applicable”.
In practice
| Disclosure | Question in the Standard | What it is not |
|---|---|---|
| C6(a) | Does the undertaking have a code of conduct or human-rights policy for its own workforce? | A test of whether the policy is effective or whether no incidents occurred. |
| C6(b) | If yes, does it cover child labour, forced labour, human trafficking, discrimination, accident prevention or other specified issues? | Permission to answer “yes” because a broad values statement exists without checking actual policy scope. |
| C6(c) | Does the undertaking have a complaints-handling mechanism for its own workforce? | Proof that the mechanism is trusted, accessible or effective. |
| C7(a) | Were there confirmed own-workforce incidents in the listed categories during the reporting period? | A count of every concern, complaint or allegation received. |
| C7(b) | If yes, the undertaking may describe actions being taken to address them. | A mandatory remediation narrative or a requirement to claim closure. |
| C7(c) | Is the undertaking aware of confirmed incidents involving value-chain workers, affected communities, consumers or end-users? If yes, specify. | A statement that the undertaking has complete visibility across every business relationship. |
In practice
Grievance, complaint, allegation and confirmed incident are not synonyms
| Term | Practical working meaning | Reporting consequence |
|---|---|---|
| Grievance mechanism | A channel or process through which people can raise concerns or seek remedy. | C6 asks whether an own-workforce complaints-handling mechanism exists; existence alone does not prove effectiveness. |
| Grievance / concern | An expression that a person or group has been adversely affected or may be at risk. | Record it, triage it and protect the person; do not automatically classify it as a confirmed incident. |
| Complaint | A concern submitted through a recognised internal or external process. | It can become a confirmed incident if the undertaking’s documented confirmation criterion is met. |
| Allegation | An assertion that misconduct or harm occurred, not yet established as fact. | Public wording should not present an allegation as a substantiated conclusion. |
| Confirmed incident | A case that meets a controlled confirmation rule. Historical Commission guidance describes formal legal action or complaint, or non-compliance identified through established procedures. | The conclusion should be traceable to an authority, procedure, evidence and reporting-period cut-off. |
| Remediation | Action to restore affected people, prevent recurrence or otherwise address harm, depending on the undertaking’s connection to the impact. | Describe only what is supported: action initiated, action completed, or outcome demonstrated are different claims. |
How to define “confirmed” without inventing a universal rule
The 2026 Commission-adopted C7 text uses the term “confirmed incidents” but does not itself prescribe one investigation protocol. Historical Commission guidance is useful because it describes a confirmed incident as a legal action or complaint registered through a formal process, or an instance of non-compliance identified through established procedures such as audits, monitoring or grievance mechanisms. This guidance should be labelled historical and used as a design input, not copied as if it were a new binding definition.
A defensible internal rule states who may confirm, what evidence standard is applied, how appeals or ongoing proceedings are treated, and which date determines inclusion in the reporting period. The rule should be stable enough for comparatives and flexible enough to respect local labour, whistleblower, criminal and civil procedure.
The reporting population is produced after investigation and cut-off controls, not at the moment of intake.
In practice
| Possible confirmation route | Suitable evidence | Control question |
|---|---|---|
| Internal investigation | Approved investigation report, finding, disciplinary or corrective-action decision. | Was the investigator authorised and was the finding final under the procedure? |
| Management-system audit or formal monitoring | Non-compliance finding, root-cause record and approval. | Does the finding concern a C7 category and the reporting population? |
| External competent authority | Regulator, labour inspector, court or other authority record. | Is the matter a final finding, an allegation, or an ongoing action that must be described cautiously? |
| Grievance or complaints process | Formal complaint plus substantiation decision under the procedure. | Does receipt alone count, or is a separate substantiation decision required? |
| Supplier or customer notification | Counterparty confirmation, audit evidence or other reliable record. | What did the undertaking know, when did it know it, and how was reliability assessed? |
A practical reporting workflow
Define the reporting perimeter. Map own workforce separately from value-chain workers, affected communities, consumers and end-users.
Inventory policies and mechanisms. Confirm the current approved document, population covered, access channels, language, escalation and anti-retaliation controls.
Create a case taxonomy. Record intake type, issue category, source, entity or relationship, investigation status and confidentiality level.
Apply the confirmation rule. Identify the authorised decision-maker, evidence threshold, finality status and reporting-period cut-off.
Separate counts and narratives. Produce an own-workforce conclusion for C7(a) and a separately evidenced awareness conclusion for C7(c).
Assess remediation. Distinguish immediate protection, investigation, corrective action, remedy to affected people, prevention of recurrence and effectiveness evidence.
Perform legal and privacy review. Check personal data, whistleblower protection, privilege, defamation risk, ongoing proceedings and local disclosure restrictions.
Approve aggregate public wording. Reconcile the answer to the restricted register, disclosure index and the Option A/Option B basis statement.
Own workforce and value chain require separate awareness controls
The undertaking normally has direct access to own-workforce case channels and HR investigations. C7(c) is different: it asks whether the undertaking is aware of confirmed incidents involving specified external populations. A “no” answer is therefore a conclusion based on a defined awareness process, not a claim of omniscience.
In practice
| Population | Potential awareness sources | Limitation to disclose internally |
|---|---|---|
| Own workforce | HR case system, hotline, works council, occupational safety process, investigations, legal claims. | Fragmented channels or inconsistent country definitions. |
| Value-chain workers | Supplier grievance channels, audits, contract notifications, worker interviews, media and regulator alerts. | Coverage may be risk-based and not every tier is monitored directly. |
| Affected communities | Community channels, site engagement, permits, local authority records, NGO or civil-society information. | Language, access and trust may affect visibility. |
| Consumers / end-users | Product complaints, safety systems, regulator notifications, litigation and customer-care channels. | A product complaint is not necessarily a human-rights incident. |
Privacy and legal review: what can be public and what must stay restricted
The evidence room can be much more detailed than the public report, but both must reconcile.
Use aggregate categories and avoid names, exact locations or combinations of facts that allow re-identification.
Apply data minimisation: the sustainability report rarely needs the full case file, witness statements or medical information.
Do not publish a conclusion that could prejudice an investigation, appeal, judicial proceeding or protected whistleblower process.
Record the legal basis and approval for any omission or high-level wording; “confidential” should not become a blanket substitute for analysis.
Keep public disclosures consistent with financial statements, legal reports, regulatory filings and other corporate communications.
In practice
How to describe remediation without overclaiming
| Evidence state | Safe reporting pattern | Avoid |
|---|---|---|
| Action initiated | “The undertaking opened an investigation and implemented interim protection measures.” | “The issue was resolved.” |
| Corrective action completed | “The supplier corrective-action plan was completed and closure evidence was reviewed.” | “No further risk exists.” |
| Remedy provided | “Affected workers received reimbursement and access to an independent complaints route.” | Calling training alone a remedy to affected people. |
| Outcome evaluated | “Follow-up testing found no recurrence in the sampled population; wider monitoring continues.” | Claiming effectiveness from an activity count only. |
Hypothetical example: a discrimination complaint in a subsidiary
ILLUSTRATIVE SCENARIO / A 180-employee group receives a complaint that a supervisor discriminated in promotion decisions. The complaint is logged in December. An authorised investigation concludes in February of the following year that discrimination occurred, and the appeal period ends in March. The group reports the case as a complaint received in the first year but not as a confirmed incident for that year under its documented cut-off rule. It includes the confirmed incident in the following reporting period, explains the population and category, and describes corrective action only after legal and privacy approval. This is an illustrative process, not a universal cut-off rule.
Illustrative disclosure wording
ADAPT TO FACTS / C6. The undertaking has an own-workforce human-rights policy covering forced labour, human trafficking, discrimination and accident prevention. It does not currently include a separate child-labour provision because all direct employees are above the applicable minimum working age; this conclusion is reviewed annually. Employees can raise concerns through a confidential web and telephone channel available in the principal working languages. C7. During the reporting period, one discrimination incident involving the own workforce met the undertaking’s documented confirmation criterion. Corrective action included restoration of the affected employment decision, disciplinary action and review of promotion controls. No confirmed value-chain incidents were identified through the supplier audit, contractual notification and external-alert sources used during the period. These sources do not provide complete visibility across all tiers.
Why it works: the wording identifies the policy scope, mechanism, confirmation basis, population, category, remedy and the limitation of value-chain awareness. It does not identify individuals, present allegations as facts or claim that all risk has been eliminated.
In practice
Weak versus stronger wording
| Weak | Stronger | Improvement |
|---|---|---|
| “We received no human-rights complaints.” | “No own-workforce case met the documented confirmation criterion during the reporting period; two allegations remained under investigation at year-end.” | Separates intake from confirmed cases and explains cut-off. |
| “All supplier incidents were resolved.” | “One confirmed supplier incident was subject to reimbursement and a corrective-action plan; effectiveness monitoring remains open.” | Separates remedy, corrective action and outcome. |
| “Our hotline ensures human rights are protected.” | “The hotline is one intake channel. Access, response time, non-retaliation and outcomes are reviewed separately.” | Avoids treating mechanism existence as effectiveness. |
Common mistakes
MYTH / REALITY / Myth: “A complaints mechanism proves that the undertaking manages human rights effectively.” Reality: C6 asks whether a mechanism exists. Effectiveness requires separate evidence about accessibility, trust, non-retaliation, response, remedy and outcomes; C7 then asks about confirmed incidents.
In practice
| Mistake | Why it creates risk | Correction |
|---|---|---|
| Counting every allegation as confirmed | Overstates facts and can harm affected people and accused parties. | Maintain separate status fields and a confirmation authority. |
| Waiting only for a final court judgment | Can understate internally substantiated non-compliance. | Use multiple controlled confirmation routes consistent with law. |
| Combining own workforce and value chain | Obscures different populations and awareness sources. | Report and evidence them separately. |
| Publishing case details | Creates privacy, retaliation and legal risk. | Use aggregate wording and restricted evidence. |
| Calling corrective action “remediation” without affected-person evidence | Overstates the outcome. | Record who benefited, what was restored and what remains open. |
| Using “no incidents” without describing awareness controls | Implies complete visibility. | Document sources, coverage and limitations. |
Readiness
C6-C7 evidence and review checklist
- Approved policy and issue-coverage map.
- Complaints-mechanism procedure, access records and anti-retaliation controls.
- Restricted case register with intake type, population, category and status.
- Documented confirmation criteria, authority and reporting-period cut-off.
- Separate own-workforce and value-chain awareness sources.
- Remediation and corrective-action evidence with outcome status.
- Privacy, whistleblower, privilege and ongoing-proceedings review.
- Reconciliation to public wording, disclosure index and reporting-route claim.
- Micro-relief decision for undertakings with 10 employees or fewer.
- Named HR, legal/privacy and reporting approvals.
In practice
Related standards and connections
| Connection | Role | Non-equivalence note |
|---|---|---|
| UN Guiding Principles | Supports grievance-mechanism and remedy practice. | Implementation context, not a replacement for C6/C7. |
| GDPR and national law | Controls processing and publication of personal data. | A sustainability disclosure does not override privacy or procedural rights. |
| ESRS social standards | Potential migration destination for an entity entering CSRD scope. | ESRS materiality, disclosure architecture and assurance are different. |
| GRI Standards | Broader impact-reporting and management-of-impact context. | GRI material-topic conclusions and claims do not transfer automatically. |
Questions
Questions people ask
What is a confirmed human-rights incident?
The 2026 Commission-adopted C7 text uses the term “confirmed incidents” but does not itself prescribe one investigation protocol. Historical Commission guidance is useful because it describes a confirmed incident as a legal action or complaint registered through a formal process, or an instance of non-compliance identified through established procedures such as audits, monitoring or grievance mechanisms. This guidance should be labelled historical and used as a design input, not copied as if it were a new binding definition.
Is every complaint a confirmed incident?
A grievance, complaint or allegation should not be reported as a confirmed incident merely because it was received. The undertaking needs a documented confirmation rule, a reporting-period cut-off, separate own-workforce and value-chain populations, privacy and legal review, and evidence for any remediation statement.
How should value-chain incidents be reported?
C7(c) is different: it asks whether the undertaking is aware of confirmed incidents involving specified external populations. A “no” answer is therefore a conclusion based on a defined awareness process, not a claim of omniscience.
Does C7 require remediation disclosure?
If yes, the undertaking may describe actions being taken to address them. Describe only what is supported: action initiated, action completed, or outcome demonstrated are different claims.
How should privacy be protected?
Use aggregate categories and avoid names, exact locations or combinations of facts that allow re-identification. Apply data minimisation: the sustainability report rarely needs the full case file, witness statements or medical information. Do not publish a conclusion that could prejudice an investigation, appeal, judicial proceeding or protected whistleblower process.
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ LRA AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · EU Voluntary Standard 2026
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.
