Tender Specifications: What They Include and How to Use Them (2026)
The tender specification is the most important document in any bid pack. It defines what the buyer needs, what standards must be met, and what evidence you must provide to win the contract. Everything else in a tender submission flows from a thorough understanding of the specification.
Yet specification analysis is consistently the most abbreviated stage of the submission process. Suppliers read the questions and start writing. They miss requirements buried in annexes. They misunderstand mandatory criteria, they submit responses that are technically strong but commercially misaligned — because they answered what they assumed the buyer wanted rather than what the specification actually requires.
This guide covers what tender specifications typically contain, what each section means for your submission, and how to use the specification to write responses that score maximum marks. For the complete overview of how the tendering process works, see our guide to tendering for contracts. For the step-by-step submission guide, see our guide to how to write a bid.
What Is a Tender Specification?
A tender specification is the buyer’s detailed description of the contract they want to award. It explains what is needed, to what standard, over what period, and under what conditions. It is the foundation against which your entire submission is assessed.
The specification is distinct from the evaluation criteria — which tell you how your responses will be scored. However, the two are closely connected. Strong responses use the specification’s own language, reference its specific requirements, and demonstrate how every element of the proposed solution meets what the specification demands. Responses that ignore the specification and describe a generic service model score poorly — regardless of how well they are written. Our guide to answering tender questions covers how to align responses to specification requirements effectively.
What Tender Specifications Typically Include
Description of the contract
The opening section describes the intent and context of the contract. It explains why the buyer is procuring this service or product. It gives background on the organisation, the existing service, and the outcomes the buyer wants to achieve.
Read this section carefully. It tells you what the buyer values most — often in their own words. The language they use to describe what they want is the language you should use in your responses. Buyers award higher marks to submissions that demonstrate genuine understanding of their context — not just competence at delivering the general category of service. Use the contract description to develop your buyer research before writing begins.
Service requirements
This is the most detailed section of most specifications. It defines what you must deliver — timescales, quantities, delivery methods, quality expectations, reporting structures, and contingency requirements. For service contracts it describes the operational outputs expected. For goods contracts it describes product standards, delivery conditions, and volume requirements.
Service requirements are often divided into two sub-categories. Functional requirements define the desired outcome — what the service must achieve. Performance requirements define the inputs, standards, and measurable KPIs — how the service must be delivered and to what measurable standard. Both must be addressed explicitly in your quality responses. For every methodology or approach you describe, explain how it meets the specific service requirement stated in the specification — not just the general category of requirement.
This alignment between your proposed approach and the specification’s specific requirements is what distinguishes high-scoring responses from competent ones. Our guide to technical response questions covers how to structure responses around specification requirements.
Mandatory requirements
Mandatory requirements are pass or fail criteria. Meeting them does not earn marks. Failing to meet any single one disqualifies your submission — regardless of the quality of everything else you submit.
Mandatory requirements typically cover accreditations, insurance levels, financial standing thresholds, legal compliance obligations, and sector-specific regulatory requirements. They may also cover specific operational requirements — minimum staffing levels, required technology systems, or geographic coverage standards.
The most important discipline in specification analysis is identifying every mandatory requirement before committing to write. Apply your bid no-bid assessment against the mandatory requirements first. If any cannot be met, the opportunity is not genuinely winnable at this stage regardless of how competitive your submission might otherwise be.
Contract length and extension options
The specification will state the intended contract term — typically expressed as an initial period with optional extension periods. A contract described as “three years plus two optional one-year extensions” has a maximum term of five years. This is commercially significant — it affects the total revenue opportunity, the pricing approach, and the exit planning requirements.
Many specifications also require you to describe your exit strategy — what you will do to ensure continuity of service at the end of the contract term. This includes knowledge transfer, data handover, and staff transition arrangements. Address this explicitly in your submission. Buyers are responsible for service continuity and want evidence that you have thought beyond the contract start date.
Contract length also affects your pricing strategy. A five-year maximum term requires pricing that is sustainable across the full extended period — not just competitive for the initial three years. Factor in inflation, cost escalation, and TUPE liabilities over the full potential contract duration when building your price.
Sustainability and environmental requirements
Sustainability specifications have strengthened significantly under the Procurement Act 2023. Buyers must now consider environmental factors in procurement decisions. Many specifications include explicit sustainability requirements — carbon reduction targets, net zero commitments, environmental management standards, and supply chain sustainability obligations.
These requirements are increasingly scored rather than simply declared. A buyer requiring ISO 14001 as a mandatory standard is setting a pass/fail threshold. A buyer asking how you will reduce the carbon footprint of service delivery is inviting scored responses. Our guide to social value and tendering covers how environmental commitments interact with the broader social value evaluation framework.
Where sustainability requirements appear in the specification, address them specifically and with evidence. Generic environmental commitments — “we are committed to sustainability” — score nothing. Specific, evidenced plans aligned with the buyer’s stated targets score marks.
Contract management requirements
Most specifications describe the contract management arrangements the buyer expects — governance structures, reporting frequencies, performance review meetings, KPI monitoring, and escalation procedures. Some specify exactly who they expect your contract manager to be and what their qualifications and experience must include.
Your response to contract management questions should mirror the specification’s own requirements precisely. If the specification requires monthly performance reports in a defined format, describe how you will produce those reports. If it requires quarterly strategic reviews at director level, name the director who will attend. Vague descriptions of your general contract management approach do not address specification-specific requirements — and do not score as highly as responses that do.
How to Use the Specification to Write Stronger Responses
The single most effective technique for using a specification to write stronger responses is structural mirroring. Map your response structure directly to the specification’s requirements. Use the specification’s own language in your subheadings. Address every element of every requirement explicitly rather than generally.
This approach has two advantages. It guarantees that every specification requirement is addressed in your response. And it makes the evaluator’s job easier — they can see immediately that every requirement has been met, and they can award marks accordingly.
Build your tender timeline to include adequate specification analysis time before any writing begins. Identify every requirement. Flag every mandatory criterion. Note every KPI and performance standard. Extract the buyer’s own language for your response planning. This investment at the analysis stage produces better submissions in less total time than diving straight into writing.
Frequently Asked Questions About Tender Specifications
How long should I spend reading the tender specification?
As long as it takes to identify every requirement, every mandatory criterion, every KPI, and every evaluation criterion — before writing a single word of your response. For complex specifications this might take a full day. For simpler ones, several hours. Rushing this stage is the most common cause of non-compliant submissions and misaligned responses. The time invested in specification analysis is always recovered through faster, more accurate writing.
What is the difference between functional and performance requirements?
Functional requirements describe what the service must achieve — the outcome the buyer wants. Performance requirements describe how it must be delivered — the inputs, processes, standards, and measurable KPIs that govern delivery. Both must be addressed in your quality responses. Many suppliers address the functional requirements adequately but fail to reference the specific performance standards in the specification — which costs marks on scored responses.
What happens if I miss a mandatory requirement?
Your submission is disqualified — regardless of the quality of everything else you have submitted. Mandatory requirements are assessed before quality scoring begins. There is no partial credit for meeting most mandatory requirements. This is why specification analysis must identify every mandatory criterion before any work begins. If a mandatory requirement cannot be met, the bid no-bid assessment should identify this and prevent further resource being invested in an unwinnable submission.
Can I ask the buyer to clarify the specification?
Yes — and you should, whenever anything is genuinely unclear. Use the formal clarification process within the procurement portal before the clarification deadline. Be specific in your question. All questions and answers are shared with every bidder simultaneously. Proceeding with an ambiguous interpretation of a specification requirement is avoidable risk. A clarification question takes minutes. A submission built on a wrong assumption wastes days.
How do I handle conflicting information within a specification?
Raise it as a clarification question immediately. Conflicting information within a specification — two sections stating different requirements for the same element — is more common than buyers would like to admit. Do not choose which version to follow and proceed silently. Ask the buyer to confirm which requirement takes precedence. Their answer is shared with all bidders and provides a documented basis for your response approach.
Should I address every specification requirement even if there is no specific question about it?
Where the specification includes requirements that are not directly reflected in the evaluation questions, use your own judgement. If a specification requirement is significant and clearly relevant to the contract, address it in the most appropriate quality response section — even if no question specifically asks for it. Demonstrating thorough understanding of the full specification is a positive signal to evaluators. Missing a significant specification requirement because no question directly asked about it is a missed opportunity to differentiate your submission.
Need Help Analysing and Responding to a Specification?
Our tender writing consultants conduct thorough specification analysis on every engagement — identifying every requirement, every mandatory criterion, and every scoring opportunity before writing begins. Our team holds an 87% win rate across all sectors, working with 3,500+ organisations across 52 countries.
Send us your tender documents and we will provide a fixed-fee quote within four working hours.
About the author: Written by Joshua Smith, a seasoned bid-writing expert with experience across the UK, Middle East and US, helping organisations secure the contracts they deserve through high-quality, competitive tender responses.