RFP vs RFQ vs RFI: Which Procurement Document to Use (2026)

RFP, RFQ or RFI: which should you use? Use an RFI when you are still learning the market, an RFQ when you know exactly what you want and mainly need a price, and an RFP when you need suppliers to propose how they would meet a need and you will judge them on more than cost. The three are stages of buying, not interchangeable forms. An RFI gathers information, an RFQ gathers prices for a defined thing, and an RFP gathers proposed solutions to a described problem. Choosing the wrong one wastes everyone's time: an RFP for a commodity you could simply price, or an RFQ for something you have not yet defined. This article is general guidance, not legal advice. Public-sector procurement in particular is governed by law and policy that vary by jurisdiction, so follow the rules that apply to your organisation. ## What each document is ### RFI: request for information

An RFI is an early, exploratory document. You describe a need or an area of interest and ask the market to tell you what is possible: who the credible suppliers are, what approaches exist, rough cost ranges, and what is realistic. An RFI does not usually ask for firm prices or a binding offer. Its output is knowledge and a shortlist, not a decision. ### RFQ: request for quotation An RFQ is used when the requirement is already clear and specified. You tell suppliers exactly what you need (quantity, specification, delivery, service levels) and ask them to quote a price. Because the what is fixed, the decision turns largely on price and commercial terms. An RFQ suits commodities, standard goods and well-defined services. ### RFP: request for proposal An RFP is used when you know the outcome you need but not the best way to get there, and you want suppliers to propose a solution. You set out the problem, the objectives and the evaluation criteria, and suppliers respond with their approach, methodology, team, timeline and price. An RFP is scored on several weighted criteria, not price alone, and suits complex services, technology and anything where how matters as much as how much. ## RFI vs RFQ vs RFP, side by side | Feature | RFI | RFQ | RFP | |---|---|---|---| | Purpose | Learn about the market and options | Get a price for a defined requirement | Get a proposed solution to a need | | Maturity of your requirement | Still being scoped | Fully defined | Outcome known, solution open | | Main question answered | What is possible and who can help? | How much, for this exact thing? | How would you solve this, and at what value? | | Deciding factor | Not a decision; shortlist only | Mainly price and commercial terms | Approach, capability, quality and price | | Supplier response | Information, capability overview | Firm price quotation | Detailed proposal | | Typical use | Early research, new category | Commodities, standard goods and services | Complex services, technology, consulting | | Evaluation | Qualitative, informal | Price comparison | Weighted scoring of several criteria | ## How they fit together For a simple, well-understood purchase you may need only one document, usually an RFQ. For a larger or less certain purchase, the three work in sequence: 1. RFI to understand the market, test feasibility and shortlist credible suppliers. 2. RFQ or RFP to make the decision. Choose an RFQ if, after the RFI, the requirement is clearly specified and price is the main variable. Choose an RFP if you still need suppliers to propose how they would meet the need and you will weigh quality and approach alongside price. A common mistake is to jump straight to an RFP for something that is really a priced commodity, which burdens suppliers with writing proposals you do not need, or to issue an RFQ before the requirement is actually defined, which produces prices you cannot compare because every supplier has assumed something different. ## How to choose, quickly - You do not yet know what is available or who can supply it: RFI.

• You know precisely what you want and mainly need the best price: RFQ.
• You know the result you want but not the best method, and quality and approach matter: RFP.
• The purchase is large, complex or risky: consider RFI then RFP.
• The purchase is standard and repeatable: RFQ is usually enough. ## A note on jurisdiction and process Terminology and process vary by jurisdiction and sector. Public bodies are often bound by procurement law and policy, such as the General Financial Rules in India, the World Bank procurement framework for funded projects, or procurement regulations in the United Kingdom, the European Union and other jurisdictions, which prescribe when and how each document is used, how bids are evaluated, and what rights unsuccessful suppliers have. Private-sector buyers have more freedom but still benefit from a clear, documented process. Whatever the label, make sure the document states the process, the evaluation criteria, the timeline and whether and when a binding contract is formed. Last verified October 2026. ## Where a contract workspace helps An RFI, RFQ or RFP is the front of a process whose back end is a contract: the winning response becomes a statement of work, service levels, prices and terms that must then be drafted, signed and tracked. The gap where value leaks is between choosing a supplier and managing the contract that follows. Once a supplier is chosen, drafting that contract, checking its pricing and service levels against what was proposed, and tracking renewals and obligations can all happen in one AI workspace tuned to how your company contracts. Adira puts that whole cycle in one workspace for the contracts procurement produces. This guide alone is enough to pick the right procurement document; the workspace simply turns the chosen bid into a well-drafted, well-tracked contract.