Project mail and RFIs sorted across disciplines, coordination with the architect, construction manager and trade contractors, minutes and one decision record per project.
On a building project the mechanical, electrical, plumbing, structural and fire protection groups share one flood of mail: RFIs from trade contractors, plan review comments from the AHJ, requests from the architect, minutes from coordination meetings. Items reach the wrong discipline, decisions are made in email, and the record of what was decided lives in no single place.
This agent does the routing. It sorts project mail and comments by discipline and drawing sheet, drafts replies and transmittals for the responsible group, writes meeting minutes and action items, and keeps one decision record per project. It works with the architect, the construction manager and the trade contractors as the other parties on the project.
The discipline leader decides each reply, and a named reviewer checks it before it goes.
We connect the agent to the project mail, document control and meeting records your teams use, once your IT and security reviewers approve.
The agent sorts and drafts, and flags every item it could not assign and every decision that conflicts with an earlier one.
The responsible engineer reviews each reply, and the decision record becomes the project's history.
A project manager receives plan review comments on a mixed-use tower. The agent sorts them by discipline and sheet and drafts a reply for each. The fire protection, structural and mechanical leaders decide the responses.
A coordination lead runs a coordination meeting between the design team, the construction manager and trade contractors. The agent drafts the minutes and action items by discipline. The project manager confirms them before they are sent.
A construction administration manager sees RFIs that involve both medical gas and emergency power. The agent routes each to the groups that own it. The discipline leaders decide the answers.
A principal wants a single record of what was decided on a terminal project. The agent assembles it from mail and minutes and flags conflicts. The principal in charge decides which decisions stand.
It reads the project mail, document control and meeting records your offices use, such as Newforma, SharePoint or Bluebeam, as your IT and security reviewers approve.
No. It drafts, sorts and flags. A named engineer reads and sends each reply.
The discipline leader or project manager your firm names reviews each draft before anything goes to the architect, owner or contractor.
Yes. A rollout can begin on active projects in one office and extend to others, as your leadership sequences it.
Each comment is routed to every group it touches, with the sheets and references listed, so the answers can be reconciled.
The templates and instructions written for your firm are yours. Project data stays under the terms of the Claude plan your firm chooses, reviewed with your IT lead before connection.