The first time you open a public-sector tender pack, it can feel like being handed someone else's exam in a language you half-speak. There are several documents, cross-references everywhere, and a lot of words doing quiet, important work. The good news: a specification follows patterns, and once you learn to read those patterns, you can tell within an hour whether a contract is worth your time and exactly what a winning answer needs to contain.

This guide walks through how experienced bid teams read a spec, what to look for first, and how to turn the document into a plan rather than a pile of dread.

Know what is in the pack before you read a word of detail

A typical tender pack is not one document. You will usually find a covering instructions document (often the Invitation to Tender, or ITT), the specification itself, the award criteria and scoring methodology, a pricing schedule, the draft contract terms, and a set of response forms or a portal questionnaire. Each does a different job.

Before diving in, do a five-minute inventory. List every document, its length, and what it appears to govern. The mistake most first-time bidders make is reading the specification in isolation and missing that the scoring lives in a separate file. If you only understand one stage of the process, read our explainer on the difference between PQQ and ITT tender stages so you know which document you are actually answering.

Specification, requirements and award criteria are three different things

People use these terms loosely, but they mean distinct things, and confusing them costs marks.

  • The specification describes what the buyer wants delivered. It is the “what”: scope, volumes, locations, standards, service levels.
  • The requirements are the conditions you must meet to be considered at all. Some are pass/fail (you have the right insurance; you hold a particular accreditation). Miss one and the rest of your bid is irrelevant.
  • The award criteria are how the buyer decides who wins. This is where the marks are. It tells you what they will score and how much each part is worth.

Read all three together. A spec might describe a glittering, gold-plated service, but if the award criteria only put 10% of the marks on that area, you should not pour 90% of your effort into it.

Find the weighting and let it set your priorities

The single most useful number in any tender is the weighting split between quality and price, and then the breakdown within quality. A 60/40 quality-to-price split rewards a very different bid from an 80/20 one. Within quality, you might see mobilisation worth 25%, service delivery worth 40%, and social value worth 15%.

Read the scoring before you read the questions. The weighting is the brief; everything else is detail.

Map the percentages onto a simple table in your head or on paper, then decide where your writing time goes. If you want a deeper look at how panels turn answers into numbers, our piece on how tender evaluation and scoring works shows what a “good” versus “excellent” answer looks like to an assessor.

Hunt for the must-haves, the “shall” words and the hidden constraints

Specifications are full of signal words, and they are not interchangeable. “Shall” and “must” are mandatory; “should” and “may” are desirable or optional. Go through the spec and highlight every “shall” and “must” you find. Each one is a commitment you will have to make and, often, evidence.

Then look for the constraints that are easy to skim past. A small clinic contract once asked, in a single line halfway down page 19, for staff to be on site by 7am on a specific industrial estate with no parking. That one sentence reshaped the whole staffing and cost model. Common hidden constraints include:

  • Geographic coverage or response times that imply local presence.
  • Specific accreditations, ISO standards or DBS checks.
  • TUPE staff transferring in from an incumbent.
  • Minimum staffing levels, named roles, or cover arrangements.
  • Reporting and data formats the buyer expects you to produce.

Turn the spec into a requirements matrix

Once you have read everything, build a simple matrix. In one column, list every requirement and award question. In the next, note what evidence or commitment answers it. In the third, mark whether you can meet it today, with effort, or not at all.

This does two things. It exposes gaps early, while you still have time to find a partner or subcontractor, and it becomes the skeleton of your response. When you sit down to write, you are filling in a structure rather than facing a blank page. From there, our guide to writing a strong tender response takes the matrix and turns it into scoring answers.

Use the clarification window, and use it well

Almost every tender has a clarification period where you can ask the buyer questions in writing. Treat it as a genuine tool, not a formality. If a requirement is ambiguous, ask. If two documents seem to contradict each other, point it out. Buyers answer all suppliers at once, so a sharp question can quietly fix a problem in the spec for everyone, including you.

Keep your questions specific and avoid revealing your strategy. “Please confirm whether the 7am start applies to all sites or only Site A” is good. “How should we structure our innovative delivery model?” tells competitors what you are thinking and gets you nothing useful.

Decide whether to bid at all

Reading the spec properly is also how you make a sober bid/no-bid decision. If you fail a mandatory requirement, the deadline is unrealistic, or the price ceiling is below your cost base, walking away is a win, not a defeat. A structured approach helps; see our bid or no-bid decision framework for a quick way to score the opportunity before you commit days of effort.

If the spec is dense and you simply want a fast plain-English overview before deciding, paste the notice into our free tender summary tool to get the gist in seconds.

Frequently asked questions

How long should it take to read a tender specification properly?

For a typical SME-sized contract, budget two to four hours for a first proper read and matrix. The inventory and weighting check take under an hour; the detailed pass and requirements matrix take the rest. Anything you can reuse from past bids speeds this up considerably.

What if the specification and the contract terms seem to contradict each other?

Raise it as a clarification question during the question window. Do not assume which version wins, and do not silently price for one interpretation. Getting a written answer protects you and may force the buyer to issue a correction to all bidders.

Do I have to meet every single requirement to bid?

You must meet every mandatory (pass/fail) requirement, or you will be excluded regardless of how good the rest of your bid is. Desirable requirements (the “should” items) are different; you score better by meeting them, but missing one is not automatically fatal.

Reading the spec well is the highest-return hour in any bid. Once you can decode a pack at a glance, every future tender gets faster. Start by searching live UK tenders on Tendarix and practise pulling one apart, even if you are not ready to bid yet.