JHA drafted from the day's scope
Most job hazard analyses get written in a hurry. The crew is on site, the truck is unloaded, and someone has to fill out the form before the first task starts. So the form gets copied from...
The problem
Most job hazard analyses get written in a hurry. The crew is on site, the truck is unloaded, and someone has to fill out the form before the first task starts. So the form gets copied from yesterday, or from a similar job, with the date changed.
That is how a JHA written for trenching ends up in the folder on a day the crew is setting racking on a roof-adjacent ground mount and running a lift with a telehandler. The hazards on the paper don't match the hazards in the field.
The JHA and the toolbox talk are not the same thing. The JHA is the document: the tasks planned, the hazards in each task, and the controls that answer them. The toolbox talk is the delivery: the superintendent or foreman walking the crew through it before work starts, and the crew asking questions. A good talk needs a good document behind it. This workflow only helps with the document. The talk stays human.
How the agent workflow works
The agent reads two inputs each morning.
First, the day's scope. This comes from the schedule, the lookahead, or the daily plan: what tasks are planned, where, with which crews and equipment. It also reads the delivery list if one exists, since a material drop changes the day.
Second, a short voice note from the superintendent, thirty to sixty seconds, recorded in the truck. It covers what the schedule doesn't know: soft ground after rain, another trade working in the same area, a crane or lift planned, a new hire on the crew, an energized circuit nearby.
The agent transcribes the note and drafts a JHA with three parts: each task, the hazards tied to that task, and the controls. It also pulls in the company's own JHA template and last few approved JHAs for similar tasks, so the language matches what the crew already recognizes.
It flags two things at the top of the draft. One is any task in the scope with no matching hazard history. The other is any condition in the voice note that the schedule doesn't reflect, such as a lift mentioned in the note but absent from the plan.
The checkpoint is the superintendent. The draft goes to them before work starts. They correct it, add what the agent missed, strike what doesn't apply, and sign it. Nothing reaches the crew as a JHA until that sign-off. The superintendent then uses the approved document as the backbone of the toolbox talk.
What you need to set it up
- A place where the daily scope lives in text, such as a schedule export, a lookahead document, or a shared daily plan.
- A phone voice recorder, or a voice-note feature in whatever messaging app the crew already uses.
- An AI model that can take text and a transcript and produce a structured document.
- Your existing JHA template, plus a handful of past approved JHAs as examples.
- A rule for where the draft lands: an email, a message, or a shared folder the superintendent checks at the start of the day.
Setup time is a few hours, mostly spent cleaning up the template and gathering good past examples. The recurring cost is the AI subscription and whatever automation tool connects the pieces.
Where it breaks
The agent only knows what it is told. If the voice note skips the open trench behind the container or the overhead line at the north fence, the draft will skip it too. The note is the weak point, and it depends on a tired person talking in a truck.
Past JHAs can pull the draft the wrong way. If old documents carry a generic control that was never really enforced, the agent will repeat it with confidence. Review the examples before you feed them in.
The draft can look finished when it isn't. A clean, complete-looking page invites a quick skim and a signature. Superintendents who stop reading will end up with the same copy-and-paste problem, just better formatted.
Scope changes mid-day. A rain delay or a re-sequenced task makes the morning JHA out of date, and the agent will not notice unless someone updates the plan and runs it again.
Finally, the agent cannot judge site conditions it cannot see. It does not replace walking the work area.
The bottom line
This workflow turns a rushed form into a draft that starts from the day's real tasks. It saves the superintendent from writing from scratch, and it surfaces mismatches between the plan and what they know about the site.
It does not replace their judgment, and it does not replace the toolbox talk. The document is only useful if the person signing it reads it and the crew hears it. Treat the draft as a first pass, correct it hard, and walk the work before you sign.