ESRS S1 Own Workforce: A Practical Disclosure Guide for 2026 CSRD Reporters

If your company is in scope for the Corporate Sustainability Reporting Directive (CSRD) and you’ve just opened ESRS S1 for the first time, the most common reaction is that this isn’t really a sustainability standard at all. It looks like an HR audit. Headcount by country and employment type. Gender breakdowns at every management level. Collective bargaining coverage. Pay gaps. Adequate-wage assessments. Health-and-safety incident rates. Training hours. Family-leave uptake.

That reaction is correct, and it’s exactly the point. ESRS S1 — Own Workforce — is the standard that forces sustainability and HR teams to share data structures, audit trails, and disclosure language for the first time. For most wave-1 reporters, S1 is the largest single workstream in the CSRD report after climate (ESRS E1).

This guide walks through what S1 actually requires after the November 2025 amendments, where the new reliefs land for 2026 reports, and how to build a workforce data foundation that holds up under limited assurance.

What ESRS S1 actually covers

ESRS S1 covers the undertaking’s own workforce — both employees and non-employees who work for the company. “Non-employees” is the part that surprises first-time reporters: it includes self-employed individuals working primarily for the undertaking and workers provided by third-party staffing agencies. Pure outsourced workers in supplier operations belong under ESRS S2 (value-chain workers), not S1.

The standard is built around three buckets of working conditions:

Working conditions — secure employment, working time, adequate wages, social dialogue, freedom of association and collective bargaining, work-life balance, health and safety.
Equal treatment and opportunities for all — gender equality and equal pay for equal work, training and skills development, employment and inclusion of persons with disabilities, measures against violence and harassment, diversity.
Other work-related rights — child labor, forced labor, adequate housing, privacy.

These map to seventeen disclosure requirements numbered S1-1 through S1-17, plus governance and IRO (impact-risk-opportunity) disclosures that flow from ESRS 2 General Disclosures.

The 2026 amendments: 61% fewer datapoints, sharper focus

The November 2025 EFRAG amendments to ESRS S1 are the single most important development for anyone planning a 2026 report. According to the EFRAG draft S1 V1.5 markup, the amended standard removes roughly 61% of the original datapoints and concentrates on a smaller set of disclosures with stronger comparability properties.

Three changes matter most:

Materiality is reasserted. Under the original ESRS S1, certain workforce information was effectively “always disclose.” The amended version applies the standard only when own workforce is deemed material in the company’s materiality assessment, with workforce metrics scoped to the ten largest countries of operation and a de minimis threshold of fifty employees per country for S1-5 and S1-7 disclosures (per the EFRAG draft).

Non-employee disclosure compresses. S1-6, which previously demanded a multi-line breakdown of non-employee workforce data, reduces to a single essential datapoint — disclosed only when non-employees are critical to the business model.

Adequate wages get a methodology. The amended ESRS S1-9 anchors adequate-wage assessment in the ILO Principles for Estimating a Living Wage and lets companies choose between two methodologies for non-EU jurisdictions, provided the benchmark used is disclosed. This is significant: the previous text left preparers guessing what “adequate” meant outside the EEA.

Expected timeline: adoption mid-2026, mandatory application for financial years starting on or after 1 January 2027, with optional early application for 2026.

Phase-in reliefs you can actually use this year

For wave-1 reporters publishing FY 2026 statements (the cohort affected by the EU Omnibus stop-the-clock and the EC’s quick-fix delegated act), the following ESRS S1 disclosures may be omitted, per the BDO summary of the delegated act:

S1-13 health-and-safety metrics in paragraphs 40(d) and 40(e), plus all non-employee datapoints within S1-13.
S1-14 work-life balance metrics (family-related leave uptake).
For companies with fewer than 750 employees, the entire ESRS S1 may be omitted in the first year.
For companies above 750 employees in their first reporting year: non-employee data, disability inclusion, certain health-and-safety items, work-life balance, collective bargaining and social dialogue outside the EEA, social protection coverage, and training and skills development.

Use these reliefs deliberately — not as a way to delay every uncomfortable disclosure. Auditors will look closely at which phase-in clauses a preparer invokes, because each one signals data-readiness gaps that need to be closed by year two.

The data foundation that will break (or save) your S1 report

Most first-time S1 failures aren’t conceptual. They’re data-architecture failures. Here are the four patterns we see most often at Socious when reviewing draft S1 disclosures:

