How to read a tender pack

Start with the decision, not the document pile

A tender pack is not a book you read from page one to the end. It is a decision bundle. The buyer has usually split one commercial question across several files: can you deliver this work, can you prove it, can you price it without regret, and can you submit in the exact way requested before the deadline. Read the pack in that order. A small supplier does not need to admire the whole archive before making a first call. You need a fast, evidence-led answer to whether the opportunity deserves deeper work.

The first pass should take minutes, not hours. Open the invitation to tender or request for quotation first, then the specification, then the pricing document, then the contract terms, then any standard questionnaire. Keep a scratch note with five headings: deadline, fit, proof, price, traps. If any heading gets a hard red answer, pause before reading further. TenderReader's product brief follows the same shape because the useful question is not 'what does every page say?' It is 'what has to be true for this to be worth bidding?'

Public-pack example, anonymised: a local authority cleaning opportunity looked attractive in the notice because the title was short and the value sat inside a typical small supplier range. The pack changed the decision. The specification required supervised cover before 7am across multiple sites, the contract terms required a named escalation manager, and the pricing sheet asked for separate rates by site and by periodic deep-clean task. None of those facts made the bid impossible, but they changed the staffing, proof, and margin picture immediately.

Know the usual pack anatomy

Most UK tender packs contain some version of five document types. The invitation to tender, often called ITT, tells you the process: timetable, submission portal, evaluation method, clarification rules, and the documents you must return. The specification or service brief tells you what has to be delivered. The SQ or selection questionnaire asks whether you are eligible and suitably qualified. The pricing schedule tells you how to present your price. The contract terms tell you what you are agreeing to if you win.

Names vary. A request for quotation can hide the same structure inside one PDF. A framework mini-competition may rely on call-off terms from the original framework and add a short statement of requirements. A construction pack may use drawings, preliminaries, and bills of quantities instead of a friendly service specification. A care or support pack may put safeguarding and mobilisation requirements in appendices. Do not be thrown by labels. Ask what job each file is doing.

The mistake is treating every file as equally urgent. Process documents decide whether you can submit. Specification documents decide whether you can deliver. Commercial documents decide whether you can make money. Contract documents decide whether the risk is acceptable. Evidence documents decide whether you can score. When you know which question a file answers, you stop drowning in pages and start building a decision.

Read the timetable before the story

The timetable is the first hard gate. Find the submission deadline, the clarification deadline, site-visit dates, interview dates, mobilisation start, contract start, and any mandatory portal registration step. A bid that misses the clarification window may be forced to guess. A bid that misses a mandatory site visit may be rejected even if the written response is strong. A bid with a mobilisation date too close to your current workload can become a delivery risk before it becomes revenue.

Deadline traps often sit outside the obvious deadline line. Some portals close at noon, not midnight. Some buyers require uploaded files to be named in a specific way. Some require the pricing workbook and quality response as separate attachments. Some reject late uploads even when the portal itself is slow. Treat the deadline as the last safe moment, not the working plan. For a small team, the internal deadline should normally be at least one working day earlier.

Write the timetable into a calendar during the first pass. If the buyer has a clarification process, note the question deadline and the expected response date. If the pack says answers to clarification questions will be shared with all bidders, do not reveal your strategy in the question. Ask for factual clarity: missing appendices, unclear quantities, inconsistent dates, whether TUPE applies, whether site access can be arranged, or whether the buyer will accept an equivalent certificate.

Check eligibility before enthusiasm takes over

Eligibility is the fastest place to waste time. Look for pass/fail requirements before you read the nice parts of the opportunity. Common gates include insurance levels, accounts history, required accreditations, professional registrations, safeguarding checks, cyber certifications, health and safety evidence, audited accounts, minimum turnover, previous contract examples, and exclusions around conflicts of interest. Some are mandatory at submission. Others can be in place by contract start. The difference matters.

