Change ordermanagement
A change order is not money until it is signed.
Every change to the work is money in one of three states. Recovered, once it is signed. Pending, while it waits for approval. Or absorbed, when the work gets done and no change order is ever raised. Managing change orders is knowing which is which, before the margin quietly leaves the job.
What change order management is
Change order management is the discipline of following every change to the scope of work, from the moment it is identified through to a signed change order, and keeping the recovered, pending, and absorbed value apart so the exposure still at risk is always visible.
It is a project controls function, not paperwork. An unmanaged change moves the budget, the forecast, and the margin at the same time. A signed change order raises the contract value; a pending one is revenue that may never arrive; an absorbed one is cost with no budget behind it. Treat all three as one net number and every figure downstream is quietly wrong.
The four states of a change
Change value moves through stages, and what it means for the money is different at each one. The controls job is to treat each state honestly rather than wait for the signed total at the end.
| Stage | The change value here is… | Controls treatment |
|---|---|---|
| Identified | A change is known but not yet priced. | Log it. It is exposure, not yet a booked number. |
| Priced / submitted | Costed and sent to the owner for approval. | Pending. Forecast it as at-risk, never as booked revenue. |
| Approved (signed) | The owner has signed; the contract value increases. | Recovered. Now real revenue and real budget. |
| Absorbed | Extra work performed with no change order raised. | Lost margin. Cost with no matching budget line. |
A worked example
A job carries $2.4M in identified change value across its open changes. $1.5M has been signed and added to the contract; that is recovered, and it is the only part that is truly revenue. Of the rest, $0.6M is priced and sitting with the owner for approval, still pending, and $0.3M has already been absorbed into the work with no change order raised. Until the pending value is signed it is not revenue, it is margin at risk; and the absorbed value is already gone, hiding on a cost report as spend against a budget that was never increased. Report the signed net alone and the number looks fine. Split it three ways, and the exposure is obvious.
Where the change value splits
All the identified change value flows in from the left, then forks three ways. The green stream is recovered, signed and added to the contract. The amber stream is pending, priced but still waiting on approval. The red stream is absorbed, work done with no change order behind it. The width of each fork is the money that went that way.
Notice is half the battle
Most contracts require written notice of a change, and often a claim for added time or cost, within a fixed and short window of discovering it. The clock is strict. Miss it and a legitimate, well-documented cost can be barred from recovery entirely, no matter how sound the work or the pricing.
That is why notice tracking belongs inside change order management, not in a separate reminder somewhere. A change that is identified but not noticed in time is already halfway to absorbed. The discipline is to log the change the day it appears, start the notice clock, and carry it forward until it is either signed or formally resolved.
A single signed total hides how much value is still in motion. The view below carries the change pipeline from identified through to signed, with the value and the count at each stage, so the reader sees the exposure that has not yet converted, not just the part that has.
PCO Pipeline Funnel
PODPCO pipeline
Conversion
Pipeline
Four ways it goes wrong
Counting priced-but-unsigned change orders as contract value inflates the forecast. If the owner rejects them or negotiates them down, the revenue you already reported never arrives.
Doing the extra work without raising a change order buries the cost against an unchanged budget. It then reads as a productivity or estimating problem, when it was really a contract one.
Most contracts require written notice of a change within a fixed window. Miss it and a legitimate, well-documented cost can become unrecoverable, whatever the merits of the work.
Reporting change orders as one net number hides the pipeline. Recovered, pending, and absorbed value each behave differently, and rolling them together conceals the value still at risk.
A change log at closeout vs every period
Change exposure is only worth anything while there is still time to chase a signature or raise a notice. The difference between a log you can act on and one you cannot is entirely about when the pending and absorbed value gets separated out.
- ·The change log lives in a spreadsheet updated when someone remembers
- ·Signed, pending, and absorbed value are rolled into one net number
- ·Notice deadlines are tracked by memory, not by the system
- ·Exposure surfaces after the owner has already responded, or not at all
- ·POD reads the change order log your job already produces
- ·Each change is tracked from identified through to a signed change order
- ·A signed change flows through to the budget and the forecast baseline
- ·The value still pending is visible every period, not at closeout
POD reads the change order log your job already produces, tracks each change through to a signed change order, and flows a signed change through to the budget and forecast baseline, so the value still pending stays visible. It pairs with budget vs committed, the estimate at completion, and earned value management. A change order touches all three at once.
The project controls library
The pillar guide: where change and trend management sits among cost, schedule, and earned value.
The buy-out buffer a signed change order protects, and the contingency an absorbed one quietly drains.
Where pending and absorbed change value distort the forecast if they are booked before they are signed.
How a signed change order moves both the contract value and the earned position on the billing side.
Absorbed changes are one of the quietest ways a job goes over without a single line looking wrong.
A signed change resets the budget at completion every EAC and CPI figure is measured against.
Change order questions
What is change order management in construction?▾
Change order management is the discipline of tracking every change to the scope of work from the moment it is identified through to a signed change order, and keeping the recovered, pending, and absorbed value separated so the exposure still at risk is always visible. It is a project controls function, because an unmanaged change directly moves the budget, the forecast, and the margin.
What is the difference between a change order and a potential change order (PCO)?▾
A potential change order (PCO), sometimes called a proposed change order, is a change that has been identified and usually priced but not yet approved by the owner. A change order is the signed instrument that formally amends the contract value. The distinction matters for controls: a PCO is pending value at risk, while a signed change order is recovered value that has become real revenue and budget.
What does it mean to absorb a change order?▾
Absorbing a change means performing the extra or altered work without a change order raised or approved, so the cost lands against the original budget with no matching increase in contract value. It is the most damaging outcome, because the money is gone but nothing in a standard cost report looks wrong. The overrun hides as spend on a budget line that was never adjusted.
How do change orders affect the budget and forecast?▾
A signed change order increases both the contract value and the budget at completion, so it resets the baseline that earned value, CPI, and the estimate at completion are measured against. Pending changes should be forecast as at-risk, not booked. Absorbed changes are pure cost with no budget behind them, which is why treating all three the same way distorts every downstream number.
What is the notice requirement for a change order?▾
Most construction contracts require the contractor to give written notice of a change, and often a claim for time or cost, within a fixed number of days of discovering it. The window is short and strictly enforced. Missing it can bar recovery of an otherwise legitimate cost, which is why notice tracking belongs inside change order management, not beside it.
How does POD help manage change orders?▾
POD reads the change order log your job already produces and tracks each change from identified through to a signed change order, per project, so the value still pending is visible every period rather than at closeout. Because the same platform holds the budget, the earned value, and the forecast, a signed change flows through to the budget and forecast baseline instead of being re-keyed by hand.
POD keeps change value separated
Begin with the free budget tracker, then let POD read the change order log already moving through your jobs, so the value still pending stays visible every period rather than at closeout.