Numbered, Owned, Incorporated: A Tender Clarification Register That Survives Award

Tender clarifications have an awkward habit of being important and ephemeral at the same time. A bidder asks whether a particular finish, tolerance or delivery sequence is acceptable. The answer is sensible. It is circulated by email, copied into a Q&A log, and then overtaken by the next round of questions. By the time the contract is signed, the commercial team may be relying on an answer that exists only in a portal thread and the memory of those who attended the dialogue sessions.

That is not a record. It is a trace. A trace can be useful in a post-award discussion, but it is a weak foundation for a contractual obligation. The clarification register is the discipline that turns the trace into a record.

The Q&A log answers questions; it does not settle obligations

Most UK tender processes generate a Q&A log. It performs a necessary function: it gives bidders a common source of answers and reduces the risk of one bidder receiving a private explanation that others never see. But a Q&A log is usually an administrative document. It is not drafted as a contract schedule, it may not state which bidders are affected, and it rarely records whether the answer is intended to bind the parties after award.

That gap matters most where the clarification changes something a bidder would otherwise price differently. If the answer affects scope, specification, programme, risk allocation or payment mechanics, it is not merely a question of interpretation. It is a commercial term waiting to be written down properly.

A clarification register should therefore be treated as a live commercial instrument, not a helpdesk log. It should be numbered, owned and capable of being incorporated into the contract without reconstruction after the event.

Five fields that make a clarification usable

A practical register can be built around five fields. The format need not be elaborate, but each field should be completed before the answer is issued, not after award.

1. Reference. A unique number, such as CR-014, with the date of issue and the tender stage. Numbering allows the answer to be cited in evaluation, correspondence and the contract schedule without ambiguity.

2. Question as asked. Record the question in the bidder's own terms, with enough context to show why it mattered. Paraphrasing too early can lose the commercial point. Where the question was raised orally, record who raised it and when it was confirmed in writing.

3. Answer and authority. Set out the clarification clearly, identify who issued it and confirm that they had authority to do so. An answer from an individual who cannot bind the organisation is not a clarification; it is an opinion.

4. Bidders affected. State whether the answer applies to all bidders or only to a named bidder, and why. If confidentiality prevents wider circulation, record the reasoning and ensure the evaluation team applies a consistent baseline. Selective clarification is a fairness risk, not just an administrative detail.

5. Contract incorporation. Record the intended contractual destination: a contract clause, a schedule, an appendix to the specification, or an agreed departure. State the status as draft, agreed, incorporated or excluded. If an answer is not to be incorporated, say so expressly and explain why.

These fields can sit alongside version control, an owner and a review date. The point is not bureaucracy. The point is that a clarification which cannot be traced to a contract provision is a clarification the project may later have to argue about.

Fair comparison depends on a common baseline

A clarification register also supports fair bid comparison. Evaluation is only meaningful if bidders are pricing the same requirement. Four tests are useful before tender returns are assessed.

First, same question, same answer. Where two bidders raise the same point, the register should show a consistent response. If the answer changes, the earlier entry should be superseded rather than quietly overwritten.

Second, one channel, one version. Answers should be issued through the formal tender channel and reflected in the register. Verbal assurances at site visits or in dialogue sessions should be confirmed in writing before they are relied upon.

Third, bidder acknowledgement. For material clarifications, ask bidders to confirm that their tender reflects the answer. That confirmation is a useful check that the message has landed and a useful record if it later appears not to have done.

Fourth, evaluation against the register. The evaluation team should have the current register in front of them and should note where a bidder has priced an assumption that a clarification has already displaced. A bid that is attractive only because it ignores a clarification is not a comparable bid.

Incorporation is a drafting decision, not an afterthought

When the contract is prepared, the clarification register should be considered alongside the tender documents and the bidder's response. The contract should state how clarifications are incorporated and what happens if there is a conflict. A schedule of clarifications can be effective, but only if it is referenced in the agreement and drafted with the same care as any other schedule.

A common failure is to rely on the portal remaining available. Portals are administrative systems; they are not a substitute for a contract document. Another failure is to assume that the winning bidder's tender response incorporates every answer automatically. That may be the intention, but it should be expressed in the contract rather than inferred from the process.

Where a clarification is commercially significant, the safer course is to reflect it in the operative wording and record the register entry as the source. Where it is minor, the register can still preserve the audit trail without cluttering the contract. The register does not need to make every answer a clause. It needs to make every answer capable of being found, understood and, where appropriate, enforced.

A short routine for commercial teams

Before issuing an answer, complete the five fields and confirm that the answer is within the issuer's authority. After issuing, update the register and check that affected bidders have received the same version. Before evaluation, test the register for consistency and confirm that no material answer remains only in an email. Before signature, agree the incorporation route and reference it in the contract. After award, keep the register with the contract file and use it during handover so the delivery team knows what was promised.

None of this removes the need for judgement. Tender processes are commercial conversations, and some answers will evolve. But evolution should be recorded, not concealed. A numbered clarification register gives the tender record a life after award: not as a historical archive, but as a working reference that connects what was asked, what was answered and what the contract now requires.