Spots the change event.
Reads daily logs, meeting transcripts, RFI replies, owner emails. Flags directed work, scope adds, design changes, schedule impacts. The trigger comes to you, not the other way around.
Reads emails, meeting notes, and field reports for change events. Drafts the PCO with a cost basis. Tracks the chain from PCO to COR to executed CO. Mirrors approved owner COs to your sub commitments.
Reads daily logs, meeting transcripts, RFI replies, owner emails. Flags directed work, scope adds, design changes, schedule impacts. The trigger comes to you, not the other way around.
Labor hours, material, equipment, sub pricing, markup. Pulled from your cost codes and current vendor pricing. Time impact analysis when the schedule's affected.
PCO submitted. COR submitted. Owner review. Executed CO. Each stage tracks aging, owner contact, last touch. Stalled items get a nudge.
Owner CO executed for added scope? The agent drafts the corresponding sub CO against the original commitment, routes for sub signature. Owner-to-sub gap closes itself.
It reviews sources such as daily logs, meeting notes, RFI responses, and project emails for directed work, scope additions, design changes, and schedule impacts that may require a change order.
The agent can assemble the cost basis using labor, material, equipment, subcontractor pricing, markup, and relevant cost-code information. Your team reviews the draft before it moves forward.
Yes. It tracks the progression from a potential change order through customer review and execution, including aging, status, and the last follow-up.
When an owner change is approved, the agent can prepare the corresponding subcontractor change against the original commitment and route it for review and signature.
A 20-minute walkthrough where we run the change order clerk on a sample of your active jobs. You see the PCOs surface themselves.