Write the weekly safety talk from last week's near misses
Every Friday Claude reads the week's near-miss reports and writes a five-minute talk for the shift leads to give on Monday: what happened, why it matters and what to do differently. It names no one and blames no one.
FullProductionEvery week
Set it up6 steps
Open the Claude desktop app and sign in with the Claude account you use for work. On a personal Free, Pro or Max plan, chats can be used for training unless you switch off SettingsPrivacyHelp improve Claude.
No account yet? Ask your manager.
Where things are in Claude
- CustomizeConnectors In Claude's left sidebar: connect your email and files.
- /schedule Type it in a new Cowork task to run a prompt on a schedule.
- Scheduled In Claude's left sidebar: what runs, to pause or change it.
- Once for the whole company: your Microsoft admin approves Claude's Microsoft 365 connector and turns on its write tools, so Claude can save drafts and files. If connecting asks for an admin's approval, this is still to do: send them this step.
- Make a "Near misses" sheet in your Production folder and add a row for every report: date, shift, area or machine, what happened, what could have happened, who reported it and any action taken. For a paper report, ask Claude to type in a photo of it.
- In Cowork, connect your Production folder in OneDrive or SharePoint (the one synced to this computer).
- Type /schedule, paste this workflow's prompt and pick Weekly, Friday at 14:00.
- Read the talk, change what you want, and hand it to the shift leads for Monday.
- It runs while your computer is on and Claude is open. A Friday it was off is skipped, not queued.
Set this up on your computer: the Claude desktop app runs it.
The prompt
- Every Friday at 14:00, read this week's rows in the "Near misses" sheet in my Production folder, and the talks of the last 4 weeks in the Safety talks folder inside my Production folder.
- 1. Pick one topic for Monday: the near miss that could have hurt someone worst, or the one that keeps coming back. Say why you picked it.
- 2. Write a talk a shift lead can read out in five minutes, as a Word document in the Safety talks folder: what happened, told as a situation and never as someone's mistake; what could have happened; why it happens; what each of us does differently from Monday; and one question to ask the team. Short sentences, in the words everyone on the floor uses.
- 3. Add one line on each of the week's other near misses, and thank the people who reported them, without names.
- 4. Do not repeat a topic from the last 4 weeks unless it happened again: then say it is the second or third time.
- 5. For my safety lead only, separately: the near misses that repeat, the actions still open, and who reported each, so they can follow up. Put first anything that describes an injury or damage: it may have to be reported by law, so it goes to them today, not into a talk.
- Never name or point at anyone in the talk. Use only what the reports say; never invent a cause or an injury.
If your company keeps employee records out of AISafe version
Reads a near-miss log without the names of who reported or who was involved, and names no one anywhere. People are written by their role and shift.
What you get
A talk the shift leads can read out in five minutes, with one question for the team, and a short list for your safety lead of repeats and anything that needs more than a talk.
Get this workflow for your team
Two minutes each: everyone gets a plan of ready workflows like this one, inside your company's rules.
Your manager sees progress and hours. Never what Claude reads or writes.
FirstPrompt's workflow library adapts parts of Anthropic's knowledge-work-plugins (Apache-2.0), rewritten by FirstPrompt. Source and licence