How to Read a Tender Document (Without Missing Critical Requirements)

A UK tender pack rarely arrives as a single, tidy document. It turns up as a bundle — an invitation to tender, a specification, a pricing schedule, a selection questionnaire, a stack of appendices and a set of contract terms — often running to a hundred pages or more. Somewhere in that bundle are a handful of requirements that will decide whether your bid is even read. Miss one and months of effort can be discarded on a technicality.

Reading a tender properly is not about ploughing through every page from front to back. It is a deliberate process of working out where the binding requirements live, extracting them, and turning them into a plan before you write a single answer. Done well, it takes a few focused hours and saves you from the two outcomes every bidder dreads: disqualification on a technicality, or winning work you cannot actually deliver.

This guide sets out a repeatable method for reading any UK public sector tender — an ITT, a selection questionnaire or a framework call-off — so that nothing critical slips past you. You will learn what each document in the pack is for, the order to read them in, where requirements tend to hide, and how to capture everything in a simple compliance matrix. There is a worked example, a requirements-extraction checklist, and the common mistakes that catch out even experienced bid teams.

Why reading a tender document properly is a skill worth having

Public procurement is rules-based. Evaluators have very little discretion: if the documents say a response must be no longer than 1,000 words, or that you must hold £5 million of public liability insurance, those are hard lines. A brilliant answer that ignores them still fails. The first job of reading a tender is therefore defensive — finding every condition you must satisfy simply to stay in the running.

The second job is commercial. The same documents tell you how the buyer will score the bid, what they genuinely care about, where the contract risk sits, and whether the work is profitable. Read well, a tender pack is the most honest brief you will ever get from a customer. Read carelessly, it is a minefield. The difference is method.

What is actually inside a UK tender pack

Most opportunities are advertised on Find a Tender (for higher-value contracts) or Contracts Finder (for lower-value ones), with the documents downloaded from an e-tendering portal such as Jaggaer, In-Tend, ProContract or Atamis. The pack usually contains some combination of the following:

Not every tender uses these exact names, and a single-stage 'open' procedure bundles selection and award together. But almost everything you receive will map to one of these roles. Identifying the role of each document is the first step to reading the pack efficiently. For a fuller breakdown of the ITT itself, see our guide on what an ITT is, and on the two-stage process in our PQQ vs ITT explainer.

How to read a tender document: a step-by-step method

Work through the pack in this order. The sequence matters — it front-loads the requirements that can disqualify you, so you never invest writing time in a bid you were never eligible to win.

Step 1 — Do a fast orientation pass

Before extracting anything, skim the entire pack once to build a mental map: how many documents there are, roughly how long each is, and what each covers. Don't take notes yet. You are answering one question — 'what have I been sent, and how is it organised?' Ten minutes here saves hours of re-reading later.

Step 2 — Pin down the deadlines and submission mechanics

Find, and record in one place: the submission deadline (date, time and time zone), the clarification-question deadline, and exactly how the bid must be submitted — which portal, in what file formats, and any limits on file size or number of attachments. Portals close to the second; a bid uploaded at 12:00:01 against a 12:00 deadline is rejected. Note any site visits or bidder days, which often carry their own, earlier deadlines.

Step 3 — Map every document and how they relate

List each document and its role (instructions, selection, specification, pricing, terms). Cross-references are where requirements hide: the ITT may say 'comply with the requirements in Schedule 4', and Schedule 4 may introduce an obligation that appears nowhere else. Follow every reference and note where each one leads.

Step 4 — Extract the mandatory pass/fail requirements first

These are the conditions you must meet simply to be considered — minimum turnover, insurance levels, certifications (ISO 9001, Cyber Essentials, CHAS), mandatory policies, and the exclusion grounds in the selection questionnaire. They are usually pass/fail: meet them or be excluded. Pull every one into a list now. If you cannot meet a mandatory requirement, and cannot do so by award (for example by committing to raise insurance on award, where the tender allows it), that is a no-bid decision — made in an hour, not after a week of writing.

On larger central government contracts, this is also where a PPN 006 Carbon Reduction Plan requirement will sit — a pass/fail condition of participation that many bidders miss until it is too late to produce one.

Step 5 — Read the specification like the buyer wrote it

Now read the specification properly. Highlight every instance of 'must', 'shall' and 'is required to' — these are obligations. Distinguish them from 'should' and 'may', which are preferences. Note volumes, locations, service levels, KPIs and any standards you must comply with. The specification is also where you find the questions behind the questions: if the buyer repeatedly stresses safeguarding or business continuity, expect those themes to reappear in the scored questions.

Step 6 — Decode the award criteria and weightings

Find exactly how the bid is scored: the quality/price split, the weighting of each question, the scoring scale (for example 0–5), and any minimum quality threshold below which you are excluded regardless of price. Under the Procurement Act 2023, contracts are awarded to the 'most advantageous tender' (MAT) — the successor to MEAT — which makes explicit that quality and social value can outweigh price. Map your effort to the marks: a question worth 30% deserves far more attention than one worth 5%. Our guide on tender evaluation weighting shows how to read scoring matrices in detail.

Step 7 — Read the contract terms and schedules

The conditions of contract decide whether winning is worth it. Look for liability caps, liquidated damages, payment terms, termination rights, performance bonds or parent company guarantees, and TUPE obligations where staff may transfer to you. These rarely affect your score, but they heavily affect your risk and margin — and they often justify a clarification question or a priced contingency.

Step 8 — Build a requirements (compliance) matrix

