How do you write a compliant public sector procurement specification?

Writing a compliant public sector procurement specification means producing a document that clearly defines what your organisation needs, follows applicable procurement regulations, and enables suppliers to respond on a genuinely level playing field. In the UK, this means aligning your specification with the requirements of the Procurement Act 2023, which replaced the Public Contracts Regulations 2015 and came into full effect in 2025. The sections below answer the most common questions procurement professionals ask when drafting or reviewing a public sector tender specification.

What makes a procurement specification ‘compliant’ in the public sector?

A compliant public sector procurement specification is one that is outcome-focused, non-discriminatory, proportionate to the contract value, and written in a way that does not favour or exclude any particular supplier. It must align with the relevant procurement legislation and, where applicable, reflect the contracting authority’s standing orders and internal governance requirements.

Compliance in this context is not simply about following a checklist. It reflects a broader obligation under UK procurement law to treat suppliers equally, to be transparent about requirements, and to ensure that the market can genuinely compete for the contract. A specification that is vague, technically biased, or unnecessarily restrictive can expose the contracting authority to legal challenge and, in serious cases, may require the entire procurement to be restarted.

For most public sector organisations, compliance also means ensuring the specification is proportionate. A small contract for office supplies does not require the same depth of technical specification as a major IT outsourcing arrangement. Matching the level of detail to the complexity and value of the requirement is itself part of good procurement practice.

What are the essential components of a public sector procurement specification?

A well-constructed public sector procurement specification typically includes a clear statement of the requirement, the scope of services or goods, technical or functional standards, performance expectations, delivery timescales, any mandatory legal or regulatory requirements, and the context in which the contract will operate. These elements together give suppliers the information they need to submit a credible, costed response.

Breaking this down further, most specifications will contain:

• Background and context: A brief explanation of the organisation, its objectives, and why the procurement is taking place
• Scope of requirement: A precise description of what is being purchased, including volumes, locations, and any phased delivery requirements
• Technical or functional requirements: The standards, capabilities, or outputs the supplier must meet
• Service levels and performance standards: How performance will be measured and what the expectations are once the contract is live
• Compliance and regulatory requirements: Any legal, safety, environmental, or sector-specific obligations the supplier must satisfy
• Contract term and key milestones: The duration of the contract and any critical delivery dates

The specification should be written in plain language wherever possible. Technical jargon that is not defined, or assumptions about supplier familiarity with internal processes, can reduce the quality of responses and disadvantage smaller or newer market entrants.

How do you avoid writing a specification that favours a particular supplier?

To avoid writing a specification that favours a particular supplier, focus on outputs and outcomes rather than describing a specific product, brand, or existing solution. If a requirement is written around the features of an incumbent supplier’s system or service, it will effectively exclude the rest of the market and create grounds for legal challenge.

This is one of the most common compliance risks in public sector procurement specification writing, and it often arises unintentionally. A team that has worked with a particular supplier for several years may naturally describe the requirement in terms of what that supplier already provides. To counter this:

• Write requirements based on what the organisation needs to achieve, not how it is currently being delivered
• Avoid referencing proprietary technologies, named products, or specific methodologies unless they are genuinely the only viable option and this is clearly documented
• Where a named standard or product must be referenced, include the phrase “or equivalent” to preserve market openness
• Have someone with no incumbent relationship review the draft specification for inadvertent bias
• Conduct a market engagement exercise before finalising requirements to understand what the market can realistically offer

Pre-market engagement is particularly valuable here. Speaking to a range of potential suppliers before writing the specification helps ensure the requirements are genuinely achievable, commercially realistic, and not inadvertently shaped by one supplier’s framing of the problem.

What is the difference between a specification and an evaluation criteria document?

A specification defines what the organisation needs from a supplier. An evaluation criteria document defines how responses to that specification will be assessed and scored. The two serve distinct purposes and must be kept clearly separate, though they must also be tightly aligned with each other.

The specification tells suppliers what to deliver. The evaluation criteria tell them how their proposals will be judged. If evaluation criteria reference requirements that do not appear in the specification, or if the specification contains requirements that are not reflected in the scoring methodology, the procurement process becomes inconsistent and potentially open to challenge.

