AI for Superintendents: End the Status Chase

Spend a day shadowing a superintendent on any commercial job and you will notice something odd. Very little of the day is spent superintending. Most of it is spent answering questions, and most of the questions have answers that already exist somewhere.

Below are five questions pulled from one actual Wednesday. Each one interrupted real work. Each one had an answer sitting in a system that nobody could get to fast enough.

"Did the steel show up?"

Asked by the project manager, from the office, at 7:40 am. The delivery ticket was signed at 6:55 and photographed by the receiving foreman, who put the photo in his phone, where information goes to retire. The PM needed the answer to release the erector's mobilization. The super walked to the laydown area to check with his own eyes, because that was genuinely the fastest available method.

Total elapsed: eleven minutes. Times per week this class of question arrives: dozens.

"Did we pass the inspection?"

Asked by the drywall sub's PM at 9:15, about yesterday's framing inspection on level two, because his crew is loaded for board delivery and hanging cannot start until framing signs off. The inspection result was in the daily log, entered at 4 pm the previous day. The sub's PM does not have access to the GC's daily log, and would not think to look there if he did, because logs are where information is written, not where it is found.

"Is the change order for the lobby approved yet?"

Asked by the electrician's foreman at 11:00, whose crew will either rough-in the revised lobby layout this week or demobilize to another job for ten days. The change order sat approved in the owner's system since Monday. The approval notification went to the GC's PM, who was in a bank of meetings, and the update never made the jump from his inbox to the field.

The electrician demobilized. He came back twelve days later.

"What's the concrete schedule for Friday?"

Asked by the pump operator's dispatcher at 1:30, then again by the testing lab at 2:10, then a variant by the finishing sub at 3:00. Same answer, three retellings, three interruptions. The pour schedule existed. It lived in a spreadsheet updated Tuesday nights, emailed to a list that never quite matches the set of people who need it.

"Who moved my scaffold?"

Asked by the painting foreman at 3:45, with feeling. Nobody logged it. The masonry crew needed it, took it, and intended to mention it. The answer to this one genuinely did not exist anywhere, which at least makes it an honest question.

The pattern under the questions

Four of the five questions had recorded answers. What they lacked was retrieval. Construction has spent two decades digitizing its records, and the result is that the truth about a jobsite now lives in six systems, two spreadsheets, a group text, and the receiving foreman's camera roll. The superintendent became the human interface across all of it, which is why supers routinely report spending two to three hours a day just relaying status.

The fix that is starting to spread through the industry is not another system. It is a different kind of participant in the project channel. Teams have begun running agents that sit where the conversation already happens and can actually answer. The drywall PM types his framing inspection question into the shared job channel and an agent replies in seconds, pulling from the daily log, with the inspector's notes attached. The steel question never gets asked at all, because the agent watching deliveries posted the signed ticket to the channel at 6:57 and cross-checked it against the purchase order while it was at it. On one job I heard about, that cross-check caught a short shipment, forty pieces on the ticket against forty-four on the PO, and the agent flagged the gap to the PM before the truck left the gate. That discrepancy would previously have surfaced during erection, which is the most expensive possible moment to learn you are missing steel.

The change order story plays out differently too. An agent tracking the approval queue sees the owner's sign-off land Monday afternoon and immediately notifies the GC's PM and the electrical sub's PM, both of them, in the channel where the lobby work is being coordinated. If the human PM wants to add context before the sub acts on it, he has a window to do so. But the default is that approval news travels at the speed of the approval, not the speed of the PM's calendar. The electrician does not demobilize. The ten lost days do not happen.

Notice what the agent is doing in each case. It is not managing the project. It is not making judgment calls about sequencing or negotiating with subs. It answers, it watches, it relays, it flags. When something needs an actual decision, the crane conflict, the short shipment, the schedule slip, it puts the decision in front of the right human with the facts assembled. The judgment stays with people. The fetching stops belonging to them.

The judgment stays with people. The fetching stops belonging to them.

What the super does with the hours

Supers who work this way describe the change in almost embarrassed terms, because the hours they got back went to things that sound old-fashioned. Walking the deck. Watching the crews. Catching the blocked stair egress before the safety officer did. Coaching the young foreman who sequences his crew badly. The parts of superintending that require thirty years of scar tissue and a pair of eyes on the work.

That was always the job. Answering "did the steel show up" never was. It just paid the same and took half the day.

The scaffold, for the record, is still missing.