Capability template for health, safety and environment
Safety walk follow-up
After a safety walk, the manager gets a follow-up brief that ties each concern workers raised to the commitment the manager made, its owner and due date, and the message to give back. Gaps arrive as questions, never as guesses.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
People on the floor hear what happened to what they said. The manager walks away from the walk with every concern written down once, beside the commitment made for it, the person who owns it, the date it is due and a short message to give back to the people who raised it. A concern nobody has decided about is shown as exactly that, not left out.
The brief never turns a conversation into a promise. A concern that was discussed is not marked resolved, and a commitment is only what the manager said it is. Where an owner, a date, an owner's acceptance or a decision is missing, the brief asks the manager for it and holds the message until it is settled. The manager edits, approves and gives the messages; the AI assistant sends nothing and assigns nothing.
Who starts the work, and when
The manager who walked the site starts it, the same day or the next, while the walk is fresh: a site, plant, warehouse or operations manager, or the safety coordinator who keeps the record. Run it again at each agreed check-in with the current status of each commitment, so overdue items and finished items that have not yet been reported back to the workers are easy to see.
What they supply
- The walk notes. Each concern with a reference, the area, the role of the person who raised it and what was said. Roles, not names.
- The commitments the manager has decided, each with its reference, wording, owner, due date and whether the owner has accepted it. Concerns with no row stay open as decisions.
- The give-back date, when the manager will next speak to the people who raised the concerns, such as a shift briefing.
- At a check-in: the status of each commitment and the date its message was given.
What comes out
One brief in a fixed order. A header with the walk and the counts, then every concern with its commitment, owner, due date, whether the owner accepted, a drafted message to give back and any flag. Then the decisions the manager still has to make, the commitments grouped by owner, and, at a check-in, what is overdue, what is reported done but not yet told to the workers, and what is ready for the manager to close.
A good brief can be checked against the walk notes line by line, and each worker's concern can be found in it in the words they used.
An invented example
Illustrative example with invented data. Quillon Packing, the people and the concerns below are all invented. The inputs come first, then the brief.
What the manager supplies
Walk notes. Walk date Tuesday 3 November 2026. Manager's role: Operations manager. Areas walked: Goods-in dock, Packing hall, Maintenance workshop.
ref,area,raised_by_role,concern
C1,Goods-in dock,Night-shift forklift driver (the only driver on nights),The light at door 3 is out and the aisle is dark when the shift starts.
C2,Packing hall,Packer,Pallet wrap offcuts pile up by the line 2 exit and people could slip on them.
C3,Packing hall,Line supervisor (Mara),The line 2 emergency stop is stiff. Two supervisors have had to press it twice.
C4,Maintenance workshop,Maintenance technician,The label on the solvent cabinet is peeling and nobody is sure what is on the bottom shelf.
C5,Goods-in dock,Goods-in clerk,Delivery drivers walk through the forklift lane to reach the office.
C6,Packing hall,Packer,The break room is too warm in the afternoons.
Commitments the manager decided.
ref,commitment,owner,due_date,owner_accepted
C1,Replace the light at door 3,Maintenance lead,2026-11-06,yes
C2,Put a bin at the line 2 exit and add offcut clearing to the end-of-shift clean,,2026-11-10,
C3,Inspect and fix the line 2 emergency stop,Maintenance lead,2026-11-05,yes
C4,Relabel the solvent cabinet and list what is on the bottom shelf,Stores clerk,2026-11-13,no
C6,none. Reason: the break room moves to the new building in January,,,
Settings. Give-back date: Friday 6 November 2026, at the start-of-shift briefing. Today: Wednesday 4 November 2026. First run, no statuses.
The brief
SAFETY WALK FOLLOW-UP BRIEF: walk of Tuesday 3 November 2026
For: Operations manager. Areas walked: Goods-in dock, Packing hall, Maintenance workshop. Prepared: Wednesday 4 November 2026, from 6 concerns and 5 commitment rows, and no status file. Give-back date: Friday 6 November 2026.
Concerns: 6. Commitments stated: 4. Decided no action: 1. Awaiting decision: 1. Concerns flagged: 5.
C1, Goods-in dock. Raised by: Night-shift forklift driver (the only driver on nights).
Concern: The light at door 3 is out and the aisle is dark when the shift starts.
Commitment: Replace the light at door 3.
Owner: Maintenance lead. Due: Friday 6 November 2026. Owner accepted: yes.
Message to give back: "You told us the light at door 3 is out and the aisle is dark when the shift starts. The Maintenance lead will replace the light at door 3 by Friday 6 November 2026. If it has not happened by then, tell the Operations manager."
FLAG, needs attention now, role may identify the person: the concern describes a light as out and the aisle as dark, and the notes say there is one night-shift forklift driver. See decision 1.
C2, Packing hall. Raised by: Packer.
Concern: Pallet wrap offcuts pile up by the line 2 exit and people could slip on them.
Commitment: Put a bin at the line 2 exit and add offcut clearing to the end-of-shift clean.
Owner: not stated. Due: Tuesday 10 November 2026. Owner accepted: not recorded.
Message held: no owner stated.
FLAG, owner not stated: the commitment has a due date and no owner. See decision 3.
C3, Packing hall. Raised by: Line supervisor.
Concern: The line 2 emergency stop is stiff. Two supervisors have had to press it twice.
Commitment: Inspect and fix the line 2 emergency stop.
Owner: Maintenance lead. Due: Thursday 5 November 2026. Owner accepted: yes.
Message held: the due date, Thursday 5 November 2026, is before the give-back date, Friday 6 November 2026.
FLAG, needs attention now, due before the give-back date: the concern describes an emergency stop as stiff and needing two presses, and the due date is one day before the give-back date. See decision 2.
C4, Maintenance workshop. Raised by: Maintenance technician.
Concern: The label on the solvent cabinet is peeling and nobody is sure what is on the bottom shelf.
Commitment: Relabel the solvent cabinet and list what is on the bottom shelf.
Owner: Stores clerk. Due: Friday 13 November 2026. Owner accepted: no.
Message held: the Stores clerk is recorded as not having accepted.
FLAG, owner has not accepted: the commitment names the Stores clerk and the answer recorded is no. See decision 4.
C5, Goods-in dock. Raised by: Goods-in clerk.
Concern: Delivery drivers walk through the forklift lane to reach the office.
Commitment: No commitment decided.
Owner: not stated. Due: not stated. Owner accepted: not recorded.
Message held: no commitment decided.
FLAG, no commitment: nothing has been decided for this concern. See decision 5.
C6, Packing hall. Raised by: Packer.
Concern: The break room is too warm in the afternoons.
Commitment: None. Reason: the break room moves to the new building in January.
Owner, due date and owner accepted: not applicable.
Message to give back: "You told us the break room is too warm in the afternoons. Nothing will change from this walk, because the break room moves to the new building in January."
Decisions for the Operations manager: 5
1. C1, needs attention now and role may identify the person. The light at door 3 is out and the aisle is dark when the shift starts. The replacement is due Friday 6 November 2026. Is anything needed at door 3 before the light is replaced? The notes say the night-shift forklift driver is the only one on nights, so the message will be recognized as theirs. Do you give it to the driver directly, to the shift as a group, or both?
2. C3, needs attention now and due before the give-back date. The line 2 emergency stop is described as stiff, needing two presses. The inspection is due Thursday 5 November 2026 and the messages are given on Friday 6 November 2026. Is anything needed on line 2 before the inspection? The message is held: do you want it given earlier, reworded, or given on 6 November with the outcome of the inspection?
3. C2, owner not stated. The bin and the end-of-shift clearing are due Tuesday 10 November 2026 and no owner was supplied. Who owns this, and have they accepted? The message is held until you answer.
4. C4, owner has not accepted. The solvent cabinet relabelling and list are due Friday 13 November 2026 and the Stores clerk is recorded as not having accepted. Who will own this commitment, or will you speak to the Stores clerk first? The message is held until you answer.
5. C5, no commitment. The goods-in clerk says delivery drivers walk through the forklift lane to reach the office. Nothing has been decided. What, if anything, will you commit to, with which owner and by which date? Or do you decide to take no action, and if so, for what reason? The message is held until you answer.
Commitments by owner
Maintenance lead: C3, Thursday 5 November 2026; C1, Friday 6 November 2026.
Stores clerk: C4, Friday 13 November 2026.
Owner not stated: C2.
Decided no action: C6.
No commitment decided: C5.
Left out
C3: a person's name in the role cell, replaced by the role.
Draft for the Operations manager's approval. Nothing has been sent, assigned, recorded as resolved or changed. It states no regulatory duty and does not judge whether any commitment is enough.
Every concern, owner, date and reason in the brief comes from the notes, the commitments and the settings above. The counts: six concerns; four with a commitment (C1 to C4); one decided no action (C6); one undecided (C5); five flagged (C1 to C5). Two messages are ready to give (C1 and C6) and four are held (C2 to C5), each with its reason.
Where it fits
- Health, safety and environment, where promises made on the floor are the cheapest way to earn or lose trust.
- Operations and process improvement, where the person who runs the work also owns what is promised about it.
- Construction, where a site walk produces a long list on a short timeline.
- Manufacturing, where concerns come from several shifts and lines and are easily lost between them.
- Logistics and trade, where docks, yards and vehicles produce concerns that cross teams.
- Established businesses, where walks happen on a rhythm and the follow-up lives in someone's notebook.
It is not a risk assessment. Workplace risk assessment rates hazards and proposes controls. This capability keeps track of what the manager promised in response to what people said, and does not judge whether a promise is enough.
What has to change for your company
Decide how you refer to roles so that no one is identified, and who counts as too few to be named even by role. Set the give-back occasion and who gives the messages. Decide who may be an owner and how an owner accepts. Agree the statuses your team uses, and who alone closes a concern. Add the wording you want at the close of each message, such as how to raise it again. It states no regulatory duty; your competent person confirms what applies where you operate. It runs in ChatGPT, Claude, Copilot or Gemini from notes and files you supply, and needs no connection to any of your systems.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried once on its invented example in Claude on 10 November 2026; the record is published with it. That run was by the model that revised the template after an earlier trial and an independent review, so it is not an independent check, and it was a first run: the check-in path has not been tried. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on one or two past walks your manager remembers well, plus hard cases written in advance, each with its expected behavior: a concern with no commitment, a commitment with no owner, an owner who has not accepted, a name in the notes, a safety device described as not working, a due date earlier than the give-back date. The manager checks every line against the notes before anyone relies on it. Pilot acceptance-test preparation builds that test set, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: