How to write an RFQ suppliers can answer
A practical approach to specifications, response tables and clarifications that produces comparable offers.
Write for the person preparing the offer
An RFQ should let a supplier decide whether it can meet the need and prepare an answer without guessing. Start with the purchase itself: what is required, why the requirement matters and which conditions are mandatory. Avoid copying an old document without checking its assumptions. A familiar template can still contain a delivery term or item description that belongs to a different purchase.
Use short descriptions and separate requirements from background information. If you need an equivalent item, explain how equivalence will be judged. If no alternative is acceptable, say that clearly and explain the required specification. Give attachments descriptive names and identify which version governs the response. A supplier should not have to infer the current requirement from a chain of files.
Define the quantity and delivery basis
State quantities and units at line level. Distinguish a firm quantity from an estimate used for planning. Explain whether the supplier should quote a whole package or individual units. Delivery requirements need a clear starting point and an acceptance condition. A lead time counted from order confirmation is different from one counted from receipt of an advance payment.
Ask suppliers to state their assumptions in a dedicated place. If the quantity may change, ask how that affects capacity and commercial terms. Keep those assumptions out of free-form price notes where reviewers may miss them. Confirm whether partial deliveries are acceptable and how they should be proposed. This helps the buyer compare realistic delivery plans rather than labels such as available or fast.
Use a response table
A response table gives each supplier the same questions. Include item reference, offered specification, unit, price basis, currency, delivery commitment and any requested evidence. Separate optional alternatives from the main offer. Ask for exceptions explicitly. A blank response should not silently mean compliance, and a supplier should not need to rewrite the RFQ to explain a condition it cannot meet.
Test the table by filling it in as if you were a supplier. Can each question be answered from normal commercial records? Are you asking for the same information twice? If you intend to evaluate quality, state what evidence you expect. If the buyer cannot explain how a field will be used, consider removing it. A shorter response set can be more useful than a large collection of unused facts.
Explain evaluation before collecting offers
Keep mandatory gates separate from scored preferences. State the criteria and describe the scoring basis. When using weighted criteria, check that the team understands how the scores combine. Do not add an attractive new factor after seeing the offers. If an essential requirement was omitted, handle the change openly through the applicable process rather than quietly applying it during evaluation.
The evaluation method should reward evidence suppliers can provide. A vague request for quality invites promotional text that is hard to compare. A specific request for acceptance evidence or a defined service commitment is easier to review. Name the people who will assess non-price criteria and make sure they have the necessary context. Keep commercial normalization separate from judgments about technical eligibility.
Give clarifications a shared process
Set a deadline for questions and a channel for answers. Decide who can respond on behalf of the buyer. When a clarification changes the requirement, publish the change to all affected suppliers and allow suitable time to respond. Retain the prior version and the explanation. This avoids a situation where one supplier has information that the others never received.
At submission, check completeness before ranking. Ask for clarification through the declared process when an answer is ambiguous. Do not guess that a missing unit means the one you expected. Record how unresolved exceptions affect comparability. The buyer should be able to explain why the selected offer answered the request, not merely why its total appeared attractive in a table.
Checklist
- Check the specification and governing document versions.
- State quantities, units and the delivery basis.
- Provide a response table and a separate exceptions field.
- Declare mandatory gates and weighted criteria.
- Assign clarification owners and share material changes.
- Check completeness before evaluating offers.