Most RFQs don’t fail because the pricing template was wrong. They fail because someone answered a “quick question” in an email thread, a Teams chat, or a hallway conversation—and the answer never made it to the rest of the bidders. That’s how you end up comparing offers built on different assumptions, then trying to defend a decision you can’t properly explain.
A fair Q&A process isn’t bureaucratic. It’s self-preservation: it keeps the scope stable, protects you from accusations of favoritism, and prevents vendors from reverse-engineering what you want by fishing for hints.
Treat Q&A as part of the RFQ, not a side activity
The Q&A window is effectively a controlled amendment process. Every clarification can change cost, lead time, risk, or the way a supplier interprets your requirements. If you let Q&A happen informally, you’re running multiple RFQs at once—one per supplier relationship.
A common frustration: internal stakeholders want you to “just answer them” because the incumbent is asking, or because a preferred supplier is “easy to work with.” That convenience is exactly what poisons the process. Even if your intent is clean, unequal access to information is enough to create a defensibility problem.
Non-negotiable rule #1: one point of contact (and it’s not your technical lead)
Designate a single procurement point of contact (POC) for all bidder questions. Not “procurement plus the engineer if it’s technical.” Not “email anyone on the project team.” One inbox, one owner, one log.
This feels slower for technical teams, but it avoids two predictable failures: (1) different people answer the same question differently; (2) a well-meaning SME gives extra context to a supplier they know, which becomes an unintentional advantage.
RFQ cover letter: “All questions must be submitted in writing to [name/email]. Questions sent to any other contact may not be answered.”
Internal instruction: “If a supplier contacts you directly, do not answer. Forward to the POC within the same day.”
One channel: a dedicated email address or sourcing portal message function—avoid chats and calls for Q&A.
Non-negotiable rule #2: every Q and every A goes to every bidder
If one supplier asks a question, assume other suppliers either have the same question or will be disadvantaged by not seeing the answer. Share the full Q&A set with all invited bidders at the same time, in the same format.
Yes, some suppliers will complain that their questions are “proprietary.” That’s usually a sign the question is actually a solution pitch (“Can we propose an alternative spec?”) or a pricing probe (“What’s your budget range?”). You can still protect legitimate confidentiality by editing identifying details while keeping the substance.
What to share (and what not to)
Share: clarifications of requirements, definitions, measurement methods, delivery locations, acceptance criteria, required certifications, invoicing rules, and bid format corrections.
Share: answers that change how bids should be constructed (e.g., “include installation” vs “exclude installation”).
Do not share: supplier-specific solution designs, unique commercial terms they propose, or anything that reveals a bidder’s strategy.
Do not answer: “What will win?” “Who is the incumbent?” “What is the target price?”—redirect to evaluation criteria already stated in the RFQ.
Non-negotiable rule #3: set a hard Q&A deadline before the submission deadline
Without a cutoff, you’ll get a “one last question” the night before bids are due. If you answer it, you’ve effectively extended the deadline for the supplier who asked. If you don’t answer it, you’ll get an incomplete bid or a post-award argument that they were blocked from bidding properly.
Set the Q&A deadline far enough ahead that you can publish answers and still give suppliers time to adjust pricing. As a practical rule: don’t close Q&A less than a couple business days before bids are due, and longer for complex scopes. The exact gap depends on how disruptive answers could be.
What to do when a late question is genuinely important
It happens: a bidder spots a real ambiguity after the deadline. If the question exposes a requirement that could materially change bids, you have two defensible options: issue an addendum and extend the bid deadline for everyone, or confirm you won’t answer and accept the risk of incomparable bids. The first option is annoying. The second option can be expensive.
Non-negotiable rule #4: document like you’re going to be audited (because you might be)
Even in private sector sourcing, you can face internal audit, a disappointed stakeholder, or a supplier escalation. Your best defense is a clean record showing equal treatment and controlled scope.
A Q&A log with: question ID, date received, bidder (internal only), question text, answer text, responder/approver, date published, and whether it triggered an addendum.
A single “Q&A Bulletin” document (or numbered bulletins) issued to all bidders, time-stamped and stored with the RFQ package.
Version control: if an answer changes, publish a corrected bulletin and clearly mark what changed—don’t quietly replace files.
Retention: keep emails/portal exports and the final Q&A set in the sourcing file with the evaluation notes.
Why side conversations with favored vendors wreck defensibility
The damage isn’t only ethical; it’s practical. Side conversations create three problems you can’t fix later: unequal information, invisible scope creep, and evaluation distortion.
Unequal information: a supplier who gets extra context can price tighter, propose a better workaround, or avoid padding risk. Invisible scope creep: a “quick call” turns into “we can assume you meant X,” and now you’re comparing apples to oranges. Evaluation distortion: you start scoring suppliers on how well they guessed what you wanted rather than how well they met the written requirements.
The uncomfortable truth: even if you’re certain you didn’t share anything sensitive, you can’t prove what wasn’t said. That’s why strict channels matter.
A simple Q&A communication protocol you can copy into your next RFQ
Use this as a lightweight operating rule set. It’s restrictive by design; you can always loosen it later, but tightening a messy process mid-RFQ is painful.
Channel: Questions only via a single email address or portal message function. No calls for Q&A.
POC: Procurement owns intake, logging, publishing. SMEs draft answers; procurement publishes.
Deadline: Q&A closes on [date/time/time zone]. Answers published by [date/time].
Broadcast: All Q&As issued to all bidders as “Q&A Bulletin #n” (PDF or portal post).
Addenda rule: Any answer that changes requirements, pricing basis, or deliverables triggers a formal RFQ addendum (and deadline extension if needed).
No direct contact: If suppliers contact stakeholders, stakeholders forward to POC and do not respond.
Confidentiality handling: Remove supplier-identifying details when publishing questions; keep substance intact.
Audit file: Store bulletins, addenda, and the Q&A log with the RFQ and evaluation record.
If you adopt only one habit: publish Q&A bulletins on a schedule (even if there are “no new questions”). Predictability reduces chasing, reduces backchannels, and keeps you in control of the clock.