How to read a UK tender specification before writing

How do you read a UK tender specification before writing?

A tender specification sets out what the buyer needs, how they expect it to be delivered and what evidence they need before trusting you with the contract. Read it alongside the invitation to tender, pricing schedule, draft contract, evaluation criteria, response templates and every supporting appendix.

Don’t start writing because the deadline looks close. Separate pass or fail requirements from scored questions, check the delivery risks and map the evidence your team already has. This saves hours of rewriting and stops a strong service being lost in a weak response.

Why this matters before anyone opens a blank document

You’ve found a tender that looks promising. The contract value is tempting. The deadline is manageable, at least on paper.

Then the documents arrive.

There are twelve attachments, a pricing workbook with six tabs, a draft contract nobody has read yet, and a quality question that appears to ask for five different things in 750 words. Your team is still delivering services, answering emails and trying to get home at a sensible time.

This is where bids often become stressful for the wrong reason.

A tender specification is not background reading. It is the buyer’s test. It tells you what they need and where your offer could become difficult to deliver. It also shows what the buyer will measure, what it may reject and which performance requirements matter.

The strongest tender responses are usually won in the first read of the documents, not in the final hour of editing.

A good review also protects your bid or no-bid decision. A £2 million opportunity can still be the wrong contract if it creates delivery risk, cannot be priced sensibly, fails to offer value for money, or depends on evidence you don’t have.

Put the tender documents in the right order

Don’t read documents randomly, switching between tabs whenever something catches your eye. Pull everything together first.

Start with the contract notice and use it to understand the opportunity’s basic route and scope. The notice tells suppliers who the buyer is, what is being bought and which procurement route applies.

Treat the contract notice as a signpost, not a substitute for the full tender documents. The live tender pack contains the commitments that will shape your response.

Build one complete tender pack

Save the invitation to tender, specification, technical specifications, response schedules, pricing workbook, draft contract, evaluation methodology, appendices, clarification log and portal instructions in one place.

Check files with names that sound harmless. “Schedule 7”, “Appendix C” and “Tenderer Instructions” can contain requirements affecting eligibility, pricing, delivery or certification.

A published Find a Tender opportunity can help you understand the headline scope and route. Check any published pre-market engagement material too, where available. However, the buyer’s live tender documents and portal instructions always take precedence.

Read the contract before you fall in love with the opportunity

The specification may describe a service you can deliver well. The contract might introduce payment terms, liability limits, data handling duties, mobilisation dates or subcontractor restrictions that change the decision.

Ask whether you would still want the work after reading the terms.

If the answer is “only if everything goes perfectly”, pause. Hope is not a delivery model.

Separate compliance checks from the marks

A quality answer cannot rescue a failure against the mandatory requirements. Treat compliance and scoring as two separate pieces of work.

This is one of the simplest changes a busy bid team can make. It also stops the usual last-day scramble for insurance certificates, policies and declarations.

List every pass or fail requirement

Look for wording such as “mandatory”, “minimum”, “must”, “required”, “pass or fail”, “selection criterion” or “condition of participation”.

The specification and its appendices may also contain pass or fail conditions. These can include insurance levels, safeguarding checks, financial information, professional registrations, accreditations, cyber conditions, declarations and required attachments.

Create a separate compliance list for these mandatory requirements. Record the evidence, who owns it, where it is stored, and when it needs approving.

Where certification, testing or accreditation is mandatory, record exactly what evidence is required and who must issue it.

• Can you meet every stated minimum requirement by the submission deadline?
• Are all declarations complete and signed by the right person?
• Do named subcontractors need their own information or documents?
• Does the tender submission portal require a particular format, file size or naming convention?

The buyer decides whether each stated condition has been met. A quality answer cannot cure a missed mandatory requirement, so check the live tender wording carefully.

Treat quality questions as scoring opportunities

The evaluation criteria tell you where the marks sit. A 10-point question needs a stronger evidence plan than a five-point question.

It doesn’t always need twice the words. It does need a clearer answer to what the buyer asked, how you will deliver it and how you can prove it.

Turn the specification into an evaluator-first map

Reading top to bottom is useful once. Reading it again with a proper matrix is where the work starts.

Set up one row for every question, sub-question and contract requirement. Give important technical and contract requirements their own rows rather than hiding them inside a broader response. This becomes your working document for the whole tender.

Capture what the buyer is actually asking for

