Safety Moment Template
Two-page safety moment pack: a one-page card (topic, why now, what happened in a few sentences, the one key message, one question for the group, one commitment, questions raised with their follow-up, who delivered it, where, and how many attended) and a one-page log of twenty-four moments with the source of each topic, whether an action was raised and its reference. A safety moment is a voluntary practice, not a legal requirement, and no source opened for this page sets a length, a frequency or content for one.
What's inside
Page 1: the card
- Moment — topic, date, start time, minutes taken, delivered by with signature, team or crew, location, number of attendees, and the format: story, question, card or prompt, short video, demonstration or other
- Why now — what prompted the topic: incident, near miss, hazard or observation, audit or inspection finding, coming task or season, change or other; the reference and a sentence on the trigger
- What happened or what we know — a few sentences, facts only, with no names and no blame
- The one key message — one sentence the group should remember
- One question for the group — an open question, and what the group said
- One commitment — what will be done differently, by whom and by when
- Questions or concerns raised — three rows with the answer or action, owner, due date and log or action number; whether a follow-up action was raised, its reference, and where the attendance list is kept
Page 2: the log
Twenty-four lines: date, topic, delivered by, team or crew, source of the topic (incident, near miss, hazard or observation, other), attendees, action raised yes or no, and action reference. A periodic review block compares the topics held with the events in your own records.
What requires or shapes this record
No source opened for this page makes a safety moment a legal requirement, and none sets a length, a frequency or content for one. It is a voluntary practice. The records it touches are lighter than a training record: CCOHS recommends keeping the topic, worker feedback and attendance of safety talks, and says regular records can help show due diligence, and OSHA's guide says workers stop reporting hazards when they get no response, which is why the card has a follow-up column. Rules on safety, toolbox or tailgate meetings in some trades and places are a separate question that this page does not answer.
- CCOHS, Safety Talks: How To (OSH Answers, first published 22 May 2025)
The Canadian Centre for Occupational Health and Safety describes safety talks, also called toolbox talks, safety briefings or tailgate meetings, as short, informal meetings on one health and safety topic, usually about five minutes, usually at the start of a shift or before a task, and not a replacement for formal education and training. Topics come from identified hazards, risk assessments, inspection and incident reports and worker feedback. It recommends records of the topic and content, worker feedback and attendance. The card's why-now box and the log's source of topic follow that advice. The page does not say that talks are required by law.
- IOGP, Safety culture on the cards (21 March 2016)
IOGP is the oil and gas producers' association, and its article uses the term safety moment. It describes 52 Safety Moment cards that Safer Together, a group of operating and contractor companies in Queensland's gas industry, developed in 2014 from the leadership characteristics in IOGP report 452. Each card is a prompt under one of seven themes. A leader picks one, reads it out and asks an attendee to respond; sessions last about five minutes and are held from board meetings to management walkabouts, with no preparation. The card's single question for the group follows that pattern. IOGP's example prompt is about leadership and culture and not one task, which is why the form asks for the trigger separately.
- OSHA Safe + Sound, Better Safety Conversations (7-page guide)
OSHA's guide does not use the term safety moment, but it covers the practice of a short story. A story describes a real event in a few sentences, delivered in 15 to 20 seconds, and should come from the speaker's own workplace, company or industry, because fresh stories close to the listeners carry more weight. It asks that workers be reminded they can raise concerns without fear of reprisal, that actionable items be noted and followed up, and says a common reason workers do not report hazards is that they never get a response. The card's section 3 and its table of questions raised follow this. Leaving out names is the form's own choice, in the same spirit.
- HSE, Toolbox talks (page updated 10 August 2022)
Britain's Health and Safety Executive describes a toolbox talk as a short presentation to the workforce on a single aspect of health and safety, and the page says nothing about records. The sources read use safety moment, safety talk and toolbox talk loosely, and none defines the first, so the form's introduction says what a moment does not replace: a toolbox talk, a pre-task briefing and training. Say in your own procedure which terms you use.
Each source checked on 17 October 2026. Not legal advice; check the text in force for your site.
Field by field
The card is built around one message, one question and one commitment so that a moment stays short. The log is the record of what was held; the numbers in it show activity, not that a hazard is controlled. Attendance is a count, kept apart from any check on whether people understood; if your site needs names, keep a sign-on list and note where it is. Nothing on the form sets a length, a frequency or a required topic, because none of the sources opened does.
- Topic, date, start time and minutes taken
- Why: One line for the topic so it can be searched later. The minutes taken show whether the moment stays short; CCOHS describes safety talks as about five minutes and IOGP's cards as about five.
- Common mistake: A topic recorded as "safety", so nobody can match it to anything later.
- Delivered by, signature, team and location
- Why: A rota spreads the load, and the record shows who led which team where. The signature is the leader's, not an attendance sheet.
- Common mistake: The same supervisor every week, so the team only ever hears one voice.
- Number of attendees
- Why: A count shows reach. CCOHS recommends recording attendance for safety talks. A count is not evidence of understanding.
- Common mistake: Treating a signature or a count as proof that the message landed.
- Format
- Why: Story, question, card, short video or demonstration. Recording what people actually saw lets a later reader see what was shown.
- Common mistake: Showing a video and recording only "safety moment held".
- Why now: trigger and reference
- Why: The trigger ties the moment to an incident, near miss, hazard or observation in your own records, or to a coming task or season. The reference lets a quarterly review match topics to events.
- Common mistake: Picking topics from a poster calendar while the site's own near misses are never mentioned.
- What happened or what we know
- Why: OSHA's guide asks for a real event in a few sentences, delivered in 15 to 20 seconds, from your own workplace where possible. Say what happened and what can be learned.
- Common mistake: Naming the person, or telling the story to assign blame, which works against reporting.
- The one key message
- Why: One sentence the group should remember. If it needs two, the moment is two moments.
- Common mistake: Three messages, so nobody remembers any of them.
- One question for the group, and what was said
- Why: An open question starts a conversation; the answers show what the group knows about the hazard and what they raised.
- Common mistake: A yes or no question, or a question the leader answers without waiting.
- One commitment
- Why: What will be done differently, by whom and by when. It moves a moment from a story to a change that can be checked.
- Common mistake: "Be careful", with no owner or date.
- Questions or concerns raised
- Why: OSHA says workers stop reporting when they get no response. Each question gets an answer or an action with an owner and a due date, and a number in your own log.
- Common mistake: Replying "we will look into it" with no owner, so the question comes back next week unanswered.
- Follow-up action raised and reference
- Why: Ties the moment to the action process and lets the log count how many moments led to an action.
- Common mistake: Putting the action in the meeting notes with no reference, so it cannot be found at the next review.
- Log: source of topic and action raised
- Why: Incident, near miss, hazard or observation, or other. The column shows whether topics come from your own events or from somewhere else.
- Common mistake: Marking Other on every line, which hides where topics really come from.
- Periodic review
- Why: Lines up the topics held against your own incident, near miss and observation records, and names events that no moment has covered yet.
- Common mistake: Reporting the count of moments held as if it were safety performance.
Worked example
IllustrativeOne safety moment in a maintenance team, with its log line (invented team, people and references)
| Section | Entry |
|---|---|
| 1 Moment | Topic: stepladders and wet floors. Weekly maintenance meeting in the workshop. Delivered by a technician as a story; 4 minutes; 12 attendees. |
| 2 Why now | Hazard or observation: observation report OBS-0311 of a stepladder set up on a freshly mopped aisle last week. No one was hurt. |
| 3 What happened | The technician told it in four sentences: someone at another company stepped onto a stepladder standing on a wet floor, it slid, and they were off work for six weeks. No names, and nothing about who was at fault. |
| 4 Key message | Check that the floor is dry and the ladder feet grip before you climb. |
| 5 Question | Where in our workshop is the floor wet at the start of a shift? The group named the wash bay door and the aisle by the parts sink, and two people said mopping happens at shift change. |
| 6 Commitment | Mop and put out signs before the shift starts, and check the ladder feet before every climb. The supervisor adds both to the shift-start routine from Monday. |
| 7 Questions raised | Do the wet-floor signs in the workshop suit the aisles? The supervisor could not answer on the spot; logged as action A-2026-0147, owner the supervisor, due at the next meeting. Follow-up action raised: yes. |
| Log line | Date and topic as above, delivered by the technician, maintenance team, source H (hazard or observation), 12 attendees, action raised Y, reference A-2026-0147. |
The moment does not replace tomorrow's ladder job, which needs its own briefing from its own task analysis. At the quarterly review the supervisor lines the log up against the observation reports: four of the last ten moments were about ladders and none about vehicle movements, which appear in many reports, so the next rota is planned around that. The figures are invented to show the method.
When a spreadsheet stops being enough
A paper card and a spreadsheet log work for one team. They stop working when several leaders and sites hold moments, when someone has to see which incidents, near misses or observations the topics came from, when questions raised at the meeting must reach an owner and be answered, and when a quarterly review has to compare the topics held with the events in your records.
A software record can offer quick entry on a phone at the meeting, a rota for leaders and a library of prompts, a link from a moment to the incident, near miss or observation behind it, open questions with owners and due dates, and reports by topic and team. Ask what happens offline, and how the tool keeps a safety moment apart from a toolbox talk and a pre-task briefing. The list below applies the toolbox talk rule: a sourced toolbox-talk or safety-briefing capability. Nothing in it shows that a product logs safety moments as such, so ask how a short talk, its attendance count and its follow-up are recorded.
Same rule for every product: tagged “Training Management”, “Training & Competency Management”, “Safety Management”, “Construction Safety” or “Toolbox Talks”, with a sourced toolbox-talk or safety-briefing capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.
Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered
Safesite · Toolbox talks with attendance evidence · Documented
Vendor source · Profile checked
Raken · Toolbox talks · Conditional
Vendor source · Profile checked
SafetyReports · Training records and recurring requirements · Conditional
Vendor source · Profile checked
Procore Quality & Safety · Toolbox Talk attendance form · Conditional
Vendor source · Profile checked
Salus · Rosie AI assistant · Documented
Vendor source · Profile checked
Tekmon · Toolbox Talks (vendor-stated) · Vendor-stated, not yet publicly confirmed
Ask to see it in a demo · Profile checked
All 6 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.