What belongs in a useful safety review?

A safety review should help people decide where to focus. Counts are a starting point, but they need dates, context and a route back to the records.

Start with scope

State which schools or sites are included and the reporting period. Separate events during the period from records still open at the review date. Twelve open incidents is a different measure from twelve incidents reported this month.

Review incidents with context

Look at severity, type and location alongside the total. Compare like-for-like periods. If you use a rate, make the denominator clear. A change in near-miss reporting may reflect a change in reporting behaviour, so avoid assuming that a lower count is automatically better.

Follow overdue work

Review the actions that remain outstanding, particularly those linked to more serious findings. Look at the owner, time overdue and reason for delay. Make the next decision clear, rather than reading through a list without assigning follow-up.

Check inspection progress

Compare completed inspections with the work that was scheduled. Identify missed checks, records awaiting review and repeated findings. A completion percentage needs a stated denominator to be useful.

Review risk and controls

Use the organisation's existing scoring method. Distinguish the initial exposure from the exposure remaining after controls. Look at review dates and evidence about whether controls are operating as intended.

Look ahead

Review upcoming document expiries, planned checks and other work due before the next meeting. A current document record is not, by itself, proof that all compliance obligations are satisfied.

Finish with decisions

Record the decision, owner and due date for each agreed action. At the next review, return to those decisions and the supporting evidence.

Use the meeting to make decisions

A review can be short and still be useful. Start with the period and locations, identify the records that need attention, and finish with the decisions the team has made. Keep unresolved questions visible for the next meeting.

For example, an overdue action may be waiting for equipment or a specialist visit. The useful decision is the next step, its owner and the appropriate timing under your procedure. Repeating the overdue count without agreeing that next step adds little to the review.

Work with the CSV checklist

The download contains an area, a review question, a decision, an owner and a due date. Open it in a spreadsheet tool and use one working copy for the review. Add enough context to make each decision understandable when the team returns to it.

• Confirm the locations and reporting period before comparing figures.
• Mark missing or stale information so it does not disappear into a total.
• Record the decision and the person accountable for the next step.
• Return to the previous review's decisions before starting a new list.

The checklist helps organise a discussion. Use your organisation's existing assessment methods and procedures for the decisions themselves.

If follow-up is the gap, read from inspection finding to verified correction. See the reporting context in CerthixED and CerthixCO.