These three notices look almost identical when they land in your inbox, and they mean very different things. Treating a Sources Sought like an RFP wastes effort you cannot get back. Ignoring one because it is "not a real solicitation" can cost you the chance to shape a competition before the RFP ever drops, which is often where contracts are actually won.
The confusion is understandable. All three are government requests, all three reference a requirement, and all three can show up on the same portal looking the same. But each sits at a different point in the acquisition lifecycle, the government is doing something different at each one, and your response should look completely different. This guide breaks down what each is, what the government is actually doing, and how to respond to each so you are shaping the deal instead of just chasing it.
The short version
| Notice | What the government is doing | Binding? | Your move |
|---|---|---|---|
| Sources Sought | Market research: who can do this, and should it be a set-aside | No | Capability statement, low effort, high leverage |
| RFI | Gathering input to shape the requirement and approach | No | Substantive input that quietly favors your strengths |
| RFP | Running the competition for binding proposals | Yes | Full, compliant proposal effort |
The acquisition timeline, briefly
Most significant procurements move through a predictable arc: market research, then requirement shaping, then a draft, then the final solicitation, then award. Sources Sought and RFIs live in the early, pre-solicitation stages. The RFP is the main event. Understanding where a notice sits in that arc tells you how much it is worth and what kind of response it deserves. The earlier the stage, the cheaper your influence and the more open the outcome.
Sources Sought: the government is doing market research
A Sources Sought notice exists to answer two questions for the contracting officer: who can actually perform this work, and is there enough capable competition in a particular category to justify a set-aside. Your response is a capability statement, not a proposal.
Why responding matters more than it looks
The Sources Sought response feeds the set-aside decision directly. If several qualified small businesses respond and demonstrate capability, the contracting officer can set the work aside, which shrinks your future competition dramatically. If the qualified field looks thin, the work may go full and open against everyone. By responding well, you are not just raising your hand. You are influencing the competitive structure of the eventual RFP. For how those set-aside categories work, see federal set-aside types explained.
The capability statement done right
A strong capability statement maps your experience directly to the stated requirement, states your socioeconomic status and certifications plainly, cites relevant contracts with scope and dollar values, and is tight. It is not a brochure. Contracting officers are skimming for evidence that you can do this specific work and that you fit a set-aside category. Give them exactly that, and get on their radar before the competition has a name.
RFI: the government is shaping the requirement
A Request for Information gathers industry input on approach, feasibility, pricing models, technical options, and draft documents. The government is still deciding what it wants and how to ask for it, and it is inviting you to influence both.
This is one of the highest-leverage and most underused moments in capture. Thoughtful input can nudge the eventual scope, structure, and evaluation criteria toward what your firm does best. Comments on a draft RFP are a form of RFI, and they deserve their own playbook, which we cover in how to respond to a draft RFP. The key discipline with an RFI is to be genuinely useful to the buyer while quietly advancing your position. Pure marketing gets ignored. Substantive expertise that happens to favor your approach gets read and remembered.
RFP: the real competition
The Request for Proposal is where binding offers are submitted, evaluated, and an award is made. This is where your full proposal machinery belongs, and where the document gets serious about Section L instructions and Section M evaluation factors. If you are going to spend real bid-and-proposal money, spend it here. For how to read the two sections that govern your proposal, see Section L vs Section M and how to read Section M like a winning capture manager.
The RFP's close cousins: RFQ and IFB
Two related instruments cause their own confusion. An RFQ, Request for Quotation, is a simpler request used in commercial and simplified acquisitions; a quote is not technically a binding offer the way a proposal is. An IFB, Invitation for Bid, is a sealed-bid process used when the requirement is well defined and award goes to the lowest responsive, responsible bidder, with price doing almost all the work. The more discretion the government wants in the evaluation, the more likely you are looking at an RFP rather than an IFB.
Why the stage changes your move
The economics flip as you move down the timeline. Sources Sought and RFI responses are low effort and high leverage, because you are shaping and positioning while the outcome is still open. The RFP is high effort and lower leverage on the structure, because the rules are now fixed and you are competing inside them.
The single biggest capture mistake is showing up only at the RFP. By then the requirement, and sometimes the most likely winner, have already been shaped by the firms that engaged during market research. Incumbents understand this instinctively. Smart challengers use the early notices to close the gap. You can also use public award data to understand who has been winning this kind of work and how to position against them; see using USASpending for competitor research.
How to respond to each
- Sources Sought: a tight capability statement mapped to the stated requirement, with socioeconomic status and relevant contracts front and center. Low effort, but do it well.
- RFI: substantive, genuinely useful input that subtly favors your approach. Never just marketing. Treat draft RFP comments the same way.
- RFP: full compliance with every Section L instruction and every Section M factor. This is where the proposal hours go, after you have run a clean bid/no-bid decision.
Common mistakes
Over-investing in a Sources Sought. A twelve-page proposal in response to a market research notice signals you do not understand the stage. Skipping early notices entirely. The cheapest influence you will ever have is in the pre-solicitation phase. Generic capability statements. A response that is not mapped to the specific requirement gets filed and forgotten. Tipping your hand in RFI comments. Be helpful and persuasive, but remember your competitors may see the spirit of your input reflected in the final.
A worked example: one requirement, three notices
Picture a single agency need, say a multi-year program for IT support services. Early on, the agency posts a Sources Sought to gauge whether enough capable small businesses exist. Your move is a tight capability statement that proves you can do the work and states your set-aside category, because your response helps decide whether the eventual RFP is a small business set-aside or full and open. Months later, the agency releases a draft RFP or RFI with a draft statement of work and evaluation approach. Now your move shifts to shaping: you comment on ambiguous requirements, suggest evaluation criteria that reward your strengths, and quietly begin building your proposal. Finally the RFP drops. The shaping window is closed, the rules are fixed, and your move is full compliance and a sharp, well-evidenced proposal. Same requirement, three completely different responses, each matched to what the government is doing at that moment.
Where these notices live, and how to track them
Sources Sought, RFIs, draft RFPs, and final solicitations are all posted to the same federal opportunity systems, which is part of why they blur together. The discipline that separates strong capture teams is reading the notice type first, before anything else, because it determines the entire response. A team that triages by type catches the cheap shaping opportunities early and reserves its expensive proposal effort for the notices that are actually competitions. Reading dozens of these a week by hand is where the time goes, and where a fast, accurate read of each notice pays for itself.
Bottom line
Read every Sources Sought and RFI as a shaping opportunity and respond cheaply but well. Reserve your heavy proposal effort for the RFP, where it counts. The teams that win the RFP are very often the ones that were already engaged when it was still a notice.
For the next steps once a real RFP arrives, see how to evaluate an RFP in under 10 minutes, pull the staffing requirements with key personnel extraction, and build the requirement into a compliance matrix before you write a word.