Sources Sought vs RFI: What’s the Difference and How to Respond

You log into SAM.gov (System for Award Management), pull up the Contract Opportunities search, and start scanning. Some notices are labeled “Sources Sought.” Others say “Special Notice” or “RFI.” You are not sure which ones to respond to, what to say, or whether responding even matters.

Here is the short answer to sources sought vs RFI. A Sources Sought notice asks who can do the work. A Request for Information (RFI) asks how the work should be done. Both are presolicitation tools. Neither is a contract. Neither requires a bid. And responding to either one costs you nothing except time.

Here is what most new contractors do not know: responding to a Sources Sought notice is how small businesses trigger set-asides under Federal Acquisition Regulation (FAR) 19.502-2(b). Skip it, and you may have just handed a full-and-open competition to Booz Allen and Leidos. That is why this article exists.

What a Sources Sought Notice Is

A Sources Sought notice is a free post on SAM.gov where a federal agency says: we are thinking about buying something. Are there businesses out there, especially small businesses, that can do this work? Tell us about yourselves. It is the government’s way of taking attendance before it writes the official solicitation.

It is not a Request for Proposal (RFP). No contract will be awarded from it. The U.S. Army Acquisition Support Center put it plainly:

“A sources-sought notice was not a solicitation that anticipated the award of a contract… Award of a sole-source contract must not be based solely on evaluation of the responses to either of these pre-solicitation notices.”

Responding does not commit you to bid on anything. The agency cannot award you a contract based on your Sources Sought response. Think of it as a low-risk introduction: you raise your hand, the agency learns you exist, and the record gets built for what comes next.

The regulatory foundation for Sources Sought sits across several FAR sections. FAR 10.001(a) and FAR 10.002(b) (Market Research) establish the purpose: agencies must conduct market research before soliciting offers above the simplified acquisition threshold. FAR 5.204 (Presolicitation Notices) provides the publication mechanism: notices must be posted to SAM.gov, the Governmentwide Point of Entry. FAR 5.205(c) (Special Notices) covers the posting category for many of these notices. And FAR 19.502-2(b) (Total Small Business Set-Asides) is where the strategic stakes live, which we cover in the Rule of Two section below.

What an RFI (Request for Information) Is

A Request for Information (RFI) is also a free post on SAM.gov, but the agency is asking something different. Instead of “who can do this?” an RFI usually asks “how should we structure this?” The agency wants your industry knowledge: feedback on a draft Performance Work Statement (PWS), pricing approach guidance, technical feasibility input, or comments on draft evaluation criteria.

The agency is using your expertise to write a better solicitation. That is the whole point.

FAR 15.201(e) is the governing authority. Here is the exact text:

“RFIs may be used when the Government does not presently intend to award a contract, but wants to obtain price, delivery, other market information, or capabilities for planning purposes. Responses to these notices are not offers and cannot be accepted by the Government to form a binding contract. There is no required format for RFIs.”

Two things stand out in that text. First: your response cannot form a binding contract. Same protection as a Sources Sought. You are not on the hook. Second: there is no required format. The agency can ask for whatever it wants, and your response should mirror what it asked for. There is no universal RFI template.

Sources Sought vs RFI: Differences Side by Side

The quickest way to understand the two notice types is to compare them directly. This table is the core of the article, and it is also the answer to the most common Google search on this topic.

On the “Can you bid later?” caveat: Technically you can bid on the eventual RFP even if you skipped the Sources Sought. But if the contracting officer used Sources Sought responses to decide whether to set the contract aside for small business, and you weren’t counted, you may now be competing against a much larger field. Responding is how you get counted.

Why Responding Matters: The Rule of Two

This is the section most GovCon articles skip. It is also the most important one for small businesses.

Sources Sought responses are how small business set-asides happen. Not how they might happen. How they are supposed to happen, by law.