A red eligibility item is not always a stop sign, but it is always a decision. If the buyer asks for GBP 10m public liability and you carry GBP 5m, ask whether the higher level must be in place at award or only before contract start. If the pack asks for ISO certification and you have an equivalent documented process, ask whether equivalent evidence is accepted. If the pack asks for three similar contracts and you have two strong examples plus subcontractor support, decide whether the score risk is acceptable.

Public-pack example, anonymised: an IT services pack asked for Cyber Essentials Plus and two named security roles. The supplier had Cyber Essentials, not Plus, and one person covering both roles. The opportunity was still technically deliverable, but the eligibility and scoring risk moved it from 'strong fit' to 'only bid if the buyer confirms equivalence'. That question had to be asked before the team spent two days writing method statements.

Separate what is mandatory from what is scored

Tender language can blur three different ideas: must, should, and would like. Mandatory requirements decide whether your bid is compliant. Scored requirements decide how many points you win. Nice-to-have preferences may influence the buyer but usually do not carry explicit pass/fail force. Read modal verbs carefully. 'Must provide' is not the same as 'should describe'. 'Tenderers are required to' is stronger than 'the authority expects'. If the pack has a compliance matrix, use it as your map.

The evaluation criteria show what the buyer will reward. If quality is 60 percent and price is 40 percent, the written method matters. If price is 80 percent, the commercial model carries most of the decision. If social value has a separate score, generic charity statements will not be enough. If presentation or interview is scored, the bid workload extends beyond submission. A good bid/no-bid call checks whether you can score, not just whether you can deliver.

Build a two-column note: mandatory evidence and scored evidence. Mandatory evidence includes certificates, policies, declarations, accounts, insurances, and signed forms. Scored evidence includes method statements, case studies, mobilisation plans, risk registers, social value commitments, and contract management approach. This split stops a common failure: writing a beautiful answer while forgetting a required attachment.

Read the specification for the operating model

The specification is where the work becomes real. Do not only list tasks. Look for frequency, volume, geography, access windows, service levels, response times, reporting requirements, named systems, buyer dependencies, and handover obligations. A cleaning contract with daily tasks across ten sites is a different business from one with weekly visits to one building. A support contract with out-of-hours escalation is different from a daytime-only service. A transport contract with school-term timing has a different staffing rhythm from ad hoc courier work.

Turn the specification into an operating model. Who does the work? How often? From where? With what equipment? Under whose supervision? What proof must be recorded? What happens when something goes wrong? Which tasks are fixed, and which are demand-led? If you cannot describe the operating model in plain words after one read, the pack probably needs clarification or a deeper operational review before bid writing starts.

Pay attention to assumptions hidden in appendices. Asset lists, site lists, volume schedules, incumbent TUPE data, drawings, and sample reports often carry the real workload. If a pack gives a total value but no volumes, pricing may be guesswork. If a pack gives volumes but says they are indicative only, margin risk shifts to you. If a pack says the supplier must validate all measurements, schedule time to do that before pricing.

Open the pricing schedule early

Many teams read the pricing sheet too late. The pricing schedule tells you how the buyer wants the commercial answer shaped. It may ask for fixed annual price, day rates, unit rates, lot prices, mobilisation costs, optional extras, discounts, indexation, or open-book assumptions. The shape of the sheet can decide whether the opportunity fits your business. A supplier with strong day-rate discipline may struggle with a fixed price that absorbs uncertain demand. A supplier with tight route density may dislike a schedule that pays per site without mileage assumptions.

Check whether the schedule permits assumptions. Some buyers forbid caveats and treat them as qualifications, which can make the bid non-compliant. Others provide an assumptions box or clarification route. If the contract transfers volume risk to the supplier, price accordingly or walk away. A low price that wins an unprofitable contract is not a win. It is delayed pain with a purchase order number.

