No surprises is a process,
not a promise.

A project that only reports committed cost against budget is reporting history. Cost trending makes the forecast arrive before the commitment does, and it is the most under-used discipline available to an owner’s team.

Most report actuals and commitments against the control estimate, call the difference variance, and run the risk register as a separate exercise on its own cycle. Both are competent. Neither tells you what the project will cost while there is still time to react.

A risk, a trend and a committed cost are the same item at three stages of maturity. A risk is probabilistic and sits in the contingency model. It becomes a trend when you are certain it will occur — and not only as a change order: an internal overrun, an omission from the original budget, an insufficient allowance, additional staff, a claim.

The certainty test matters more than the number. If you are not sure it will happen it stays on the risk register, even if you can price it — approving a trend and then withdrawing it when the event never occurs teaches the team that the register is negotiable. Be sure it will be committed; you need not know the value yet.

• Unconfirmed. A potential impact has been identified, but there is not yet enough information to evaluate it and you are not sure it is real. It is early warning, and the team can be steered before anything is allocated. If it is a risk item it stays in the risk register.
• Uncommitted. The cost is estimated to reasonable accuracy, or the contract, change order or purchase order is being executed. Contingency is allocated, but nothing can be spent against it until the trend is committed.
• Committed. The estimate is firm, or the contract or purchase order is executed. The project can draw down contingency.

Only approved uncommitted and committed trends go into the forecast to complete.

Approved trends are added to the value from the discrete risk quantitative analysis — a Monte Carlo model run monthly — at whatever confidence level the company works to, P70 or P90, and to the equivalent schedule uncertainty analysis when slippage is possible. The total is compared with the approved contingency budget, and will sometimes exceed it.

What you act on is not a single month above the line, because the modeled value moves month to month; it is a sustained overrun. The first response is to spend a month re-ranking the top risks — initial rankings are usually conservative — and driving the mitigation actions to closure so consequence and likelihood come down. If the overrun survives that, re-evaluate the remaining budget for savings.

Cost and risk are therefore not two conversations. The trend register is where the risk process turns into money, and the reconciliation tells you whether the approved budget still holds.

Double counting, and it runs both ways. The same item sits in the contingency model as a risk and in the trend register as a trend, so the project carries the money twice and the forecast looks worse than the project is; a team that believes it takes cost out of scope that never needed touching. The reverse is quieter: a risk closed out because it has become a trend that is never raised, or contingency drawn down against something never trended.

Both have the same cause: two registers, two owners, and no reconciliation between them. One owner for both, line by line, every month before the cost report is issued.