SOP templatesHealth & Safety

Workplace Incident Reporting SOP Template

A procedure for reporting, investigating and closing out workplace injuries and near misses, for use by any employee, supervisor or safety team.

FreeNo sign-upWord, PDF, Excel & CSV
Ilia PirozhenkoReviewed by Ilia Pirozhenko, Founder, Perfect WikiUpdated September 15, 202612 steps4 roles3 min read
Standard operating procedureSOP-SAF-001 ยท Rev 1.0
Owner
Safety Officer
Effective date
September 15, 2026
Review cycle
Every 12 months

1.Purpose

To make sure every workplace injury and near miss is reported promptly, investigated for root cause, and followed up with corrective action to prevent recurrence.

2.Scope

Applies to all employees, contractors and visitors, covering injuries, illnesses, near misses and property damage events occurring on company premises or during work activities.

Definitions

Near miss
An event that could have caused injury, illness or damage but did not, often due to timing or luck rather than a control working as intended.
Root cause
The underlying reason an incident occurred, as opposed to the immediate or surface-level cause.
Corrective action
A change made to eliminate or reduce the root cause of an incident so it does not happen again.

3.Responsibilities

Employee
Reports any incident or near miss immediately, cooperates with the investigation and follows interim controls put in place.
Supervisor
Secures the scene, completes the initial report and supports the investigation for incidents in their area.
Safety Officer
Investigates root cause for serious incidents, tracks corrective actions and maintains the incident register.
Department Manager
Reviews incident trends for their department and approves resources for corrective actions.

RACI matrix

ActivityEmployeeSupervisorSafety OfficerDepartment Manager
Report the incident immediatelyR/ACII
Secure the scene and preserve evidenceRR/ACI
Investigate root causeCRR/AI
Assign and implement corrective actionsIRAC
Report to a regulatory authority if requiredIIR/AC

R = Responsible, A = Accountable, C = Consulted, I = Informed

4.Materials and PPE

Materials, tools and systems

  • โ†’Incident report form
  • โ†’Incident register
  • โ†’Camera or phone for scene photos
  • โ†’Root cause investigation template
  • โ†’Corrective action tracking log

5.Procedure

  1. 5.1

    Ensure immediate safety

    Employee

    Get first aid or emergency medical help for anyone injured, and remove people from further danger before doing anything else.

    Warning: Never delay calling for medical help in order to document the scene first.

  2. 5.2

    Secure the area if a hazard remains

    Supervisor

    If a hazard that caused the incident is still present, cordon off the area or shut down the equipment involved so no one else is exposed.

  3. 5.3

    Notify the supervisor immediately

    Employee

    Report the incident or near miss to your supervisor as soon as it is safe to do so, describing what happened and who was involved.

    Checkpoint: The supervisor is notified the same day the incident or near miss occurs.

  4. 5.4

    Preserve the scene

    Supervisor

    Leave the scene undisturbed where possible and take photos of the area, equipment and any damage before cleanup begins.

  5. 5.5

    Complete the incident report form

    Supervisor

    Fill out the incident report form with the facts: date, time, location, people involved, description of what happened and any immediate actions taken.

  6. 5.6

    Review the initial report

    Safety Officer

    Review the completed report for completeness and decide whether the severity warrants a full root cause investigation.

  7. 5.7

    Investigate the root cause

    Safety Officer

    For incidents meeting the investigation threshold, interview witnesses, review conditions and equipment, and identify the underlying root cause rather than stopping at the immediate cause.

    Checkpoint: The investigation identifies a root cause, not just the immediate action that triggered the incident.

  8. 5.8

    Identify corrective actions

    Safety Officer

    Based on the root cause, identify corrective actions using the hierarchy of controls, favoring elimination or engineering changes over relying on behavior alone.

  9. 5.9

    Assign and implement actions

    Department Manager

    Assign each corrective action an owner and due date, and track implementation until every action is verified complete.

  10. 5.10

    Report to a regulatory authority if required

    Safety Officer

    Determine whether the incident meets the criteria for reporting to a regulatory authority, and submit the report within the timeframe required by local regulations.

  11. 5.11

    Communicate lessons learned

    Supervisor

    Share relevant findings and new controls with the affected team so similar tasks elsewhere benefit from the lessons learned.

  12. 5.12

    Log and review at the safety meeting

    Safety Officer

    Log the incident in the incident register and review incident trends, including near misses, at the regular safety meeting.

6.Quality checks

  • โ†’Every reported incident has a completed report on file within 24 hours.
  • โ†’Serious incidents show a documented root cause, not just an immediate cause.
  • โ†’Corrective actions are tracked with an owner and due date until verified closed.
  • โ†’Near misses are logged with the same rigor as incidents that caused injury.

7.Records

  • โ†’Incident report forms
  • โ†’Incident register
  • โ†’Root cause investigation reports
  • โ†’Corrective action tracking log

8.KPIs

  • โ†’Number of incidents and near misses reported per month
  • โ†’Percentage of corrective actions closed by their due date
  • โ†’Average time from incident to completed investigation

9.Common mistakes

  • โ†’Only reporting incidents that caused an injury and skipping near misses.
  • โ†’Stopping the investigation at the immediate cause instead of the root cause.
  • โ†’Assigning a corrective action with no owner or due date.
  • โ†’Cleaning up the scene before it has been documented and photographed.

10.Revision history

RevisionDateDescriptionReviewed by
1.0September 15, 2026Initial releaseIlia Pirozhenko

This is a template. Adapt it to your organization, equipment and local regulations before use.

Ask this SOP

Nobody opens a PDF in the middle of a task. They ask.

Add this SOP to Perfect Wiki and your team gets answers in the chat app they already use, with a link to the exact step. Ask from ChatGPT, Claude or Copilot too.

Perfect Wiki AIExample answer

A coworker slipped on a wet floor but wasn't hurt, do I still need to report it?

Yes, report it as a near miss to your supervisor the same day, since near misses reveal hazards before someone gets hurt and get the same follow-up as an incident that caused injury.Source: step 5.3 ยท Notify the supervisor immediately
Ask your own question about this SOPโ€ฆSign up to keep asking
Word file vs Perfect Wiki

A downloaded SOP starts going out of date the day you save it.

Screen recorders like Scribe and Tango capture clicks. Perfect Wiki holds the whole procedure, including your recorded guides, and answers questions about it.

Word or PDFPerfect Wiki
Finding itDig through folders and email threadsAsk in Teams, Slack, kChat or Mattermost
Keeping it currentEmail a new version and hopeEdit once with AI, everyone sees the update
Everything in one placeText and imagesEmbed Scribe and Tango guides, SharePoint files and videos
Who can change itAnyone with the fileEditors you choose, everyone else reads
Common questions

Frequently asked questions

Didn't find what you're looking for? Contact our support โ†’

Your SOP library

Keep every SOP where your team can ask it.

Perfect Wiki is the knowledge base for Microsoft Teams, Slack, kChat and Mattermost. Store your SOPs, embed your Scribe and Tango guides, and let AI answer questions with a link to the right step.

No credit cardSetup in under 10 minutesCancel anytime