How to read a tender pack without losing a day to it

The first tender pack a supplier downloads is usually the reason the second one never gets downloaded. Fifteen files, several hundred pages, and no obvious place to start. But packs are more standardised than they look, and there is a reading order that tells you what you need in about an hour.

Read in this order, not front to back

The document you are given first is rarely the one that decides anything. Go looking for these, in this sequence:

• The instructions to tenderers — deadlines, submission method, format rules, and the clarification window. Everything procedural that can void your bid is here.
• The evaluation or award criteria — how the marks are split between price and quality, what each scored question is worth, and how scores are described. This tells you where to spend your effort.
• The selection or qualification requirements — insurance levels, turnover, accreditations, exclusion questions. The disqualifiers.
• The specification — what actually has to be delivered.
• The contract terms — particularly liability, termination, and payment.
• The pricing schedule — read it before you write anything, because it often reveals what the buyer really wants.

If the first three raise a problem, you have spent an hour rather than a week.

The scoring is the brief

Most losing bids are well-written answers to a question nobody asked. If a question is worth 15% and asks about mobilisation, the answer is about mobilisation — not about your company's history, however good it is. Where a scoring guide describes what "good" and "excellent" look like, treat that description as a checklist and make sure each element is visibly addressed. Evaluators mark against the guide, not against your prose.

Note the word limits, and note whether appendices count. A brilliant answer that exceeds the limit is often truncated or scored zero.

Build a compliance matrix before you write

Make a simple table of every requirement, where it appears, who in your business owns the answer, and what evidence backs it. It is dull and it is the single highest-value hour in the process: it turns "have we covered everything" from a worry into a check, and it makes the final review possible for someone who was not writing.

Use the clarification window properly

Questions are answered to all bidders, which makes suppliers reluctant to ask. Ask anyway, but ask well. Questions that clarify an ambiguity, a contradiction between documents, or a disproportionate requirement are worth asking — a buyer who realises two documents disagree will usually fix it, and that fix may be worth more to you than the confidentiality you gave up.

Do not ask questions whose answer reveals your approach, and do not leave them to the last day: clarification windows close well before the submission deadline, and the answer may change what you write.

Give yourself a submission buffer

Portals are busy at deadlines, uploads fail, and files are larger than you expect. Aim to submit a day early. The most avoidable way to lose a public contract is to be assembling a submission at the moment the portal closes, and it happens constantly.

Triage before you commit the team

Two people should not start writing before someone has done the hour described above. Make the first read a deliberate, single-person job with a defined output: a short note saying what the contract is, what the disqualifiers are, how the marks are split, when it closes, and a recommendation to bid or not.

That note is what the bid/no-bid conversation should be about. Without it, the decision is usually made by whoever is most enthusiastic, on the basis of the title.

Read the contract terms before the specification excites anyone

The specification describes work you probably want. The contract describes what you are agreeing to, and it is where the problems live: liability caps, service credits, indexation, termination, intellectual property, staff transfer obligations. On public work these are frequently non-negotiable, which makes reading them early more important, not less.

If a term is genuinely unacceptable to your business, that is a no-bid — and it is much cheaper to discover on day one than after the pricing is done.

Note what the pack does not say

Gaps are information. If a specification does not state volumes, or the incumbent arrangement, or why the contract is being tendered now, those are the questions worth asking. A requirement that is vague at tender stage tends to become contested at delivery stage, and the clarification answers become part of the contract documentation — which is exactly why asking is worth more than assuming.