Copy the full question into your matrix, including the buyer’s command words, such as “describe”, “demonstrate”, “explain” and “provide examples”.

Then split it up. A mobilisation question may also ask about staffing, governance, risks, communication, timescales and reporting. Functional requirements and output specifications can be hidden within a wider question. If one is missed, the answer is incomplete, even if the prose is lovely.

Record:

• The question number and weighting
• Every sub-question and requirement
• Mandatory requirements, tracked separately from scored requirements
• The word or page limit
• The scoring method and scoring descriptors
• The evidence needed for each point
• The response owner, reviewer and approval date

Give evidence a home before drafting

For each requirement, identify the proof. The evidence column should cover contract examples, performance data, staff CVs, policies, mobilisation plans, client references and named delivery partners.

Some evidence may need to come from a subcontractor or delivery partner. Confirm what is required early enough for them to provide it.

Include contract management responsibilities in the ownership field, with a named person and evidence source. Avoid vague notes like “add case study”. Write down which case study, what result it proves, and where the figure came from.

Bidsmithery™ works from the evaluator’s side of the table too. An answer can sound convincing internally, yet leave the evaluator searching for evidence they can award marks against.

Know the difference between input and output specifications

Not every specification gives you the same freedom to shape your delivery model. The buyer may prescribe the method or leave room for your approach.

Input specifications tell you the method

Input specifications may state the required staffing levels, service hours, equipment, processes, locations or reporting format. Show clearly how your proposed delivery model will meet each instruction.

For example, a buyer may require two on-site advisers, available between set hours, using a named reporting system. Your job is to show how you will meet those instructions without making promises your operational team cannot keep.

Read these details carefully. They can affect cost, recruitment, travel and mobilisation. They may also refer to standards, certifications or named accreditations.

Output specifications focus on the result

Output specifications describe the outcome, while supporting requirements may still set boundaries for delivery. A council may require reduced waiting times, better access to advice, higher tenant satisfaction or faster repairs.

These performance requirements give suppliers more room to explain their approach. Your tender must still link your method to the required result and support it with credible evidence.

This flexibility doesn’t mean fewer commitments. It means the buyer expects a credible case for why your model will work.

Check standards, technical requirements and delivery assumptions

Specifications can include standards, quality expectations, security arrangements, accessibility needs and testing requirements. These may sit in the main document or be tucked away in an appendix.

The Procurement Pathway can help you understand the rules behind public procurement specifications. For your bid, however, the live tender documents and clarification responses determine what you must address.

Read every referenced standard in full. Check whether the buyer requires a named standard, permits an equivalent, or asks for certification, testing or accreditation evidence. Do not assume that a familiar certificate proves the specific requirement.

If UKAS or another accreditation body is named, check the exact wording and who must hold the accreditation. Ask a clarification question if the acceptable evidence or route to equivalence is unclear.

Ask clarifications when documents conflict

Tender documents are not always as tidy as anyone would like.

The technical specifications may ask for monthly reports, while the contract says quarterly. The pricing schedule may assume a different staffing model. One document may require UKAS evidence, while another is silent on it. A named standard may also conflict with a reference to equivalent international standards.

Don’t bury the contradiction in your draft and hope nobody notices. Some conflicts affect mandatory requirements and eligibility, not just the quality score.

Keep a clarification log

A clarification log keeps the clarification process organised and gives everyone a clear record to follow.

Record the document name, page or schedule, exact wording, the issue, your proposed question and the buyer’s answer.

Keep it factual. A good clarification question is focused and easy to answer.

For example: “Please confirm whether performance reporting is required monthly, as stated in section 4.2, or quarterly, as stated in Schedule 3.”

Check every amendment after it lands

Clarification responses and document updates can change your approach. Recheck the amended requirements, compliance matrix, answer plan, pricing assumptions and evidence list.

Check the complete tender pack after every amendment. Update contract management records and tell any colleagues or suppliers affected by the change.

There is no prize for one person holding the most up-to-date version in their inbox.

Read for commercial reality, not just bid potential

A contract can fit your capability and still fail the commercial test.

Senior leaders need a clear view of what the service will cost to deliver, what risks sit with the supplier, and what the team will need to give up to mobilise it. Check the mandatory requirements before committing bid resources.

Test scope, capacity and mobilisation

