clarification questions

Clarification Questions: How to Ask Buyers the Right Things Before You Bid

Bidwell14 min read
Clarification Questions: How to Ask Buyers the Right Things Before You Bid

Most bid teams read a tender pack, find three things that make no sense, and then hesitate. Is it allowed to ask? Will the question make us look weak? Will every rival see it? Will the buyer answer in time to matter? The hesitation costs more than the question would have. Teams guess, the guess turns out wrong, and a response that could have scored well loses marks on a point the buyer would happily have cleared up.

Clarification questions are one of the few moments in a live procurement where a supplier can speak to the buyer directly. Used well, they sharpen your bid/no-bid decision, stop you answering the wrong question and occasionally fix a genuine error in the documents. Used badly, they waste a window, reveal your strategy to competitors or arrive too late to help anyone.

This guide covers what you can usually ask, how answers tend to be shared, how to write a question that gets a useful reply, and how to use the answers once they come back. It is written for small teams who are deciding whether a tender is worth the hours, as much as for teams already writing.

What a clarification question is for

A clarification question asks the buyer to explain something in the procurement documents. It is not a negotiation, a sales call or a chance to argue that the specification should be different. The purpose is to make sure every supplier is responding to the same understanding of what the buyer wants and how it will be judged.

In practice that covers a fairly wide range of things:

  • Ambiguity: a requirement that can be read two ways.
  • Contradiction: the specification says one thing and the pricing schedule assumes another.
  • Missing information: volumes, locations, current service levels or data you need to price or plan.
  • Process: word limits, attachments, file formats, how to submit, what happens if a portal fails.
  • Evaluation: how a question will be scored, what counts as evidence, whether a criterion is pass or fail.

The common thread is that each question asks the buyer to clarify something they have already put in front of you. That framing matters, because it is the one buyers are set up to answer.

What you can usually ask, and what you cannot

The exact rules sit in each tender's instructions to suppliers, so the first job is always to read that section. It will usually tell you where to submit questions, the deadline for them, and how answers will be published. Treat it as the rulebook for that procurement rather than relying on what the last buyer did.

Questions buyers generally welcome

  • Questions that point out an apparent error or inconsistency in the documents.
  • Requests for data that every bidder needs to price fairly, such as volumes or site lists.
  • Questions about the scoring approach where the published methodology is unclear.
  • Practical questions about the submission: formats, limits, whether appendices count towards word counts.
  • Questions about whether a particular approach or delivery model would be acceptable, phrased neutrally.

Questions that tend to go nowhere

  • Asking for advice on your answer. "Would this case study be suitable?" invites the buyer to evaluate your bid before submission. Most will decline.
  • Asking who else is bidding. Buyers will not tell you.
  • Asking for the incumbent's pricing or performance in detail. Some information on current service may be shared, but commercial detail about a named supplier generally is not.
  • Lobbying for a change to the specification. You can point out that a requirement may unnecessarily restrict competition, but a question that reads as "please change this so we qualify" is unlikely to land.
  • Questions already answered in the pack. These waste the buyer's time and suggest you have not read the documents.

Questions after the deadline

Most tenders set a clarification deadline some days before the submission deadline, so that answers can be shared in time for everyone to use them. Questions sent after it may be ignored. If something genuinely critical emerges late, it can still be worth asking and stating plainly why it was not raised earlier, but there is no guarantee of a reply. Plan as though the clarification deadline is the real one.

How answers get shared

This is the part that worries suppliers most. In UK public sector procurement, the principle of equal treatment means buyers generally share clarification answers with every bidder, not just the one who asked. The usual pattern is a clarification log or Q&A document published through the tender portal, with the question anonymised and the answer alongside.

Anonymised does not always mean invisible. If your question names your product, your location, your subcontractor or an unusual delivery model, competitors reading the log may work out who asked and what you are planning. The answer reaches them either way. The detail in your question is what gives your thinking away.

Asking for a question to be treated confidentially

