The Case for Closing the Year With Money Still on the Table

Every November, a familiar conversation starts in UK project meetings. The forecast shows a contingency line with money still in it. Someone sensible asks what happens to the balance. Someone else, usually with the best intentions, says it seems a shame to leave it sitting there when there are useful things the team could do before year-end.

That is the moment to slow down. As we head towards the end of 2026, with budget cycles closing and next year's plans taking shape, the temptation to sweep unspent contingency into something visible is understandable. But contingency is not spare cash. It is a promise the organisation made to itself about uncertainty, and quietly breaking that promise has a cost that rarely appears on a spreadsheet.

A contingency line is a promise, not a prize

Contingency exists because projects do not unfold exactly as planned. It covers the supplier who delivers late, the approval that takes longer than expected, the technical issue nobody scoped properly, or the small change that turns into a larger one. It is budget held against risk, not budget waiting for a good idea.

When the money remains unspent, that does not mean the project was over-funded. It often means the risks did not land, or the team managed them without needing to draw down the full reserve. Either way, the correct conclusion is not that the project has won a prize. The correct conclusion is that the reserve did its job by being available and not needed.

I have seen this go wrong in a very ordinary way. A project reaches November with a healthy contingency balance. A few small extras get approved because there is room. A supplier is asked to bring forward a piece of work that was not really a priority. By the time the year closes, the money is gone and nobody can point to a meaningful improvement in the outcome. The project has not benefited. It has simply spent its safety margin.

The quiet damage of a year-end sweep

The real problem is not the individual spend. It is the lesson the team learns. If unspent contingency is routinely reallocated at year-end, people quickly work out that the safest way to protect their project is to spend the reserve before someone else does. That is how you get rushed purchases in December, low-value change requests in the final weeks, and a risk register that starts to look suspiciously empty because nobody wants to be the person holding an unused line.

There is also a governance point. Contingency usually sits inside an approved budget with an agreed purpose. Moving it to a different use without a proper decision blurs accountability. If the money was approved for risk, releasing it for new work should go through the same route as any other change. Otherwise the project has found a side door around change control, and everyone involved knows it.

None of this means contingency should become a sacred pot that can never be touched. If a genuine new risk appears and the sponsor or client agrees to use the reserve, that is exactly what it is there for. The distinction is simple: drawdown should be triggered by a documented risk or an approved change, not by the calendar.

A simple close-out rule

The rule I would use is this: unspent contingency can only be released against a named risk that has been retired, transferred, or formally accepted by the person who owns the consequence. If none of those apply, the balance returns to the organisation's central pot. It does not get reassigned to a project wish list because the year is ending.

In practice, that means a short close-out note with three things for each contingency drawdown or release:

• the risk or change it relates to;
• the decision-maker who approved the movement;
• what happens to any remaining balance.

That sounds formal, but it can be a one-page record. The point is not bureaucracy. The point is to make the conversation honest. If someone wants to use the remaining money, they should be able to say which risk has changed, which change request covers the new work, and who has accepted the trade-off.

What to say in the November meeting

When the question comes up, the useful response is not a flat no. It is a clear explanation of the principle. Something like: we are not releasing contingency because it is left over. We are closing it because the risks it covered are closed. If new work needs funding, bring it through change control and we will assess it on its merits.

That approach also gives the finance team a better story for 2027 planning. A project that closes with money on the table is not a failure. It is evidence that the reserve was sized sensibly and the team did not treat uncertainty as an excuse to spend. That is a far better signal than a flurry of December activity that nobody can quite justify in January.

The behaviour you reward is the behaviour you get

Budgets teach people how to behave. If the unspent balance is celebrated as a windfall, teams learn to spend it. If it is treated as a sign of control, teams learn to protect it. The difference will show up next year, when the same people are estimating risk and deciding how much cover to ask for.

So leave the money on the table. Close the year with discipline, not with a scramble. The contingency you did not spend is not a missed opportunity. It is the project proving it knew the difference between a reserve and a reward.