Finally, consolidate everything into a single requirements matrix — a simple spreadsheet listing every requirement, where it appears (document and page), whether it is mandatory or scored, its weighting, who on your team owns it, and its status. This one document becomes your master plan: it proves nothing has been missed, drives your writing, and doubles as your final compliance check before submission.

Where critical requirements love to hide

Most missed requirements aren't missing from the pack — they are simply in places people skim. These are the usual hiding places:

• Inside specification prose. A single 'the supplier must hold ISO 14001' sentence buried in a paragraph carries exactly the same weight as a bold heading.
• In the schedules and appendices. TUPE lists, asset registers and policy requirements often introduce obligations repeated nowhere else.
• In the response template itself. Word counts, character limits and 'do not exceed two sides of A4' instructions live in the answer boxes — and breaching them can void a response.
• In clarifications and addenda. Buyers issue answers and amendments during the live period; these are binding and routinely change deadlines, scope or scoring. Re-read every addendum.
• In the pricing schedule instructions. 'Rates must be fully inclusive' or 'do not alter this spreadsheet' are easy to miss and commonly disqualify bids.
• In weighting footnotes. Minimum quality thresholds and abnormally low tender clauses are often a single line of small print.
• In the contract KPIs. Service credits and performance regimes define what 'good' looks like — and what it costs — once you have won.

Worked example: reading a council grounds-maintenance ITT

A landscaping SME downloads a five-year grounds-maintenance ITT from a county council's In-Tend portal. The pack is 140 pages across nine documents. Instead of reading start to finish, the bid manager works the method:

• Orientation pass (10 minutes): nine documents identified — ITT, SQ, specification, pricing schedule, four schedules and the contract terms.
• Deadlines: submission at 12:00 on the 28th via the portal; clarifications close on the 14th; a mandatory site visit on the 9th — the earliest and easiest deadline to miss.
• Mandatory requirements: £10m public liability, £5m employer's liability, ISO 9001, a CHAS (or equivalent SSIP) accreditation, and a Carbon Reduction Plan under PPN 006. The firm holds everything except an up-to-date CRP — flagged on day one, with three weeks to publish one.
• Specification: 47 'must' obligations extracted, including reactive-works response times and a mandatory pesticide-use policy hidden in Schedule 3.
• Award criteria: 60% quality / 30% price / 10% social value, with a minimum quality threshold of 60%. Two questions carry half the quality marks — that is where the writing effort goes.
• Contract terms: service credits for missed grass-cutting cycles, and a TUPE transfer of nine staff — a real cost the price must absorb.

By lunchtime, the bid manager has a complete requirements matrix and a confident bid/no-bid decision — not a vague sense of a big document and a looming deadline. The CRP gap alone, caught on day one, is the difference between a compliant bid and an automatic exclusion.

Your requirements-extraction checklist

Run through this as you read any tender pack:

• ☐ The submission deadline (date, time, time zone) and method are recorded in one place.
• ☐ The clarification-question deadline and any site-visit or bidder-day dates are noted.
• ☐ Every document in the pack is listed with its role (instructions, selection, specification, pricing, terms).
• ☐ All cross-references ('see Schedule X') have been followed and logged.
• ☐ Every mandatory pass/fail requirement (turnover, insurance, certifications, policies, CRP) is captured.
• ☐ Each 'must' and 'shall' obligation in the specification is extracted.
• ☐ The award criteria, weightings, scoring scale and any minimum quality threshold are understood.
• ☐ Word counts, page limits and formatting rules from the response template are recorded.
• ☐ Key contract terms (liability, liquidated damages, TUPE, payment) have been reviewed for risk.
• ☐ All clarifications and addenda issued during the live period have been read.
• ☐ Everything is consolidated into a single requirements/compliance matrix.

Common mistakes when reading a tender

• Reading front to back. Linear reading wastes time and buries the requirements that matter among detail that doesn't. Read by document role, requirements first.
• Treating the specification as the whole tender. Mandatory obligations also live in the SQ, the schedules, the pricing instructions and the contract terms.
• Ignoring addenda. Amendments issued mid-competition are binding and routinely change deadlines, scope or scoring. Check the portal regularly.
• Skimming the response template. Word and page limits are easy to miss, and breaching them can void an answer.
• Confusing 'should' with 'must'. Only mandatory language ('must', 'shall') creates a pass/fail obligation — but missing a genuine 'must' is fatal.
• Leaving the contract terms to the end, or to no one. Liability, TUPE and liquidated damages decide whether the work is profitable; read them before you commit.
• Not writing it down. A requirement you noticed but didn't capture is a requirement you'll forget. Build the matrix as you read.

Let BidPilot do the first read for you

Conclusion

Reading a tender well is a method, not a marathon. Work the pack in order — deadlines, mandatory requirements, specification, scoring, contract terms — capture everything in a requirements matrix, and follow every cross-reference into the schedules where obligations hide. Do that, and the two nightmares of bidding (disqualification on a technicality, and winning unprofitable work) simply stop happening.

Once you have read the document and extracted its requirements, the next step is to interpret them: deciding whether to bid and how to win. Use our bid/no-bid decision checklist to make the call, and our step-by-step tender analysis guide to work through the detail.

Related guides: How to analyse a UK tender document, what is pass/fail in procurement, tender evaluation weighting, common tender disqualification reasons, and PPN 006 Carbon Reduction Plans.

Authoritative sources

• GOV.UK — Find a Tender service (higher-value public contracts).
• GOV.UK — Contracts Finder (lower-value public contracts).
• GOV.UK — The Procurement Act 2023: a short guide for suppliers.
• GOV.UK — Selection questionnaire (standard SQ) guidance.