Basis of design, criteria and calculation package documents that stay consistent with the drawings and schedules, across every discipline group and office.
When several offices issue SD, DD and CD submissions, the documents around the drawings drift apart: a criteria narrative that no longer matches the schedules, a calculation package assembled by hand from different templates, a code analysis record written in a format only one group uses. Leaders learn of the gap when a reviewer finds it.
This agent does the assembly. It works from the firm's templates and the project's own files, drafts basis of design and criteria narratives, builds calculation package covers and indexes, keeps specifications in step with schedules, and flags every place where a document and a drawing disagree. It covers mechanical, electrical, plumbing, structural and fire protection groups on the same pattern.
It does not run the analysis, size equipment or interpret a code. The engineer of record decides what each document states, and a named reviewer reads every draft before it moves.
We connect the agent to the project folders, models and templates the discipline groups already use, once your IT and security reviewers approve.
The agent assembles each document, compares it with drawings and schedules, and flags every disagreement and blank it could not fill.
The engineer of record or discipline leader edits and approves each document, and the corrections go back into the firm's templates for the next project.
A group of discipline leaders is starting design development on a university science building. The agent drafts the mechanical, electrical and plumbing narratives from the owner's requirements and the firm's last laboratory project. The leaders resolve each flagged item, including lab exhaust and emergency power, before the architect receives it.
A structural team closes the calculations for an arena roof and a transfer structure. The agent builds the cover, index and input summary from the analysis files. The author reads every figure against the model before the package is bound.
A fire protection group is preparing a high-rise submission. The agent compares the hydraulic calculation sheets with the sprinkler zones on the drawings and lists each place they differ. The engineer of record decides which side is corrected.
A project manager prepares the CD set for a hospital addition. The agent checks that each discipline's narrative, schedules and specification sections cite the same equipment tags and flags the rest. The principal in charge signs off the open-items list before issue.
It reads the project folders, model exports and templates your offices already use, such as Revit, Bluebeam, SharePoint or Newforma, and the analysis outputs your engineers save. We connect only what your IT and security reviewers approve.
No. Calculations, equipment selection and code interpretation stay with your engineers. The agent assembles text, packages and comparisons from files your engineers have produced.
A reviewer your firm names reads each draft, and the engineer of record decides what the document states, signs and seals it. The agent does neither.
Each discipline group's templates become instructions of their own. One group goes first, and the same pattern is fitted to the other groups and offices as your leadership decides.
Your standards and templates are held in a Claude Project or a connected folder. When they change, the instructions are updated, and the next drafts follow the new text after your reviewers check it.
The templates, instructions and documentation 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.