Ask clarification questions that change your bid

A clarification question is worth sending only if its answer would change your solution, your price or your score, and only if it reaches the buyer early enough for that answer to change the bid. The stage isn't over when the answers arrive, either. It closes once every published answer, rivals' included, is in your compliance matrix, drafts and pricing. The sections below follow the work in order: setting the timetable, filtering the questions, wording them, approving and sending them, applying the answers and handling the gaps.

Who runs the clarification stage and what they need

Give one named person ownership of the buyer's clarification channel, and name an approver for each area a question can touch: technical, commercial and legal. The owner can be the bid manager or the tender manager running the response. What matters is that every question going out and every answer coming back passes through one person who answers for what the bid then says. The approvers are the people who already own those areas on the bid: the solution lead for technical points, whoever owns pricing for commercial ones, and legal for contract terms.

The clarification stage is one part of running a whole tender response, and it draws on inputs the team should have open from the first read of the pack:

• the instructions to bidders, with the clarification deadline, the named channel and any rules on late or sensitive questions
• the award criteria, weightings and marking scheme
• a clarification log, with columns for the clause, the question, the test it passed, the approver, the date sent, the answer, what it affects and the assumption you'll bid on if you don't ask

The assumption column is the one that gets forgotten, and it's the one that protects you when you decide not to ask.

Set the clarification timetable on day one

Work back from the buyer's clarification deadline and fix two internal cut-offs before anyone reads the pack in depth: one for writers and subject matter experts to propose questions, and one for approvers to clear them. The reason is simple. An answer only matters if it comes back with enough time to change the solution and the price, and a question that sits in someone's inbox for a week eats that time.

Batching helps. Everything proposed by the first cut-off goes to approvers as a set and out to the buyer together, and a smaller second round catches the gaps that only surface once drafting starts. You can see where the clarification window sits in the tender timeline and plan the rest of the bid around it.

Timing is also a lever. In EU member states, Directive 2014/24/EU obliges the buyer to answer a question asked in good time at least six days before the tender deadline, or to extend the deadline. A late or insignificant question earns no extension. A question that matters, sent early, either gets you an answer you can use or moves the deadline. One sent late earns nothing.

In the UK, take the timetable from the buyer's own instructions: read the clarification period and what it says about late questions, and set your cut-offs against those dates.

In SEQUESTO: specialist agents in Agent Force, part of SEQUESTO aOS, extract every dated requirement in the tender, including the clarification deadline, into the tender timeline from day one. James then adds your internal sign-off stages as milestones, each with time and a named reviewer allocated.

Ask only what would change solution, price or score

Raise a question only when its answer would change your solution, your price or your score; for every other gap, bid on an assumption you've logged. That filter matters more than any wording advice, because a question you didn't need costs approver time and tells rivals something about you, and it gains you nothing in return.

The three tests

Run each gap in the log against these three, and record which one it passes:

1. Solution. Would the answer change what you propose to deliver, how you'd deliver it or with whom? A scope boundary that decides whether a service is in or out passes. A detail you'd handle the same way whichever way the buyer answers doesn't.
2. Price. Would it change a cost line, a risk allowance or the pricing model? Volumes, contract length and who carries a cost are the usual candidates.
3. Score. Read the gap against the award criteria, their weightings and the marking scheme. A gap in a heavily weighted question, where the answer decides which mark band you can reach, passes. So does an unclear pass/fail requirement, since misreading it can cost the bid outright.

A gap that passes none of the three goes into the assumption column. A gap that passes one still has to clear a second question: what does asking it reveal? Anonymised questions still reach every bidder, so a question that exposes a differentiating approach can cost more than the answer is worth.

When to bid on an assumption instead

Bid on an assumption when no test passes, or when the answer would change the bid but the only way to ask would reveal your approach to rivals. In that second case, first try to word the question neutrally; if you can't, decide deliberately and record the decision with the clause and the reason.

Before relying on an assumption, check the instructions. Some treat a stated assumption as a qualification of the bid, and a qualified bid can fail where an unanswered question wouldn't. Write the assumption into the response only in the form the documents allow, and keep the same wording in the log so the bid manager can see every assumption the bid rests on at sign-off.

Word each question for every bidder to read

Write every question as if each rival will read it, because the buyer may publish it to all of them with only your name removed. Wording decides whether the answer settles the point and whether the question gives your approach away.

What anonymity does not hide

The OECD Guidelines for Fighting Bid Rigging in Public Procurement (2025 update) tell buyers to resolve suppliers' queries about the tender process and specifications online and anonymously. That removes your name. It doesn't remove what the question says. Asking whether the buyer would accept a particular delivery model tells every rival that someone is planning to offer it.

