Defence procurement is not a separate rulebook, and treating it like one is the mistake
There is a persistent assumption in commercial teams that defence and security procurement runs on its own rules. The official guidance says the opposite in its first sentence: contracting authorities awarding defence and security contracts are generally governed by the provisions in the Act, just like any other contracting authority. The specific provisions exist to cater for what the guidance calls limited differences. Limited is the operative word, and it is the one that gets forgotten.
The exceptions have reasons, and the reasons are testable
The guidance gives two justifications for defence flexibilities, and both are factual claims about a specific procurement rather than general permissions. The first is that some provisions on equal treatment and openness might not be practical where the nature of the defence market limits the scope for competition. That is a statement about a market, and it can be examined. How many capable suppliers are there. What evidence supports the view that competition is not available.
The second is that some provisions may put at risk the UK's defence and security interests, with security of supply for critical defence supplies given as the example. Again, that is a specific risk that can be articulated for a specific requirement.
Neither reason supports a blanket approach. If a team cannot state which of these two situations applies to the contract in front of it, the derogation is being used out of habit rather than for the purpose the Act provides it.
What most organisations get wrong
The biggest failure is training. If your defence commercial team knows section 7 well and the rest of the Act loosely, you have the balance exactly backwards. The guidance is unusually direct on this, saying that authorities awarding defence and security contracts need to understand the whole of the Act, and naming competitive tendering procedures, conditions of participation and award criteria as areas where the same provisions apply.
The second failure is classification by convenience. Requirements that touch security get labelled defence and security because that label is more comfortable, not because the analysis supports it. That decision usually happens early, informally, and without a written rationale, which makes it the weakest point in the whole file if the award is ever challenged.
The third is mixed procurement. Modern requirements rarely arrive as pure defence packages. They combine platforms with support services, software with hardware, secure elements with entirely ordinary ones. The guidance flags mixed procurement, valuation, exemptions and thresholds as particularly relevant, which is a strong hint about where the real difficulty lies.
What to do about it
Make classification a formal, recorded step with a named decision maker. One page is enough: what the requirement is, why it does or does not fall within the defence and security provisions, and which related guidance was considered. That page is cheap to write in advance and impossible to write convincingly after the fact.
Then treat every derogation as an exception that has to earn its place. State which flexibility is being relied on, which of the two rationales applies, and what evidence supports it. Where only part of a requirement justifies flexibility, apply it to that part rather than the whole.
And invest the training budget in the general regime. The differences are limited by design. The bulk of what a defence commercial team does every day is governed by exactly the same rules as everyone else, and the gaps that cause problems are usually in the shared mechanics rather than the specialist ones.
The takeaways
- The general provisions of the Act govern defence and security contracts, with limited specific adjustments.
- Derogations exist for two stated reasons: markets with limited competition, and risks to UK defence and security interests.
- Competitive tendering procedures, conditions of participation and award criteria apply in the same way as elsewhere.
- Classification and mixed procurement decisions are the weakest point in most defence procurement files.
- Record which derogation is used and why, rather than applying flexibility by default.
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.