Sources Sought Is Not a Contract: A 7-Step Federal Notice Triage for Small Businesses

Before a small business spends hours writing a federal response, it should answer one question correctly: what kind of notice is this? A “Sources Sought” notice can look like a contract opportunity, carry a response deadline, name a NAICS code, and ask detailed capability questions. But it is still usually part of the government’s market research—not a solicitation, not an offer, and not an award.

A current Department of Veterans Affairs example makes the distinction concrete. On October 16, 2026, the VA Technology Acquisition Center published Sources Sought notice 36C10B27Q0052 for robotic process automation training. The official SAM.gov record lists an October 30, 2026, 3:00 p.m. EDT response deadline, NAICS 611430, PSC U012, and no set-aside. The notice itself says the request is for market-research purposes under Federal Acquisition Regulation Part 10, is not a solicitation, does not guarantee that a solicitation will be issued, and does not obligate the government.

That difference matters. A capable company may decide that a well-supported response is worth preparing. Another company may discover that its experience, registration, staffing, accessibility, delivery model, or authority is not ready. Both outcomes can be useful—if the business reads the notice as evidence instead of treating the deadline as pressure.

What changed—and who should care?

The current event is the VA’s October 16 posting of an active training-related Sources Sought notice. It is relevant to small businesses, training providers, technology educators, potential subcontractors, and new federal-market entrants that may see a matching NAICS code and assume a bid is available.

The controlling framework is broader than this one notice. FAR Part 10 directs agencies to conduct market research to understand whether capable sources exist, whether commercial services can meet the need, and whether small-business programs may be appropriate. FAR 15.201 explains that early exchanges with industry help agencies and potential offerors understand requirements and capabilities. For RFIs, it states that responses are not offers and cannot be accepted to form a binding contract.

Plain-language result: a market-research response may inform a later acquisition strategy, but it does not create a contract, guarantee a future solicitation, prove vendor eligibility, or establish that the government accepts the respondent’s claims.

The seven-step federal notice triage

1. Classify the notice before reading it as an opportunity

Record the exact notice type shown on the official page: Sources Sought, RFI, Presolicitation, Combined Synopsis/Solicitation, Solicitation, Special Notice, or Award Notice. The label changes the action. A Sources Sought notice is commonly an information-gathering stage. A solicitation is a different stage with its own instructions, representations, evaluation rules, and deadlines.

2. Lock the identifiers, version, and deadline

Save the official URL, notice ID, agency, contracting office, published date, response date with time zone, amendment history, NAICS code, PSC, set-aside field, contact route, and archive or inactive date. Recheck the official page immediately before any response because an amendment can change the questions, deadline, or submission instructions.

For the current VA example, the key identifiers are notice 36C10B27Q0052, VA Technology Acquisition Center, published October 16, 2026, and due October 30, 2026, at 3:00 p.m. EDT. Treat every field as notice-specific; do not reuse instructions from a different opportunity.

3. Separate stated requirements from planning signals

Create two columns. In the first, place what the notice expressly requests. In the second, place what a future procurement might require but the current notice does not establish. The VA notice describes live virtual instructor-led training, demonstrations, knowledge checks, limited hands-on work, accessible course content, and a Power Automate mini-lab. Those details describe the market research need; they do not prove that a contract will follow or that the final requirement will remain unchanged.

Also log inconsistencies instead of silently fixing them. The current notice refers to “Fiscal Year 2025” while listing an October 1, 2026, through June 30, 2027 delivery window. A reader should preserve the exact wording and seek clarification through the official route before relying on an interpretation.

4. Choose the responding entity from evidence

Do not start with the most impressive brand name. Start with the legal entity that can support the requested facts. Verify the exact legal name, current registration or identifier when required, authority to respond, relevant experience, staffing, licenses or certifications actually requested, and ownership of the proposed materials. If a status is unknown, mark it unknown. Historical registration evidence is not current proof.

5. Build a requirement-to-evidence matrix

For every requested capability, label the company’s position as one of five states: demonstrated, adjacent, proposed, partner-dependent, or unsupported. Attach a proof pointer for every demonstrated claim. Examples include an executed contract, delivery record, curriculum sample, accessibility test, instructor résumé, evaluation record, or client-approved reference.

This is where disciplined companies protect their credibility. A prototype is not past performance. A planned hire is not current staffing. A possible teaming arrangement is not a committed partner. A public course page is not proof that the organization can deliver the exact government scope.

6. Treat requested pricing or a ROM as planning information

Some market-research notices request price ranges or a rough order of magnitude. State the period, assumptions, number of learners, delivery format, travel, software licenses, accessibility work, hardware, support, partner costs, and exclusions. Do not turn planning information into an unsupported fixed-price promise. The notice controls whether pricing is requested and how it should be presented.

7. Submit once—and prove what actually happened

Before any response, recheck the live notice, amendment state, exact recipient or portal, subject line, file names, page limits, required questions, and authority to submit. After submission, preserve the Sent copy or official portal receipt. A clear Sent record proves transmission from the sender; it does not prove agency acceptance, evaluation, eligibility, award, or future contact. If delivery is uncertain, inspect the receiving state before retrying so a duplicate is not created.

A reusable one-page decision worksheet

What a small business can do today

1. Open the official SAM.gov notice—not a newsletter or opportunity aggregator.
2. Copy the notice type, ID, deadline, and amendment history into a pursuit sheet.
3. Write one sentence describing what the government is learning at this stage.
4. Build the five-state evidence matrix before drafting any promotional narrative.
5. Stop and request qualified procurement, legal, accounting, security, accessibility, or technical review when the notice raises those issues.

This sequence is reversible: it improves the decision even when the correct answer is “do not respond.” It also reduces wasted time, inflated capability claims, and accidental commitments.

How NABA contributes

The New American Business Association can contribute by turning official federal sources into plain-language readiness tools for immigrant, new-American, and small-business owners: notice-type education, evidence mapping, duplicate control, and questions to take to qualified professionals. NABA does not use a public explainer to claim that it—or any reader—is registered, eligible, certified, approved, competitive, selected, or capable of a specific federal requirement.

For the step before notice triage, use NABA’s no-fee SAM.gov readiness checklist. The two tools serve different decisions: registration readiness and notice-stage readiness.

Official sources

• SAM.gov — VA TAC Robotic Process Automation Training, notice 36C10B27Q0052
• Federal Acquisition Regulation Part 10 — Market Research
• FAR 15.201 — Exchanges with industry before receipt of proposals

Source status: reviewed October 19, 2026. The official notice and current FAR control. This public education resource is not legal, procurement, tax, registration, security, accessibility, or bid advice.