Look for arithmetic traps. Are values exclusive or inclusive of VAT? Are there separate tabs for years, lots, or service lines? Are formulas protected? Does the buyer ask for monthly and annual totals? Does the tender evaluate total contract price, basket price, or rates? If there is an error in the workbook, ask a clarification question rather than silently fixing it. Your pricing must match the buyer's evaluation method.

Treat contract terms as commercial evidence

Small suppliers often postpone contract terms because they feel legal. Read them earlier. Terms can change margin, cash flow, and operational risk. Look for payment terms, liability caps, indemnities, termination rights, performance credits, liquidated damages, data protection roles, insurance levels, audit rights, TUPE, intellectual property, price review, indexation, subcontracting consent, and variation mechanisms. These are not abstract clauses. They decide how bad a bad month can become.

A contract with 60-day payment terms may need working capital. A contract with no indexation in an inflation-sensitive service may become risky in year two. A contract with broad unlimited liability may exceed your insurance. A contract that allows the buyer to vary volumes without price adjustment may transfer demand risk. A contract that restricts subcontracting may remove your delivery plan. None of these automatically means no-bid, but each needs an explicit decision.

If you do not have legal support, at least classify terms into three buckets: acceptable, needs clarification, and unacceptable without negotiation. Procurement processes often limit negotiation after submission. If the pack says contract terms are non-negotiable, do not assume you can fix them after winning. If a clause is a business-breaking issue, ask before bidding or step away.

Find the evidence burden

Every scored answer needs evidence. Buyers rarely want claims alone. They want examples, numbers, named processes, policies, responsible roles, reporting samples, mobilisation plans, risk controls, and proof that you have done similar work. As you read, mark every place where the buyer asks you to 'demonstrate', 'evidence', 'describe how', 'provide examples', or 'confirm'. Those words create work for the bid team.

A good evidence pass asks whether the proof already exists. Can you reuse a case study? Is the policy current? Do you have a named contract manager? Can you show performance data? Can you quantify response times, quality checks, complaint handling, staff training, or customer satisfaction? If the answer is 'we can write something', be careful. Writing is not the same as evidence.

Public-pack example, anonymised: a care services tender asked bidders to describe safeguarding training, escalation, incident logging, and audit. The supplier delivered similar work but had incident logs spread across spreadsheets and email. The opportunity was viable, but the evidence burden was higher than expected. The bid decision became partly an operations clean-up decision.

Read lots and variants with discipline

Lots can make a tender easier or harder. A lot may be geographical, service-specific, value-banded, or buyer-specific. Check whether you can bid for one lot, several lots, or all lots. Check whether the buyer will award multiple lots to one supplier or cap awards. Check whether each lot needs a separate quality response, separate pricing sheet, or separate evidence. A small lot may still create a large writing burden if the pack duplicates the response requirement.

Variants and optional services also need care. If the buyer lists optional extras, decide whether they are truly optional or likely to be called off. If the pack asks for innovation or added value, make sure it does not create unpaid commitments. If the buyer permits alternative proposals, confirm that a compliant base bid is still required. Do not let a clever variant hide a weak mandatory response.

When lots are available, compare fit by lot, not just by whole tender. You may be a strong bidder for a regional maintenance lot and a poor bidder for a national helpdesk lot. You may have better evidence for one service line than another. The best bid/no-bid answer can be 'bid lot 2 only'.

Use clarification questions without showing your hand

Clarification is a tool, not an admission of weakness. Use it to resolve ambiguity that affects compliance, price, or delivery risk. Ask questions that a buyer can answer factually. 'Please confirm whether the insurance level must be in place at submission or before contract start' is useful. 'Will we lose marks if we do not have this exact certificate?' may be harder for the buyer to answer. 'Can you provide volumes by site?' is useful. 'How should we price this?' is not.

