How Do I Describe the Actions My Company Takes to Address Workplace Incidents?

What is this section actually asking for?

This part of your ESG report asks you to describe how your company handles workplace incidents, including the process for reporting them, responding immediately, investigating what happened, taking corrective action, and supporting anyone affected. It also asks how you learn from incidents to prevent them from happening again.

Importantly, this is about your process, not necessarily a detailed narrative of every single incident that has occurred. Whether your company had one incident this year or none at all, you can still describe a credible incident management approach. The difference is simply how much specific incident detail you include alongside it.

‍

Start with your process, not the incident count

Before describing any specific incidents, it helps to explain the basic mechanics of how incidents are handled at your company:

• Reporting: How employees report an incident or near-miss, and to whom.
• Immediate response: What happens right after something occurs, such as first aid, securing an area, or contacting relevant support.
• Investigation: How you find out what happened and why.
• Corrective action: What changes as a result.
• Support for affected employees: What happens for the person or people involved.

For a small company, this does not need to look like a formal safety department. A credible description might be as simple as:

"Employees report any incident or near-miss directly to their manager or the office lead, who documents what happened and, where relevant, discusses corrective steps with the team."

This is a legitimate, honest process description, even without dedicated safety staff.

‍

If you've had confirmed incidents, describe them clearly

Where your company has had a genuine incident worth reporting, a consistent structure makes the description far easier to follow and more credible than a general narrative. Useful elements to include:

• What happened: A brief, factual description of the incident.
• Immediate response: What was done right away.
• Investigation: How you looked into what caused it.
• Root cause: What actually led to the incident, distinguishing the immediate trigger from any deeper contributing factors.
• Corrective actions: Specific changes made as a result, ideally noting whether they were quick fixes or longer-term improvements.
• Support provided: What was done for anyone affected.
• Follow-up: How you checked the corrective action actually worked, and whether the issue recurred.

This structure works whether the incident is a minor slip, an ergonomic issue like repetitive strain, or a more serious near-miss. The level of detail should be proportionate to the seriousness and learning value of the incident. A minor, one-off issue does not need the same depth of investigation narrative as something that revealed a systemic gap.

‍

Look for the root cause, not just the immediate trigger

One of the most valuable things you can show in this section is that your company looks beyond the immediate cause of an incident to understand what allowed it to happen. It often helps to separate:

1. The immediate cause: The direct trigger, such as a wet floor sign being moved.
2. Contributing factors: Conditions that made the incident more likely, like a busy time of day or only having one sign available.
3. Systemic issues: Deeper gaps in process or communication that, if fixed, would prevent similar incidents more broadly, such as having no clear protocol for maintaining signage during cleaning.

Describing all three levels, where relevant, shows that corrective action addresses the real problem, not just the surface symptom. A response that only fixes the immediate trigger without considering why the conditions existed in the first place tends to look reactive rather than genuinely preventive.

‍

Describe corrective actions with a sense of timeline

It is useful to distinguish between actions taken immediately, in the following weeks, and over a longer period. This shows a company responding proportionately, addressing urgent risk right away, while also working on the underlying issue over time. For example:

• Immediate: Securing a hazard, providing first aid, or implementing temporary fixes.
• Short-term: Process or equipment changes completed within weeks.
• Longer-term: Training programmes, policy updates, or broader operational reviews.

Not every incident needs all three tiers. A minor issue might only need an immediate fix, while something that reveals a systemic gap might justify a longer-term response.

‍

Support for affected employees matters

Wherever an incident has affected an employee, briefly describing the support provided (such as medical costs covered, time off, adjusted duties, or ongoing check-ins) shows that your company treats incidents as something that affects real people, not just a compliance exercise. This does not need to be extensive for a minor issue, but it should be proportionate and genuine.

‍

If you have no incidents to report, say so plainly

It is entirely possible, and often the case for a small company, that there were no incidents worth reporting in the period. In that case, the strongest answer describes your process honestly and notes that no incidents occurred, rather than inventing a case study to fill space. For example:

"No workplace incidents were reported during the reporting period. Employees are able to report concerns directly to management, and any incident would be investigated using the process described above."

‍

Summarise the bigger picture if you have multiple incidents

If your company tracks incidents at a slightly larger scale, it can help to briefly summarise patterns across the period. For example, you might note common contributing factors across several incidents, or overall figures like total incidents and any lost time.

This is not necessary for every company, but where it is genuinely useful (such as if a few incidents share a common root cause), it demonstrates a company learning at a broader level, rather than just fixing individual problems in isolation.

‍

Common mistakes to avoid

• Describing only the immediate cause: Missing contributing or systemic factors makes corrective action look superficial.
• Listing actions without a timeline: It is harder to judge whether a response was proportionate without knowing what happened immediately versus over time.
• Forgetting support for affected employees: Corrective actions alone do not show that the company cared about the people involved.
• Inventing incidents or exaggerating severity: If there is genuinely little to report, an honest, brief statement is far better than a fabricated narrative.
• Overstating formality for a small company: Describing an elaborate investigation process that does not actually exist creates a mismatch. Describe what genuinely happens, even if it is modest.

‍

How Wardn helps

Wardn provides a structured template with example wording to help you describe your incident management process consistently, whether you are reporting a specific incident or explaining your general approach when none occurred. The same structure can be reused each year, making it straightforward to compare incident patterns over time and show how your process has developed.

‍

Frequently asked questions

What if our company had no workplace incidents this year?

That is a good outcome, and the honest answer. Describe your incident reporting and response process, and simply note that no incidents were recorded during the period.

How much detail should we give for a minor incident?

Enough to show what happened, what was done immediately, and whether any change resulted. A minor, one-off issue does not need the same depth as something that revealed a systemic problem.

What's the difference between an immediate cause and a systemic issue?

The immediate cause is the direct trigger of the incident (like a misplaced warning sign). Systemic issues are deeper gaps in process or communication that allowed the conditions for the incident to exist in the first place (like having no clear protocol for signage during cleaning). Addressing both shows a more thorough response.

Do we need a formal investigation process to describe this section well?

No. For a small company, a straightforward description of who is told, how it is looked into, and what changes as a result is a credible process, even without a dedicated safety team.

Should we include figures like incident rates if we're a small company?

Only if it is genuinely useful and trackable. Small companies often do not have enough incidents for a meaningful rate calculation, and a simple factual account of what happened (or did not) is a perfectly adequate alternative.

‍