In practice, the evaluation criteria should flow directly from the specification. If the specification places significant weight on social value, environmental performance, or technical capability, the evaluation criteria should reflect those priorities with corresponding scoring weightings. This alignment gives suppliers a clear signal about what matters most to the contracting authority and enables them to structure their responses accordingly.

It is also worth noting that evaluation criteria must be disclosed to the market before the tender closes. Changing criteria after responses have been received is a serious compliance breach. This makes it essential to finalise both documents before the tender is issued, rather than treating the evaluation methodology as something that can be developed after the fact.

How should you involve stakeholders when writing a procurement specification?

Stakeholders should be involved early in the specification-writing process to ensure the document accurately reflects operational needs, not just what the procurement team assumes those needs to be. The most effective approach is to engage end users, technical leads, finance colleagues, and legal advisers before drafting begins, rather than circulating a completed draft for comment at the end.

Different stakeholders bring different perspectives that are all necessary for a complete and accurate specification:

• End users and service managers understand the day-to-day operational requirements and can identify gaps or impractical assumptions in a draft specification
• Technical specialists can validate that the functional and technical requirements are accurate, measurable, and achievable
• Finance leads can confirm that the scope and volume assumptions are realistic and aligned with available budget
• Legal and compliance teams can ensure that any regulatory, data protection, or contractual obligations are correctly captured
• Senior sponsors can confirm that the specification aligns with the organisation’s strategic direction and priorities

Stakeholder engagement should also include a formal sign-off process before the specification is published. This creates accountability, reduces the risk of post-publication changes, and ensures that the document has been reviewed by those who will ultimately manage the contract once it is awarded.

What are the most common mistakes that make a procurement specification non-compliant?

The most common mistakes that make a public sector procurement specification non-compliant include writing requirements that are too vague to evaluate fairly, using specifications that inadvertently favour an incumbent, setting requirements that are disproportionate to the contract value, and failing to align the specification with the evaluation criteria.

Other frequent errors include:

• Copying a previous specification without updating it for changes in scope, legislation, or market conditions, which can embed outdated or irrelevant requirements
• Including requirements that cannot be evidenced or scored, which makes evaluation subjective and harder to defend if challenged
• Setting minimum standards that exceed what the requirement actually needs, which reduces competition and may deter capable suppliers from bidding
• Failing to consult the market before finalising requirements, which can result in a specification that is technically unrealistic or commercially unviable
• Issuing a specification without legal or governance review, particularly for higher-value contracts where regulatory obligations are more complex
• Changing the specification after the tender has been issued without formally notifying all bidders, which creates inequality between those who saw the original version and those who received the amendment

Many of these mistakes are avoidable with structured internal review processes and, for more complex requirements, external specialist input. A specification that has been drafted collaboratively, reviewed for bias, and aligned with both the evaluation criteria and the applicable regulatory framework is far less likely to attract challenge and far more likely to attract strong, competitive responses from the market.

How eXceeding helps with public sector procurement specification writing

eXceeding works with public sector organisations to develop compliant, well-structured procurement specifications that attract strong market responses and withstand scrutiny. Whether you are running a straightforward tender or a complex, high-value procurement, our consultants bring the regulatory knowledge and category expertise to get the specification right from the outset.

• Drafting and reviewing procurement specifications across a wide range of categories and contract values
• Conducting pre-market engagement to validate requirements and test market appetite before the tender is issued
• Aligning specifications with evaluation criteria to ensure consistency and defensibility throughout the process
• Facilitating stakeholder workshops to capture operational requirements accurately and secure internal sign-off
• Providing expert tender management support from specification through to contract award

If your organisation needs specialist support to write a compliant public sector tender specification, or to source an experienced procurement professional to lead the process, get in touch with the eXceeding team to discuss how we can help.

Related Articles

• When does procurement outsourcing fail and why?
• What is tail spend and how should organisations manage it?
• How do you design a procurement operating model?
• Is your procurement function holding back business growth?
• What role does data play in modern procurement strategy?