Look at contract length, expected volumes, geographical coverage, staffing, contract management, reporting and implementation timescales. Check the full specification, performance requirements and any call-off terms that could affect volumes or mobilisation.

Then ask the less glamorous but more useful questions:

• Can your current team deliver this without weakening existing contracts?
• Is the mobilisation period realistic for recruitment, training and systems setup?
• Can you evidence every sustainability, social value and environmental commitment you intend to make?
• Does the contract offer value for money once delivery, management, risk and margin are included?
• Can your service model meet every stated technical, testing and certification requirement?
• Are there dependencies on the buyer, partners, subcontractors or the wider supply chain?

Look for commitments hidden in plain sight

Data protection, safeguarding, business continuity, equality and environmental requirements can appear across several documents. They may not carry a separate score, but they still shape how you must deliver.

These commitments can also affect staffing, evidence, costs and risk. Review what the buyer must provide and what approvals or dependencies could affect delivery.

This is where strategic bid consultancy can help if the issues stretch beyond one tender. Sometimes the problem isn’t the answer. It is the process, evidence or decision-making behind it.

Mirror the buyer’s structure in your response

Structural mirroring means following the buyer’s question order and language so evaluators can find each answer fast.

It also helps them apply the evaluation criteria consistently against the buyer’s scoring guide.

It is not copying their wording back at them. It is removing the need for them to hunt through a clever but confusing response.

Make every requirement visible

Use headings that match the question or sub-question. Mirror the relevant requirements, signpost your commitments and put evidence close to the point it proves.

If the buyer asks for mobilisation, governance, risk management and reporting, use those four elements in your answer. Don’t write a general story about being a trusted partner and expect the evaluator to join the dots.

Put each requirement and its supporting evidence beside the relevant commitment. This makes the response easier to check and reduces uncertainty.

They are assessing several bids, often to a fixed scoring guide. Make the marks easy to award.

Match your evidence to the weighting

A higher-weighted question needs more than a polished opening paragraph. Give it relevant proof, named responsibilities, practical steps, measures and realistic timescales.

A good answer often follows a simple pattern:

1. State what you will do.
2. Explain how it will work in this contract.
3. Show who is responsible, how contract management will work, and when it happens.
4. Prove that you can deliver it with relevant results, examples or certification where required.

That is far more useful than filling space with generic company information.

Before finalising the tender submission, check that every requirement is visible and supported by clear evidence.

Common mistakes that cost marks before writing starts

Most tender mistakes are not dramatic. They are small omissions that gather pace when the deadline gets close.

The team means well. Everyone has read something. Nobody has read everything.

Some omissions involve mandatory requirements and can invalidate an otherwise strong response.

Starting with the narrative

Writing the introduction first feels productive. It can also send the bid in the wrong direction before you have checked scope, evaluation criteria and contract terms.

Build the response plan first. Then write with purpose.

Treating old content as ready-made proof

Past answers can save time, but only if they fit the current requirement. Check every previous claim against the current requirement.

Check every date, number, client example, policy reference and promised process. Confirm that every certificate, test or inspection record is current and relevant.

A case study from a different sector may still be useful. Explain why it is relevant. The evaluator can’t award credit for evidence that’s missing or out of date.

Leaving review until the final evening

Proofreading finds typos. A proper review finds missing requirements, weak proof, unclear commitments and inconsistencies between quality answers and pricing.

A red team bid review tests compliance, scoring logic, evidence and consistency before submission. It is not about handing your bid away. Your people keep the knowledge, while someone experienced tests what may be losing marks.

Key takeaways

• Read the full tender pack before assigning writing tasks.
• Keep mandatory compliance checks separate from scored quality questions.
• Break each question into clear requirements, evidence and owners.
• Check the contract, pricing and mobilisation model before you commit.
• Use the buyer’s structure so evaluators can find what they need.
• Raise clear clarification questions when the documents conflict.
• Review the completed submission as an evaluator would, not as its author.

Protect your energy as well as your submission

A tender specification is where you find out what winning will really require. Read it properly and your team can make a grounded decision, build a stronger response and avoid promising work they cannot deliver.

External review is not a sign of weakness. It protects energy, confidence and headspace when your team has spent days too close to the draft.

If repeated bids for public sector procurement are stretching your people, Bid Win Rate Accelerator training gives teams a practical way to spot patterns and strengthen future submissions. If you need a sounding board on an upcoming opportunity, Book a free fit call.

Frequently asked questions