How to Run a Toolbox Meeting
Ten minutes on the tailgate, once a week, about the risks in this week's work. Done properly it changes what happens on site; done as a signature sheet it changes nothing at all.
A toolbox meeting is a short, informal safety conversation with the people doing the work — usually on site, usually before anyone starts. It's the most practical safety tool a small trade business has, and it's also the one most commonly reduced to passing a sheet around for signatures. The difference between the two versions is entirely in how you run it. This guide covers what a toolbox meeting is for, how to pick a topic worth ten minutes, how to actually run one, and what to record.
Doing this job for a living? See job management in ServiceYak.
What a toolbox meeting is for
A toolbox meeting — toolbox talk, tailgate meeting, prestart — is a short conversation about the specific risks in the work that's about to happen. Not safety in general. This site, this week, these tasks.
It does three things a safety manual can't:
- It gets information out of people's heads. The apprentice who noticed the loose handrail, the subbie who's cutting above you on Thursday. That coordination only happens if there's a moment for it.
- It makes the risk specific. "Watch your back" changes nothing. "The units are on the second floor and there's no lift, so we're hiring a stair climber" changes the day.
- It shows what you actually care about. A crew works out very quickly whether safety is something the boss does or something the boss says.
Consulting your workers about health and safety is a duty under WHS law, not a nice-to-have, and a regular documented toolbox meeting is one of the simplest ways a small business meets it. What's required of you depends on your state or territory and the work you do, so check with your regulator rather than assuming a signature sheet covers it.
When and how often
Weekly is the standard that suits most trade businesses, with a shorter prestart on top for anything unusual. The rhythm matters more than the length:
- Monday morning, before anyone leaves the yard. Covers the week's jobs, anything that came up last week, and what's changed on site.
- A quick prestart on any day with something genuinely new — hot work, working at height, an unfamiliar site, a confined space, another trade arriving.
- Straight after an incident or near miss, while it's fresh. This is the highest-value one you'll ever run.
- When someone new starts, even mid-week. They've got none of the context everyone else is carrying.
Ten to fifteen minutes is right. A toolbox meeting that regularly runs half an hour has become a job briefing with safety attached, and people stop listening to both.
Picking a topic worth ten minutes
The best topic is almost always something that happened in your business in the last fortnight, or something about this week's work specifically. Generic topics off the internet are what turn these meetings into a formality.
| Source | What it gives you |
|---|---|
| Last week's near miss | The most relevant topic available, and the one people actually listen to |
| This week's jobs | The specific hazards in what you're about to do — access, heights, live services, traffic |
| A new site | Access, parking, other trades, amenities, emergency arrangements, who's in charge |
| New gear or a new method | How it's used, what it replaced, and what's different about it |
| A seasonal risk | Heat and hydration, storms, short daylight, wet surfaces, fatigue at the end of a long run |
| A rule people are drifting on | PPE, isolation, testing before touching, ladder use. Name it before it becomes normal |
| Something from the crew | Ask what they'd raise. The best topics usually come from whoever's closest to the work |
One topic per meeting. Three topics in ten minutes means nobody remembers any of them.
How to run one
- Pick the topic the day before. Two minutes of thought beforehand is what stops it becoming "anyone got anything?" — which reliably produces silence.
- Stand somewhere you can all hear each other. Off the road, away from the compressor, everyone in a circle rather than a line facing you. It sounds trivial and it decides whether anyone speaks.
- Start with what changed. Last week's incidents, what got fixed, what's new on site this week. Sixty seconds.
- Cover the one topic. What the hazard is, what could go wrong, and what we're doing about it. Point at the actual thing if it's in front of you — a real ladder beats a diagram every time.
- Ask a question you can't answer yourself. "What's the worst thing that could happen on the Henley job this week?" gets a real conversation going. "Any questions?" gets you nodding and silence.
- Agree actions and name owners. Anything raised gets a name and a date, or it doesn't get raised again next time. This is the step that determines whether these meetings are worth running.
- Record it and move. Date, site, topic, who attended, actions. Then straight to work — dragging it out is how you teach people to dread it.
Never handle a discipline issue in a toolbox meeting. The moment one becomes the forum for a spray, people stop raising the near misses — and near misses being raised is the entire return on the exercise.
What to record, and what to do after
A record does two jobs: it proves the consultation happened, and it stops actions evaporating. Keep it short enough that you'll actually keep it.
- Date, site and who ran it.
- Who attended — including subbies and anyone else on site who joined in.
- The topic, in a line.
- What was raised by the crew, in their words.
- Actions — what, who, by when.
- Sign-off, if that's how you work. Names are the point; signatures are the formality.
Then close the actions. Open the next meeting with what happened to last week's, every time. A crew that sees the loose handrail get fixed will tell you about the next one; a crew that watches their input disappear into a folder will stop talking, and you'll be running a signature sheet again.
ServiceYak keeps the site notes, photos and job history for each site on the job itself, so the hazards someone flagged on the last visit are there in front of whoever's going out this week rather than sitting in a notebook in another van.
Frequently asked questions
How long should a toolbox meeting be?
Ten to fifteen minutes, one topic. If it's regularly running longer it's turned into a job briefing and attention drops off, which costs you the safety conversation you were there for. Run a separate prestart for anything genuinely new on the day.
Do sole traders need to run toolbox meetings?
There's no crew to consult, but the thinking still pays. Before an unfamiliar job, spend five minutes on what could go wrong and what you'd do about it, and write it down. It matters more when you're on your own, because there's nobody there to spot what you missed. As soon as you have a subbie or an apprentice with you, run the real thing.
What should we talk about at a toolbox meeting?
One hazard that's specific to this week's work, or something that happened in your business recently. Near misses, a new site's access and other trades, a new tool, a rule people have drifted on. Generic topics downloaded from the internet are the fastest way to teach a crew that the meeting is a formality.
Do we have to keep records of toolbox meetings?
Keep them. WHS duties around consulting workers are ongoing, and a dated record of what was discussed and who was there is the simplest evidence you're meeting them — as well as the only way actions get followed up. The specific requirements depend on your state or territory and the work you do, so confirm them with your regulator.