Originally published at Agents in the Trades, a daily library of real AI agent workflows from solar, construction, and field operations.
Before the crew mobilizes, an agent assembles the day in one page — weather, crew, deliveries, and open loops sorted into Must, Should, and Could — so the superintendent starts with decisions made, not tabs open.
The numbers: 30–45 min/day saved (typical) · Medium setup difficulty · Run by the superintendent
The problem
A superintendent's first hour is a scavenger hunt. Weather is in one app, the crew count in a text thread, deliveries in email, inspections on a calendar, and yesterday's unfinished business in his head. By the time it sits in one place, the crew is already waiting — and the day has started reacting instead of executing.
The cost is what slips while he gathers: a delivery moved to the afternoon, a wind window that closes at noon, an item the office has awaited since Tuesday. None of it is hidden. It is just scattered, and scattered information gets found late.
How the agent workflow works
Overnight, the agent pulls the pieces together: jobsite weather, the calendar, the crew roster and any call-outs, scheduled deliveries and inspections, and open items carried from prior days.
It checks weather against the work, not just the forecast — wind, heat, and lightning flagged against the planned scope, especially rooftop or lift work, with the risky window named plainly.
It sorts the day into Must, Should, and Could. Must blocks the crew, an inspection, or a delivery today. Should keeps the week on track. Could can wait without cost.
It adds the human layer: who is waiting on a reply, what changed overnight, and the one highest-leverage move — the action that unblocks the most work if it happens first.
The brief lands before the day starts as one short page, in the same order every morning. Quick wins are marked separately from deep work.
The superintendent edits, not assembles. He corrects the order, kills anything stale, and adds what only he knows. The agent never sends or promises anything on the back of the brief — it prepares the day; he runs it.
What you need to set it up
- Sources the agent can read each night: a calendar, an email inbox, the crew roster, and a weather source for the jobsite. A paper notebook stays invisible until someone types it in.
- Your priorities written down once: what counts as Must on your jobs, your weather thresholds, and who counts as waiting too long.
- A running open-items list the agent can carry forward. It can start as a simple document — the brief is only as current as that list.
- An agent platform connected to those sources. Cost is honest: a few hours of setup, plus agent tooling you already pay for — no new project software required.
- A fixed delivery time — one message, before mobilization, every workday. A brief that arrives after the toolbox talk is trivia, not a tool.
Where it breaks
The brief is only as good as its inputs, and field inputs go stale fast. A call-out phoned in at 5:40, a delivery rescheduled in a call the agent never heard, a scope change agreed at the trailer door — none of that is in the overnight pull, so the brief can be confidently out of date by sunrise.
Weather is the second limit: a forecast is a probability, not a call, and go or no-go on wind or lightning stays with the superintendent on site. The Must, Should, Could order is also a judgment; the agent will sometimes rank the loudest email above the quiet item that actually blocks the crew. Read it like a draft from a good assistant who was not on site yesterday — usually right, always worth a sixty-second check.
The bottom line
Best fit for superintendents and foremen running traveling crews and a day that starts before the office does. It does not manage the job. It hands you the job, already gathered and sorted, early enough that your first decision is a decision — not a search.
More real agent workflows from the field — what each does, what it costs, and where it breaks — at Agents in the Trades, with a weekly newsletter at daroys-newsletter.beehiiv.com.
