This disclosure asks an organisation to explain how it identifies work-related hazards, assesses the risks they create, and investigates incidents when they happen. In practice, the report should show the approach used to spot hazards, judge their significance, and learn from events so that controls can be improved over time. The emphasis is on the process, not just on having a policy in place.
The practical focus is on whether this approach is applied across the organisation’s activities and locations, rather than only at a few well-managed or flagship sites. A useful explanation would make clear how consistently the organisation covers different operations, contractors or work settings where relevant, and how findings from investigations feed back into prevention and risk management.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.
A quick mental checklist before you prepare this disclosure — tick each as you settle it.
Key datapoints to prepare
How to prepare it
Request the safety process evidence from EHS / Operations
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your organisation’s own names first for safety checks, incident reviews, stop-work routes, near-miss reporting, corrective actions, and management-system reviews; then map those terms to the disclosure wording before sign-off.
Please send anything you have for GRI 403-2 on hazard identification, risk assessment, hierarchy of controls, worker reporting, reprisal protection, stop-work rights, and incident investigation.
Why it fails: It uses framework language only, so the owner has to translate the ask themselves. It also does not say which teams, systems, time period, or internal process names to pull, so the response is likely to be incomplete or inconsistent.
Please send the safety process pack for [period] across [sites/teams], using your own terms for pre-task checks, hazard spotting, risk reviews, stop-work, near-miss reporting, incident reviews, and action close-out. Include the source system, date range, who is authorised to do the checks, how worker reporting is protected, and how findings lead to improvements.
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
Describe the practical steps used to spot hazards, assess risk, investigate incidents and decide follow-up actions, including how the organisation checks the quality of those steps and the capability of the people doing them.
Explain what the disclosed processes mean in practice for workers: how risks are identified and controlled, how concerns can be raised safely, how people can withdraw from unsafe work, and how findings are used to strengthen the safety system.
If the approach changed during the period, note whether that was due to new risks, incident findings, revised controls, or improvements to the safety management process, and explain the effect on the reported arrangements.
Preparation tools & forms
Professional preparation tools for GRI 403-2 — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.
For each claim, check the evidence
Evidence pack to prepare
Common reporting gaps
Mistakes to avoid when collecting the data
Where judgement is often needed
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
*Synthetic illustration only.* We use a mix of planned site inspections, task-based reviews, and checks for unusual or one-off activities to spot dangers and judge risk for both employees and agency staff working under our control. - We apply a stepwise control approach: first trying to remove the hazard, then substituting, isolating, engineering out, changing procedures, and finally relying on training and protective equipment where needed. - The people who run these checks are trained and signed off for the task, and we review the findings to tighten our safety system, update controls, and track whether the changes are working. - Workers can raise unsafe conditions through supervisors, a hotline, or a digital form; they may also stop work if they believe it is unsafe, and our rules prohibit retaliation for either speaking up or stepping away. We also investigate incidents by looking at what happened, what hazards were present, and what fixes are needed, then use the same control hierarchy to decide corrective actions and wider system improvements.
Illustrative only; shows one way a reporter might describe the required processes in plain language.
*Synthetic illustration only.* Our checks cover routine warehouse activity and unusual events such as peak-season overtime, contractor work, equipment breakdowns, and temporary traffic changes, for both our own staff and third-party workers under our day-to-day control. - We identify risks through walk-throughs, job reviews, incident trend analysis, and pre-task assessments, then choose controls in order of preference from removal of the hazard through to last-line safeguards. - We keep the process reliable by using trained assessors, refresher training, and periodic quality reviews, and we feed the results into our safety management cycle so that procedures, training, and controls are updated where needed. - Workers may report hazards through team leads, QR-code reporting, or the safety mailbox, and may leave a task they believe could harm them without penalty; when incidents occur, we investigate the event, reassess the related risks, decide follow-up actions using the same control order, and record any system changes needed.
Illustrative only; shows a second plausible reporter with different wording and operational context.
How companies report GRI 403-2
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A warehouse team uses a new pallet wrapper for the first time, while a contractor is also working in the same loading bay. The safety lead has a routine walk-through checklist, but no separate check for unusual tasks or shared work areas.
After a minor chemical splash, the site manager says the team now uses gloves and eye protection, but the incident note does not show how the fix was chosen or whether the earlier risk review was updated.
A production worker reports a loose guard on a machine, but the supervisor asks them to keep working until the end of the shift. The worker is unsure whether speaking up could affect their overtime allocation next week.
A maintenance contractor and an in-house supervisor both investigate a near miss, but neither has formal training in incident review. The resulting note lists what happened, yet it does not show who checked the quality of the review or whether the reviewers were competent for the task.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
Start with the page’s plain-language explainer and the datapoints to prepare, then follow the step-by-step preparation section to turn your notes into a draft. The page also gives narrative starters, visualisation ideas and a GRI content-index line to help you shape the output.
The page points you to hazard and risk scanning, control selection, process quality checks, safety system learning, reporting channels, anti-retaliation protection, right to stop work, stop-work protection, incident investigation, incident risk review, corrective action choice and system improvement actions. Use those as your collection checklist so you can assemble a complete evidence trail.
Use the page’s step-by-step preparation section to set out what is in scope, how the data will be gathered and how the process is checked for quality. The page is designed to help you document the method clearly enough for assurance review.
The page is aimed at sustainability/ESG managers, HR or data owners, and assurance reviewers, so ownership should sit with the people who can evidence the process and explain the data. Use the workbook to assign tasks and keep the evidence pack aligned to those owners.
The page includes an evidence pack with five items and six assurance claims to verify, each framed around claim, risk and evidence. Build the pack around those items so a reviewer can trace the disclosure back to source material and process checks.
The page lists common reporting gaps and mistakes to watch for, so it is useful as a pre-submission check. Use it to spot missing datapoints, weak process evidence or unclear drafting before you finalise the disclosure.
The Download Centre includes a Prep & Assurance workbook in .xlsx format that is meant to support preparation and assurance readiness. Use it to organise the datapoints, evidence and sign-off steps before drafting the disclosure.
The page includes synthetic illustrative examples, including a quantitative table, to show how a disclosure can be structured. Treat them as format guidance only and make sure any figures in your own draft are internally consistent.
The page says ESRS S1 (Own Workforce) is the closest correspondence, so the same underlying data may be useful across both. Use that as a reuse check, but still review the wording and presentation for the framework you are reporting under.
The draft-output section gives narrative starters and a GRI content-index line, which you can use as a starting point for the report text. Build the narrative from the datapoints and evidence you have already assembled rather than writing it first.
Get your GRI 403-2 tools — free
Your preparation tools are free for LRA Community members and students. Register once (it's free) and your download starts right away — plus the Disclosure Library, templates and the LRA AI-assistant.
You're in — your download is starting
Your file is downloading now. Your Community Cabinet — with the Disclosure Library, templates and the LRA AI-assistant — is ready too.
Open your Cabinet →