FAR 19.502-2(b) states that the contracting officer shall set aside any acquisition over the simplified acquisition threshold for small business when there is a reasonable expectation that two or more responsible small business concerns will submit offers at fair market prices.

Translate that into plain English. If the contracting officer can reasonably expect two or more capable small businesses to bid at fair prices, the contract must be set aside for small business. Sources Sought responses are how the contracting officer makes that determination. It is called the Rule of Two, and your response is the vote.

Here is what that means in practice. If you are a small business with the right NAICS and you do not respond to a Sources Sought, you are not counted. If only one small business responds, the Rule of Two is not satisfied. The agency cannot set the contract aside. Your competition just became every large defense contractor that wants the work.

If you and one other small business respond, the Rule of Two is satisfied. The contract becomes a small-business-only competition. You are now competing against a much smaller field. Your response is the difference between those two outcomes.

In 2024, the Government Accountability Office (GAO) sustained a protest against the U.S. Navy in Knudsen Systems, Inc. The Navy’s market research, including its Sources Sought notice, was flawed: the Navy had told potential responders the nonmanufacturer rule did not apply and then realized it did, but did not redo the market research. GAO held the Navy’s market research was insufficient because it did not consider whether prospective small business offerors could comply with the nonmanufacturer rule once that rule applied to the procurement. The point for contractors: market research is legally consequential. Your Sources Sought response is part of the official record the agency relies on, and that GAO can review.

Three secondary benefits come from responding even when you are not the obvious front-runner. You get on the agency’s radar before the RFP drops. Some contracting officers read every response and remember the names. You may land on a short bidder list for a smaller follow-on requirement under the simplified acquisition threshold. And you get free competitive intelligence: you learn what the agency is buying, at what scale, and when, weeks before competitors who wait for the formal solicitation.

For a deeper look at set-aside types including 8(a), Service-Disabled Veteran-Owned Small Business (SDVOSB), Woman-Owned Small Business (WOSB), and HUBZone, see Government Contract Set-Asides.

How to Respond to a Sources Sought Notice

Think of this like a job interview application. You are not being hired yet. You are proving you are worth interviewing.

1. Read the notice three times. What is the agency asking for? Match by NAICS code, socioeconomic certification (8(a), SDVOSB, WOSB, HUBZone), specific past performance, or all of the above. The notice tells you.
2. Confirm your NAICS code matches. If the Sources Sought specifies NAICS 541512 and you are registered under 541611, you may not be a fit. Confirm your size status under the NAICS at sba.gov/size-standards. Respond honestly. For a full NAICS guide, see NAICS Codes for Government Contracting and SBA Size Standards.
3. Build a cover sheet. Include: company name, Unique Entity Identifier (UEI, which replaced DUNS in April 2022), Commercial and Government Entity (CAGE) code, primary NAICS code, business size status under that NAICS, all socioeconomic certifications that apply, and a point of contact with name, title, email, and phone.
4. Write a capability narrative. One to two pages. Explain how your capabilities map to each requirement in the notice. Use the same vocabulary the notice uses. If the notice says “cybersecurity assessment services,” do not write “cyber audit work.” Mirror their words. For a capability statement template, see Capability Statement Template.
5. Include three to five past performance references. For each one: customer name, contract number if it is not restricted, period of performance, dollar value, a two- to three-sentence scope description, and a point of contact. Pick past performance that most directly mirrors the work in the Sources Sought. See Past Performance in Government Contracting.
6. Skip pricing unless explicitly asked. Almost no Sources Sought asks for pricing. Submitting unsolicited prices is one of the most common rookie mistakes. If the notice does ask for ROM pricing, give a range with assumptions, not a firm bid.
7. Keep it to 3-5 pages total. Contracting officers triage hundreds of responses. Five pages is the practical ceiling.
8. Submit by the deadline through the channel listed in the notice. Email, SAM.gov upload, or agency portal. The notice will specify. Late responses are usually rejected without review. Set a calendar reminder for 24 hours before the deadline.
9. Save your response. When the formal RFP drops in 60-90 days, you can reuse a large portion of this response in your proposal.
10. Do not call the contracting officer to confirm receipt. They received it. Calling signals you do not understand the process.

