The change pipeline is a leading indicator
Approved change is history. What predicts the outcome is the volume sitting unpriced, unagreed, and unreported — and the rate at which it is arriving.
Change reporting on most projects consists of one number: the value of variations approved to date, sometimes with a forecast of the total.
That number is a record of decisions already taken. It says nothing about the project's direction, because every change it contains has been assessed, agreed, and absorbed. The information that would predict the outcome sits behind it, in the items that have been notified and not yet resolved.
The stages that should be reported separately
A change moves through a sequence, and each stage carries a different quality of information.
Notified. An event has occurred, or an instruction has been given, that the contractor considers a change. No value, often no detail. This is the earliest signal available and it is almost never reported upward.
Submitted. A claim or quotation has been received with a value attached. The value is the contractor's opening position and should be read as such, but the population and the total are now measurable.
Under assessment. The submission is being evaluated. Time spent here is a cost in itself, because unresolved change affects sequencing and the commercial relationship.
Agreed. Value and time impact settled. This is the number that gets reported, and it is the only stage that carries no predictive content.
Reporting only the last stage means the project's exposure is described exclusively by what has already been resolved.
What the pipeline tells you
Four readings come out of a staged report, and none is available from a single total.
Arrival rate. Changes notified per month, plotted over time. A rising rate is the clearest early signal of an incomplete design or a deteriorating scope definition, and it typically leads the cost impact by a quarter or more.
Aging. How long items sit in assessment. A growing tail of old unresolved items is how a project accumulates a claim. Each individual item may be minor; the aggregate, assembled later with prolongation attached, is not.
Cause distribution. Whether change is arising from design development, owner instruction, site conditions, or contractor-initiated substitution. The mix says what is actually wrong. A pipeline dominated by design development points at a design that was released before it was ready — and predicts more of the same.
The unpriced total. The value of notified and submitted items not yet agreed. This is the number that belongs next to the cost-to-complete, because it is the part of the forecast that has not yet entered the committed position.
A project reporting five percent approved change and holding twelve percent unagreed is not a project with five percent change. It is a project that has not finished counting.
Why the pipeline goes unreported
Partly because it is uncomfortable. A notified change with no value is difficult to report without appearing to forecast a cost the project does not accept.
Partly because it is contested. Many notified items will be rejected, so reporting the submitted total looks like conceding the contractor's position. That objection is answerable by reporting the range — submitted value and the project's assessed value — rather than by reporting neither.
And partly because the data is held commercially rather than reported as management information. The commercial team knows the pipeline; the report the sponsor sees is generated from the approved ledger.
Reading it as an owner
Three questions extract most of the value from a change report.
How many items are open, and how old is the oldest quartile? Aging is the most reliable predictor of a claim, and it is the easiest thing to fix while the items are individually small.
What is the arrival rate doing? Three months of rising notifications is a design or definition problem, and it will not resolve itself. It is the point at which the remaining design should be reviewed for readiness rather than for compliance.
What is the unagreed total, at both parties' valuations? The gap between the two positions is the size of the negotiation the project is heading toward, and it should appear in the risk position rather than emerging at settlement.
Change is not a sign of failure. Every project of consequence has it. What distinguishes a controlled project is that the pipeline is measured while the items are small enough to resolve individually — which requires reporting the stages before the last one.
