When the Tender Pack Disagrees With Itself

Tender documents are meant to tell suppliers what they are bidding for.

This sounds obvious enough that Parliament has effectively written it into the machinery. Under the Procurement Act 2023, a contracting authority should not invite tenders until the tender notice and associated documents contain enough information for suppliers to prepare them; the requirements themselves are supposed to be sufficiently clear and specific.

And yet a tender pack is rarely one document.

There may be an invitation to tender, a specification, several schedules, a pricing workbook, selection material, contract terms, appendices, technical drawings and, once suppliers start asking questions, a clarification log. During a competitive procurement, the buyer may also modify the tender documents. A supplier's clarification question can itself reveal something that needs to be amended.

So the pack that is supposed to provide the answer can also change while somebody is reading it.

For bidders, this produces a particularly irritating species of work: document archaeology.

One file says £5m of insurance. Another says £10m. A schedule appears to make a certificate mandatory; another seems to qualify the requirement. The pricing workbook contains an instruction that does not quite fit the specification. Somebody has uploaded a document called FINAL, followed two days later by another document whose existence raises uncomfortable questions about the first one's career prospects.

The instinct is to ask: which one is right?

That is usually one question too early.

First establish what is actually conflicting#

Two pieces of tender information can look inconsistent without necessarily being competing instructions.

One may be an old version. One may have been superseded by a formal clarification. One provision may apply only to a particular lot, service or stage. A general requirement may be qualified elsewhere by a more specific one. Or the documents may genuinely disagree.

Those situations should not be collapsed into the same thing.

A useful first pass is therefore less legal than forensic:

1. What are the two statements?
2. Where exactly do they appear?
3. Do they concern the same requirement?
4. Which versions of the documents are they in?
5. Has either document subsequently been amended?
6. Is there a clarification notice dealing with the issue?
7. Does the procurement specify an order of precedence between documents?

That last question matters because there is no sensible universal rule that says, for example, “the specification always beats the ITT” or “the newest-looking PDF wins”.

Procurement and contract documents can establish their own hierarchy. One published Greater London Authority contract, for example, contains an explicit order of precedence covering contract terms, tender clarifications, the specification, tender responses and later clarification material. Its existence is useful precisely because it shows why hierarchy has to be established from the documents themselves rather than imagined by the bidder.

Where an order of precedence exists, it can resolve what otherwise looks like a contradiction.

Where it does not, things become more interesting.

A clarification can change the pack#

The Procurement Act expressly provides for modifications to the terms of a competitive procurement. Those terms include material in the tender notice and associated tender documents, including requirements, conditions of participation and award criteria. Cabinet Office guidance gives the obvious example: a supplier asks a clarification question and the answer reveals that the documents need amending.

When modifications are made, the authority has notification and transparency obligations. Official training material says changes should be made clear and details made available to suppliers at the same time; authorities must also consider whether bidders need more time to respond.

That means the clarification log is not necessarily supplementary reading for the unusually conscientious.

It may contain information that changes how the original pack should be read.

This creates a slightly unpleasant property of modern tendering: understanding the requirement may require understanding its history.

The instruction on page 46 may have been perfectly clear when published. It may no longer be the operative instruction three weeks later.

The dangerous response is quiet interpretation#

A bidder eventually has to make assumptions. That does not mean every uncertainty should be converted into one privately.

Where a contradiction could affect eligibility, price, technical compliance, mandatory evidence, scoring or the shape of the proposed solution, silently selecting the interpretation that seems most convenient can create a much larger problem at evaluation.

Procurement lawyers consequently place considerable weight on clarification. Bevan Brittan, for example, describes a “wait and see” approach by bidders as potentially risky and points to clarification as the mechanism for resolving issues before they prejudice the bid.

The practical distinction is materiality.

A stray difference in terminology may not justify turning the clarification portal into a correspondence course.

A £5m difference in an insurance requirement probably deserves more attention.

So does an apparent contradiction about whether a certification is mandatory, whether subcontractors can satisfy a condition, whether experience must belong to the bidding entity, or whether a pass/fail threshold applies.

The question is not simply whether two sentences disagree.

It is whether choosing wrongly changes the bid.

Clarification is not a licence to stop reading#

There is an opposite failure mode: spotting ambiguity and immediately throwing it back at the buyer.

Before raising a question, a bidder should usually establish whether the answer is already somewhere else in the procurement record. That means checking the current document set, amendments, clarifications and whatever hierarchy the buyer has established.

Apart from avoiding unnecessary questions, this changes the quality of the question itself.

The work is not merely reading. It is maintaining provenance: statement, source, version, status.

Large bid teams can distribute that job across procurement staff, subject specialists, commercial teams and legal advisers.

In a smaller company, it can belong to whoever happened to open the ZIP file first.

The real burden is keeping the contradictions alive#

Software has an awkward habit around inconsistent information: it likes resolution.

One figure goes into a field. One requirement becomes canonical. Duplicate statements are merged. A summary is produced.

That is useful only when the underlying material deserved to be merged.

Mighty Andy is being built around the opposite rule for tender analysis: where two relevant sources genuinely disagree, the disagreement should survive the analysis.

The useful output is not:

It is closer to:

The distinction seems small until somebody has to stake a bid on it.

The purpose of that kind of analysis is not to automate the bidder's judgement. It is to stop the machinery underneath the judgement disappearing: where the requirement came from, whether it changed, what remains uncertain and what needs somebody's attention.

Tender packs will not become single, perfectly ordered documents because bidders would find that more pleasant.

They are assemblies produced by different people, functions and stages of a procurement. Some change. Some qualify others. Some acquire clarifications. Occasionally, two of them simply disagree.

The important thing is not to make the disagreement disappear before anyone notices.