Avoid revealing your strategy. Clarification responses are often shared with all bidders. Do not disclose a unique delivery method, pricing assumption, or weakness unless necessary. If you need to ask about an equivalent accreditation, state it neutrally. If a conflict exists between documents, cite the file names and clauses. The buyer may issue an amendment. Save copies of all answers because they become part of your evidence trail.

If a question is critical and the buyer does not answer clearly, record that uncertainty in the bid/no-bid decision. Some ambiguities can be priced. Some cannot. A disciplined no-bid caused by unresolved risk is not a failure. It is a protected margin.

Score the opportunity before writing the response

Before writing, give the opportunity a simple fit score. TenderReader uses a decision-support rubric with components rather than a magic prediction. You can do the same manually. Score strategic fit, eligibility, evidence strength, delivery capacity, margin confidence, deadline pressure, buyer attractiveness, and competition context. Use low, medium, high, or a 1 to 5 scale. The point is not precision. The point is forcing the team to name the reasons.

A strong opportunity usually has a real buyer need, clear scope, manageable terms, credible margin, strong evidence, enough time, and a route to delivery without breaking current commitments. A weak opportunity may still be exciting, but excitement is not capacity. If the only reason to bid is 'it would be great to win', slow down. Procurement rewards proof, compliance, and price discipline more often than ambition.

The score should produce one of three decisions: bid, no-bid, or clarify first. 'Clarify first' is underrated. It stops teams from turning uncertainty into writing effort. If the answer to one factual question would change the decision, ask it before a full response begins.

Make the first-pass output reusable

The first pass should leave artefacts, not only opinions. Create a deadline list, a mandatory evidence checklist, a pricing-risk note, a question list, a one-paragraph scope summary, and a decision note. If you bid, these become the skeleton of the response. If you no-bid, they become learning for the next tender. If you clarify first, they keep the team aligned while waiting for the buyer's answer.

Keep the decision note factual. Good: 'No-bid because the pack requires Cyber Essentials Plus at submission, three similar public-sector contracts, and 24/7 support cover; we have none of those today.' Weak: 'No-bid because it feels too big.' Good: 'Bid lot 1 only because our evidence and route density match the North West sites; lot 2 would require subcontracting not permitted under the draft terms.' This language makes future decisions better.

TenderReader's brief exists to produce this kind of artefact quickly: deadlines, eligibility, values, criteria, source evidence, and a decision-support recommendation. The product does not replace judgement. It helps you put judgement on top of the right facts earlier.

Common red flags

• The submission deadline is close and the pack requires multiple bespoke method statements.
• The buyer asks for evidence, accreditations, or turnover that you cannot honestly provide.
• The pricing schedule transfers uncertain demand to you without enough volume data.
• The terms include liability, payment, or termination clauses that would hurt the business if things go wrong.
• The specification requires geography, hours, equipment, or mobilisation speed that would strain current delivery.
• The evaluation weighting rewards evidence you do not have, not just work you can perform.
• The pack contains contradictions and the clarification deadline has passed.
• Winning would depend on underpricing, unpaid extras, or heroic delivery assumptions.

A 30-minute reading order

Minutes 0 to 5: find the deadline, clarification deadline, submission portal, mandatory site visit, contract start, and required returned documents. Minutes 5 to 10: scan eligibility gates, insurance, certifications, accounts, declarations, and pass/fail wording. Minutes 10 to 15: read the specification headings and appendices for geography, volume, frequency, service levels, and mobilisation. Minutes 15 to 20: open the pricing schedule and contract terms. Minutes 20 to 25: mark evidence burden and scored criteria. Minutes 25 to 30: write bid, no-bid, or clarify-first with reasons.

This is not enough to submit a bid. It is enough to protect your time. Deep reading comes after the opportunity survives the first pass. If the first pass finds a blocker, stop early and spend the saved time on better-fit opportunities. The discipline is simple: read for decision first, response second, polish last.

FAQ

Related pages

• Bid or no-bid decision framework
• Tender pages by sector and region
• Data and accuracy