Some instructions allow you to request that a question be handled confidentially, typically where it relates to commercially sensitive information specific to your bid. The buyer then decides. If they consider the answer relevant to all bidders, they may publish it anyway, or they may give you the option to withdraw the question. Read the instructions for how that buyer handles it, and do not assume a confidentiality request will be granted.

The answers become part of the tender

A published clarification usually forms part of the procurement documents. That means an answer given to another bidder's question can change what you need to write. A clarification log that grows to forty entries in the last week is not background reading. Someone on the team needs to read every entry and check whether it affects your response, your pricing or your compliance.

Practical rule: assume every word of your question will be read by your strongest competitor, and write it accordingly.

Why clarifications belong in the bid/no-bid decision

Most teams treat clarification as a writing-stage activity. The more valuable use is earlier, while you are still deciding whether to bid at all.

A bid/no-bid decision often turns on two or three unknowns. How many sites are in scope? Is the accreditation a pass or fail requirement, or a scored one? Does the pricing model allow for a mobilisation period? If you cannot answer those from the documents, you are about to commit writing hours on a guess.

A short, early set of clarifications can settle the decision. If the answer confirms that a must-have requirement rules you out, you have saved the whole response. If it confirms the scope suits you, you bid with more confidence and a better idea of where the marks sit. Our bid/no-bid analysis guide sets out a scoring approach, and clarifications are how you fill in the boxes you would otherwise leave blank.

Read the pack once, quickly, for questions

Before anyone starts writing, give one person the job of reading the full pack with a single aim: listing everything that is unclear, contradictory or missing. Not drafting, not planning win themes. Just questions. A pass like this often surfaces issues that would otherwise appear halfway through drafting, when the clarification deadline has passed.

If you want a sense of where your own gaps sit before you take on a tender, the tender readiness checker is a quick self-assessment, and it can help you separate questions for the buyer from questions you need to answer internally.

How to write a clarification question that gets a useful answer

Buyers answer the question you ask, not the one you meant. A vague question gets a vague answer, often a reference back to the document you were already confused by. A few habits make a real difference.

Quote the document

Name the document, section and paragraph, then quote the words causing the problem. "Specification, section 4.2, states that 'the supplier shall provide cover at all sites'. The site list in Appendix C contains twelve sites, while the pricing schedule has rows for nine. Please confirm which list applies." The evaluator, or whoever answers clarifications, can find the issue in seconds and respond precisely.

Ask one thing at a time

A question with four parts tends to get an answer to two of them. Split compound questions. It also makes the published log easier for everyone to use, including you.

Offer the interpretations

Where a requirement is ambiguous, set out the readings you can see and ask which is correct. "Please confirm whether the 250-word limit for question 6 applies to the whole answer or to each of the three sub-parts." A buyer can reply with one word. An open question such as "Please explain the word limit" invites a paragraph that may not resolve anything.

Prefer closed questions where you can

"Is ISO 9001 certification a pass/fail requirement, or will it be scored under question 3?" is easier to answer definitively than "How will quality accreditation be assessed?" Closed questions do not suit everything, but where the decision is binary, ask for the binary answer.

Keep your strategy out of it

Compare two versions of the same question:

  • "We intend to deliver the out-of-hours service from our Leeds depot using our two existing night teams. Would that meet the response time requirement?"
  • "Section 5.1 requires a two-hour response out of hours. Please confirm whether this is measured from receipt of the call or from logging of the job."

The second gets the information you need without telling anyone how you plan to deliver. Ask about the requirement, not about your solution.

Stay neutral in tone

Clarifications are read by buyers who may also, in some procurements, be close to the evaluation. There is nothing to gain from sounding irritated by a confusing document or from implying the buyer has made a mistake. "Please confirm" and "please clarify" do the job. If there is an error, point at it plainly and let the buyer correct it.

Worked examples

The examples below are illustrative, written to show the shape of a good question rather than taken from any real tender.

Scope and volume

Weak: "Can you provide more information about the size of the contract?"

