A firm fixed contract works well when a public body knows the deliverable, can describe the scope without hand-waving, and wants a price it can plan around. In UK government operations, that usually means a fixed-price arrangement for outputs rather than a blank cheque for effort. I would use it when clarity matters more than flexibility, because that is exactly where the model is strongest - and where it can fail if the specification is weak.
What matters most at a glance
- Best fit: clear outputs, stable scope, and measurable acceptance criteria.
- Main benefit: budget certainty for the authority and a clean commercial structure.
- Main risk: vague specifications turn fixed price into a dispute magnet.
- Practical rule: if you cannot define the work, do not force a fixed-price model.
- UK context: contract management now matters more after the Procurement Act 2023 changes.
What people usually mean by a fixed-price contract
In practice, people use the phrase to describe a contract where the buyer agrees a price in advance and the supplier delivers a defined scope of work. In public procurement, the cleaner term is usually fixed-price or firm-price, and the commercial logic is simple: the buyer pays for the agreed outputs, not for the supplier's actual costs. Official UK guidance treats this as a contract based on a fixed value for completing outputs, usually paid on completion.
The real issue is not the label, but the structure. A fixed-price deal only works when the scope, acceptance criteria, and payment rules are already clear before delivery starts. If those pieces are vague, the supplier will either price in a risk premium or reopen the meaning of the scope later. I see that as the first test of any procurement exercise: can the requirement be understood by two different teams and still mean the same thing?
Once that logic is clear, the next question is where this model actually fits in government work.
When this pricing model fits government work
I reach for fixed price when the output is visible, measurable, and unlikely to change much during delivery. It is a strong fit for public-sector work where the authority needs cost certainty, the supplier can price the work with confidence, and the service can be described in plain language. That combination is common in government operations, especially where budgets are tight and approval chains are long.
- Standard goods with known specifications.
- Routine services with clear deliverables, such as scheduled maintenance or defined training.
- Projects where the volume of work is bounded and the acceptance point is obvious.
- Work that benefits from early market engagement before tender, so the scope can be tested.
If the quantum, meaning the volume or frequency of work, is unknown, fixed pricing becomes much less attractive. The same is true if the requirement is still evolving or the authority cannot estimate the baseline cost with confidence. In those cases, a more flexible mechanism is often the better commercial choice, and that trade-off takes us straight to risk allocation.
How risk shifts between the buyer and supplier
The best way to understand a fixed-price deal is to look at risk. For the buyer, the appeal is obvious: budget certainty, simpler approvals, and less exposure to open-ended costs. For the supplier, the deal only works if delivery stays inside the assumptions priced into the bid. UK commercial guidance is clear on this point: when services are defined as fixed price, the financial and operational risk of delivery moves from the client to the supplier.
| Risk area | Buyer impact | Supplier impact |
|---|---|---|
| Scope changes | Can trigger a variation and extra cost | Must price and manage change carefully |
| Inflation | May need an agreed indexation rule or revised price path | Absorbs pressure unless the contract allows uplift |
| Delivery efficiency | Benefits if the supplier works efficiently | Opportunity to protect or improve margin |
| Specification gaps | Risk of disputes, delay, or poor value | May push back on items that were not clearly included |
This is why a fixed-price contract is never just a pricing choice. It is a deliberate transfer of uncertainty, and the winner is usually the side that described that uncertainty most clearly before signature. The next step is comparing this model with the other payment structures public bodies actually use.
How it compares with other payment models
In UK public procurement, fixed price sits alongside several other ways of paying for work. The right model depends on how stable the requirement is, how easy it is to measure progress, and how much control the authority wants over spend during delivery. I find this comparison useful because teams often choose the model they know best, not the one that fits the work.
| Model | Best used when | Main strength | Main weakness |
|---|---|---|---|
| Fixed price | Outputs and scope are clear | Budget certainty | Weak specs create disputes or risk premiums |
| Service fee | Ongoing service is steady and hard to measure by output | Smoother cash flow | Less direct link to delivery |
| Staged payments | Work can be split into clear milestones | Good visibility over progress | Can become admin-heavy |
| Payment by results | Outcomes can be measured meaningfully | Aligns money with outcomes | Outcome measures can be contested or delayed |
| Cost-plus | Scope is uncertain or innovative | More flexible when baselines are unclear | Budget certainty is weaker |
For many government teams, the real decision is not fixed price versus nothing else. It is fixed price versus a model that better reflects uncertainty. If you force the wrong pricing structure onto the work, the contract usually tells you before delivery is finished.
How to structure one so it survives delivery
The contract itself needs to do more than state a price. It has to tell both sides what counts as done, what is excluded, and what happens when reality shifts. In my experience, the contracts that work best are the ones that make five things explicit from the start.
- A precise output specification. The scope should be specific enough that an unfamiliar reviewer could tell whether delivery passed or failed.
- Acceptance criteria. Define how the authority will test the work, who signs it off, and what happens if it fails first time.
- A short list of assumptions and exclusions. This is where hidden dispute risk usually lives.
- A formal change control route. Any variation should go through an authorised process, with price, risk, and timing updated together.
- An indexation rule, if the term is long enough to need one. If price movement is allowed, name the index and the trigger rather than leaving it vague.
I also like to see KPIs or service levels that match the outputs, not vanity metrics that look impressive but do not control quality. An SLA, or service level agreement, is simply the part of the contract that defines the standard of service the supplier must meet, so it belongs in the same conversation as price. Once those pieces are aligned, the contract becomes much easier to manage after award.
The mistakes that usually make the model fail
The contract type is not the problem most of the time. The problem is a sloppy buying process. These are the errors I see repeatedly in public-sector work.
- Vague requirements. If the specification is ambiguous, the supplier can argue that extra work sits outside the fixed price.
- Assuming volume is fixed when it is not. A stable unit price is not the same thing as a stable total cost.
- Loading too much risk onto the supplier. Push too much uncertainty across and you usually pay for it in the bid.
- Letting scope creep happen informally. Small unwritten changes are how fixed-price contracts lose control.
- Skipping market engagement. Early dialogue can reveal whether suppliers can price the work without building in a heavy premium.
The practical lesson is simple: if you want fixed price to behave well, you have to manage change as tightly as you manage price. That becomes even more important once the contract is live, because UK public contracts now sit in a stricter post-award environment than many teams are used to.
The checks I would run before signing off in 2026
Before I sign off a fixed-price public contract, I ask four questions: is the scope tight enough to price, is the evidence of acceptance clear, is the change process usable by real people, and is the risk transfer proportionate to what the market can actually carry? Around one-third of government spending is through contracts, so this is not a small procurement detail; it is core operational control.
- Can the requirement be described as outputs, not just effort?
- Do we know what success looks like on day one of delivery?
- Have we tested the spec with the market before award?
- Does the contract say how modifications will be handled if reality changes?
That last question matters more in 2026 than it did in the old let and forget era. Under the Procurement Act 2023, many post-award modifications must fit one of the permitted grounds, and if they do not, the authority may need to run a new procurement. So the real discipline is not just choosing a fixed-price model; it is making sure the contract can survive the lifecycle that follows. My rule of thumb is simple: use it when the work is clear, the outputs are measurable, and change can be controlled without improvisation. If those conditions are missing, another pricing model will usually deliver better value and fewer disputes.