How to Respond to an RFI

The mindset shift for an RFI: a Sources Sought asks “are you capable?” An RFI asks “what do you know?” You are educating the contracting officer, not pitching yourself.

1. Read the notice for what the agency actually wants. Common RFI requests: feedback on a draft PWS, pricing approach guidance (per-hour vs. firm-fixed-price vs. time-and-materials), feasibility input on a tight schedule, or technical questions about whether commercial off-the-shelf products exist.
2. Mirror the structure they gave you. If the RFI lists eight numbered questions, your response has eight numbered answers. If they provided a template, use it. Do not reorganize. Do not pivot to your capabilities.
3. Be honest about constraints. If the schedule is unrealistic, say so and explain why. If the technical requirement will not work as written, propose an alternative. A smart RFI response can reshape the eventual RFP. That is the whole point of the RFI process.
4. Provide pricing only if asked. RFIs ask for ROM pricing more often than Sources Sought notices do. If asked, give a range with stated assumptions: “Assuming a 12-month base period and remote work, our ROM range is X to Y.” If not asked, do not volunteer.
5. Avoid sales pitches. Many RFIs do not ask for a capability statement. Putting a marketing brochure in front of a contracting officer who asked a technical question signals you did not read the notice.
6. Mark proprietary content clearly. Federal RFI responses are often shared internally. Some agencies post sanitized summaries publicly. If you include trade-secret pricing or methodology, mark it with the proprietary legend specified in the notice. When in doubt, do not share what you would not want a competitor to see.
7. Submit by the deadline through the listed channel.
8. Track for the eventual RFP. Many RFIs lead to RFPs within 90-180 days. Note the expected timeline. Set a SAM.gov saved search alert so you catch it when it drops. See How to Find Government Contracts and How to Read an RFP.

The 7 Most Common Misconceptions

These errors show up constantly in forums, training materials, and even some paid GovCon courses. Know them so you do not repeat them.

1. “A Sources Sought is a formal solicitation.” It is not. No award flows from a Sources Sought notice. It is a market research tool under FAR Part 10. The agency cannot legally award a contract based on Sources Sought responses alone.

2. “If I respond, I’m committing to bid on the RFP.” False. Responding creates zero obligation. You can respond to the Sources Sought, read the eventual RFP, and decide it is not a fit. No penalty. No record of your response affects your ability to walk away.

3. “I shouldn’t respond if I’m not 100% qualified.” Wrong, especially for small businesses. Responding signals interest and helps satisfy the Rule of Two. If you can cover 80% of the scope and would team with a partner for the rest, say that. Silence does not protect you. It helps your competitors.

4. “Pricing is required on a Sources Sought.” Almost never. The agency is conducting market research, not collecting bids. Submitting unsolicited pricing is a rookie signal. If the notice asks for ROM pricing, give a range with clear assumptions. If it does not ask, leave pricing out.

5. “An RFI is always optional, so I’ll skip it.” Technically yes, it is optional. Strategically, that is a mistake. The agency is literally asking how to write the contract. If you do not answer, your competitor will. A well-written RFI response can shape the eventual RFP to your strengths. That is what informed-bidder advantage means.

6. “FAR 5.205(d) is the Sources Sought rule.” This one is wrong and it circulates widely. FAR 5.205(d) covers Architect-Engineering services. It requires synopses for A-E contracts above $25,000. It has nothing to do with Sources Sought as a market research tool. The correct authorities are FAR Part 10 (market research), FAR 5.204 (presolicitation notices), FAR 5.205(c) (special notices), and FAR 19.502-2(b) (Rule of Two). A number of GovCon training providers have repeated the FAR 5.205(d) error online. Federal readers will catch it. This article does not make that mistake.

