Milestones, staffing, hours against budget and scope change across the portfolio, aligned with the architect's and the owner's schedules.
A firm with many active projects across offices keeps its project facts in different places: milestones in one schedule, hours in the accounting platform, scope changes in email, the architect's dates in a meeting note. Principals see a problem late, and each project manager reports in a different shape.
This agent does the gathering. It reads the schedules, time and fee records and project correspondence your firm already keeps, assembles a status view per project and per discipline group, and flags deliverables at risk, hours running past budget and requests that look like additional services. It lines each project up with the architect's and the owner's schedules.
We connect the agent to the schedules, time records and project folders your project managers use, once your IT and security reviewers approve.
The agent assembles the status for each project, compares it with budget and the architect's schedule, and flags what drifts.
The project manager and principal in charge review each status and decide what changes. The firm's own corrections shape the next one.
A director of project management sees a medical center project slip in the architect's schedule. The agent lists the mechanical, electrical and plumbing deliverables affected and the hours still open on each. The principal in charge decides how to restage the team.
An operations leader needs to cover a data center design and a university laboratory from different offices. The agent lays the open deliverables against each discipline group's commitments. The discipline leaders decide who moves.
A project manager finds that owner requests for added smoke control studies have built up in email. The agent drafts a list of the requests with the scope language each touches. The principal decides which become additional services.
A principal reviews a mixed-use tower approaching its structural and fire protection budgets. The agent compares hours by phase with the plan and highlights where the gap opened. The principal and the engineer of record decide how to respond.
It reads the scheduling, time and project records your offices already keep, such as Microsoft Project, Deltek Vantagepoint or BQE Core, and the project folders your managers use. Your IT and security reviewers approve every connection.
No. It gathers, compares and flags. The project manager, discipline leaders and principal in charge decide staffing, scope and fee.
A reviewer your firm names, usually the project manager, reads each output. Principals see only what a person has checked.
One office or portfolio goes first. The same instructions are then fitted to the other offices as your leadership decides.
The instructions are updated to match the new format, and your reviewers check a sample before it is used on live projects.
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.