Pattern 1 — HRIS coverage gaps. Many companies run multiple HR systems across regions or acquired entities. ESRS S1 requires reconciliation to total headcount disclosed in the financial statements, broken down by employment contract type (permanent, temporary, full-time, part-time), gender, and country. If HR Country A is on Workday, Country B is on local payroll software, and Country C is on a spreadsheet, you have a reconciliation problem before you have a disclosure problem.

Pattern 2 — Non-employee blind spots. Procurement holds the contractor data, not HR. The S1-6 essential datapoint on non-employees in the amended standard still requires you to identify when non-employees are critical to the business model — which means HR, Procurement, and Legal need a shared definition of “non-employee” and a shared count.

Pattern 3 — Living-wage assessment without a method. Sustainability teams often produce a single global “all employees paid above local minimum wage” line and call it adequate-wage compliance. Under the amended S1-9 that won’t pass — you need to name the methodology (e.g., Anker Methodology, WageIndicator, the ILO Principles framework) and disclose the benchmark for each material jurisdiction.

Pattern 4 — Incident classification drift. Health-and-safety metrics under S1-13 (accidents per million hours worked, days lost) require consistent classification across sites. Plants that count near-misses differently than head office, or that exclude contractor incidents from site-level statistics, will produce internally inconsistent disclosures that assurance providers will flag.

How AI changes the S1 workflow

The historical answer to S1 complexity has been “hire more people in the sustainability team.” That doesn’t scale. Most enterprise sustainability teams reviewing the amended S1 are 4–8 people. They cannot manually reconcile workforce data across 20 HRIS instances every reporting cycle.

What AI does well in this workflow is the unglamorous part: pulling structured employee records from HRIS APIs (Workday, SAP SuccessFactors, BambooHR), mapping internal job-grade taxonomies to ESRS-compatible categories (management vs. non-management, employment contract types), reconciling counts to financial-statement headcount with explicit variance reports, and flagging missing or anomalous fields before they end up in the disclosure.

Socious Report handles this through an ESRS data-ingest layer that connects to your HRIS, payroll, and incident-reporting systems, runs the S1 disclosure logic on the ingested data, and produces the disclosure narrative with every numerical claim traceable back to the source record. The output is what assurance providers actually want: an audit trail, not a PDF.

For deeper context on how this works for environmental disclosures, see our companion guide on ESRS E1 climate disclosure and the practical ESRS datapoint mapping guide.

Common pitfalls and how to avoid them

Treating S1 as an HR project. S1 is a board-level disclosure that pulls from HR data. Governance, not HR systems, owns the materiality determination — and the boilerplate that says “own workforce is material” without supporting evidence is a finding waiting to happen.
Confusing S1 with S2. Workers in your supply chain belong in ESRS S2 (workers in the value chain). The line is drawn at who works primarily for your undertaking. Get this wrong and you’ll either over-disclose (S1 ingesting supplier worker data) or under-disclose (treating contractor workforce as someone else’s problem).
Ignoring pay-gap math. Gender pay gap under S1-16 is calculated on gross hourly pay, not annual salary. Many preparers calculate it on annual figures, which inflates the gap due to part-time concentration among women in many jurisdictions.
Skipping the materiality narrative. Under the amended S1, almost everything is conditional on material own-workforce impacts. Without a documented materiality determination linking ESRS 2 IRO disclosures to each S1 datapoint, the disclosures look arbitrary.

What to do in the next 60 days

If you are a wave-1 reporter publishing FY 2026:

Map your S1 disclosure list against the amended EFRAG datapoint set — not the original 2023 ESRS — to confirm what you actually need to disclose.
Decide explicitly which phase-in reliefs you will use. Document the reason for each.
Pick your living-wage methodology now. It is the slowest external dependency in the S1 workflow because it usually requires a third-party benchmark provider.
Stand up the reconciliation between HRIS headcount and financial-statement headcount before September. Audit teams will ask for it.
If you operate across multiple jurisdictions, set the top-ten countries against the de minimis threshold and freeze the list early. Re-scoping mid-cycle is expensive.

ESRS S1 is the standard where compliance and operational reality collide most directly. The companies that come out of their first S1 cycle well-positioned aren’t the ones with the largest sustainability teams — they’re the ones who built the HR / Procurement / Sustainability data plumbing before the disclosure deadline, not during it.

If you’d like to see how Socious Report ingests workforce data and produces audit-ready ESRS S1 disclosures, book a demo or download our CSRD readiness assessment.