7. “Sources Sought responses are private.” Partially true. Agencies do not publish individual responses. But your response becomes part of the agency’s market research record, which is an official document. Other industry participants can request that record through the Freedom of Information Act (FOIA). Do not include anything in your Sources Sought response that you would not want a competitor to eventually read.

Where to Find Sources Sought Notices and RFIs

These notices are publicly posted. You do not need a subscription or a broker to find them.

• SAM.gov Contract Opportunities is the primary source. Filter by Notice Type: “Sources Sought” finds most Sources Sought notices directly. “Special Notice” is where most RFIs appear. “Presolicitation” is sometimes used as a synonym for Sources Sought. Read each one. Set up saved searches with email alerts by NAICS code so you get new notices automatically.
• GSA eBuy is for vendors who hold a GSA Schedule contract. Agencies post RFIs and equivalents there for Schedule-eligible work.
• Agency-specific portals include NIH NITAAC for health and IT work, DLA DIBBS for Defense Logistics Agency supply requirements, and Army, Air Force, and Navy small business portals for service-branch work.

For a full walkthrough of SAM.gov search and alert setup, see How to Find Government Contracts.

Frequently Asked Questions

What is the difference between sources sought and RFI?

A Sources Sought notice and a Request for Information (RFI) are both market research tools used by federal agencies before they release a solicitation. Neither is a contract or a request for a bid. The key difference: a Sources Sought asks who can do the work and is used to justify small business set-asides under the Rule of Two. An RFI asks how the work should be done and is used to refine technical requirements and pricing approaches.

Do I have to respond to a sources sought notice?

No, responding is voluntary. But if you are a small business and the contract aligns with your NAICS code, you should respond. Your response is part of the market research the contracting officer uses to decide whether the contract becomes a small business set-aside under FAR 19.502-2(b). Skipping it does not bar you from bidding later, but it may mean you are bidding in a full-and-open competition instead of a small-business-only one.

Is a sources sought a contract?

No. A Sources Sought is a market research notice under FAR Part 10. It is not a solicitation. No contract award can be made from it. The U.S. Army Acquisition Support Center has confirmed in published guidance that a sources-sought notice does not anticipate the award of a contract, and that sole-source awards must not be based solely on sources-sought responses.

How long should a sources sought response be?

Three to five pages is the standard. Include a cover sheet with your UEI, CAGE code, NAICS code, size status, and certifications. Add a one- to two-page capability narrative aligned to the specific requirement in the notice. Then include three to five past performance references with customer name, contract number, dollar value, period of performance, and a point-of-contact. Stay within five pages. Contracting officers read hundreds of these.

Can I bid on the contract if I didn’t respond to the sources sought?

Yes, technically. Failing to respond to a Sources Sought does not legally bar you from bidding on the eventual RFP. But your absence may have affected whether the contract was set aside for small business. If the contracting officer did not see enough small business interest, the contract may have gone to full-and-open competition. In that case, you are bidding against large businesses, not just other small ones. Responding is how you keep the field smaller.

What happens after a sources sought notice?

One of three things. The agency releases an RFP, often as a small business set-aside if the Rule of Two was satisfied by the market research. The agency releases the RFP as full-and-open competition. Or the requirement is canceled, deferred, or restructured. The Sources Sought itself never converts directly into a contract. The typical timeline from Sources Sought to RFP is 60 to 180 days, though it varies widely by agency and requirement complexity.

What is the Rule of Two in government contracting?

The Rule of Two is the standard in FAR 19.502-2(b) that requires a contracting officer to set aside any acquisition above the simplified acquisition threshold for small business when there is a reasonable expectation that two or more responsible small business concerns will submit offers at fair market prices. Sources Sought responses are the primary evidence the contracting officer uses to make that determination. Two or more capable small business respondents trigger a mandatory set-aside. Fewer than two means full-and-open competition. Your response is the vote.