An RFI (request for information) gathers broad information to learn the market. An RFQ (request for quotation) collects firm, comparable prices for a requirement that is already fully defined. An RFP (request for proposal) invites suppliers to propose a solution, scored on more than price. Many events use an RFI to narrow the field, then an RFP or RFQ to select.
Picking the wrong one is a common way sourcing slows itself down. Send a full RFP when a price on a fixed spec was all you needed, and you spend weeks comparing proposals that cannot be compared. Send an RFQ when the approach mattered, and you price the wrong thing. This guide covers when to reach for each.
What is the difference between an RFI, RFQ and RFP?
Each request has one job. The table puts the three side by side.
| Question | RFI | RFQ | RFP |
|---|---|---|---|
| Full name | Request for information | Request for quotation | Request for proposal |
| Its one job | Learn what the market offers | Get firm, comparable prices | Choose the best overall solution |
| Use it when | You are still scoping the need | The spec is locked and price is the variable | Approach, capability and risk matter as much as cost |
| What you ask for | Capability, experience and approach, in broad terms | Prices for defined line items, quantities and terms | A proposed approach, team, timeline and price |
| How you evaluate | Fit for a shortlist | Line by line price comparison | Weighted scoring across criteria |
| What comes next | An RFQ or RFP to the shortlist | An award, a purchase order or a contract | Negotiation and a contract |
RFI, RFQ and RFP compared. Many events run an RFI first, then an RFQ or RFP.
What is an RFI used for?
A request for information is how you explore a market before you invest in a full evaluation. Send it early, when you do not yet know who the credible suppliers are, what approaches exist or what is realistic. It asks broad questions: what do you offer, what is your experience in our sector, how would you approach a problem like ours.
An RFI is not about price or commitment. Its output is a shortlist and a better brief, good enough to write a sharp RFP or RFQ.
Example: Contoso, a manufacturer entering a new region, sends an RFI to a broad list of logistics providers to understand coverage and capabilities, then invites the strongest few into a formal RFP.
When should you skip the RFI?
If you already know the market and the suppliers, an RFI only adds weeks. Go straight to the RFQ or RFP. An RFI earns its place only when discovery has real value.
When should you use an RFQ?
A request for quotation fits when the requirement is fully defined and the main variable is price. You give suppliers a precise specification, quantities, delivery terms and service levels, and they return firm prices. Because everything except price is fixed, an RFQ compares line by line, which suits commodities, standard services and repeat purchases.
Example: Fabrikam needs a large order of laptops built to one defined spec, with a fixed support term. There is nothing to propose, only a price to quote, so an RFQ returns clean, comparable numbers quickly.
Raw materials are a classic RFQ. A global premium petfood manufacturer used to run its quarterly raw material sourcing on email and Excel, shortlisting suppliers, consolidating responses and comparing ingredients by hand. It moved those RFQs to RFPflow on ServiceNow, including split awards across suppliers.
Source: global premium petfood manufacturer case study.
The common trap
Sending an RFP when an RFQ would do. If the only real variable is price, asking for full proposals wastes the suppliers' time and yours, and buries a simple decision under narrative you do not need.
When do you need an RFP instead?
A request for proposal fits complex decisions where price is only part of the story. You describe the outcome, and suppliers propose how they would reach it: approach, timeline, team, technology and cost. Responses are scored across weighted criteria, so the winner is the best overall fit, not automatically the cheapest bid.
Use an RFP when you are buying a capability rather than a commodity: implementation partners, software platforms, managed services, anything where how the supplier works matters as much as what it charges.
Example: Northwind selects a new contract management platform with an RFP covering functionality, security, implementation approach, support and total cost, and scores each proposal against weights agreed before the bids arrived. For the full process, see how to run an RFP.
Which one should you use?
- Step 1 Do you know the market? If not, start with an RFI and build a shortlist
- Step 2 Is the spec locked and price the variable? If yes, send an RFQ and compare line items
- Step 3 Do approach, capability or risk decide it? If yes, send an RFP with weighted criteria
- Step 4 Award and contract Whichever you ran, the award should flow into the contract
AI contract lifecycle managementThese are not mutually exclusive. A mature event often runs an RFI to narrow the field, then an RFP or RFQ to select, then moves the award straight into a contract.
What mistakes slow a sourcing event down?
- Choosing the wrong request: an RFP where an RFQ belonged is slow and hard to compare. An RFQ where an RFP belonged prices the wrong thing.
- Fuzzy requirements: if suppliers read the ask differently, their responses cannot be compared and scoring becomes guesswork.
- Scoring agreed after responses arrive: this is how bias gets in. Agree the weights before you see a single response.
- Comparing complex pricing by hand: multi line, multi tier pricing read across PDFs is where errors and missed savings hide.
Can one system run RFIs, RFQs and RFPs?
Yes, and the system matters as much as the document. Even with the right request, an event runs slowly when it is spread across inboxes, spreadsheets and a separate contract tool. Every handoff is a chance to lose data, and the last one, award to contract, is where teams retype the whole deal.
RFPflow runs all three request types on one record. Suppliers respond by portal, email, Word or Excel, pricing rounds run against historical benchmarks, awards can be split by line item, and the award drafts the contract in Contractflow. It runs natively on ServiceNow and standalone.
- Scores each response against your weighted criteria
- Drafts a summary for every section
- Recommends suppliers, with its reasons
- Chooses the request type, criteria and weights
- Accepts or changes every score
- Makes the award and approves the contract
One sourcing event in RFPflow, from request to award.
When does the choice of request not matter much?
For small, low risk purchases from a catalog or an existing framework agreement, none of the three is worth the effort: buy against the terms you already negotiated. With a sole supplier, a formal competition adds paperwork without adding competition.
The RFx toolkit pays off when the spend is material and there is a real field to choose from. Below that line, a well kept catalog and good contract terms do more than any request document.
The bottom line
RFI to learn, RFQ to price, RFP to choose. Match the request to what you already know, agree the scoring before responses land, and keep the whole sequence on one record so the award becomes the contract instead of a retyping exercise.