The four-hop ESRS S2 reporting flow

ESRS S2 disclosure reads, at the group sustainability statement, as a single set of figures attributed to a single reporting entity. The operating reality underneath those figures is structurally four hops removed from the worker the disclosure is about. Each hop is audit-traceable. Each hop fails forensically if the evidence was not captured at hop zero — the worksite, contemporaneously with the work it documents.

The four hops, named

Hop 0 — Worksite. Per-worker evidence is generated. Grievance-channel acknowledgement, working-time log under ArbZG or Code du travail or WAGwEU equivalent, accommodation receipt, A1 portable document, posted-worker filing receipt, contract translated into the deployment-jurisdiction language, qualification trail referencing EN ISO 9606-1, EN 15085, Anerkennung or IHK FOSA decisions, tariff-floor traceability per Lohngruppe. This is the substrate.

Hop 1 — Operating company aggregation. The operating-company subsidiary — a mid-market civil contractor inside a PE portfolio, a TGA Generalunternehmer inside a listed industrial holding, a balance-of-plant EPC inside a renewables platform — aggregates worksite-level evidence into deployment-cycle records. Per-project, per-deployment, per-jurisdiction. Maintained as the forensic audit record and as operational input to the next hop.

Hop 2 — Workforce-mobilisation operator. Where applicable, a Bayswater-style operator that manages cross-border deployment maintains its own aggregation layer. Per-deployment-cycle evidence packs feed both the operating company’s internal records and the operator’s own auditable archive, with chain-of-custody preserved across the transfer.

Hop 3 — Group or fund consolidation. The listed parent — a CAC 40 industrial, a DAX construction group, an FTSE 250 services platform — or a PE fund holding the portfolio company in a Triton, Apax, EQT, KKR-style structure consolidates portfolio operating-company data into group-level disclosure. ESRS S2 data-points S2-1 through S2-5 are populated at this layer, becoming the group sustainability statement.

Hop 4 — LP and institutional investor. Fund-level disclosure flows to limited partners — sovereign wealth funds, pension funds, insurance balance sheets, family offices. LPs that are themselves CSRD in-scope integrate the fund data into their own ESRS S2 disclosure under the value-chain workforce lens.

Where the flow breaks — and how

The flow does not break at the consolidation layer. It breaks at hop zero or hop one, and the failure surfaces at hop three when the parent’s auditor moves from analytical procedures to substantive testing.

Failure mode 1 — Missing grievance-channel records at hop zero. ESRS S2-2 (engagement processes) and S2-3 (channels to raise concerns) require evidence that the value-chain workforce has functional grievance pathways. If the operating company’s Tier-1 subcontractor did not maintain a grievance-channel log at the worksite, that log does not exist anywhere upstream. The disclosure becomes a written description of a system that operationally did not function.

Failure mode 2 — Substantiated-incident gap at S2-5. The Amended ESRS strengthens S2-5: substantiated human-rights incidents involving value-chain workers must be disclosed, with substantiation requiring an investigation process, a finding, and a remediation record. Without a documented investigation-and-finding process running contemporaneously, the disclosure either fails assurance or carries a qualification in the auditor’s report.

Failure mode 3 — Targets and progress unattainable at S2-4. S2-4 requires time-bound outcome metrics — attrition, wage-compliance, recognition-cycle figures — sufficient to demonstrate progress against material impacts. Without per-deployment-cycle data captured at hop one, the operating company cannot populate targets, and the parent cannot demonstrate trajectory between cycles.

Failure mode 4 — LP demands forensic recovery. When the parent’s external auditor flags a gap at hop three, the LP receives the fund-level report with the qualification noted. The LP’s responsible-investment team escalates. The parent or fund operations team initiates forensic recovery — re-interviewing workers, reconstructing records, retrieving subcontractor invoices, rebuilding payroll trails. Legal, audit, and LP-relationship costs compound. The recovery is rarely complete.

What “captured at hop zero” actually means

For every worker deployed to a project at hop zero, the deployment-gate evidence pack contains:

1. Grievance-channel reference. Worker is presented with the multilingual hotline, escalation pathway, and response-time SLA. Acknowledgement is logged with date, language version, and worker signature or digital confirmation.

2. Working-time documentation. ArbZG, Code du travail, WAGwEU, or jurisdiction-equivalent timesheet. Working-day log, rest-period compliance, overtime calculation, maintained per shift across the deployment cycle.

3. Wage-compliance evidence. Tariff-floor traceability per Lohngruppe or jurisdiction category, payslip cross-referenced to SEPA-traceable bank transfer, tariff calculation methodology documented per jurisdiction.

4. Accommodation evidence. Lodging address, lease or hotel contract, distance to worksite, sanitary-standard verification per jurisdiction’s posted-worker accommodation requirements.

