All templates
Health & SafetySOPUS edition

Toolbox Talk Template with Attendance Record template

A toolbox talk is a short, focused safety discussion — typically ten minutes, held at the start of a shift, on one topic relevant to the work that day — with a signed attendance record proving who was there. It is also called a tailgate meeting or safety huddle; whatever the name, it is the cheapest ongoing safety training a crew can get.

Free to use
US-focused
Updated 13 July 2026

The talk itself is only half the document. The other half is the attendance record: names, signatures, date, topic, and presenter. When an inspector, insurer, or attorney asks whether workers were trained on a hazard, the stack of signed talk records is often the answer — a safety program you can hold in your hand.

This template gives you both: the structure of a talk that fits in ten minutes and actually lands, and the attendance record section to print on the back of every talk sheet.

The template

Full text, ready to adapt.

Highlighted fields are placeholders — replace them with your organisation's specifics. A starting point, not legal advice.

Toolbox Talk Template with Attendance Record

SOP · Health & Safety

1. Purpose and scope

This procedure sets out how {{org.name}} plans, delivers, and records toolbox talks at [site/location]. It applies to all supervisors and crew leads who deliver talks and to all workers who attend them.

Talks are held [frequency — e.g. weekly, or daily on active job sites] at [time and place], last about ten minutes, and cover one topic each. Every talk produces a signed attendance record.

2. Roles and responsibilities

  • Safety lead ([name/role]): sets the talk schedule and topic calendar, reviews completed records, and owns this procedure.
  • Presenters (supervisors and crew leads): prepare the talk, deliver it, run the attendance record, and hand the signed sheet to [name/role] the same day.
  • Workers: attend, sign the record, and raise hazards and near misses during the talk — the discussion is where the crew's knowledge surfaces.
  • [Name/role]: files the records at [system/location] and flags anyone who missed a talk for a catch-up before their next shift on the affected task.

3. Choosing the topic

  • This week's work: the highest-risk task on the schedule — that is the talk the crew needs today.
  • Recent events: any incident, near miss, or inspection finding at {{org.name}} or on a nearby site — nothing gets attention like "this happened here".
  • Seasonal hazards: heat illness in summer, cold stress and icy surfaces in winter, storm and wind work.
  • Recurring fundamentals on rotation: ladders, housekeeping, PPE, lifting, lockout/tagout, chemical handling — the topics that cause injuries precisely because they feel routine.
  • Keep the year's topic calendar at [location] and mark off what was actually delivered — the gap between planned and delivered is the first thing to audit.

4. Structure of a 10-minute talk

  1. 1Open with why (1 minute): name the topic and tie it to today's work — "we are pouring on the second floor today, so this is about guardrails and openings."
  2. 2Tell the story (2 minutes): a real incident or near miss involving this hazard — ours if we have one, an industry example if not. Concrete beats abstract.
  3. 3Cover the hazard (3 minutes): where it shows up on this site, what it does to people, and the [2–4] specific controls that apply here — not a recitation of the whole standard.
  4. 4Show, don't just tell (2 minutes): demonstrate with the actual equipment where possible — the harness, the guard, the label, the lockout device.
  5. 5Ask the crew (2 minutes): "where have you seen this go wrong?" and "what makes this hard to do right on this site?" — then write down what they say and act on it.
  6. 6Close with the one thing: a single sentence the crew should carry into the shift — then run the attendance record before anyone walks away.

5. Attendance record

Every talk sheet includes this record, completed at the talk — not reconstructed later. It is the proof of training; treat it with the same care as a timesheet.

  • Header: date, time, site/location, topic, presenter name and signature.
  • One row per attendee: printed name, signature, and [employee ID / trade / employer, on multi-employer sites].
  • Notes section: questions raised, hazards reported, and any follow-up actions with an owner and date.
  • Absentee line: who was scheduled but not present, and the date their catch-up was delivered.
  • Signatures are collected at the talk, in ink or in [app/system] — a name written in by the presenter is not a signature.

6. Delivery tips

  • Hold the talk where the work happens, standing, at shift start — a conference room at 3 p.m. is a different, worse meeting.
  • One topic per talk. Two topics means neither is remembered.
  • Speak plainly and translate where needed — a talk the crew did not understand is not training, whatever the signatures say.
  • Never read a sheet aloud verbatim; know the three points you need to land and talk to the crew, not the paper.
  • Follow up visibly on what the crew raises — the fastest way to kill toolbox talks is to ignore the answers you asked for.

7. Records and review

Signed talk sheets are filed at [system/location] and retained for [period]. [Name/role] reviews them [frequency] for coverage (did every crew get every scheduled talk?), attendance gaps, and unresolved follow-up actions.

This procedure and the topic calendar are reviewed [frequency, e.g. annually], after any recordable incident, and when the work or the season changes. Owner: [name/role]. Next review due: [date].

Make it yours

How to adapt this template.

1

Build a topic calendar for the next [quarter] from your actual schedule of work, your incident history, and the season — then let recent events override it freely.

2

Print the talk outline on one side of the sheet and the attendance record on the other, so the record cannot get separated from the talk.

3

Brief your presenters on the 10-minute structure and have them practice one talk on you before they run one on a crew.

4

Collect signatures at the talk itself and file sheets the same day — reconstructed records are obvious and worthless.

5

Audit monthly: pick two filed sheets and ask two attendees what the talk covered. If they cannot say, fix the delivery, not the paperwork.

A document is not a system

Turn this template into trained, proven behaviour

A policy in a drawer proves nothing. In TrainedTeam this template becomes assigned training with knowledge checks, e-signature acknowledgments, version history, and an audit-ready record of who completed what, when.

Toolbox Talk Template with Attendance Record template FAQs

Does OSHA require toolbox talks?

No — OSHA does not mandate toolbox talks or any particular format. What OSHA standards do require is training on the hazards of the job, and regular documented talks are one recognized, practical way to deliver and refresh it. The signed records also demonstrate good faith and an active safety program during inspections and investigations.

How long should a toolbox talk be?

About ten minutes. Long enough to cover one topic with a story, the controls, and a question to the crew; short enough that it happens at shift start without eating production time. If a topic genuinely needs thirty minutes, it needs a training session, not a toolbox talk.

Why does the attendance record matter so much?

Because it is the only durable evidence the talk happened. Inspectors, insurers, and attorneys ask "was this worker trained on this hazard?" — a dated, signed record answers it; a presenter's memory does not. Collect signatures at the talk and file the sheet the same day.

Who should deliver toolbox talks?

The crew's own supervisor or lead, not a visiting safety manager — the person the crew works for is the person whose safety message carries weight. The safety lead's job is to arm presenters with good material and audit that talks actually happen.

What topics work best?

The ones tied to that day's work and that site's history. A talk about the task the crew starts in twenty minutes beats a generic topic every time, and a near miss from your own site beats a statistic from anywhere else. Rotate the fundamentals through the calendar, but let real events jump the queue.