RFIs, submittals and shop drawings, site observation reports, ASIs, commissioning support and closeout across every active project.
When several offices run construction administration at once, the same pressure repeats: RFIs and submittals from trade contractors arrive in different formats, site observations reach the file late, and a bulletin from the architect needs a response from three disciplines. The construction administration manager sees the backlog before the project team does.
This agent does the first pass. It sorts incoming RFIs and submittals by discipline and specification section, compares each against the contract documents, drafts a response with its references, assembles site observation reports from notes and photographs, and tracks open items through commissioning and closeout. It never decides whether a submittal complies.
The engineer of record or discipline leader reviews, responds and signs, and a named reviewer checks each draft before it goes to the architect, owner or contractor.
We connect the agent to the document control and submittal platforms your teams use and to the project's specifications, once your IT and security reviewers approve.
The agent sorts incoming items, compares each with the contract documents, and drafts a response or report with every reference and open question marked.
The responsible engineer reviews and sends each response. The corrections feed the firm's standard responses for the next project.
A construction administration manager receives a switchgear submittal for a data center. The agent lists each place the submitted data differs from the specification section. The electrical discipline leader decides what to accept and what to return.
A trade contractor sends several RFIs about riser routing in a hospital tower. The agent groups them, finds the related drawings and drafts a response for each. The fire protection and structural engineers of record decide the answers.
A structural team inspects transfer framing on a courthouse. The agent assembles the observation report from notes and photographs, carrying forward the items still open. The engineer who observed the work decides what the report states.
A CA manager prepares closeout for a university research building. The agent assembles the punch list, commissioning issues and record document status by discipline. The principal in charge decides when the file is complete.
It reads the submittal logs, RFI records and project folders your teams already use, such as Procore (the contractor's platform), Autodesk Construction Cloud, Newforma or Bluebeam, as your IT and security reviewers approve.
No. It compares text and flags differences. The engineer of record or discipline leader decides compliance and signs the response.
A reviewer your firm names reads every draft. Nothing goes to the contractor, architect or owner until a licensed engineer has read it and sent it.
Yes. A rollout can begin on projects that are mid-construction in one office and then extend to other offices, as your leadership sequences it.
Each discipline's review habits become instructions of their own. Mechanical, electrical, plumbing, structural and fire protection reviewers can each be added one at a time.
The agent works from the contract documents loaded for each project. When a bulletin or revision is issued, the reference set is updated and your reviewers check the next drafts against it.
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.