Exemptions are a decision you have to defend, not a shortcut you get to take

What an exemption actually switches off

An exempted contract is one to which the rules on covered procurement do not apply. That is the whole effect, and it is narrower than the way exemptions are often described internally. The covered procurement rules stop applying. The Act has a wider definition of procurement that continues to reach exempted contracts for specific purposes, so exempt does not mean unregulated.

It also does not mean unaccountable. An authority still spends public money, still has to reach a defensible commercial decision, and still has internal governance and audit obligations that the Procurement Act has nothing to do with. Teams that treat an exemption as removing all constraint tend to discover the remaining constraints from an auditor rather than from a procedure note.

What most organisations get wrong

The most common problem is timing. Exemptions get identified when a team is already committed to an outcome and looking for a route that fits. Reasoning that arrives after the destination has been chosen is reverse engineered, and it reads that way to anyone reviewing the file later.

The second problem is vagueness. Files often assert that a contract was exempt without naming the Schedule 2 category or setting out the facts that bring the contract within it. That is not a record of a decision, it is a record of a conclusion. If a supplier challenges the award, the difference between those two things is the case.

The third is drift. A contract can be correctly exempted on day one and quietly stop fitting the category as it is varied, extended and expanded over several years. Nobody revisits the original assessment because the original assessment was filed as a completed task rather than a live position.

The fourth is bundling. Where exempted and non exempted elements sit in one requirement, wrapping the lot in the exemption is the single most challengeable move available, and it is common precisely because it is convenient.

What to do about it

Build the Schedule 2 check into the start of every procurement as a positive question with a recorded answer, including where the answer is that no exemption applies. That normalises the assessment and removes the sense that reaching for an exemption is an unusual move requiring justification only when it succeeds.

Insist on named categories. One line stating which exemption is relied on, three or four lines of supporting facts, and a named decision maker is enough. It takes minutes to write while the reasoning is fresh and is worth a great deal if the award is questioned.

Report on exemption use at portfolio level. Exempted contracts sit outside the competed pipeline, which means they are invisible in most procurement reporting, which means nobody notices when a team starts relying on them routinely. Visibility is the control that actually works here.

And revisit the position at variations. If the contract has grown into something the original exemption was never assessed against, that is the moment to look again rather than at the end of a five year term.

The takeaways

• An exemption disapplies the covered procurement rules, not every obligation in the Act.
• The stated rationale is narrow: freedom to procure appropriately where the rules would be unsuitable.
• Name the Schedule 2 category and record the supporting facts before entering into the contract.
• Bundling non exempted work into an exempted arrangement is the most challengeable pattern there is.
• Track exemption use across the portfolio, because exempted contracts are invisible in normal pipeline reporting.

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.