A subcontractor can bring the past performance, people, facility, clearance, equipment, or license that makes a federal bid possible. It can also make the prime ineligible before the agency evaluates a single technical page. That is the practical risk behind the ostensible subcontractor rule.

For small-business set-aside work, the question is not simply whether the prime is small under the solicitation's NAICS code. SBA can treat a prime and its subcontractor as affiliates if the subcontractor performs the contract's primary and vital requirements or the prime is unusually reliant on that subcontractor. The result can be a size determination that combines the firms' receipts or employees. If the combined business is too large, the prime is not eligible for the award.

This is not a paperwork issue to solve after submission. It is a capture, teaming, and proposal-design issue. The solicitation package, the teaming agreement, the staffing plan, and the actual division of work all need to tell the same story: the small-business prime is genuinely leading and performing the contract.

What the ostensible subcontractor rule actually tests

The rule appears in SBA's affiliation regulations at 13 CFR 121.103(h)(4). It treats an ostensible subcontractor relationship as a joint venture for size-determination purposes, creating affiliation between the firms.

SBA generally looks for either of two conditions. First, the subcontractor performs the primary and vital requirements of the procurement. Second, the prime contractor is unusually reliant on the subcontractor. Either can be enough.

Those standards are deliberately fact-specific. There is no safe percentage of subcontracted work that automatically eliminates the risk. A prime might retain 51 percent of the labor cost and still have a problem if the subcontractor supplies the only qualified program manager, the technical method, the required facility, the key equipment, and the contract experience that matters most.

Likewise, a subcontractor can perform a large share of routine work without becoming ostensible if the prime retains real management, performs central requirements, and has its own demonstrated capability. The answer depends on the solicitation and the relationship, not a generic staffing ratio.

A similarly situated entity may be exempt from affiliation under this rule in certain small-business subcontracting arrangements. That exception is technical and depends on the applicable program and size status. Do not assume that two firms calling themselves small solves the issue. Confirm the solicitation's set-aside, both companies' status, and the current SBA requirements before relying on an exception.

Primary and vital means the work that makes the contract work

Start with the statement of work, not the teaming agreement. The primary and vital requirement is usually the requirement that defines why the agency is buying the contract in the first place.

For a base operations support requirement, that could be the day-to-day facilities management function. For an IT procurement, it may be the engineering, cybersecurity, systems integration, or help-desk operation described as the core objective. For a construction project, it may be the trade work, site management, or licensed specialty performance that drives delivery and acceptance.

Agencies sometimes make this easy to identify. The performance work statement may label a task as core, mission-critical, or essential. Evaluation factors may heavily weight a particular technical capability or the experience of proposed personnel. Other times, the answer sits across several attachments: the scope, labor categories, technical evaluation criteria, transition plan, and deliverables.

That is why a SAM.gov notice alone is not enough. SAM.gov tells you a contract exists. The attachments tell you which work SBA may view as central to the contract.

When reviewing a solicitation, identify the requirements that are operationally indispensable: the work that drives performance risk, acceptance, customer mission, or evaluation. Then compare that list to the team structure. If nearly every indispensable item sits with the subcontractor, the arrangement needs a closer look.

Unusual reliance shows up in the details

SBA considers the full relationship between the proposed prime and subcontractor. The proposal is evidence, but it is not the only evidence. SBA can review agreements and practical dependencies that reveal who is actually in control.

Common pressure points include the prime's lack of relevant experience, the subcontractor's dominant role in proposal preparation, shared officers or employees, subcontractor-provided bonding, a critical license held only by the subcontractor, and a subcontractor supplying key personnel who will run the work. Financial backing, equipment access, office space, and specialized infrastructure can also matter.

None of these facts automatically creates affiliation. A newer small business may reasonably team with a more experienced company. A subcontractor may provide specialized expertise. The problem is cumulative. If the prime has little independent capability and the subcontractor supplies the experience, management, resources, and performance engine, SBA may see unusual reliance.

The proposal often makes this worse unintentionally. Consider a narrative that says the large subcontractor will provide the program manager, technical lead, transition team, quality manager, recruitment pipeline, management system, and prior contract examples, while the prime will handle contract administration. That is not a persuasive small-business prime story. It is evidence that the subcontractor is carrying the contract.

Do not confuse this rule with limitations on subcontracting

The ostensible subcontractor rule and the limitations on subcontracting are related only in the sense that both scrutinize who performs the work. They are not the same compliance test.

Limitations on subcontracting generally concern how much work or cost a small-business prime may subcontract, subject to the applicable statutory and regulatory framework. The ostensible subcontractor rule concerns affiliation and whether the subcontractor is effectively the real performer or the prime's operational foundation.

Passing one test does not guarantee you pass the other. A team can meet an applicable subcontracting percentage and still create an ostensible subcontractor problem. Conversely, an affiliation analysis does not replace the need to map performance and cost responsibilities against the solicitation's subcontracting restrictions.

Treat them as separate review tracks. One asks whether the prime is legitimately small and independent for this relationship. The other asks whether the prime will perform the required share of the work.

Build the team around a defensible prime role

The best time to address this issue is before a name appears in a staffing matrix. The small-business prime should have a clear, credible role that is more than signing the offer and invoicing the agency.

That starts with capability. The prime should be able to explain its relevant experience, its management approach, the personnel and systems it controls, and the specific contract functions it will perform. A gap is not fatal, but the prime needs enough independent substance to lead the work.

Then make the proposal reflect reality. The prime should control contract management and program direction where appropriate, contribute meaningful personnel, own defined technical or operational responsibilities, and show how it will supervise subcontract performance. If the subcontractor holds a specialized role, define that role precisely rather than letting it expand across every critical task.

Review the teaming agreement and subcontract with the same discipline. Watch for terms that give the subcontractor effective control over major decisions, staffing, financing, or performance management. Also review any arrangements that involve bonding, licenses, facilities, equipment, or proposal support. A contract document can undermine a proposal even when the narrative sounds balanced.

A practical pre-submission review

Before finalizing a small-business set-aside offer, run the team through four questions:

  • What are the solicitation's primary and vital requirements, based on the scope and evaluation factors?
  • Which company performs each of those requirements, and which company supplies the people and assets behind them?
  • What can the prime point to as its own experience, control, management capacity, and contract performance responsibility?
  • Do the proposal, staffing plan, teaming agreement, subcontract, and cost approach describe the same division of responsibility?

If the answer to the second question is mostly the subcontractor, do not try to fix the issue with vague language about oversight. Rework the team structure or reassess the bid. If the prime cannot credibly perform a central role, the opportunity may be a bad fit for that prime-subcontractor arrangement.

This review should happen after every amendment, too. An amendment can change the scope, add a mandatory certification, alter key personnel requirements, or shift evaluation weight toward a capability the subcontractor owns. What looked defensible under the original solicitation may not be defensible after the agency changes the package.

For teams managing a large opportunity pipeline, a document-level briefing can surface the scope, mandatory qualifications, evaluation criteria, and amendment changes that should trigger this review. InstantSam can help teams identify those source-document facts quickly, but it cannot decide your affiliation risk from a notice alone. That judgment requires the actual team arrangement and, when stakes justify it, qualified legal advice.

A strong subcontractor can make a bid more competitive. The small-business prime still has to look, act, and perform like the prime. Build that proof into the team before proposal pressure turns a useful partnership into an eligibility challenge.