How are municipal near misses documented?

With a short, low-friction report capturing what happened, where, when and what could have resulted, followed by review and any corrective action. The record is kept separate from injury incidents because its purpose is early warning, and reporting collapses if it is treated as a disciplinary process.

What should a public works tailboard talk include?

The specific job and location, the hazards present that day, the controls in place including traffic control and PPE, the equipment being used, emergency arrangements, and a record of worker questions and attendance.

Does incident software replace an employer's reporting obligations?

No. Notice, reporting and investigation obligations under Ontario's Occupational Health and Safety Act and its regulations rest with the employer and constructor. Software helps you capture, route and retain information; it does not discharge a legal duty.

Public works resource

Public Works Incident, Near-Miss and Safety Documentation Guide

How are public works incidents and near misses documented?

In short

Incident and near-miss documentation is the practice of recording safety events in municipal operations — injuries, equipment damage, property damage, hazards and events that could have caused harm but did not — along with the immediate response, the follow-up investigation and any corrective action taken. In Ontario, certain workplace events also trigger statutory notice and reporting duties under the Occupational Health and Safety Act, which software does not satisfy on an employer's behalf.

Legal duties come first, records second

Ontario employers and constructors have notice and reporting obligations under the Occupational Health and Safety Act for certain events, including critical injuries and fatalities, and duties involving the joint health and safety committee or health and safety representative. Those obligations are set by the Act and its regulations, and by your municipality's policies — not by any software product.

Treat everything below as operational practice that sits alongside those duties. If there is any question about whether an event is reportable, follow your municipal procedure and escalate immediately rather than waiting for the paperwork.

Four things worth recording separately

Record type	What it captures	Why it is kept separate
Incident	An event that caused injury, damage or loss	Often triggers statutory duties and formal investigation
Near miss	An event that could have caused harm but did not	The cheapest available warning; suppressed if treated like discipline
Hazard report	A condition, not an event	Fixable before anything happens at all
Field observation	Something a worker noticed worth passing on	Keeps the reporting habit alive between events

Why near misses go unreported

Near-miss reporting fails for predictable reasons: the form is long, the reporter fears blame, nothing visibly happens afterwards, or the crew believes management already knows. All four are fixable, and only one of them is about software.

The single strongest driver of near-miss reporting is visible follow-through. A crew that sees a hazard they reported get fixed reports again. One that never hears back stops within a month.

A workable documentation flow

1.Report. Capture it quickly — who, where, when, what happened, and any immediate danger. Photos where safe.
2.Secure and respond. Address immediate risk, provide first aid or medical attention, and preserve the scene where required.
3.Notify. Follow the municipality's notification procedure, including statutory notices where they apply.
4.Document. Complete the full record while memory is fresh, including conditions, equipment involved and witnesses.
5.Investigate. Establish the sequence and the contributing conditions. Look for the conditions, not just the person.
6.Correct. Assign each corrective action to a named owner with a date.
7.Follow up. Verify the action was implemented and effective, not simply marked done.
8.Close and share. Close the record and pass the lesson to other crews who face the same conditions.

Tailboard and pre-job talks

A tailboard talk is a short pre-job discussion at the work location covering the job, the hazards specific to that site and the controls in place. Its value comes from being specific — a generic talk about slips and trips before a catch basin job on a curve with sightline problems is a formality, not a control.

The job: what is actually being done, and by whom.
The location: sightlines, grades, traffic speed, pedestrians, utilities, confined or below-grade conditions.
The hazards today: weather, ground conditions, adjacent operations.
The controls: traffic control, PPE, spotters, exclusion zones, lockout, permits.
The equipment: what is being used, condition, pinch points, swing radius.
Emergency arrangements: nearest access, how help is called, muster point, exact civic location.
Questions and acknowledgment: worker concerns raised, and who attended.

Corrective actions that actually close

Most safety systems fail at step six, not step one. A corrective action without an owner and a date is a note. Departments that close actions reliably keep them in the same list as operational work, review them at the same meeting, and escalate the overdue ones — because a safety action competing with a work order it cannot be seen next to always loses.

Checklist

Incident and near-miss record checklist

Use it as written or adapt it to your own municipal policy. It is a practical aid, not a compliance guarantee.

Date, time and exact location recorded, including road segment or facility.
People involved, witnesses, and the supervisor notified.
Description written factually, separating observation from conclusion.
Immediate actions taken, including first aid or medical referral.
Statutory and municipal notification requirements considered and documented.
Equipment, materials and conditions involved identified.
Photographs taken where safe and lawful.
Contributing conditions examined, not just individual actions.
Corrective actions assigned to a named owner with a due date.
Verification that each action was implemented and effective.
Lesson shared with crews exposed to the same conditions.

Common mistakes

Treating near-miss reports as performance issues, which ends reporting.
Writing conclusions into the incident description instead of observations.
Assuming the software record satisfies a statutory notice obligation.
Closing corrective actions without verifying effectiveness.
Keeping safety actions in a separate list nobody reads daily.

Frequently asked questions

How are municipal near misses documented?: With a short, low-friction report capturing what happened, where, when and what could have resulted, followed by review and any corrective action. The record is kept separate from injury incidents because its purpose is early warning, and reporting collapses if it is treated as a disciplinary process.
What should a public works tailboard talk include?: The specific job and location, the hazards present that day, the controls in place including traffic control and PPE, the equipment being used, emergency arrangements, and a record of worker questions and attendance.
Does incident software replace an employer's reporting obligations?: No. Notice, reporting and investigation obligations under Ontario's Occupational Health and Safety Act and its regulations rest with the employer and constructor. Software helps you capture, route and retain information; it does not discharge a legal duty.

References and sources

This page is operational guidance for public-works staff. It is not legal advice. Where a regulation is discussed, work from the current consolidated text and your municipality's own policies and legal advice.

Occupational Health and Safety Act, R.S.O. 1990, c. O.1 (including notice and reporting provisions, ss. 51-53)
Primary source for Ontario workplace notice, reporting and investigation duties.
Ontario Ministry of Labour, Immigration, Training and Skills Development — workplace health and safety

Last reviewed against its sources: 2026-08-16. Regulatory material changes; confirm current text before relying on it operationally.