Near misses, unsafe conditions and incidents reported by QR in 30 seconds, turned into a ready-to-read Monday toolbox talk. For small sites. 14-day free trial.
Every site has one: the lead everyone steps over until Thursday.
Put the reporting QR where people actually stop — the break room, canteen or locker area — and let them write it down on a break.
Close the loop. When someone reports a hazard, tell the crew what changed: "You reported it, we fixed it." Even a small fix, said out loud on Monday, shows reporting is worth the effort.
Monday toolbox talks shouldn't start from a blank page. SafeMonday turns the week's near-miss reports into a ready-made talk every Friday. £29 per site per month, 14-day free trial, no card needed to start. https://t.co/MmZN5Czt5T
Near-miss tip: ask for a photo. Ten seconds with a phone shows what words miss: the cluttered walkway, the missing guard, the poor lighting. The supervisor sees the problem as it was, not as it was remembered.
Toolbox talk tip: open with something that actually happened on your site last week, not a generic slide. "Last Tuesday, someone nearly..." gets people talking far faster than a list of rules.
A wet floor with no sign is an unsafe condition.
Walking past it is an unsafe act.
Both are worth reporting before anyone slips, and neither needs a form that takes 10 minutes.
It's Friday. Somewhere a supervisor is about to search "toolbox talk ideas" for Monday morning.
The best topic is already on your site: the near miss someone mentioned on Tuesday and nobody wrote down.
Three questions that turn a near miss into a useful toolbox talk:
1. What nearly happened?
2. Why was it possible? (the condition or the habit, not the person)
3. What changes on Monday?
If the crew can answer number 3, the talk worked.
@ClickB4UDigMB Good checklist. One addition for the crew: if anyone finds a marking missing or the paperwork not on site, that's worth recording even when nothing gets hit. Those "we nearly dug blind" moments are exactly what the next toolbox talk should cover.
@TacticalLearnX@SuffolkBuilds Strongly agree. The most job-specific material a site manager has is what nearly went wrong on their own site last week. Short talk, local example, one action to take away, and it lands better than a generic module.
@ohs_talks The "real example from your own site" part is the hardest to do on a Monday morning, because by then nobody remembers what happened midweek. Jotting down near misses as they happen during the week gives you a ready pile of local examples.
@joemcguireins Worth adding: track how many near-miss reports led to a fix, not just how many came in. A rising count can mean a healthy reporting culture, so the follow-up rate is the number that tells you whether people's reports are being acted on.
@uwandulu Agree. The catch on physical sites is friction: if logging one means finding a supervisor or filling in a long form, it doesn't get logged. Make it quick, make it no-blame, and show people what changed because of it. That last bit is what keeps reports coming.
@RigScopeEnergy1 New starters see what the rest of us have stopped noticing. Asking them at the end of week one, 'what surprised you here?', is a habit worth keeping.
@leadthemiddle Underrated. A two-minute 'here's what's changed since yesterday' at the start of the shift heads off a lot of near misses before they happen.
@CandCoConsSA Agree. Observations earn their keep when someone acts on them and tells the team. One fix a week, talked through on Monday, beats a spreadsheet of 200 entries nobody reads.
@HSSE_Tips Good point. Temporary layouts are where near misses pile up, because the routes people learned last month no longer apply. Worth a two-minute brief to the crew every time the layout changes.