How to Build a Supplier-Ready Procurement Request

A good RFQ makes it easier for suppliers to understand what is needed and easier for your team to compare responses. It defines the item, performance requirements, quantity, destination, timing, documents, and commercial assumptions in one place. Use this practical workflow to prepare a request that is clear without promising an award or a particular outcome.

Who this guide is for: purchasing teams, project managers, operations staff, and technical reviewers preparing a product or equipment request. Your organization’s procurement policies and approval authority always govern the process.

1. Define the outcome and scope

Start with the job the product must do. A short statement of need gives suppliers context and helps reviewers distinguish essential requirements from assumptions. For example, describe the application, operating environment, and what a successful delivery must include.

• Identify the project, department, or internal reference number.
• Describe the intended use and desired outcome in plain language.
• Separate items included in this request from services, installation, or accessories that are out of scope.
• List the decision-maker and technical contact, plus a response deadline and question process.

Practical check: Ask a colleague who did not draft the request to summarize what is being purchased and what is excluded. If they cannot, clarify the scope before sending.

2. Specify the product and technical requirements

Provide enough information to identify a compliant product. Include manufacturer, model, part number, revision, dimensions, materials, capacity, operating range, power requirements, interfaces, and applicable standards when they matter. Attach the current datasheet, drawing, or bill of materials (BOM) rather than relying on a product name alone.

Mark each requirement as mandatory or preferred. If equivalents may be considered, explain the review method: which performance characteristics must match, which documents must support the comparison, and who approves any substitution. Avoid vague instructions such as “or similar” without defining what similar means.

• Quote units and tolerances consistently; identify the standard or revision used.
• Specify new, refurbished, or other acceptable condition.
• List included accessories, configuration, software, cables, and spare parts.
• State inspection, testing, labeling, packaging, or acceptance criteria where required.

3. Set quantities, delivery, and receiving details

For each line, state the quantity and unit of measure (for example, each, case, or set). Identify whether partial shipments are allowed and whether quantities may vary. Give the delivery destination, requested date or delivery window, and any known receiving constraints.

Include site access rules, delivery appointment requirements, receiving hours, dock or lift-gate needs, inside delivery, packaging or pallet rules, and a site contact if these apply. A requested date is a planning target until the supplier confirms availability and the delivery schedule.

Useful line-item format: item number · description · manufacturer/model · required specification · quantity/unit · condition · destination · requested delivery window.

4. List required documents and commercial terms

Tell suppliers which records are needed and when. Depending on the product and transaction, that could include product data, warranty information, country-of-origin details, safety documentation, certificates, export information, or other compliance forms. Requirements vary, so confirm them with the responsible procurement, legal, tax, and compliance reviewers.

Ask for price validity, currency, lead-time assumptions, shipping or freight basis, payment terms, warranty, exclusions, and cancellation or return conditions. If the supplier should identify taxes, duties, or other charges separately, say so. Do not assume a charge is included when the quote does not state it.

5. Request comparable quotes and review them consistently

Give every supplier the same specification, quantities, destination, response date, and question channel. Request that exceptions, substitutions, unavailable line items, and assumptions be stated explicitly. This reduces the risk of comparing different products or delivery terms as if they were the same offer.

Build a side-by-side review with one row per requirement and columns for compliance, quoted unit and extended price, separately stated charges, availability, estimated delivery, documents, warranty, quote validity, and exceptions. Flag missing information and request clarification through the same documented process for all suppliers when your rules require it.

6. Run the final release checklist

Before release, confirm the package is complete, internally approved, and sent to the intended supplier list using the approved channel.

• Scope and intended outcome are clear; exclusions are stated.
• Specifications, units, revisions, BOM, and drawings agree with one another.
• Mandatory requirements are separated from preferences; equivalency rules are clear.
• Quantity, condition, destination, delivery window, and receiving instructions are present.
• Required documents and quote response fields are identified.
• Price, freight, validity, lead-time, warranty, and exception assumptions are requested.
• Questions, deadline, point of contact, and required internal approvals are stated.
• Confidential, export-controlled, or otherwise sensitive information is shared only through authorized channels.

Copy-and-use RFQ outline

Adapt this outline to your organization’s approved format. Remove fields that do not apply and add any mandatory clauses required by your procurement process.

Project / reference:
Buyer / technical contact:
Response deadline and question process:

1. Scope and intended use:
2. Item list (item no. | description | make/model/part no. | specification | qty/unit):
3. Mandatory requirements:
4. Preferred requirements / equivalency review:
5. Product condition, accessories, and configuration:
6. Required documents and certifications:
7. Delivery destination, requested window, and receiving instructions:
8. Quote response: unit price, extended price, currency, separate charges, validity:
9. Availability, lead-time basis, shipping method, and assumptions:
10. Warranty, exclusions, and commercial terms:
11. Supplier exceptions or substitutions (identify each):
12. Buyer approvals / evaluation criteria reference:

Frequently asked questions

Should I name a preferred brand or model?

Include it when it is needed to identify the requirement, and follow your organization’s rules for brand-specific specifications. If alternatives can be considered, define the technical evidence and approval needed to establish equivalency.

What if I do not know every technical detail?

Identify what is confirmed, what remains open, and who can answer technical questions. Ask for clarification before release when missing details could change product fit, safety, pricing, or delivery.

Can a quoted delivery date be treated as guaranteed?

Only treat it as committed when the supplier’s written offer and your organization’s accepted terms say so. Stock, production, transit, and receiving conditions can change; document the basis and confirm before award or order.

Does this outline replace procurement policy?

No. It is a practical drafting aid. Your procurement rules, contract terms, agency requirements, and applicable laws control.

Need help discussing a sourcing requirement? Contact SG7 to request a quote.