Kern van de disclosure
The practical focus is on whether health and safety coverage is real and consistent across the organisation, not just at a few well-managed sites. Readers will want to understand whether the approach applies across all operations, locations and types of workers, how issues are identified and followed up, and whether the organisation can show that its system works in day-to-day practice rather than only on paper.
Dit educatieve materiaal van LRA ondersteunt het opstellen van de disclosure. Raadpleeg voor de exacte vereisten altijd de officiële European Commission-bron.
Voorbereiden
Wat te verzamelen vóór het opstellen
Vink elk veld af zodra het bewijs binnen is. Eigenaren zijn de teams die de bronbestanden doorgaans beheren.
-
Reporting coverage share
Sustainability reporting / HR analyticsThe share of the relevant workforce or activity base that is included in the reported figure, using the same population and period as the underlying source data.
Bewijs Coverage calculation file, source population definition, and reconciliation to the HR or operational system used for the denominator.
Let op The numerator is taken from one population while the denominator comes from a different source system or period, so the percentage does not reconcile to the underlying headcount or activity base.
-
Work-related deaths
Health and safetyA narrative summary of any deaths linked to work, separating those arising from accidents and those arising from illness, with the reporting period and affected population clear.
Bewijs Incident log, occupational health records, investigation notes, and any internal fatality review or case file.
Let op Accident-related deaths and illness-related deaths are merged or one category is omitted, so the reported narrative does not match the underlying case classification.
-
Work accident count
Health and safetyThe number of reportable work accidents in the period, using the organisation’s agreed incident definition and counting method.
Bewijs Incident register, investigation log, and monthly safety dashboard reconciled to the central incident system.
Let op Local incident logs are counted differently from the central incident system, so the accident total does not reconcile to the source register.
-
Accident frequency rate
Health and safety / HR analyticsThe accident rate expressed per one million hours worked, using the same accident count and hours base for the same reporting period.
Bewijs Safety KPI calculation sheet, accident count source, and hours-worked extract from payroll or timekeeping.
Let op The rate is calculated from a different hours base or period than the accident count, so the per-million-hours figure is not aligned to the source inputs.
-
Work illness cases
Occupational healthThe number of work-related illness cases recognised in the period, using the organisation’s agreed case definition and classification rules.
Bewijs Occupational health case log, medical referral records, and case classification summary.
Let op Non-work-related conditions are included, or work-related cases are missed because the case definition is not applied consistently to the source log.
-
Lost work days
Health and safety / HRThe total days lost because of work-related injury or illness in the reporting period, counted on the same basis used in the incident and absence records.
Bewijs Absence records, incident case files, return-to-work notes, and the days-lost calculation worksheet.
Let op Days lost are mixed with calendar days or partial absences, or the count is taken from a different case set than the incident records.
Voordat u begint
- Have you fixed the headcount base for the period, so the coverage percentage is calculated against the right group of workers?
- For deaths linked to work incidents or work-related illness, have you agreed which cases are included and which reporting period they sit in?
- Before counting injuries, have you settled what counts as a work accident in your organisation and whether the tally covers the full period you are reporting on?
- If you are using an injury rate, have you confirmed the hours base and the calculation method so the figure is built on the same work-hours measure throughout?
- For work-related illness cases, have you agreed the definition and source of the count, so the number can be traced back to a clear record?
- Have you decided how to total time away from work after incidents or illness, and whether the days are taken from a consistent internal source?
Hoe u dit voorbereidt
De gegevens opvragen
Request the health and safety incident data
Vertaal de disclosure naar een interne bedrijfsvraag — en pas die daarna aan op het taalgebruik van uw organisatie.
What are the period-end health and safety figures we need to report for our own workforce and work activities?
Use your organisation’s own terms first, then map them to the reporting labels. For example, ask for your incident log, case register, absence records and hours worked data in the language your teams already use, rather than using framework wording in the request.
Zwak verzoek
Please provide the ESRS S1:S1-13 health and safety metrics for the reporting period, including coverage, fatalities, accidents, accident rate, illness cases and lost days.
Waarom dit misgaat: It uses framework language only, does not say which internal records to pull, and leaves the owner guessing about the population, source system, counting basis and exclusions. That makes it harder to return a usable, auditable pack.
Beter verzoek
Please send the latest figures from your incident log, case register and absence records for [period] and [boundary]: fatal work-related events, accident cases, accident rate per 1m hours, work-related illness cases, lost days, and the coverage % for the group you track. Include the source file, the population covered, the counting method, the hours-worked basis, and any exclusions so we can map your terms to the reporting labels.
Sjabloon voor een formele e-mail
Subject: Request for health and safety data for [reporting period] Hi [name/team], I’m pulling together the health and safety figures for [reporting period] and need your latest data for [entity / site / business unit]. Please send, in your own working format if easier: - the count of fatal events linked to work activities, including any cases tied to injury or illness; - the number of accident cases; - the accident rate calculated per one million hours worked, or the inputs needed to calculate it; - the number of work-related illness cases; - the number of lost days linked to those cases; - the coverage percentage for the population included in your tracking. Please also include: - the period covered; - the population and boundary used; - the source system or file; - the counting method; - any exclusions or special cases; - the person who prepared the data and the date it was last updated. If you already have a report, export or dashboard extract, that is fine. Please attach the file or share the link and note any assumptions. Thanks, [preparer name]
Korte versie voor Teams / Slack
Hi [name] — could you send the latest H&S figures for [period] for [site/business unit]? I need: fatal work-related events, accident count, accident rate per 1m hours, illness cases, lost days, and the coverage % for the group you track. Please include the source file/system, boundary, counting method, and any exclusions. A dashboard export is fine. Thanks.
Sectorvoorbeelden
Manufacturing
Context. Multiple plants with shop-floor incidents, contractor activity and shift-based hours tracking.
Aangepast verzoek. Please send the latest plant H&S extract for [period] covering employees and contractors at [site(s)]. Include fatal work-related events, accident cases, accident rate per 1m hours, work-related illness cases, lost days, and the coverage % for the population in your plant dashboard. Please add the incident log export, hours worked basis from roster/timekeeping, and any exclusions such as off-site travel or legacy cases.
Voorbeeldantwoord. Attached: plant dashboard export, incident log extract, roster hours file, and a note confirming the site boundary, the worker groups included, and the counting rules used for accidents, illness cases and lost days.
Financial services
Context. Office-based workforce with occupational health cases, travel-related incidents and central HR / H&S reporting.
Aangepast verzoek. Please send the latest workplace safety and occupational health figures for [period] across [entity / office locations]. Include fatal work-related events, accident cases, accident rate per 1m hours, work-related illness cases, lost days, and the coverage % for the population in your central tracker. Please include the tracker export, the hours worked basis used for office staff, and any exclusions such as commuting or non-work-related medical absences.
Voorbeeldantwoord. Attached: central H&S tracker export, occupational health case summary, payroll hours basis note, and a short memo confirming the office boundary, the worker groups included, and the exclusions applied.
Stel uw disclosure op
Notities die gegevens tot een disclosure maken
LRA-trainingssjablonen — pas ze aan op uw organisatie en controleer de officiële bron vóór goedkeuring.
Methodenotitie
Explain how the organisation defined the workforce population covered by the figures, how it counted deaths, accidents, illness cases and lost days, and how it calculated the accident rate per million hours.
Contextnotitie
Set out what the figures say about the reach of the reporting population and the level of harm experienced in the period, including whether the numbers point to isolated events or a broader pattern.
Toelichting op schommelingen
If any figure moved materially, describe the main operational or reporting reasons for the change, such as a shift in workforce coverage, a change in incident frequency, or a different mix of accidents and illness cases.
Vermelding in de inhoudsindex
S1-13 Health & Safety — [location / page] / [notes]Downloadcentrum
Hulpmiddelen en formulieren voor de voorbereiding
Download voorbereidingstools voor S1-13 gedurende 24 uur met gratis toegang na e-mailverificatie. Links naar bronrapporten blijven openbaar.
Controleren
Controleer bij elke bewering het bewijs
We included non-staff cases in the accident and fatality figures where they arose within the organisation’s own labour force.
Risico An assurer will test whether the boundary really captures non-employees and whether those cases were counted consistently rather than omitted or double-counted.
Te controleren bewijs Incident logs, investigation files, workforce boundary notes, consolidation rules, and the working paper showing how non-staff cases were identified and added to the totals.
We split the accident and fatality figures into separate lines for staff and non-staff so the two groups can be read apart.
Risico An assurer will check whether the split is genuine, whether the categories are applied consistently, and whether the totals reconcile to the underlying incident records.
Te controleren bewijs The reporting template, source incident register, classification guidance, reconciliation to the final table, and any review notes confirming the split between the two groups.
For the accident-rate calculation, we used standard hours that reflect paid leave and documented how those hours were estimated.
Risico An assurer will probe whether the hours basis is reasonable, whether leave was treated consistently, and whether the estimation method could distort the rate.
Te controleren bewijs Payroll or timekeeping extracts, the hours-estimation methodology, assumptions for leave, calculation sheets, and sign-off showing the basis used for the denominator.
We reported both the count and the rate for recordable accidents affecting our own workforce during the period.
Risico An assurer will test whether the numerator and denominator are complete, whether the rate maths is correct, and whether the period boundary was applied properly.
Te controleren bewijs Accident register, period cut-off checks, calculation workbook, source data extracts, and a review trail showing how the count and rate were derived.
We disclosed the number of calendar days lost by employees because of recordable accidents and recordable ill-health cases.
Risico An assurer will check whether days lost were counted on a calendar basis, whether only employee cases were included, and whether the totals tie back to case records.
Te controleren bewijs Case files, absence records, return-to-work records, day-count methodology, and a reconciliation from individual cases to the published total.
We counted employee cases of recordable work-related ill health for the reporting period and used the case register as the source.
Risico An assurer will probe whether the health cases meet the internal recording rule used, whether duplicates were removed, and whether the period coverage is complete.
Te controleren bewijs Occupational health records, case classification notes, the incident or health register, duplicate-check evidence, and the final tally working paper.
Voor te bereiden bewijsdossier
Veelvoorkomende hiaten in de rapportage
- A percentage is stated without the underlying counts (numerator and denominator).
- The denominator — what the figure is a share of — is not explained.
- Partial scope is reported as if it were complete coverage.
- One-off activities are counted as if they were ongoing programmes.
- Boundary or period changes that move the figure are not flagged.
- Exclusions from the reported scope are not listed or explained.
Waar concepten misgaan
Fouten om te vermijden en waar een oordeel nodig is
De linkerkolom toont wat opstellers fout doen bij het verzamelen; de rechter waar u een oordeel moet vellen en toelichten.
Fouten om te vermijden
- Wrong ownerThe request goes to a manager who does not hold the incident logs, so the team chases the wrong person instead of the operational owner who keeps the records.
- Framework language onlyThe ask is written in reporting jargon, so site teams cannot match it to their own injury, absence, or case-tracking terms.
- Unclear boundaryThe data pull does not state which sites, workers, or business units are in scope, so different teams count different populations.
- Wrong period basisThe team mixes events from different reporting windows, so the figures do not line up with the same time period.
- Mixed counting methodOne source counts cases, another counts people or days, and the numbers are merged without separating the basis used for each measure.
- Source labels lostOriginal incident codes, case notes, or system tags are stripped out during extraction, making it hard to trace each figure back to the source record.
- Populations mergedEmployee, contractor, and other worker records are rolled together even where they should be kept separate for the data pull.
- No evidence trailThe extract is saved without the supporting file names, timestamps, or reviewer notes, so no one can show how the number was built.
- No sign-off recordThe final dataset is used without a named reviewer confirming it, so there is no clear trail of who checked the figures before reporting.
Oordeel vereist
- Set the reporting boundary after buyouts and disposalsUse the same cut-off rule across the group for new and sold businesses, explain which sites or teams were added or removed, and note any effect on the headcount base, incident totals and hours used for the coverage figure.
- Choose one working definition where local rules differIf countries or business units record injuries, illness or lost time differently, pick one group-wide method for the report, describe the local differences, and say how you converted the source records into one consistent set of figures.
- Decide how to treat people close to the boundaryState whether you include contractors, agency staff, interns, temporary workers or other near-boundary groups in the safety data, and explain the rule used so readers can see who sits inside the count and who does not.
- Fix the timing rule for when an event enters the yearExplain whether you count an accident, illness or lost day when it happens, when it is reported, or when it is confirmed, and keep that timing rule consistent across all measures in the disclosure.
- Separate measured figures from estimatesWhere records are incomplete, say which numbers come from direct logs and which are estimated or extrapolated, describe the method used to fill gaps, and identify any material assumptions that could move the totals.
- Be clear on how you calculate the rate per hours workedDisclose the hours base used for the rate, including whether it covers only the people in scope or a broader workforce pool, and explain any adjustments made for part-year service, overtime or missing time records.
- Explain how you handle privacy limits in small teamsIf a site, team or country is so small that naming the underlying cases could identify people, aggregate the figures to a higher level, say where that was done, and keep the method consistent from year to year.
- State your rounding rule and keep it stableTell readers whether you round each line item before or after totals are built, what precision you use for counts and rates, and whether any rounding could cause small differences between component figures and the published total.
- Clarify how you treat mixed-source illness and fatality recordsIf one case is recorded in more than one system or may involve both an accident and a health condition, explain the rule used to avoid double counting and show how you decided which category the case sits in.
Voorbeelden
Hoe het op de pagina leest
Synthetisch, geschreven door LRA — niet afkomstig uit een bedrijfsrapport en geen tekst uit een standaard.
we report the share of our workforce covered by the figures below, alongside work-related deaths, injury events, injury frequency, illness cases and days lost. The numbers are internally consistent and shown for a single reporting period.
Illustrative workforce health and safety summary (people / cases / days / %)
| Measure | Women | Men |
|---|---|---|
| People covered by the reporting scope | 4200 | 5800 |
| Deaths from work-related causes | 1 | 2 |
| Injury events | 48 | 72 |
| Illness cases | 6 | 9 |
| Days lost | 310 | 490 |
Use this as a model for a concise quantitative disclosure that brings together coverage and the main health-and-safety outcomes for the period.
we set out the proportion of our people included in the data, then the period’s fatal outcomes, injuries, injury rate, sickness cases and time lost. All figures are internally consistent and intended purely for training.
Illustrative workforce health and safety summary (people / cases / days / %)
| Measure | Direct employees | Agency workers |
|---|---|---|
| People covered by the reporting scope | 3600 | 1400 |
| Deaths from work-related causes | 0 | 1 |
| Injury events | 35 | 15 |
| Illness cases | 4 | 2 |
| Days lost | 220 | 95 |
Use this as a second model with a different sector and a different mix of figures, while still covering the same required datapoints.
Kwaliteitsladder
- Basis
I report a 92% workforce coverage rate, with 3 work-related deaths, 18 accidents, 2.4 cases per million hours, 5 illness cases and 120 lost days.
- Beter
I report that our 92% coverage figure relates to the people included in our health and safety tracking, and for that group we recorded 3 work-related deaths, 18 accidents, 2.4 cases per million hours, 5 illness cases and 120 lost days.
- Best
I report that, for the 92% of our workforce covered by our health and safety tracking this year, we recorded 3 work-related deaths, 18 accidents, 2.4 cases per million hours, 5 illness cases and 120 lost days, and the higher lost-day total mainly reflects two longer recovery periods after serious incidents.
Toets uw begrip
Scenario’s om door te werken
Your group has three subsidiaries and one joint operation. Two subsidiaries keep full incident logs, while the joint operation only shares quarterly summaries, so you can see the total headcount but not every worker covered by the same safety tracking method.
A contractor working on your site dies after a workplace accident, and later in the year an employee dies from a work-related illness. The draft report team is unsure whether to separate these events or combine them in one line.
During the year, one site records 14 lost-time accidents and another records 6 more. The safety team also has the total hours worked and can calculate a rate, but the draft narrative only mentions the accident count because the rate looks small.
Your occupational health provider sends a year-end file showing 9 work-related illness cases, but two of those cases were first logged by HR and one was later reclassified as not work-related. The draft table still shows 9 because that was the first number received.
Vraag de AI-assistent van de Knowledge Hub naar deze disclosure
Ontvang praktische antwoorden die passen bij uw rapportagecontext.
Controleer je tekst
Plak één of twee alinea’s. Het fragment wordt alleen voor deze controle gebruikt en niet in uw gesprek opgeslagen.
De vergelijking gebruikt voorbeelden op deze kaart, niet hun prevalentie in het rapportcorpus.
Advies, geen assurance
Verwijzingen naar het raamwerk
Relevante ESRS-vereisten en verwante disclosures
ESRS
S1-13
binnen ESRS S1: Own Workforce
Guides that settle this question
Gerelateerd & verkennen
Meer in ESRS S1 →Volledige catalogus bekijken →Zoeken in alle disclosures →
FAQ
Vragen die deze pagina beantwoordt
Use the page’s step-by-step preparation section to work through the disclosure in order, then check the datapoints, evidence pack and common mistakes before drafting. It is designed as practitioner guidance, so you can use it to organise the work rather than treat it as an official source.
The page says to prepare six datapoints: reporting coverage share, work-related deaths, work accident count, accident frequency rate, work illness cases and lost work days. Start by confirming which of these you can evidence and where each figure will come from.
The page flags reporting coverage share as a datapoint to prepare, but it does not give a formal definition or calculation method. Use the page’s preparation steps and evidence pack to make sure your chosen scope and calculation are documented and consistent.
The page does not assign roles, so ownership needs to be set internally. In practice, this usually means agreeing who gathers the workforce data, who checks the evidence, and who signs off the draft before assurance.
The page includes an evidence pack with five items to support assurance readiness, plus six assurance claims to verify. Use those as the basis for your file so each reported figure can be traced back to source records and review checks.
The page has a section on common reporting gaps and mistakes, so it is useful for a pre-submission check. Use it to spot missing data, weak evidence, unclear scope or inconsistencies before you finalise the disclosure.
The Download Centre includes a Prep & Assurance workbook in .xlsx format and a printable Library Card in .pdf. Use the workbook to organise the datapoints, evidence and assurance checks, then use the page’s draft-output section to turn that into a disclosure.
Yes, as a structure only. The page says the example disclosures are synthetic and illustrative, so you can use them to see how the data table and narrative might look, but not as a source of real figures or requirements.
The page suggests visualisation ideas, narrative starters and a content-index line for the draft output. That gives you a practical starting point for turning the prepared data into a readable disclosure.
The page includes a 'From company reports' table that links to real published reports where the topic is disclosed. Use it to see how others present similar information, while still building your own disclosure from the page’s guidance and your own evidence.
Meer vragen waarbij deze pagina helpt