Stronger: "The specification refers to 'approximately' the current call volumes but does not give a figure. Please could the authority provide monthly call volumes for the last twelve months, or confirm that this information will not be provided?"

The stronger version is specific, asks for data every bidder needs, and allows for the buyer to say no, which is itself useful to know when you price.

Evaluation

Weak: "How will social value be scored?"

Stronger: "The assessment methodology gives social value a 10% weighting but question 8 does not state which outcomes the authority is prioritising. Please confirm whether responses should address all themes listed in Appendix F, or whether a response focusing on one theme can achieve full marks."

Under the Procurement Act 2023, buyers must publish how tenders will be assessed, including the relative importance of criteria. A clarification that asks how a published criterion applies to a specific question is squarely within what buyers expect to answer. Our guide to tender evaluation criteria and scoring covers how those methodologies usually work.

Contradiction

Stronger: "The instructions to suppliers state a contract term of three years. The draft contract, clause 2.1, states an initial term of two years with an option to extend by one year. Please confirm which applies for pricing purposes."

Errors like this are common in large packs assembled from several templates, and buyers generally want to hear about them before tenders arrive priced on different assumptions.

Submission mechanics

Stronger: "Question 4 permits supporting diagrams. Please confirm whether text within diagrams counts towards the 500-word limit."

Small questions about mechanics feel trivial until a compliant-looking response is marked down or disqualified on a technicality.

Accreditation and eligibility

Stronger: "The selection questionnaire requires Cyber Essentials Plus. Please confirm whether a supplier holding Cyber Essentials, with Plus certification in progress, would be excluded, or whether certification is required by contract start rather than at tender submission."

This is exactly the sort of question that decides bid/no-bid. If you have the certification in progress, the answer tells you whether the bid is worth writing. If the answer is that certification is needed at submission, you have saved the effort.

Timing your questions

When you ask matters almost as much as what you ask.

Ask early

Buyers often answer in batches, and a question raised in the first week usually gets a reply while you still have time to use it. Questions raised near the clarification deadline may be answered close to the submission date, by which point your structure is fixed and your pricing is half built. Early questions also give the buyer more time to correct genuine errors, sometimes by reissuing a document.

But not before you have read the whole pack

Asking a question that is answered in an appendix you had not opened yet is the most common clarification mistake. The quick read-through for questions should cover every document, including the draft contract and pricing schedule, before anything is sent.

Watch the log as it grows

Check the published clarifications regularly, not just once at the end. Another bidder may have asked your question already, saving you the trouble, or asked something that changes your approach. Set a habit: every time the log updates, one named person reads the new entries and flags anything that affects the response.

Keep a record of what you asked

Log every question you send, the date, and the answer when it arrives. If an answer never comes, you have a record that you asked. If a later answer conflicts with an earlier one, you can point to both. It also builds a picture of how that buyer handles clarifications, which helps the next time they go to market.

Clarifications in different procurement routes

The basic idea is the same across routes, but the practicalities shift.

Open tenders

In an open procedure, the clarification window is often the only formal contact you will have with the buyer before award. That makes it worth using carefully. There is no later stage where misunderstandings get ironed out, so anything unresolved at the deadline is a guess you carry into submission.

Competitive flexible procedures

The Procurement Act 2023 introduced the competitive flexible procedure, which can include stages such as dialogue or negotiation depending on how the buyer designs it. Where there is a dialogue stage, some of what would be a written clarification in an open tender may be discussed directly. The documents for each procurement set out how that works, so read the procedure description rather than assuming.

Frameworks and mini-competitions

Framework entry tenders often run long clarification logs because the scope covers many future call-offs. Mini-competitions under a framework tend to have short windows, sometimes very short. If a mini-competition gives you days rather than weeks, the case for asking early, and asking only what matters, gets stronger. Our comparison of frameworks, DPS and open tenders covers how the effort falls on each route.

Supplier engagement before the tender

