How Should a Prime Draft an SDVOSB Sub's Content into a Sources Sought or RFI Response?

A Sources Sought response is the prime's first signal to a contracting officer about how the team would deliver the work. Service-Disabled Veteran-Owned Small Business (SDVOSB) subcontractor content has to be specific, attributable, scoped to the sub's actual capability, and consistent with Commercially Useful Function (CUF) expectations, all without inflating the prime's page count or overstating what the sub will perform. This guide covers the joint-response discipline.

Read the complete guide: How Do Primes Evaluate, Structure, and Contract with an SDVOSB IT Subcontractor?

What Is a Sources Sought Notice and Why Does the Sub's Content Matter?

A Sources Sought notice is a market-research instrument under FAR 5.205 and FAR 10.002. The contracting officer uses Sources Sought responses to assess market capacity, validate North American Industry Classification System (NAICS) selection, and decide whether the requirement can be set aside for small business, SDVOSB, or another socioeconomic category. Sources Sought is not a solicitation; no proposals are due, no awards are made, and the response does not bind either party to the eventual procurement.

What Sources Sought does affect, materially, is the eventual set-aside structure of the contract. A contracting officer who receives substantive responses from two or more SDVOSB firms (or one SDVOSB prime plus a teamed prime-and-SDVOSB-sub response) has the structural basis to set the requirement aside for SDVOSB under the Rule of Two at 38 USC 8127 (at the Department of Veterans Affairs) or under FAR 19.1405 (at other agencies). A weak SDVOSB capability response signals limited market capacity, and the contracting officer may proceed unrestricted or with a different socioeconomic set-aside.

This is why the sub's content matters disproportionately to its eventual workshare. The sub's capability paragraph in a Sources Sought response is shaping the structural set-aside decision before any solicitation is published. Generic SDVOSB sub content that does not clearly establish the sub's specific capability undermines the prime's set-aside positioning. Specific, capability-tied sub content reinforces it.

How Is an RFI Different from a Sources Sought?

A Request for Information (RFI) is governed by FAR 15.201 and is broader in scope than a Sources Sought. RFIs may request technical concepts, proposed acquisition strategies, pricing ranges, draft Performance Work Statement (PWS) feedback, and recommendations on contract structure. The prime-sub response discipline is the same, but the content surface area is larger.

RFIs sometimes ask for pricing in a way that Sources Sought rarely does. Prime-sub coordination on pricing input requires care: any pricing the prime cites in an RFI response that depends on the sub's labor rates should be supported by a labor-rate exhibit attached to the executed Teaming Agreement, not invented for the RFI. Pricing that appears in an RFI without supporting documentation can be later cited as overoptimistic during proposal negotiation.

The same Procurement Integrity Act considerations under 41 USC 2102 apply to both Sources Sought and RFI responses: no use of source-selection information, no use of contractor bid or proposal information, no use of any non-public information not properly disclosed under an executed NDA.

What Sub Content Should the Prime Include?

The sub's contribution to a Sources Sought or RFI response is concrete and bounded. Five components, no more.

• Specific past-performance citations. Agency name, contract number (if unclassified), dollar value, period of performance, and the sub's specific role on the contract. The Contractor Performance Assessment Reporting System at cpars.gov is the verifiable backstop. Each citation should be one to three sentences.
• Capability paragraph linked to one or two PWS or Statement of Work elements. Not generic. The capability paragraph should reference the specific PWS line item, sub-task, or labor category the sub will address. "Subcontractor will perform endpoint security and patch management for the 27 sites described in PWS Section 3.4" is specific. "Subcontractor brings managed IT services capability" is generic and adds nothing.
• SDVOSB certification status, UEI, and CAGE. One sentence with the certification status from certifications.sba.gov, the Unique Entity Identifier and Commercial and Government Entity code from SAM.gov, and the date of last verification.
• Cybersecurity posture. Cybersecurity Maturity Model Certification (CMMC) status, current Supplier Performance Risk System (SPRS) score, and any agency-specific posture (Health Insurance Portability and Accountability Act for VA work, NIST SP 800-171 for DoD-flowed work). One short paragraph.
• Key personnel naming with caveats. Name personnel only when their availability for the eventual contract is confirmed. Otherwise reference labor categories with capability descriptions. Naming personnel who later cannot perform is the failure pattern that ends up in CPARS.

For more on identifying which capability gap to lead with, see How an SDVOSB IT Firm Should Approach VA IT IDIQ Prime Awardees.

What Sub Content Should the Prime Avoid Including?

The avoidance list is as important as the inclusion list. Each item below is a common Sources Sought failure mode that creates downstream exposure.

• Generic "experienced team" language. "Subcontractor has an experienced team of certified professionals" is filler. The contracting officer reads it as filler. The page-count budget is better spent on specific past performance.
• Past performance not directly relevant to the requirement. A sub's $40,000 task order at a state agency is not relevant past performance for a $20 million federal IT requirement. Including irrelevant past performance signals that the sub does not have relevant past performance.
• Pricing speculation. Sources Sought rarely asks for pricing; RFIs sometimes do. When pricing is requested, the sub's contribution should be supported by an executed Teaming Agreement labor-rate exhibit. Sub-contributed pricing without that documentation is a future negotiation problem.
• Capability claims that exceed CUF-compliant scope. The sub's capability paragraph should describe a real, distinct scope the sub will perform. "Subcontractor will perform 100% of the technical execution while Prime provides overall management" is not CUF-compliant on its face. See the CUF requirements at 13 CFR 125.6.
• Key personnel names without confirmed availability. Any named individual in a Sources Sought response should be available to perform on the eventual contract. Naming an unavailable person creates a downstream substitution issue and a CPARS risk.
• References to specific competitors. "Ghosting" by name (drafting capability framing that disqualifies a competitor) is risky in all constructs and may violate FAR 3.104 (Procurement Integrity Act implementation). Frame capability positively against the requirement, not negatively against named competitors.

