Why government stopped writing its own contracts, and what PPN 08/23 was really solving
PPN 08/23 looks like a housekeeping note. It replaced PPN 04/14 and PPN 06/14, listed three templates and asked departments to use them. Read the background section, though, and a sharper argument appears. The problem it set out to solve was not that bespoke contracts are expensive, although they are. It was that a government which contracts on inconsistent terms confuses its own suppliers and quietly loses the ability to make policy stick through its contracts.
The real cost of bespoke drafting
The note lists the direct costs first: additional expenditure, more negotiation and resource time, departments reinventing contracts that already exist. Those are the arguments finance directors respond to, and they are real.
But the more interesting risk is the next one. Bespoke drafting risks failing to include contractual clauses in support of government policies. Every policy that lands through contracts, whether payment practice, carbon reduction or supply chain transparency, depends on a clause existing in the agreement. A department writing its own terms is a department that can quietly omit those clauses without anyone noticing until it matters.
Then there is the supplier-side cost. Inconsistent policy positions confuse suppliers and create inefficiency through additional clarification questions. Every hour a bidder spends deciphering unfamiliar terms is an hour not spent on the substance of the bid, and that burden falls hardest on smaller organisations without in-house legal capacity.
Standardisation as SME policy
The note is explicit that the suite is designed to create a level playing field for small and medium-sized enterprises. That framing is often missed, because standardisation gets discussed as a legal efficiency measure rather than a market access measure.
The logic is simple. A large supplier can absorb the cost of reviewing bespoke terms across dozens of bids. A ten-person firm cannot, and will either price the risk in, decline to bid, or sign something it does not fully understand. Familiar templates reduce all three outcomes.
It follows that heavy local amendment erodes the benefit even when each individual change is defensible. A template that has been reworked until suppliers must review it line by line is functionally a bespoke contract wearing a familiar cover.
What has changed since
PPN 08/23 has been updated by PPN 013, issued in February 2025 to align with the Procurement Act 2023 and the Procurement Regulations 2024, then revised in April 2025. The April revision matters most: it expanded use of the Short Form Contract to non-complex goods and services above the relevant thresholds, where proportionate and appropriate and within limits each organisation sets.
That directly overturns the line in PPN 08/23 that the Short Form Contract should not be used for above threshold procurements. Anyone still working from the 2023 note for a live procurement is applying a restriction that no longer exists.
PPN 08/23 anticipated this. It stated that the suite of Standard Contracts is updated periodically and that the note would cover each future iteration. That was a sensible piece of drafting, and it is a useful reminder that the templates themselves, not just the notes about them, move over time.
What to take from it now
Use the current note for live work, but keep the reasoning from this one. The selection logic of value, complexity, likely negotiation and tiering has not changed, and it is still the fastest way to land on the right template.
Check the framework question first, as the note does. Standard Contracts are for bespoke purchases or those a suitable government commercial tool cannot handle. Reaching for a template when a framework already covers the requirement adds work rather than saving it.
Remember that the exceptions are legitimate. The note accepts that Standard Contracts need not be used where a more suitable form exists, naming departmental terms attached to purchase orders for very low value work, a government framework, and industry-specific contracts such as those used in construction. Standardisation is not a rule to be applied where it makes no sense, and pretending otherwise gives the policy a bad name internally.
And track how your organisation actually uses the suite. Adoption rates by template are a far better indicator of whether standardisation is working than any policy statement, and they usually reveal where local drafting habits have survived a policy that was meant to end them.
The takeaways
- PPN 08/23 replaced PPN 04/14 and PPN 06/14 and established the three-template suite.
- Its ban on using the Short Form Contract above threshold has been relaxed by PPN 013 as revised in April 2025.
- Bespoke drafting risks omitting the clauses that make government policy operative.
- Standardisation is an SME access measure as much as a legal efficiency one.
- Heavy local amendment recreates the problem the suite was designed to remove.
Want the full breakdown?
The complete explainer covers the key facts, the requirements in detail and a practical action list, free and printable in the Procurement Library.