Two habits leak the most. The first is the what-if: "would you welcome an option for X?" can prompt the buyer to add X as a requirement for everyone, so you raise the bar you meant to clear alone. The second is bundling several issues into one question, which invites a partial answer and shows more of your thinking than any single issue would. There's more on what a question signals to the buyer and to rival bidders if you want to go further.

A wording template

Build each question from four parts, in this order:

1. The reference: document, section, clause or page.
2. What the document says, quoted or closely paraphrased.
3. The issue, in one sentence: what is ambiguous, contradictory or missing.
4. A closed question that offers the options: "Please confirm whether bidders should A or B."

As an illustration, where the specification and the pricing schedule give different contract terms, the question might read: "Clause [x] of the specification states a contract term of [term]. The pricing schedule asks for prices over [term]. Please confirm which term bidders should price." It names nothing about your solution, raises one issue, and leaves the buyer a choice between options rather than an essay to write.

Approve each question and send it through one owner

Have each question approved by the owner of the area it touches, then by the bid manager, before the named sender puts it through the channel the tender documents specify. A clarification question is a written statement to the buyer that rivals may read, so it deserves the same scrutiny as any answer in the bid.

The area approver checks that the question is needed and that its wording doesn't concede a point or reveal the approach. The bid manager's approval confirms it passed the three tests and fits the timetable. Record both in the log against the question.

Keep a single sender even when partners or subcontractors have questions of their own. They send them to the owner, who puts them through the same tests and approvals. Two voices from one bid on the same channel can ask overlapping questions, contradict each other or reach the buyer outside the named channel altogether.

Keep the portal receipt or sent message for every question, and rely only on answers given in writing through that channel. If a point comes up in a phone call or a site visit, ask for it in writing before you change the bid. A spoken answer is hard to stand behind once the bid is signed off.

In SEQUESTO: a configurable workflow can give clarification questions their own item type and review chain, so each question reaches its technical, commercial or legal approver and then the bid manager. Once approved, the named sender puts it through the buyer's channel, since a person on the team always submits.

Work every published answer into the bid

Treat every published answer as a change to the tender pack, whoever asked the question, and close it only once you've checked it in the compliance matrix, the drafts and the pricing. Answers to rivals' questions count as much as your own: buyers share significant answers with every bidder, so the answer that changes your bid may come from a question you never thought to ask.

Read every clarification bulletin as soon as it's published, and log each answer the same day. For each one, record the compliance matrix rows it touches, every draft section that relies on the point and every price line it affects. Then give each of those an owner and a date. An answer can also change a word limit, a template or a mandatory attachment, so check it against the instructions as well as the content.

Closing an answer means verifying it, not assigning it. Open each affected row, section and price line, confirm the change is made, and record who checked it and when. An answer marked "sent to writer" isn't closed.

Answers that amend the documents need one more check. In EU member states, the Directive also obliges the buyer to extend the time limit where it makes significant changes to the procurement documents. After any answer that changes the pack, re-read the portal and the instructions for a new submission date and move your internal timetable if it has changed.

Act on missing, late or contradictory answers

Treat a missing answer as no answer, never as agreement, and decide how to handle each gap before the internal cut-off for final drafts. Every question in the log needs an outcome: an answer applied, a follow-up sent or an assumption stated.

No answer

Bid on a stated assumption where the documents allow it, written into the log and the response in the same words. If you're working under the Directive and asked in good time, the buyer's duty to answer or extend (set out above) gives you grounds to chase. Send the chaser through the same channel, citing your question and the date you sent it.

A late answer

Apply it, even if it lands after your internal cut-off, and check at once whether the submission date has moved. If you don't have time to apply it everywhere, work first on the pass/fail requirements and the most heavily weighted questions it affects, then record what you couldn't change.

An answer that contradicts the pack

Send a follow-up that cites both sources and asks the buyer to rule between them. Quote the clause and the answer's reference side by side, then close the question: "Please confirm whether bidders should follow clause [x] or the answer to clarification [y]." A closed question invites a ruling.

Clarification stage checklist

Use this on each tender to confirm the stage is complete before submission:

• The clarification deadline, the named channel and both internal cut-offs are in the bid timetable, with a named channel owner and approvers for technical, commercial and legal points.
• Every logged gap has a recorded result against the solution, price and score tests, and every gap that failed them has an assumption in the log.
• Every question cites its clause, raises one issue, asks a closed question and has been read for what it would tell a rival.
• Every question sent has a recorded area approver, the bid manager's approval, a send date and a receipt.
• Every published answer, rivals' included, is mapped to its matrix rows, drafts and price lines and marked verified with a name and date.
• The submission date has been re-checked after every answer that amended the documents.
• Every unanswered, late or contradictory answer is closed with a follow-up or a stated assumption.

Open the log on the day the next tender lands, and set the two cut-offs before anyone starts writing.