Tender clarification logs: avoiding mismatched assumptions
Admin · 22 October 2026
Illustrative image. Photo by Pedro Miranda on Unsplash. Unsplash License.
Tender prices are difficult to compare when bidders have interpreted the same information differently. One may include a temporary arrangement, another may exclude it, and a third may have allowed for an alternative specification. A clarification log helps the procurement team expose and resolve these differences before they become embedded in an award recommendation. Its value lies in the quality of the answers and their incorporation into the tender record, not in the number of queries marked closed.
For estimators, consultants and client procurement leads, the challenge is to maintain one reliable account of what has been asked, decided and communicated. Questions arrive through meetings, portals and correspondence, often while design information is still developing. Without a controlled route, an answer can reach one participant and never reach the people pricing or evaluating the affected work.
Give each question a stable identity
Assign a reference to each query and record its origin, date, package and relevant document references. Describe the ambiguity precisely enough that the response owner can investigate it without reconstructing the tender from scratch. A question such as “confirm scope” is too broad. Identifying a conflict between a drawing note and a schedule gives the team something specific to resolve.
Retain the original question even when it is summarised for reporting. A short management description may omit a qualification that matters to the answer. Link related queries rather than deleting them as duplicates without review. Similar questions from several bidders can indicate that the issued information is unclear, while apparently identical wording may refer to different locations or package boundaries.
Route the question to the right owner
Allocate a response owner who has access to the relevant expertise and authority. Technical clarification may need a designer, while a scope boundary may require coordination between commercial and technical teams. Distinguish the person drafting an answer from the person authorised to release it. This prevents a helpful informal comment from being treated as an approved change to the basis of tender.
Set a response date linked to the bidder’s need and the procurement programme. Allow time for review, communication and any resulting repricing. If the question cannot be resolved promptly, state what further information is required and escalate the effect on the tender process. A late answer can be material even when its wording is short, particularly if it changes a supplier selection or a significant quantity.
Separate clarification from change
Some responses explain existing information; others amend it. The team should assess which is happening and use the appropriate issue process. If a drawing or specification changes, identify the superseded information and the new revision. Avoid using a log entry as the only place where a substantive design amendment appears. The tender record should allow bidders to locate the complete current requirement.
The APM explanation of change control provides general context for evaluating changes to an approved baseline. In a tender setting, the project’s procurement rules and contractual arrangements determine the formal process. The working principle is to make the effect of an answer visible, including whether it changes scope, programme assumptions or the information against which bids will be assessed.
Write an answer that can be priced
A useful answer resolves the actual ambiguity. “As specified” is unhelpful when the question concerns conflicting specifications. Identify the applicable requirement and its location, or issue the revised information needed. Where a decision remains open, do not present it as settled. Explain the interim basis the procurement team has formally adopted, if any, and how bidders should address the uncertainty through the stated process.
Check the answer with the disciplines or packages it affects. A change to a component may influence supports, services, access or installation. An answer that resolves one bidder’s question can create a new inconsistency elsewhere. Review these interfaces before release where possible, and record any linked actions. This is particularly important when procurement packages divide design, supply and installation responsibilities between organisations.
Control communication to bidders
Use the communication route established for the procurement and apply its rules consistently. The appropriate handling of bidder-specific information, confidentiality and shared clarifications should be determined by the procurement team. Do not assume that every question can be circulated unchanged or that a material answer can remain in a private email. Seek the relevant advice where the distinction is unclear.
Record when the answer was issued, to whom and with which attachments. Where acknowledgement is required, track it. The evaluation team should know which information formed the basis of each submission. If an addendum is issued close to the deadline, assess the implications for bidder response through the applicable process. A timestamp alone does not establish that the change has been understood and incorporated.
Use the log during bid evaluation
Compare qualifications and assumptions in the returned bids with the issued clarification record. Check whether bidders have incorporated the relevant amendments and identify any departures that remain. A compliant-looking total can conceal an exclusion in an attachment. Bring the commercial and technical reviews together so that a price comparison reflects the actual scope offered rather than only the headline figures.
Consider a hypothetical package where the tender documents leave temporary weather protection unclear. One bidder includes it, another excludes it and the clarification later assigns a defined requirement to the package. Evaluation should confirm how each bid responds to that clarification. The team should not simply deduct the apparent difference without understanding the scope, method and interfaces included in the allowance.
Close queries with evidence
Define what “closed” means in the log. It may require an approved answer, formal issue and incorporation into the relevant documents. A question should not disappear merely because somebody has drafted a response. Where closure depends on later information, keep that dependency visible and identify the responsible person. This prevents a reporting dashboard from showing completion while the tender basis remains uncertain.
Maintain a distinction between the status of the query and the status of its consequences. The answer may be issued while a revised drawing, pricing adjustment or programme review is still outstanding. Linked actions can track those consequences without confusing the original record. Review them before award so that the team understands which matters have been resolved and which require explicit treatment in the agreement.
Carry the record into delivery
The award process should establish the documents and clarifications that form the agreed scope through the appropriate contractual procedures. Do not assume that a spreadsheet automatically has contractual effect. The relevant advisers should confirm how accepted clarifications and qualifications are incorporated. Retain a clear record of the final position so the delivery team does not have to interpret competing tender drafts.
At mobilisation, review the consequential clarifications with the people responsible for the work. Highlight unusual boundaries, accepted alternatives and outstanding information. Estimators may understand assumptions that site personnel have never seen. A structured handover reduces that knowledge gap and gives the project a route for resolving questions against the agreed record rather than individual memories of negotiation.
Finally, review recurring query themes. If several tenders repeatedly generate questions about the same scope boundary, improve the initial documents and package review. A clarification process should resolve the current procurement while producing evidence that makes the next one clearer. Its success is a shared, traceable understanding of the work that bidders priced and the project ultimately agreed to buy.
Archive the issued attachments with the log, using stable references. A link to a document that is later replaced can undermine the record of what bidders actually received. Preserve the issued version alongside the subsequent revision and its explanation.