These four acronyms get used interchangeably, and they should not be, because they sit at different points in how the government buys and they ask for very different things from you. Two of them are market research, where the government is not buying anything yet: a Request for Information (RFI) and a Sources Sought notice. The other two are solicitations that can lead to an actual award: a Request for Quotation (RFQ) and a Request for Proposal (RFP). Knowing which one you are looking at tells you whether a contract is even on the table, how much effort to spend, and what kind of response will land.
This page sorts the four into those two families, explains what each one is, and covers the part that matters most: what each means for the technical person who got pulled in to help respond.
Two families: market research and solicitations
Before any real solicitation goes out, an agency does homework. It tries to understand what the market can deliver, who can deliver it, what realistic pricing looks like, and how to write a solicitation that attracts the right vendors. That homework is market research, and the RFI and the Sources Sought notice are its two main instruments. Neither one results in a contract.
When the agency is ready to actually buy, it issues a solicitation. The RFQ and the RFP are both solicitations, and the difference between them comes down to complexity and how the buy gets evaluated.
| Family | Contract result? | Primary focus | Your response is | |
|---|---|---|---|---|
| RFI | Market research | No | Understand the market | Informational input |
| Sources Sought | Market research | No | Find capable vendors, set-aside check | A capability statement |
| RFQ | Solicitation | Yes | Price for a known need | A quote (not a binding offer) |
| RFP | Solicitation | Yes | A full evaluated solution | A binding offer |
RFI: the market research one
A Request for Information is a market research tool, usually issued during early planning, governed by the rules on exchanges with industry in FAR 15.201. The agency is not buying anything. It is trying to learn what solutions exist, who provides them, and how to shape a future solicitation. An RFI does not commit the government to issue anything later, and responding does not create any contractual obligation either way.
Responding still matters, and not for the obvious reasons. An RFI response puts your company on the agency’s radar before the formal solicitation exists, and more importantly, it is a chance to influence the requirements before they are locked. If the agency is unsure how to approach a problem, an informed RFI response can introduce the methodology, standard, or solution approach that the eventual RFP gets written around. That is leverage, and it disappears the moment the solicitation is final.
Sources Sought: the set-aside one
A Sources Sought notice is also market research, but it has a narrower and more specific job: determining whether enough capable vendors exist, particularly small businesses and socioeconomic categories like 8(a), WOSB, SDVOSB, and HUBZone, to shape the agency’s acquisition strategy. The mechanism that matters is the set-aside. If enough qualified small businesses respond and demonstrate capability, the agency may be required to set the contract aside for small business competition rather than competing it openly. This is sometimes called the rule of two: two or more capable small businesses can change who is allowed to bid at all.
That is the practical difference from an RFI, even though the two are often used interchangeably. An RFI broadly asks whether a solution exists and what the market looks like. A Sources Sought asks, more pointedly, who can do this work and whether the small-business pool is deep enough to restrict competition. If your firm qualifies under a socioeconomic category, responding to a Sources Sought is one of the highest-leverage things you can do, because your response can directly influence whether the contract becomes one you are eligible to compete for with less competition.
RFQ: the pricing one
A Request for Quotation is used when the government already knows what it needs and is primarily after pricing. RFQs show up in simplified acquisitions, commercial and off-the-shelf buys, and orders against GSA Schedule contracts. The evaluation leans heavily on price and on whether you meet the stated specifications, so the response is lighter on technical narrative than an RFP and heavier on accurate pricing and clean compliance.
One legal distinction is worth carrying, because it surprises people. A quote submitted in response to an RFQ is not a binding offer. It is informational. The binding move happens in the other direction: the government issues a purchase order or task order, and that order is the offer, which your company then accepts to form the contract. This is the opposite of how an RFP works, and it is why the word “quote” is precise rather than casual. You are quoting a price, not making a binding commitment to perform on submission.
RFP: the full-proposal one
A Request for Proposal is the formal, negotiated solicitation most people picture when they think of government contracting. It is governed by FAR Part 15, it asks for a complete proposal including technical approach, management, past performance, and price, and it results in a contract award. The proposal is evaluated against the weighted criteria in Section M, whether that is a best-value tradeoff or lowest price technically acceptable.
Two things distinguish the RFP from everything above it. First, the effort is real: most RFP responses run weeks and hundreds of hours across multiple contributors and volumes. Second, a proposal submitted in response to an RFP is a binding offer. Once you submit, the government can accept it and form a contract on those terms, which is exactly why compliance and accuracy carry so much weight. The first thing to do when an RFP lands is to read Section L and Section M, because those two sections govern how you must respond and how you will be scored.
A note on the cousins
A few related notice types show up constantly and are worth recognizing. An Invitation for Bid (IFB) is sealed bidding under FAR Part 14: pure price competition with a public bid opening, common in construction, no negotiation. A Request for Task Order Proposal (RFTOP) competes a task order among holders of an existing IDIQ contract and looks like a smaller, faster RFP. A Broad Agency Announcement (BAA) is used for research and development, where vendors propose ideas and the agency funds the ones it likes. A pre-solicitation notice is simply a heads-up that a solicitation is coming. You do not need to master these to respond well, but knowing they exist keeps you from mistaking one for an RFP.
What this means if you are the technical contributor
The notice type tells you two things immediately: how much effort the response demands, and when in the lifecycle you are being pulled in.
- RFI or Sources Sought. Light effort, capability-statement level, no proposal to write. But do not dismiss these as not worth your time, because this is the one stage where a technical contributor can shape the playing field. An RFI response is where you can suggest the approach, the architecture, or the standard that the eventual RFP gets built on. If you are a strong technical voice, your most valuable contribution to a pursuit may happen here, months before the RFP exists.
- RFQ. Moderate effort focused on meeting specifications and supporting accurate pricing. Your technical role is usually confirming that the proposed solution genuinely meets the stated requirements and feeding the assumptions behind the price, rather than writing extended narrative.
- RFP. The heavy lift. This is where your technical approach becomes a scored, evaluated part of the proposal, and where the document defining the work, whether a SOW, PWS, or SOO, shapes how much of the solution design is yours to author.
The strategic takeaway is the one most technical people miss: by the time the RFP drops, the requirements are already set, often shaped by whoever engaged during market research. Winning work frequently begins at the RFI and Sources Sought stage, long before there is a proposal to write. If you only ever get involved when the RFP lands, you are showing up after the most influential decisions have already been made.
The Proposal Stack is a newsletter for technical GovCon professionals who get pulled into proposal work and want to contribute well without becoming full-time proposal writers. The guides here decode the vocabulary. The newsletter covers how this plays out in practice, issue by issue. Subscribe here.