Skip to content

Site safety

Safety measures: read the counts, definitions and underlying work

By Review.LivePublished 3 min readHow we write

An owner with three crews reports no lost-time injuries and asks why a superintendent still raises concerns. The corrective-action list contains overdue items, while some crews have not submitted their reporting records. The weekly summary turns all missing entries into zero and shows a reassuring picture.

A hand holding a pen over a blue clipboard, ready to fill in a checklist.
Photo: Phil Hearing on Unsplash

Read a number with its definition, coverage and supporting work. Program guidance distinguishes past-event measures from measures of prevention activities, and calls for examining whether arrangements are working. Neither type alone certifies safety. Zero recorded injuries can coexist with unresolved hazards; missing information is a gap, not another zero.

Turn the concern into a workable site routine

  1. Write what each number actually means. Define the event or action counted, the reporting period, the included crews and the source record. Distinguish recorded injuries, received concerns and verified corrections. Do not combine different definitions under one heading because they fit the same chart. Keep the required regulatory records and definitions in their own applicable process; your management sheet is not a substitute.
  2. Choose measures linked to current decisions. Select a manageable set of activity measures alongside the relevant event information. Examples could include overdue assessed actions, completed planned reviews or the response to received concerns. State what each can and cannot show. Counting a briefing confirms that it happened, not that everyone understood the task; closing an action needs appropriate verification of the condition.
  3. Show the denominator and missing coverage. Give the underlying counts when presenting a percentage and identify the population actually reviewed. Mark an absent record as missing and assign its follow-up. For a changing project, note differences in crews or work rather than treating every week as comparable. Avoid interpreting a small change as proof of a trend without examining the records and circumstances.
  4. Ask about severity, conditions and response. Read the action description and unresolved exposure alongside the count. A single serious protection gap can require urgent attention even when the overall total is low. Check whether a rise in reports reflects new hazards, improved reporting, changed coverage or several factors. The direction of the graph cannot decide which explanation is supported.
  5. Assign the decision and return next week. Use the sheet to identify the responsible response, missing evidence and next review. Confirm what was actually corrected or clarified. Retain prior definitions and record deliberate changes so comparisons remain understandable. The objective is a received decision and verified follow-through, not a permanently green scorecard or a reward for whichever crew produces the lowest count.

Common mistakes

  • Changing missing records into zero.
  • Comparing percentages with different definitions or coverage.
  • Closing serious conditions because an overall count looks small.

Checklist

Make the weekly picture interpretable

  • Count definitions and source records visible.
  • Selected measures linked to actual decisions.
  • Denominators and missing coverage identified.
  • Severity, conditions and response reviewed.
  • Owned decisions and follow-through returned.

Check your understanding

The contractor recorded no injuries and more near misses this month. Does that prove improvement?

Show the answer
Examine coverage, actual hazards, reporting conditions and the response. Those counts describe recorded events; they do not establish effective controls or explain a change without supporting evidence.

Sources

  1. Program evaluation and improvement — measures, participation and effectivenessOccupational Safety and Health Administration · United States educational program guidance; not Canadian regulatory reporting definitions · accessed