Free Pack · Three Ready-to-Run Talks
Toolbox Talk Topics Crews Actually Listen To
Searching for toolbox talk topics on a Sunday night usually means one thing: the roster says you're presenting at pre-start, and the last three topics earned the same glazed silence. The problem isn't your crew's attention span. It's that they've heard "slips, trips and falls" forty times, and familiarity is the enemy of listening.
There's a format that reliably breaks through: real incidents, told plainly, translated to your site, ending in questions the crew answers, not warnings they endure. Aviation has taught with its own accidents for fifty years. It works because the stakes are real and the lessons are specific.
The Format
A real event, a lesson, a translation
Every talk in our format runs the same four beats, in about three minutes read aloud: what happened (the plain public record), the lesson the industry took, what it looks like on your site, and two or three questions handed to the crew.
The three talks in the free pack are built from aviation's canonical accidents: "Someone always flies the aircraft" on task fixation and who watches the big picture when a problem pulls the crowd in; "If it wasn't confirmed, it didn't happen" on the deadliest accident in aviation history, caused entirely by assumption; "A challenge is data, not disrespect" on what happens when the junior person notices and hints instead of challenging.
Topic Bank
Twelve topic angles that still have stakes
- 01
Task fixation
When something breaks, who is still watching everything else?
- 02
Handover assumptions
What actually got confirmed at shift change, and what got assumed?
- 03
“Should be right”
Which isolation on this site gets verified by memory instead of by test?
- 04
Interruptions mid-task
What's our rule when a critical sequence gets broken?
- 05
The quiet new starter
Would the newest person here stop the job? Honestly?
- 06
Fatigue as arithmetic
Hours awake and hours slept, not toughness. What's tonight's number?
- 07
Radio and phone ambiguity
What's our readback for critical instructions?
- 08
Normalisation
What do we do “because we've always done it” that we'd never design in today?
- 09
Stop-work in practice
When was it last used here, and what happened to the person who called it?
- 10
Permit drift
Does the permit still describe the job we're actually doing this afternoon?
- 11
First shift back
What changed on site while you were off swing?
- 12
The debrief nobody runs
What did yesterday teach us that today's brief should carry?
Delivery
How to deliver a talk that lands
Reading aloud is allowed, these are written for it. Stand at the job, not the crib room. One topic, three minutes, and end on the questions: a talk that finishes with discussion did its job; a talk that finishes with a warning just finished. Close with the one line to remember: a crew forgets paragraphs, but it keeps sentences.
Free Download
Get three ready-to-run talks, free
The Pre-Start Briefing Pack includes all three aviation talks in full read-aloud format, plus the THREAT Brief template and a Challenge and Response card. One email. No spam.
FAQ
Questions supervisors actually ask
How long should a toolbox talk be?
Three to five minutes, one topic, ending in discussion. Ten minutes of coverage beats nothing, but three minutes of engagement beats ten of coverage every time.
How often should we run them?
A common rhythm that works: a short daily pre-start brief plus one themed talk per week. Consistency beats length.
Are toolbox talks mandatory in Australia?
They're not named in legislation, but they're standard evidence of the consultation and communication duties under WHS law. The value, and the legal weight, comes from genuine two-way discussion, not the sign-on sheet.
Where do these talks come from?
From the public investigation records of real aviation accidents, translated for industrial crews by a current airline pilot with time in Western Australian mining production.