How Does Attribution Work in a Joint Response?

Two attribution models work in joint Sources Sought and RFI responses; choose one explicitly per response, do not mix.

Section-level attribution. The response has a "Subcontractor's Section" or "TDS-IS Section" that contains the sub's content with clear attribution. Past performance, capability paragraph, and key personnel content are grouped together under the sub's name. This model is cleaner for contracting officers and easier to maintain across multiple sub contributions, but uses more page-count budget.

Paragraph-level attribution. The response weaves the sub's content into the prime's narrative with inline attribution: "Subcontractor TDS-IS will perform endpoint security and patch management..." or "TDS-IS, our SDVOSB partner, holds NIST SP 800-171 SPRS score of [score]..." This model is denser and reads more like a single team's response, but requires more careful drafting to maintain attribution clarity.

The capability statement appendix model is a hybrid: the response narrative uses paragraph-level attribution for inline content, and the response includes an appendix with each party's full capability statement as a separate document. This model is common for primes with multiple subs in a teaming arrangement, where each appendix capability statement is the team-member's own document.

Whichever model is used, the prime is the contracting party for the response. The prime's signature block, primary point of contact, and Procurement Integrity Act representation cover the entire response. The sub's content is attributed within the response but does not change who is responding.

How Do You Stay CUF-Compliant in the Response?

The Sources Sought or RFI response should describe a workshare structure that is consistent with the eventual subcontract structure. If the response describes the sub as performing 30% of the work, the eventual subcontract should reflect that allocation. Significant divergence between Sources Sought-stated workshare and eventual contract workshare is a Commercially Useful Function red flag.

Three drafting practices keep the response CUF-compliant.

Describe a real, distinct scope the SDVOSB will perform. The sub's capability paragraph should identify a discrete scope of work, not a general support role. "Subcontractor will operate the endpoint security stack" is distinct. "Subcontractor will provide IT support" is not.

Avoid framing that suggests pass-through. "The Prime will provide overall management and the Subcontractor will perform 100% of execution" sounds like pass-through. Even if true on paper, it signals to a contracting officer that the relationship may not be substantive. Frame the prime's role substantively (specific oversight tasks, agency relationship management, integration architecture) so the response describes a partnership, not a pass-through.

Align workshare across the document set. The Sources Sought or RFI response, the eventual Teaming Agreement, and the eventual subcontract should align on the sub's workshare percentage and scope. Misalignment is reviewable evidence in any future SBA size protest or False Claims Act inquiry under 31 USC 3729. The 50% rule under FAR 52.219-14 is the quantitative complement to CUF; both must be satisfied on services contracts set aside for SDVOSB primes.

Pre-Send Checklist

Before sending any joint Sources Sought or RFI response, walk the checklist below. Each item is a frequent failure mode that this checklist catches.

• All certifications cited in the response are dated within the past 12 months
• SDVOSB certification screenshot from SAM.gov and DSBS dated within the past 90 days is on file
• Past performance citations are confirmable in CPARS or by direct reference from a prior prime
• Compliance posture artifacts (SSP summary, SPRS score, CMMC status, HIPAA artifacts where relevant) are attached or available on request
• Capability paragraphs use CUF-compliant scope language (real, distinct work)
• Workshare percentages are documented internally and consistent with the executed Teaming Agreement
• Capability statement attached to the response is consistent with the response narrative (no contradictions on past performance, capability scope, or certifications)
• Procurement Integrity Act representation is included for both prime and sub
• Key personnel named are confirmed available; otherwise labor categories are used
• Submission method (email, contracting officer portal, SAM.gov submission) is the one specified in the notice; deadline is verified against the notice's stated due date and time zone

Frequently Asked Questions

Should the SDVOSB sub respond to a Sources Sought independently if the prime is also responding? Yes, in most cases. Sources Sought responses are market research, not source selection, and a contracting officer benefits from seeing both the prime's response and the sub's independent response. Independent SDVOSB responses signal to the contracting officer that the requirement has SDVOSB capacity in the market, which affects the set-aside structure decision. The sub's independent response should reference the teaming relationship if one exists, but does not need to mirror the prime's content. Coordinated submissions, where prime and sub agree on capability framing in advance, are common and acceptable.

Does responding to a Sources Sought create any procurement-integrity restriction? No, generally. Responding to a Sources Sought notice is standard market-research participation and does not by itself create a procurement-integrity restriction under the Procurement Integrity Act (41 USC 2102). The restriction arises if the responder receives non-public source-selection information or contractor bid-or-proposal information during or after the response. Both prime and sub should document that all information used in the response was either publicly available, derived from the responder's own work, or properly disclosed under an executed Mutual NDA.