Use an RFI when you need to learn from the market, an RFQ when the requirement is clear and price is the main variable, and an RFP when suppliers may solve a complex outcome in different ways. The best choice depends on what you know—not on a mandatory template.

TL;DR

  • RFI: discover capabilities, delivery models and market options before fixing the requirement.

  • RFQ: compare price and commercial terms for a well-defined good or service.

  • RFP: evaluate different solutions to a defined business outcome.

  • Do not issue a long RFx when a short discovery, demonstration, benchmark, catalogue check or direct negotiation would create a better decision.

RFI, RFQ and RFP in plain English

Request for information: RFI

An RFI asks suppliers to help you understand the market. It is useful when you know the problem but do not yet know the available solution patterns, provider types or realistic requirements.

Typical outputs: market map, capability themes, delivery options, indicative commercial models and questions to test later.

Do not use it when: you already understand the market and are ready to evaluate. An unnecessary RFI adds supplier effort and slows the decision.

Request for quotation: RFQ

An RFQ asks suppliers to price a defined requirement. It works best when products, quantities, specifications, service levels and commercial assumptions are sufficiently comparable.

Typical outputs: quoted price, lead time, payment terms, delivery conditions and exceptions.

Do not use it when: the requirement is ambiguous or suppliers need to design materially different solutions. A price comparison is meaningless if bidders are pricing different scopes.

Request for proposal: RFP

An RFP asks suppliers to propose how they would meet an outcome. It is appropriate when capability, implementation, service, risk and commercial structure all matter.

Typical outputs: solution design, implementation approach, team, evidence, service model, risks, assumptions and commercial proposal.

Do not use it when: the buying team has already chosen a supplier, cannot support a fair evaluation or only needs a standard product at a comparable price.

A decision rule that works

  1. How well do you understand the market? If poorly, start with discovery or an RFI.

  2. How well can you define the requirement? If precisely, an RFQ may work. If suppliers need to shape the solution, consider an RFP.

  3. What will determine the decision? If price and delivery dominate, use an RFQ. If solution quality, implementation and risk matter, use an RFP.

  4. What evidence do you need? A questionnaire may be weaker than a demonstration, sample, pilot, reference or structured negotiation.

  5. Is competition the right route? An existing agreement, urgent continuity issue, proprietary requirement or credible single-source case may call for another approach with appropriate governance.

Examples

Office supplies with defined specifications

Use an RFQ or catalogue competition. The products and quantities are comparable; focus on price, availability, delivery and service exceptions.

Exploring automation for procurement intake

Use market discovery or an RFI first if the team does not understand the category. Learn how providers approach routing, integration, user experience and governance before writing fixed requirements.

Selecting a complex managed service

Use an RFP if providers may combine people, process and technology differently. Evaluate mobilisation, operating model, controls, service outcomes and exit as well as price.

Renewing a strategic incumbent

Do not run a theatrical RFP if switching is not credible. Build a fact-based negotiation, validate alternatives enough to understand leverage and document the decision.

How to build a proportionate RFx

  1. State the decision. Explain what is being selected, the intended outcome and the timetable.

  2. Provide context. Share relevant volumes, users, locations, systems, constraints, current state and desired change.

  3. Ask only decision-changing questions. Remove generic questions that will not affect evaluation or due diligence.

  4. Separate requirements. Mark mandatory, scored and informational items clearly.

  5. Publish the evaluation method. Suppliers should understand criteria, evidence and process.

  6. Create structured interaction. Allow questions, demonstrations and clarification. Complex decisions are not improved by silence.

  7. Test assumptions. Use scenarios, samples, references or a pilot where they address material uncertainty.

  8. Negotiate the complete position. Scope, implementation, service, risk, data, change and exit belong alongside price.

How to evaluate responses

  • Score evidence, not writing quality or brand familiarity.

  • Use named evaluators with relevant expertise and declared conflicts.

  • Require comments that explain high and low scores.

  • Moderate inconsistent scoring before the commercial decision.

  • Keep due diligence separate from preference: verify claims, references, security, financial and operational risks.

  • Record assumptions and conditions attached to the recommendation.

Common mistakes

  • Using an old template instead of designing around the current decision.

  • Asking hundreds of questions and scoring only a small subset.

  • Mixing mandatory requirements with preferences.

  • Comparing prices before normalising scope and assumptions.

  • Letting a polished proposal substitute for product or delivery evidence.

  • Running competition without a credible willingness to change supplier.

Where technology and vendor landscapes fit

RFx tools can support document control, communications, scoring, auctions and audit trails. They do not decide whether the process is well designed. Start with the decision and evidence model, then evaluate software using the procurement software evaluation guide.

When the requirement involves procurement technology, use the procurement AI technology landscape to understand category boundaries before creating a shortlist.

Frequently asked questions

Can an RFI be followed by an RFP?

Yes. An RFI can improve market understanding and requirements before a smaller, better-targeted RFP. Avoid making suppliers repeat the same information.

Is an RFP always required for high-value spend?

Policy and regulation vary. Commercially, value alone does not determine the best method; risk, complexity, market structure and governance also matter.

Should price be scored in an RFP?

Commercial evaluation should reflect total cost and the agreed scope. Keep the method transparent and avoid combining incomparable offers into a false precision.

How many suppliers should receive an RFx?

Enough to create credible choice without overwhelming the evaluation team or inviting suppliers that cannot realistically win. The right number depends on the market and decision.

Continue exploring

See procurement process flow for the wider sourcing sequence and how to evaluate procurement software for technology-specific evidence and validation questions.