The change, on the record in hours.
A potential change order carries the RFI answer, drawing revision or delay that caused it from the moment it opens. Priced off your own cost history, routed to the people who sign, executed in a median of 3.8 days.
What it does
A change opens from the thing that caused it — an RFI answer, a revision to sheet A-402, a delay logged in a daily log, a field directive — and the cause travels with it for the rest of its life. Pricing loads the unit rates from jobs you have already built, so the estimator starts from a number instead of a blank sheet.
Routing is the part that usually costs the month. Each change carries its approval chain — PM, cost manager, owner's rep — with the clock running on every step and reminders that do not depend on someone remembering. Scope already priced on another change or covered by an open commitment is flagged before it goes out twice.
How it works
- 01
Open it from the cause
Every change starts from a record the job already holds: an RFI answer, a drawing revision, a delay, a directive. The link is permanent, so the reason survives the hand-off and the argument.
- 02
Price from your history
Line items arrive pre-priced from what the same scope cost you before, with the source jobs listed beside each rate. The estimator adjusts what is different about this one; they do not start over.
- 03
Route and execute
The approval chain runs in order with elapsed time on each step. An executed change lands in the budget as approved change and in the general ledger on the next 15-minute sync.
Spec
- OPEN PCO
- 62 / JOB
- PCO → EXECUTED
- 3.8 D MEDIAN
- PRICING SOURCE
- OWN COST HISTORY
- DUPLICATE SCOPE
- FLAGGED PRE-ROUTE
3.8D
Median change order, potential to executed