The recurring coordination meeting is where mechanical, electrical, plumbing, structural and fire protection groups find out whether their drawings still agree. The meeting itself is short compared with the preparation behind it. Someone gathers the open clashes, the latest model exports, the outstanding requests for information and the changes each discipline issued since the last session. In most engineering practices that someone is a project engineer who would rather be designing.
An agent built on Claude can take over the gathering, and only the gathering. A named reviewer on the project checks the packet before it goes to the room, and the discipline leads decide everything that is decided. What follows walks the agenda in order and shows what the agent prepares for each item and what stays with people.
Item One: Changes Since the Last Meeting
Each discipline lead usually arrives with a private sense of what moved. The agent reads the issue log, the revision clouds and the transmittal records the practice already keeps, and drafts a single list of what changed, grouped by the discipline that changed it. It cites the sheet and the revision for every line so a lead can verify in a moment.
The list is a draft. A lead who sees a change the agent missed, or one it mislabeled, corrects it before the room sees it. The correction is the useful signal, because it tells the reviewer where the source records are thin.
Item Two: Open Clashes and Their Owners
The clash report from the coordination model arrives as a long export. The agent sorts it by location and by the pair of disciplines involved, merges duplicates, and marks the ones that appeared in the previous report and were never closed. It proposes an owner for each, based on who has historically resolved that type of conflict on the project.
It does not assign anyone. The proposal is a starting point for the lead who chairs the meeting, and the chair can overrule it in a sentence.
Item Three: Requests for Information Waiting on Design
Some requests sit in the queue because nobody on the design side has answered them. The agent lists those that touch more than one discipline and drafts a one paragraph summary of what is being asked and what each discipline would need to see to answer. It leaves the answer blank. A response that carries the seal of an engineer of record is written by the engineer.
Item Four: Code and Standards Questions
When two disciplines read a provision differently, the argument is rarely about the text. It is about which edition applies and which jurisdiction's amendments govern. The agent pulls the edition and amendments the project record names, sets the provision beside each discipline's stated assumption, and flags where they diverge. It makes no interpretation. The leads settle the reading, and the authority having jurisdiction settles it for everyone else.
Item Five: Decisions Taken
This is the one item the agent does not prepare in advance. During the meeting a person records each decision and its owner. Afterward the agent turns the notes into minutes, lists the actions by discipline and drafts the reminders. The reviewer reads the minutes against the notes before anything leaves the practice.
What the Packet Changes
The room spends less time reconstructing history and more time on the conflicts that need an engineer's judgment. The preparation effort moves from the project engineers to the reviewer, whose work is checking rather than collecting. That shift needs attention in its own right: a reviewer who stops reading carefully turns a draft into an unchecked document, and the practice should decide who reviews and how closely before the first packet is produced.