5. Qualification trail. Per-worker certification — EN ISO 9606-1 for welders, EN 15085 for railway welding, Anerkennung or IHK FOSA decisions for regulated trades, NEN 3140 or equivalent for electrical work — with scope, validity, and expiry.

6. Contract documentation. Worker contract translated into the deployment-jurisdiction language, with statutory clauses present — working hours, wage floor, accommodation provision, grievance pathway, equal-treatment confirmation.

7. A1 / posted-worker filing receipt. Pre-deployment social-security certificate plus posted-worker registration receipt accepted by the deployment jurisdiction.

8. Investigation-and-remediation register. Where an incident arises — grievance raised, regulatory finding, welfare concern — a documented investigation process activates. Investigator named, finding established as substantiated, partially substantiated, or unsubstantiated, remediation taken or in progress, outcome recorded.

This substrate flows up four hops. Without it, S2-5 disclosure is reconstructive guesswork against an audit timetable that does not accommodate guesswork. The pre-deployment evidence pack is the operational artefact that holds the substrate together at the deployment gate.

Why this matters specifically post-Omnibus

Post-Omnibus, CSRD scope tightened to undertakings exceeding 1,000 employees and EUR 450 million turnover. CSDDD scope tightened to undertakings exceeding 5,000 employees and EUR 1.5 billion turnover. The EFRAG Amended ESRS cuts mandatory data-points by approximately 61 per cent. The entities that fall out of scope obtain relief. The entities that remain in scope face a more granular disclosure burden, not a less granular one.

S2-5 was strengthened, with substantiated-incidents disclosure now explicit and mandatory. CSDDD’s direct-supplier due-diligence obligation applies from 26 July 2029 under the Omnibus-revised transposition. France Loi 2017-399 (devoir de vigilance) coexists with CSDDD at its independent thresholds — 5,000 French employees, 10,000 worldwide — and is not aligning downward to the Omnibus floors. French entities in scope file an annual Plan de Vigilance with civil-liability exposure before the Tribunal Judiciaire de Paris, regardless of CSRD or CSDDD status. The UK Modern Slavery Act 2015 §54 statement applies to UK-relevant operations on separate thresholds.

On the LP side, institutional investors that are themselves CSRD in-scope use fund-level disclosures as input data. The fund’s evidence must be source-credible at the LP’s own assurance test, which inherits the same substantiation logic from S2-5 that the operating company faced at hop one.

The four-hop flow is the operating reality for any operating-company subsidiary or portfolio company sitting inside a CSRD-in-scope group. Cycle 2026 reports — covering FY2025 — are the first wave under post-Omnibus rules. Operating companies that captured per-worker evidence at hop zero throughout FY2025 close out clean at parent audit. Those that did not are now in forensic recovery during Q2 2026, with the next deployment cycle running in parallel and no operational bandwidth for reconstruction.

Takeaway

The four-hop ESRS S2 reporting flow does not break at consolidation. It breaks at the worksite, years earlier. Per-worker evidence captured at the deployment gate is the substrate for everything upstream. Operating companies and PE portfolio companies that treat ESRS S2 as a year-end reporting exercise fail at the audit gate. Operators that treat it as continuous evidence-capture at hop zero hold the disclosure intact across four hops to the LP report. The cost of getting it right is the cost of doing the work properly once. The cost of getting it wrong is forensic recovery plus audit qualification plus LP-relationship damage — and the substrate that should have been captured at hop zero cannot, in most cases, be reconstructed at hop three. The listed-parent and PE-portfolio reader and the CSRD workforce-disclosure layer converge on the same operational artefact: the deployment-gate evidence pack, built once, flowing four hops.

---

References

1. Directive (EU) 2026/470 of the European Parliament and of the Council amending Directive (EU) 2022/2464 and Directive (EU) 2024/1760 as regards corporate sustainability reporting and corporate sustainability due diligence (Omnibus I), in force 18 March 2026.

2. Directive (EU) 2022/2464 of the European Parliament and of the Council of 14 December 2022 as regards corporate sustainability reporting (CSRD).

3. Directive (EU) 2024/1760 of the European Parliament and of the Council of 13 June 2024 on corporate sustainability due diligence (CSDDD).

4. Commission Delegated Regulation (EU) 2023/2772 of 31 July 2023 supplementing Directive 2013/34/EU as regards sustainability reporting standards (European Sustainability Reporting Standards — ESRS).

5. EFRAG, ESRS S2 — Workers in the Value Chain (Amended), 2026, datapoints S2-1 through S2-5.

6. Loi n° 2017-399 du 27 mars 2017 relative au devoir de vigilance des sociétés mères et des entreprises donneuses d’ordre.

7. Modern Slavery Act 2015 (United Kingdom), §54 (Transparency in supply chains).

8. ESRS 1, General Requirements, §53 (Materiality of impacts in the value chain).