{"id":55628,"date":"2026-09-02T01:44:05","date_gmt":"2026-09-02T01:44:05","guid":{"rendered":"https:\/\/sitemate.com\/?p=55628"},"modified":"2026-11-12T04:01:31","modified_gmt":"2026-11-12T04:01:31","slug":"how-to-use-claude-to-draft-toolbox-talks","status":"publish","type":"post","link":"https:\/\/sitemate.com\/za\/mcp\/use-cases\/how-to-use-claude-to-draft-toolbox-talks\/","title":{"rendered":"Claude for Drafting Toolbox Talks"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":22,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","rank_math_title":"","rank_math_description":"Describe the topic, the crew and the job, and Claude drafts a Toolbox Talk you can run: the hazards that matter, plain talking points and a sign-on. You review it, then deliver and capture it in the field.","rank_math_canonical_url":"","rank_math_focus_keyword":""},"categories":[1],"tags":[],"industry":[],"product":[],"region":[145],"system":[87],"content_type":[170,173],"topic":[158],"class_list":["post-55628","post","type-post","status-publish","format-standard","hentry","category-uncategorized","region-global","system-safety","content_type-ai-landing-page","content_type-llm-use-case-page","topic-toolbox-talks"],"acf":{"ai_lp_breadcrumb":"<a href=\"\/_hl-staging\/topics\/safety\/toolbox-talks\/\">Toolbox Talks<\/a><span class=\"sep\">\/<\/span><span aria-current=\"page\">How to Use Claude to Draft Toolbox Talks<\/span>","ai_lp_h1":"How to use Claude to draft Toolbox Talks","ai_lp_intro":"Preparing for Toolbox Talks is a recurring task requires supervisors to start creating talk forms from a blank page everytime, as relying on generic toolbox talk forms off the internet are usually too broad to be relevant. Modern engineers now look to solutions like Claude to supplement manual efforts. They describe their topic, crew, and site to Claude, and it runs a draft within a few minutes, which supervisors read, and edit before delivering it to their crew.","ai_lp_hero_media":"<div class=\"ailp-chat is-claude\"><div class=\"ailp-chat-attrib\"><img class=\"ailp-chat-logo\" src=\"\/wp-content\/uploads\/2026\/08\/llm-claude.svg\" alt=\"Claude\">Claude<\/div><div class=\"ailp-chat-you\">Draft a 5 minute Toolbox Talk on working at heights for a crew doing roof edge work at Northgate Stage 2 this week.<\/div><div class=\"ailp-chat-source\"><span class=\"ailp-chat-dot\"><\/span>Drafted a working at heights Toolbox Talk<\/div><div class=\"ailp-chat-reply\"><p>Here's a Toolbox Talk you can run:<\/p><p>Working at heights, roof edge work, Northgate Stage 2.<\/p><p>Why it matters this week: the crew is working within 2m of an unprotected edge on the east face.<\/p><p>Before you start, check: - Edge protection is up and rated, with no gaps at corners or access points - Every anchor point is tagged and in date, and harnesses are inspected before use - The exclusion zone below is set and signed, so nobody works underneath<\/p><p>Ask the crew: what is the plan if someone spots a gap in the edge protection mid task?<\/p><p>Want me to shape this to your Dashpivot Toolbox Talk template, ready to capture on site?<\/p><\/div><\/div>","ai_lp_body":"<div class=\"ailp-block ailp-answer\">\n<p class=\"eyebrow-sm\">The short answer<\/p>\n<p>The first thing you have to do is input the desired topic, descriptions of the crew performing the task, other issues happening on site, and Claude can output a toolbox talk draft that includes relevant hazards, suggested safety controls, a few discussion points, and a sign-on section. All there's left to do is read and review the draft, revise where needed, and deliver the talk.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>How to get Claude drafting your Toolbox Talks<\/h2>\n<p>A talk worth running comes down to three things, and none of them is a long prompt. Give Claude the specifics of the job, tell it the shape your talk needs, then tighten what comes back. Do it properly once and you have a pattern you reuse every week, where only the topic and the crew change.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-step-list\">\n<ol class=\"ailp-steps\">\n  <li>\n    <p class=\"eyebrow-sm\">Step 1<\/p>\n    <h3>Give Claude the topic and the job<\/h3>\n    <p>The draft is only as specific as what you give it. Name the topic, the crew, the site and what has actually been happening: a near miss last week, a new subcontractor on site, a change in the sequence. A talk on working at heights for a crew doing roof edge work reads nothing like a generic one, and that's the whole point.<\/p>\n    <ul class=\"checklist-tick\">\n      <li>The topic, and why it matters this week<\/li>\n      <li>The crew and the site, so the language fits the job<\/li>\n      <li>Anything recent worth naming: a near miss, an incident, a new hazard<\/li>\n      <li>The length you want, so it fits the time you have<\/li>\n    <\/ul>\n  <\/li>\n  <li>\n    <p class=\"eyebrow-sm\">Step 2<\/p>\n    <h3>Tell it the shape you need<\/h3>\n    <p>Left open, Claude writes an essay. Tell it the sections a talk actually needs and it drafts to that shape: the hazards that matter for this job, the controls, two or three discussion prompts, and a line for the sign-on. Match the shape to the form your crew fills out, so the draft is quick to drop into the template rather than being reworked.<\/p>\n    <ul class=\"checklist-tick\">\n      <li>The hazards specific to this job, not a generic list<\/li>\n      <li>The controls already in your SWMS or procedure<\/li>\n      <li>Discussion prompts the crew answers out loud<\/li>\n      <li>A sign-on line, so the talk is captured as a record<\/li>\n    <\/ul>\n  <\/li>\n  <li>\n    <p class=\"eyebrow-sm\">Step 3<\/p>\n    <h3>Tighten it to the site<\/h3>\n    <p>The first draft is a starting point, not the finished talk. Cut anything generic, add the hazards that are real on this site today, and make the language plain enough to read aloud. A minute spent tightening is what turns a passable draft into one the crew actually listens to.<\/p>\n  <\/li>\n<\/ol>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>Prompt guidance for drafting Toolbox Talks with Claude<\/h2>\n<p>The prompt is the thing worth building, not the back and forth around it. Get it right once and it becomes your drafting prompt, where only the topic and the crew change. One rule matters more than the rest: the more specific the job you describe, the less generic the talk, so name the site, the task and the crew every time.<\/p>\n<ul class=\"checklist-dot\">\n  <li>&quot;Draft a 5 minute Toolbox Talk on [topic] for a crew doing [task] at [site] this week.&quot;<\/li>\n  <li>&quot;Add the three hazards that matter most for this job, with the controls next to each.&quot;<\/li>\n  <li>&quot;Give me two discussion questions the crew answers out loud, not yes or no.&quot;<\/li>\n  <li>&quot;Rewrite it plainer, so it can be read aloud in five minutes.&quot;<\/li>\n  <li>&quot;Same shape, new topic: [topic] for [crew]. Keep the hazards specific to that job.&quot;<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>Troubleshooting prompts for drafting Toolbox Talks<\/h2>\n<p>A weak draft is usually a thin prompt, or a form that gives the talk nowhere to land, rather than a limit of the assistant. These are the fixes worth trying, in order, and most are about what you feed in and where the talk ends up.<\/p>\n<ul class=\"checklist-dot\">\n  <li>The talk reads generic: you named the topic but not the job. Add the crew, the site and the task, and it sharpens<\/li>\n  <li>The hazards are wrong for the work: Claude doesn't know your site, so paste the relevant part of your SWMS or procedure and ask it to draft from that<\/li>\n  <li>It's too long to read aloud: ask for a time limit, five minutes or less, and it cuts to what matters<\/li>\n  <li>There's nowhere to capture it: your Toolbox Talk form has no sign-on or attendee field, so add one to the template and the delivered talk becomes a record<\/li>\n  <li>The fields don't match: the draft has sections your form template does not, so ask Claude to match your form's field names<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>Limitations<\/h2>\n<p>Claude can draft your toolbox talk, but it isn't on site to verify factors that could be relevant to your specific situation. It doesn't see the site, know your crew, or understand the task like a real engineer does, so human intervention is needed to polish the draft. In this sense, reviewing its output becomes part of the job, not just an optional step.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-subheading-body\">\n<h3>What it can do today<\/h3>\n<p>The more information you input in your prompt, Claude will be able to better perform these tasks.<\/p>\n<ul class=\"checklist-tick\">\n  <li>Draft a comprehensive Toolbox Talk about any topic, shaped to the job you describe<\/li>\n  <li>Include relevant hazards, appropriate safety controls, and discussion prompts in the talk<\/li>\n  <li>Match the format of its draft to your template, if provided<\/li>\n  <li>Perform edits and reworks to tone and length in seconds<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-subheading-body\">\n<h3>What it cannot do<\/h3>\n<p>Claude can draft you a toolbox talk, but it can't paint the entire picture for you. Here are some limitations you should know.<\/p>\n<ul class=\"checklist-cross\">\n  <li>Know your site or your crew<\/li>\n  <li>Understand the intricacies of the task like a trained human<\/li>\n  <li>Evaluate and update the toolbox talk without human input<\/li>\n  <li>Advises safety controls that are specific to your job site<\/li>\n  <li>Deliver the talk itself or take sign-ons<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>What this assumes you already do<\/h2>\n<p>This page assumes your crews already run Toolbox Talks and sign on to them. Claude drafts the talk, but it only helps if there's a habit of delivering it and capturing who was there. None of this is a setup step, it's the working practice the drafting sits on top of.<\/p>\n<ul class=\"checklist-tick\">\n  <li>Your crews run Toolbox Talks, most weeks<\/li>\n  <li>There is a form or template the talk gets captured on, with a sign-on<\/li>\n  <li>Someone owns delivering the talk and getting the crew to sign<\/li>\n  <li>You know the job well enough to tell a good draft from a generic one<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>Why use Claude to draft Toolbox Talks<\/h2>\n<p>Picture this: your crew is working a task at heights for the past two weeks and the supervisor in charge of writing the toolbox talks is already loaded with actual construction work. As creating a talk from scratch every week is too much work, a generic one is repeated every time and, eventually, the crew stops paying attention. <br>\nThis is where Claude can really help augment that supervisor's workflow, as it does the drafting for them, leaving them with more time to tighten the output rather than creating it from scratch. This results in a more comprehensive and relevant toolbox talk, where the crew can listen to something worth listening.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>What a good Toolbox Talk contains<\/h2>\n<p>A talk the crew actually listens to does a few things, and a good draft should hit all of them:<\/p>\n<ul class=\"checklist-dot\">\n  <li>A specific hazard for this job, not a general topic<\/li>\n  <li>The controls that are already in place, named plainly<\/li>\n  <li>Two or three prompts the crew answers out loud<\/li>\n  <li>Language that reads aloud in the time you have<\/li>\n  <li>A sign-on, so the talk becomes a record and not just a chat<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-callout\">\n<p>It's Monday, a new crew starts on the roof edge, and there was a near miss on another site last week. The talk needs to name that hazard, this crew, today. Written from scratch, it doesn't get done before the crew starts. Drafted in a minute and tightened, it does.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>Connecting Sitemate MCP to Claude<\/h2>\n<p>Three steps, and the first one isn't in Claude. An Org Controller has to switch MCP access on in Dashpivot before the connector will authenticate for anyone.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-step-list\">\n<ol class=\"ailp-steps\">\n  <li>\n    <p class=\"eyebrow-sm\">Step 1<\/p>\n    <h3>Turn on MCP access in Dashpivot<\/h3>\n    <p>An Org Controller opens Settings, then Security, and sets the MCP Access toggle to anything other than None. Save changes. Until this is on, the connector won't authenticate.<\/p>\n  <\/li>\n  <li>\n    <p class=\"eyebrow-sm\">Step 2<\/p>\n    <h3>Add the Sitemate connector in Claude<\/h3>\n    <p>In Claude, go to Settings, then Connectors, then Add and Browse connectors. Search for Sitemate, pick the connector tagged Community, and click Connect. Sign in with your Sitemate credentials and approve access when prompted.<\/p>\n  <\/li>\n  <li>\n    <p class=\"eyebrow-sm\">Step 3<\/p>\n    <h3>Pick it in a chat<\/h3>\n    <p>Start a new chat, click the plus button, open Connectors and select Sitemate. What you can read is whatever your Dashpivot permissions already allow, so connecting Claude doesn't widen anyone's access.<\/p>\n  <\/li>\n<\/ol>\n<\/div>\n\n<div class=\"ailp-block ailp-subheading-body\">\n<h3>If the connector will not appear<\/h3>\n<p>Three things account for almost every failed connection, and the first is the most common by a distance.<\/p>\n<ul class=\"checklist-cross\">\n  <li>Nothing connects at all: MCP Access is still off in Dashpivot, and only an Org Controller can turn it on<\/li>\n  <li>Sitemate isn't in the connector list: search &quot;Sitemate&quot; exactly, and look for the Community tag<\/li>\n  <li>The connector doesn't show in a chat: start a new chat, click the plus button, and pick it under Connectors<\/li>\n<\/ul>\n<\/div>\n\n<div class=\"ailp-block ailp-heading-body\">\n<h2>How the record gets captured<\/h2>\n<p>Claude drafts the talk. Getting it in front of the crew, signed and kept, is what happens in Dashpivot. Here's how the draft becomes a form your crew fills in, and why the record matters as much as the draft.<\/p>\n<\/div>\n\n<div class=\"ailp-block ailp-step-list\">\n<ol class=\"ailp-steps\">\n  <li>\n    <h3>Storm imports the draft, then captures it on site<\/h3>\n    <p>Save the draft out of Claude as a PDF, Word or Excel file, and Storm rebuilds it as a Dashpivot template with AI Templates. From there the talk gets delivered and filled in on a phone or tablet while the crew is standing there, with the sign-on attached, rather than written up on a sheet that has to be chased later.<\/p>\n  <\/li>\n  <li>\n    <h3>Dashpivot holds it as the record<\/h3>\n    <p>Each talk lands against its project as a structured record, with the sign-on attached, which is what makes it something you can stand behind later rather than a document in someone's inbox.<\/p>\n  <\/li>\n  <li>\n    <h3>Sitemate MCP reads it back<\/h3>\n    <p>With the talks captured, Claude can read back across them the same way it helped draft this one: which topics you have covered, which crews signed on, and what is worth running next. Your own permissions still apply.<\/p>\n  <\/li>\n<\/ol>\n<\/div>","ai_lp_body_2":"","ai_lp_comparison":"","ai_lp_band_logo":"<img class=\"product-logo\" src=\"https:\/\/sitemate-headless.pages.dev\/shared\/assets\/logos\/storm-logo.svg\" alt=\"Storm\">","ai_lp_band_heading":"Storm captures the talk Claude drafts","ai_lp_band_intro":"Claude drafts the talk, but it still has to be delivered and signed. Storm captures the Toolbox Talk and its sign-on as it happens, on site, so the record is there before anyone goes looking for it.","ai_lp_capabilities":"<div class=\"custom-col-12 bento-col\">\n  <div class=\"custom-grid\">\n    <div class=\"custom-col-6 ailp-cap ailp-cap--split\">\n      <div class=\"ailp-cap-icon\"><img src=\"\/wp-content\/uploads\/2026\/08\/ai-storm-icon.svg\" alt=\"\"><\/div>\n      <div class=\"ailp-cap-text\">\n        <h3>AI Form Fill<\/h3>\n        <p>Capture what you see and say, and Storm drafts the form for you. The details land in the right fields, so there is a record to check the moment the work is done, and you review and submit it yourself.<\/p>\n      <div class=\"button-group\">\n        <a class=\"text-buttons\" href=\"\/storm\/\">Learn more about Storm<img class=\"btn-arrow\" src=\"https:\/\/sitemate-headless.pages.dev\/shared\/assets\/icons\/grey-arrow.svg\" alt=\"\" width=\"16\" height=\"16\"><\/a>\n      <\/div>\n      <\/div>\n    <\/div>\n    <div class=\"custom-col-6\">\n      <img class=\"ailp-media\" src=\"\/wp-content\/uploads\/2026\/08\/storm-form-fill.webp\" alt=\"AI Form Fill\">\n    <\/div>\n  <\/div>\n<\/div>\n\n<div class=\"custom-col-4 bento-col ailp-cap\">\n  <div class=\"ailp-cap-icon\">\n    <div class=\"sm-icon-wrap gradient-light\"><img src=\"\/wp-content\/uploads\/2026\/08\/storm-listens-to-the-work.svg\" alt=\"\"><\/div>\n  <\/div>\n  <div class=\"ailp-cap-text\">\n    <h3>Listens to the work<\/h3>\n    <p>Captures voice cleanly through machinery, wind, and movement. Accents and trade language understood. No headset needed.<\/p>\n  <\/div>\n<\/div>\n\n<div class=\"custom-col-4 bento-col ailp-cap ailp-cap--flip\">\n  <div class=\"ailp-cap-icon\">\n    <div class=\"sm-icon-wrap gradient-light\"><img src=\"\/wp-content\/uploads\/2026\/08\/storm-works-on-site.svg\" alt=\"\"><\/div>\n  <\/div>\n  <div class=\"ailp-cap-text\">\n    <h3>Works on site<\/h3>\n    <p>Built for gloves, cabs, and screen protectors. Captures inputs offline and processes in the background. No waiting on the field.<\/p>\n  <\/div>\n<\/div>\n\n<div class=\"custom-col-4 bento-col ailp-cap\">\n  <div class=\"ailp-cap-icon\">\n    <div class=\"sm-icon-wrap gradient-light\"><img src=\"\/wp-content\/uploads\/2026\/08\/storm-you-stay-in-control.svg\" alt=\"\"><\/div>\n  <\/div>\n  <div class=\"ailp-cap-text\">\n    <h3>You stay in control<\/h3>\n    <p>Storm never commits a record on its own. Every output is a draft for human review. Admins control what Storm can write to.<\/p>\n  <\/div>\n<\/div>","ai_lp_faq_heading":"Frequently Asked Questions","ai_lp_faq":[{"question":"Does Claude know my site and my hazards?","content":"<p>No, Claude only formulates drafts from the prompts you give it. Make sure to properly describe the topic, crew, task, and other recent events at your site, as vague input will most likely result in vague or generic talks.<\/p>"},{"question":"Will the talk be specific enough to actually use?","content":"<p>Yes, with a good input prompt, the toolbox talk draft will be a good foundation to use for actual talks. However, it is a still a draft that will need human review to compare against the real job and to cut any generic content. This saves supervisors time and effort, as review will be quick, allowing them to focus on making the talks land with the crew.<\/p>"},{"question":"Can I match the draft to our own Toolbox Talk form?","content":"<p>Yes, if you describe your forms sections and structure to Claude, it can draft a toolbox talk to try and match your desired Toolbox Talk form. This way, it will be easier for Claude to drop into your existing template.<\/p>"},{"question":"Where does the talk get captured?","content":"<p>The talk gets captured by Storm on site, with the data stored on the appropriate fields on the toolbox talk form. Afterwhich, it is signed-off on and stored on Dashpivot as a record of the toolbox talk.<\/p>"},{"question":"Does this work with ChatGPT and Microsoft Copilot as well?","content":"<p>Yes, it works with ChatGPT and Microsoft Copilot. Sitemate supports connection to these external applications to better augment your workflows.<\/p>"},{"question":"Do I still need to write Toolbox Talks myself?","content":"<p>Yes, you are still needed to write the Toolbox Talks. While using Claude removes the need to start from a blank page everytime, human input, review, and execution is still needed to actually create the toolbox talk itself.<\/p>"}],"ai_lp_version_history":"","ai_lp_closing_heading":"Stop starting every Toolbox Talk from a blank page","ai_lp_closing_body":""},"custom_permalink":"mcp\/use-cases\/how-to-use-claude-to-draft-toolbox-talks","_links":{"self":[{"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/posts\/55628","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/comments?post=55628"}],"version-history":[{"count":1,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/posts\/55628\/revisions"}],"predecessor-version":[{"id":55629,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/posts\/55628\/revisions\/55629"}],"wp:attachment":[{"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/media?parent=55628"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/categories?post=55628"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/tags?post=55628"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/industry?post=55628"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/product?post=55628"},{"taxonomy":"region","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/region?post=55628"},{"taxonomy":"system","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/system?post=55628"},{"taxonomy":"content_type","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/content_type?post=55628"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/sitemate.com\/za\/wp-json\/wp\/v2\/topic?post=55628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}