After the Award: The Variations That Commit Public Money Without a New Tender

The award notice is a deceptively tidy document. It names a supplier, a value and a period. It suggests a decision has been taken and a price agreed. What it does not show is the life of the contract after signature: the variations instructed by email, the extensions agreed under delegated authority, the change requests that add sites, staff or software to a deal that was competitively tested on a narrower brief.

For public bodies, those adjustments are often necessary. Contracts rarely run exactly as planned. But the paper trail they generate is thinner than the one that preceded the award, and the scrutiny applied to them is frequently lighter. The result is that some of the most significant commitments of public money are made after the moment when competition and cabinet approval are supposed to have done their work.

The gap between notice and ledger

The Ferret reviewed a sample of 26 contracts awarded by four councils and two NHS trusts, matching published award notices against later spend data and, where available, responses to freedom of information requests. The sample was not statistically representative, but it was chosen to cover areas where variation is common: highways maintenance, adult social care, IT services, estates management and waste collection.

In most cases the final or current contract value exceeded the award value. The median increase was 14 per cent. In the top quarter of the sample it was 31 per cent. Two contracts had grown by more than 60 per cent. These were not necessarily examples of wrongdoing. Some reflected genuine changes in demand or unforeseen events. But they were rarely accompanied by a public explanation of the same quality as the original award notice.

The matching exercise itself revealed a problem. Spend data published by councils and trusts often records payments by supplier and invoice date, not by contract reference. Award notices record a value, but not always a unique identifier that can be followed through the finance system. Where contracts had been varied, the published notice was sometimes updated and sometimes not. In several cases the only way to establish the final figure was to ask.

How variation clauses work

Most public contracts include a variation clause. It typically allows the buyer to instruct changes to the scope, quantity, timing or specification of the services, with pricing governed by a schedule of rates or a agreed mechanism. Such clauses are lawful and often sensible. Without them, every minor adjustment would require a new procurement, which would slow down delivery and add cost.

Procurement law places limits on how far a contract can be modified without a new competition. The rules under the Procurement Act 2023, like those that preceded them, permit modifications on specific grounds. But the legal test is not the same as an operational one. A variation may be legally permitted and still represent a significant shift in what the public body is buying, from whom, and at what price.

The contracts in our sample varied in how tightly they defined the boundary. Some set out a clear schedule of rates and a maximum percentage increase. Others used broader language, allowing the authority to instruct “additional related services” or “reasonable changes to the scope”. Those phrases leave room for interpretation, and interpretation is where money moves.

Delegated limits and the quiet approval

Internal approval thresholds matter as much as the contract terms. Many councils and NHS trusts allow senior officers to approve variations up to a set figure—£50,000 or £100,000, for example—without returning to cabinet or board. These limits are designed to keep services running. But they are often applied to individual variations rather than to the cumulative total.

A contract awarded at £9m might receive twelve variations of £80,000 each over three years. Each one sits within officer delegated authority. Together they add nearly £1m to the commitment, and none of them requires the elected members or non-executive directors who approved the original award to look at it again. In one council in our sample, the delegated scheme allowed the chief officer to approve variations up to 10 per cent of contract value, but did not require the cumulative total to be reported back once that percentage had been reached.

This is not a loophole in the sense of something hidden. The thresholds are published. The variation decisions are sometimes recorded in officer decision logs. But they are dispersed across documents and rarely aggregated into a single view of how much a contract has grown. The public record shows the original tender and the final invoice, but not the incremental decisions in between.

Scope creep by another name

Some of the largest increases in our sample came under the label of “scope change”. An NHS trust awarded a digital services contract at £2.4m. By the third year, change requests had taken it to £3.9m. The additions included extra reporting modules, additional integration work and a new patient-facing portal. Each was documented. None was competitively tested. The trust told us the changes were necessary to meet clinical requirements and that value for money had been assessed internally.

A district council awarded a waste and recycling contract at £11m over seven years. The contract included an option to extend for a further three years. The council exercised the option, adding £5.1m. That extension was provided for in the original contract, but the pricing had not been fixed at the outset. The decision was taken by the council’s cabinet member for environment under delegated authority, with a report that ran to four pages.

These are not necessarily examples of failure. They are examples of how public money is committed after the competitive process has ended, through decisions that are lawful, documented and largely invisible to the public.

What scrutiny could look like

The award notice should not be the end of the paper trail. Public bodies could publish a variation register for each significant contract, showing the cumulative value of changes, the reason for each one, and the approval route taken. They could require that once a contract has grown by a set percentage, any further variation returns to the same committee or board that approved the original award. They could use a consistent contract identifier across award notices, spend data and decision logs.

Some of this is beginning to happen. The Procurement Act 2023 introduces new transparency requirements, and some councils are experimenting with contract registers that go beyond the statutory minimum. But the gap between the award notice and the final invoice remains a blind spot in the scrutiny of public spending.

The contract that grows is not an anomaly. It is a normal feature of public procurement. The question is whether the growth is visible, whether it is tested, and whether anyone outside the contracting authority can follow it. At present, the answer is often no. The second procurement happens in increments, and the public record rarely adds them up.