Some buyers engage the market before a tender is published, through prior information notices, market sounding or supplier days. That is often a better moment for broad questions about scope and approach, because the buyer is still shaping the requirement. Once the tender is live, the space for those conversations narrows. Our guide to prior information notices explains where those early signals appear.

Using the answers

An answer that sits in a downloaded PDF does nothing for the bid. The work is turning clarifications into changes.

Update the compliance matrix

If you track requirements in a compliance matrix or checklist, every relevant clarification should be reflected in it, with a reference to the clarification number. A requirement that has changed through a clarification is the easiest thing to miss in final review, because the original document still says the old thing.

Feed the answer into the right section

Where a clarification tells you how a question will be scored, share it with whoever is writing that section, not just the bid lead. If the buyer has confirmed they want evidence of a specific outcome, the writer needs to know before they draft, not after.

Mirror the buyer's language

Clarification answers often reveal the words the buyer uses for what they care about. If a reply talks about "continuity of service during transition", that phrase belongs in your mobilisation answer. Evaluators score against what they asked for, and answers that use their framing are easier to mark.

Revisit the bid decision

Clarifications sometimes change the picture enough to change the decision. A scope that grows, a pass/fail requirement you cannot meet, or a pricing structure that pushes risk onto suppliers can all turn a bid into a no-bid. Stopping halfway is uncomfortable, but it is cheaper than finishing a response that cannot win. Record the reason, so the next decision about that buyer starts from evidence.

Common mistakes

  • Not asking at all. Silence feels safe. It rarely is. An unasked question becomes an assumption, and assumptions are where marks go.
  • Asking too many questions. Fifty clarifications from one supplier can bury the important ones. Prioritise the questions that change the bid decision, the price or the scoring.
  • Giving away your solution. Every bidder reads the log. Ask about the requirement, not your plan.
  • Asking for an opinion on your answer. Buyers cannot pre-evaluate your response, and most will say so.
  • Ignoring other bidders' questions. The log is part of the tender. Read all of it.
  • Missing the clarification deadline. It is usually earlier than the submission deadline, and late questions may not be answered.
  • Not recording what was asked and answered. Without a log, the team cannot tell which version of a requirement applies.
  • Arguing with the answer. If a reply is unhelpful, you can ask a follow-up that is more precise. Repeating the same question in stronger terms rarely helps.

A short routine for every tender

A small team does not need an elaborate process. Something like this covers most procurements:

  1. On release: note the clarification deadline and the submission route for questions. Put both in the bid calendar.
  2. Within the first few days: one person reads the whole pack and lists every unclear, contradictory or missing point.
  3. Triage: sort the list into questions that affect bid/no-bid, questions that affect price, questions that affect scoring and questions about mechanics. Drop anything the documents already answer.
  4. Draft and review: write each question with a document reference, a quote and, where possible, a closed form. Check that none reveals your approach.
  5. Send early, in one batch if the buyer prefers, and log each question.
  6. Monitor: read every update to the clarification log and flag changes to the relevant writer.
  7. Before submission: check the final response against every clarification, not just the original documents.

Where your own records help

Clarifications are about understanding the buyer, but answering them well often depends on knowing your own position quickly. Is our certification current? Have we delivered at this scale before? Do we have a case study for this sector? If those answers live in old bids and scattered folders, the bid/no-bid stage drags, and the clarification window closes before you know what to ask.

Keeping your past answers, policies and evidence in one searchable place, as our guide to building a bid content library describes, shortens that step. Bidwell's knowledge base is built for that, and when a tender goes ahead it drafts each answer from your own documents, citing its source, for you to review against the buyer's clarifications before anything is submitted.

A good clarification question is short, specific and neutral. Ask it early, assume everyone will read it, and make sure the answer changes something in your bid. That is most of the skill, and it is one of the cheapest ways to protect the hours you put into a response.

Bidwell

Stop starting from a blank page.

Set up takes 15 minutes and the first draft comes back in minutes. Easier before the next tender than during it.

Knowledge base free forever, no card.