Chapter 05
Safety meetings with evidence
How to run a weekly safety meeting that opens on the evidence, tracks action across weeks, and finishes inside thirty minutes.
01
The weekly evidence-led pack
A weekly safety meeting that runs on the captured base looks different from one that runs on memory. The pack opens with the findings of the week, classified, severity-graded, and tagged. Each finding has a clip, a 360 walk frame, or a permit reference attached. The owner is named. The clock is visible. The meeting works through the list as a list, not as a series of stories. A meeting attendee who arrives without having read the pack can pick it up in the first two minutes because the structure is consistent week to week. The pack also includes the metrics that matter — open observations, observations that breached their clock, near-miss volume, closeout rate — and a brief patterns section drawn from the captured base. The discipline of producing the pack on the same template each week, by the same person, is a small commitment that delivers an outsized return: the meeting is shorter, the decisions are better, and the record of the meeting becomes part of the audit trail.
02
Tracking action across weeks
The meeting also tracks action across weeks, which is where most safety meetings quietly fail. Findings raised in previous weeks reappear in the pack with their current status: open, in progress, closed with evidence, or breached. Open observations that have aged appear with their escalation. Closed observations come off the active list but stay searchable. The team can see the system working — the loops that closed, the loops that did not, the patterns that recurred. That visibility is what makes the routine sustainable rather than performative. It also gives the project director something to read between meetings: the gap between findings raised and findings closed is the leading indicator they need, and it is more telling than any single near-miss number. The meeting that does not track across weeks rebuilds itself from scratch every Tuesday and never compounds.
03
Stand-downs and serious findings
Some findings warrant a stand-down. A pattern of edge protection failures during a slab pour. A lifting incident with major potential. A permit-to-work breach on a hot works activity. A stand-down is an explicit pause on a class of activity until the controls are visibly back in place. The safety meeting is where the stand-down is initiated, where its scope is recorded, and where its release criteria are written down. The captured base supports the stand-down by showing the activities affected, by letting the project director communicate the scope to the supply chain in plain terms, and by capturing the verification evidence that lets the activity restart. A stand-down without written release criteria becomes either symbolic or open-ended. With them, it becomes a credible intervention.
04
The half-hour meeting and the failure modes
A safety meeting that opens on evidence tends to run shorter, not longer. The disagreements that previously consumed twenty minutes resolve in two when the captured view is on the screen. The half-hour meeting becomes the standard. The time saved goes back into actually closing the actions, which is where safety changes. The recurring failure modes are: the verbal-summary meeting that produces no record, the meeting that does not return to last week, the meeting that lists findings without owners and clocks, and the meeting that becomes a status theatre for the client. The discipline is the reverse of all four. The pack is written, the previous week is reopened, every line has an owner and a clock, and the meeting is for the team rather than for an audience.
Practice
01. Build a template for the weekly safety meeting pack. Cover findings of the week, open observations from previous weeks, breached clocks, near-miss patterns, and stand-down status. Limit the template to one or two pages.
Look for: A template with five named sections fitting on a single side of A4 (or two if necessary). Each section has a short rubric of what to include and what to leave out.
02. Run your next safety meeting against the template and time the meeting. Note where the conversation went off-template and why.
Look for: A short reflection naming the section that consumed the most time and the reason. Common reasons: an unresolved finding from two weeks earlier, a contested closeout, or a new pattern that needs investigation.
Checkpoint
Could your next weekly safety meeting open with a one-page evidence-led pack that includes last week's open items?
Recommended reading