Safety meeting, prepped by an agent
The weekly safety meeting gets built in the truck, ten minutes before the crew gathers. The superintendent grabs a topic from a binder or a generic list, reads it off, and collects signatures....
The problem
The weekly safety meeting gets built in the truck, ten minutes before the crew gathers. The superintendent grabs a topic from a binder or a generic list, reads it off, and collects signatures. Meanwhile the work that week is trenching for conduit, setting racking on a new block, and running a telehandler between laydown and the array. The topic is heat stress. The real exposure is the excavation.
Last week's action items get lost too. Someone said the laydown yard needed a second exit marked. Someone was going to replace the damaged cord reels. Nobody wrote down who. By the next meeting the items are forgotten, and the crew notices.
The information to fix this already exists. It sits in the three-week lookahead, the daily logs, the incident and near-miss reports, and last meeting's notes. Nobody has time to read all of it and connect it before Monday.
How the agent workflow works
The agent runs on a schedule, once a week, usually Friday afternoon. It reads four inputs:
- The three-week lookahead schedule, focused on the coming week's activities.
- Daily logs and near-miss or incident reports from the past few weeks.
- Last meeting's notes, specifically the open action items and who owned them.
- Any delivery or inspection entries for the coming week, such as a crane pick or a utility tie-in.
From these it produces one draft document:
- A short list of the week's higher-risk activities, each tied to the schedule line it came from.
- A recommended main topic, with a reason. For example: two near misses involving vehicles in the laydown area, and deliveries doubling next week, so the topic is traffic control and spotters.
- A list of open action items from last meeting, marked closed, still open, or no information found.
- Two or three questions to ask the crew, drawn from actual events on the site.
The superintendent checkpoint comes before anything reaches the crew. The superintendent reads the draft Monday morning, cuts what doesn't fit, corrects anything wrong, and adds what the agent couldn't know. The agent never marks an action item closed on its own authority. It only proposes that, citing the log entry it found. The agent also sends nothing to the crew and signs nothing.
What you need to set it up
You need the schedule, logs, and meeting notes in a form the agent can read: shared documents, a field management app export, or a folder of files. If everything lives on paper or in someone's head, the first job is getting it digital.
You need an AI tool that can run on a schedule and read from those sources. That could be a workflow automation tool paired with a language model subscription. Expect a few hours for the first setup and a couple more for tuning the instructions after the first few drafts.
You need a fixed template for the output so the agenda looks the same each week. Write it once, and tell the agent to follow it.
You need one person who owns the review. That is the superintendent or the site safety lead. If nobody owns it, the drafts pile up unread.
Where it breaks
The agent only knows what was written down. If near misses are talked about but never logged, it will miss them, and it may recommend a topic that ignores the thing everyone is worried about. A thin log means a thin agenda.
Schedule activity names are often vague. "Site work" or "electrical" tells the agent nothing about whether the crew is energizing or pulling wire. It may guess, and a confident guess is worse than a blank.
It can misread action items. A log entry saying "cord reels swapped" might be read as closing the item when only one reel was replaced. This is why it proposes closure and does not decide it.
Schedules slip. If the lookahead is stale, the agenda matches work that is not happening. Check the schedule date in the draft.
There is also drift in the crew's attention. If the agenda comes out as the same format every week and the superintendent just reads it aloud, people tune out. The agent prepares the meeting. It does not run it.
Finally, the agent does not replace required safety training, site-specific plans, or regulatory requirements. It drafts a meeting, nothing more.
The bottom line
The agent does the reading and cross-referencing that nobody has time for on Friday. The superintendent keeps the judgment: what stays, what goes, and what the crew needs to hear. Done well, the Monday meeting covers the work actually happening, and last week's promises get followed up. The quality of the output depends on the quality of the logs, so the first improvement is usually better reporting on site.