What Are RFP, RFQ, and RFI?
RFP, RFQ, and RFI are the three standard procurement solicitations government agencies use before awarding a contract. In other words, they are the three ways the government asks business for information before it ultimately choose who to hire. A request for information (RFI) gathers early market intelligence with no bid required, simply allowing businesses to explain what they offer. A request for qualifications or quotation (RFQ) narrows down the choices by asking whether businesses are qualified and understanding their asking price. A request for proposal (RFP) asks businesses to propose a comprehensive plan with a price and approach, with the government selecting the best proposal set forward.
# How Each One Works
An RFI comes first when an agency knows it has a need for something but hasn't decided on the best solution. It's a non-binding request for capability statements from businesses, sent to gauge what vendors or developers can actually offer. No award, no bid, and no pricing is expected in response.[1]
An RFQ is the next step, and has two meanings. In federal contracting, RFQ almost always means "request for quotation." Under this definition, vendors submit competitive pricing for a defined scope---a demand much more binding than under an RFI.[1] In municipal and state government, especially for architecture, engineering, and planning consultants, RFQ more often means "request for qualifications". Under this definition, RFQ means a step before screening even begins that narrows down a large pool of firms based on proof of experience and past performance. This is before price even enters the conversation.[^2]
Finally, an RFP is the formal, detailed solicitation, where the government asks for the most comprehensive, binding plan from a firm. RFP typically lays out the scope, evaluation criteria, and submission requirements, and asks for a complete plan, not just a number. When evaluating competing plans, governments use a technical approach, qualifications, and price together, with the process typically ending in a signed contract or a developer agreement for site-specific development deals.[1]
# Why It Matters
The three kinds of solicitation are different, and those differences can be consequential, determining who can actually compete and on what basis.
An RFQ, for example, can fence out firms that don't have the right track record before price even becomes a topic of discussion.
An RFP, while casting a wider net by allowing more firms to submit their plans in theory, can sneakily use RFQs before to pre-qualify a shortlist, only running a full RFP among the finalists. [^3]
The stakes of timing are also consequential. In Brentwood Square, Missouri, developers who waited for the city's RFP to be issued before engaging quickly fell behind firms that had already met with the city and helped shape its terms.[^4] In Santa Clara, California, the decided what it wanted for the site before releasing the RFP, with land-use goals spelled out. The partnership that won had to respond to those exact terms, not negotiate them after the fact.[^5]
For readers tracking local government meeting agendas, this is also where GatherGov is useful: it tracks the council votes, staff reports, and committee discussions where these solicitations get approved, amended, or awarded, so you see the decision before the ribbon-cutting headline.
# What Trips People Up
The biggest confusion is the name "RFQ" itself, because it means two different things depending on who issues it. A federal contracting officer's RFQ is a price request, while a city planning department's RFQ for an architect or engineer is a screening for their qualifications and past experience. The latter is often required by state rules that require governments to choose architects and engineers based on qualifications first, negotiating the fee only after, which is described under a state's qualifications-based selection (QBS) statute modeled on the federal Brooks Act.[^2] That makes reading the solicitation's actual instructions crucial in understanding what you're actually looking at.
The second largest trap is misunderstanding the levels of commitment involved in each. For example, an RFI is not a commitment, and responding to it doesn't put you in line for an award. An agency can quietly drop the whole effort after an RFI with no explanation or follow-up, so misunderstanding their intent can cause confusion and overinvestment.[1]
# Related Terms
- Qualifications-Based Selection (QBS): the selection method behind most professional-services RFQs
- Invitation for Bid (IFB): a concrete process used to examine prices when all other specs are fully defined
- Community Benefits Agreement (CBA): an agreement between a municipality and developer in which developers guarantee certain community benefits, such as investment, in exchange for approval. A CBA is often negotiated after an RFP is awarded for a development site
- Notice of Funding Opportunity (NOFO): Similar to an RFP but for grants, NOFO is a government notice that is has funding available for organizations to apply for
- Sole-Source Procurement: An exception that skips RFP/RFQ/RFI entirely by only buying something from a specific company rather than asking multiple companies to compete. Often happens if a company is the only one that can provide a specific product/service.
# Frequently Asked Questions
# Is an RFQ the same as an RFP?
Not at all. Depending on who issues it, an RFQ either asks for a price on a fixed scope or screens firms by qualifications, while an RFP asks for a full proposal that must cover approach, qualifications, and price together. Many public agencies use an RFQ first to build a shortlist, then issue an RFP only to the firms that passed.
# Do I have to respond to an RFI?
No, and responding doesn't commit the agency to anything either. An RFI is market research, not a solicitation, so there's no bid, no award, and sometimes no follow-up at all. Skipping an RFI does not make you ineligible, but it does make you less visible.
# Which comes first: RFI, RFQ, or RFP?
An RFI comes first when an agency is still exploring their options. Next is the RFQ, which narrows the field by price or qualifications. The last is typically RFP, where an agency asks for full competing proposals. Not every procurement uses all three — many go straight to an RFP.
# Can a government award a contract without issuing an RFP?
Yes, through sole-source procurement, an RFQ-only process for lower-value or design-services work, or an existing cooperative purchasing contract. These paths skip the RFP but usually require the agency to document why competitive proposals weren't necessary.
# Footnotes
-
U.S. General Services Administration, "Understand common federal contracting terms: RFIs, RFQs, and RFPs," updated May 5, 2026, https://www.gsa.gov/small-business/training-and-events/rfis-rfqs-and-rfps. [^2]: Michigan Municipal League, "Request for Proposals/Request for Qualifications," https://mml.org/programs-services/inquiry-service/request-for-proposals-request-for-qualifications/. [^3]: Miami-Dade County Strategic Procurement Department, "Request for Proposals or Qualifications," https://wwwx.miamidade.gov/global/strategic-procurement/bid-proposal-request.page. [^4]: Anita Kramer, ed., Retail Development Handbook, 4th ed. (Washington, D.C.: Urban Land Institute), Brentwood Square case study. [^5]: Dean Schwanke et al., Residential Development Handbook, 3rd ed. (Washington, D.C.: Urban Land Institute), Rivermark case study. ↩ ↩[2] ↩[3] ↩[4]