Why clarifications are mispriced
Most bid teams treat clarifications as friction - 'we are bothering the buyer' or 'we will look like we have not read the ITT'. This is exactly backwards. A short, well-targeted clarifications register signals that you have read the ITT carefully enough to find its ambiguities. Buyers reward that.
The teams who avoid clarifications end up assuming, and assumptions show up either in the price (over-priced and uncompetitive) or in the contract (under-priced and unrecoverable). Either way the bid was won or lost in the assumption, not the response.
The five questions every clarifications session should answer
- Are there scope items in the ITT we cannot price without further information?
- Are there contractual clauses (LDs, retention, payment terms, indemnities) we would respond to differently if we knew the buyer's position?
- Are there technical specifications that conflict with each other or with referenced standards?
- Are there programme constraints (access windows, parallel works, decant) that drive material cost?
- Are there evaluation criteria where we cannot tell what 'excellent' looks like to this buyer?
How to write a clarification a buyer will actually answer
Buyers read tens of clarifications. The ones they answer fully are the ones that make their job easy: short, single-issue, referenced to a specific ITT clause, and proposing a default if the buyer chooses not to respond.
Format: 'In section X clause Y, the requirement states Z. We have interpreted this as A. Please confirm, or advise the alternative interpretation. If no clarification is received by [date], we will proceed on interpretation A and reflect this in our pricing assumption.'
That last sentence is the one most teams omit. It tells the buyer that silence has consequences - and it gives you cover when the contract is signed.
The discipline that turns a register into an asset
- One owner per clarification - never 'the bid team'. If a buyer comes back with a question on the answer, you know who they meant.
- Number them. CL-001, CL-002. Buyers will reference your numbering in their response - it is more efficient than lifting your prose.
- Track received-by-date and answered-by-date. Buyers who slip your clarification deadlines weaken their procurement case if it goes adversarial later.
- Cross-reference every clarification to the RTM row it relates to. The bid library then carries a triple - requirement, clarification, response - that survives into the next ITT.
What this looks like in BuiltAI
Bidroom-in-a-Box logs every clarification with its requirement reference, owner, deadline and default interpretation. The bid QA gate at submission lists every clarification still outstanding and surfaces the assumptions that will travel into the contract. No clarification disappears between bid submission and contract signature - the buyer's answer (or absence of one) becomes part of the assumptions register the contract is signed against.