The number a prime carries into every bid
A capture manager at a large prime does not think about small-business subcontracting as outreach. She thinks about it as a number that has to close. Above a specific contract value, an acceptable subcontracting plan is a condition of award. The percentages inside that plan become contract terms. Performance against them is filed into a federal reporting system twice a year. And missing them without a documented good-faith effort carries liquidated damages measured in real dollars, assessed by the contracting officer, appealable only under the Disputes clause. That is the machine. Once you can see it running, it stops being mysterious that a prime returns a small business's call at six on a Friday two weeks before proposals are due.
What follows walks that machine end to end, and ties every claim to the part of the FAR that controls it, so a capture team can check the work rather than take our word for it.
The practical conclusion is worth stating up front. A small business that is registered, size-qualified in the right NAICS code, and able to take a real scoped workshare is not a compliance chore. It is a line item that moves an evaluation factor before award and reduces a liability after it. That is a different conversation from "we would like to work with you."
When a subcontracting plan stops being optional
FAR 19.702(a) is the trigger. Each solicitation of offers to perform a contract expected to exceed $900,000 ($2 million for construction of a public facility) that has subcontracting possibilities requires the apparently successful offeror to submit an acceptable subcontracting plan. The same rule reaches contract modifications: if a modification pushes total value past the threshold, the plan requirement attaches then.
Two exclusions matter. Small businesses do not submit plans, which is why a small prime never has this problem. Neither do set-aside acquisitions, since the whole award already counts. The requirement lands squarely on unrestricted acquisitions won by other-than-small offerors, which is most of the large-dollar federal market.
The word "acceptable" is load-bearing. An offeror that fails to submit and negotiate a plan the contracting officer will accept is ineligible for award. That is not a scoring deduction. It is a gate. Capture teams treat the plan as a proposal volume with a pass/fail on it, because that is exactly what it is.
Six categories, and they are not interchangeable
FAR 19.704(a)(1) requires separate percentage goals for six categories: small business, veteran-owned small business, service-disabled veteran-owned small business, HUBZone small business, small disadvantaged business, and women-owned small business. Six lines, six numbers, each negotiated with the contracting officer before award.
Behind those lines sit the government-wide statutory targets at 15 U.S.C. 644(g): 23 percent of prime contract dollars to small business, 5 percent to small disadvantaged business, 5 percent to women-owned small business, 3 percent to HUBZone, and 3 percent to service-disabled veteran-owned small business. Agencies negotiate their own annual goals against those floors, agency goals push down into individual plans, and plan goals push down onto the capture manager. The pressure travels in one direction.
Categories overlap, and one firm can fill several lines at once. That is why a service-disabled veteran-owned firm with the right technical skill is worth more per dollar than a general small business with the same skill. Knowing which line you fill, and which line the prime is short on, is the difference between a warm reply and a scoped request.
| Goal line in the plan | Government-wide statutory target | What a prime is usually short on |
|---|---|---|
| Small business (overall) | 23% of prime contract dollars | Rarely short in dollars; often short in technically central work |
| Small disadvantaged business | 5% | Frequently short on high-skill scopes |
| Women-owned small business | 5% | Short in engineering and R&D categories |
| HUBZone small business | 3% | The hardest line to fill; geography constrains the pool |
| Service-disabled veteran-owned | 3% | Chronically tight on software and data scopes |
| Veteran-owned small business | Set in the plan, not government-wide | Depends on the agency and the work |
Percent of what: the denominator decides the size of your slot
Here is the detail most small firms get wrong. FAR 19.704(a)(1) requires goals expressed in dollars and as percentages of total planned subcontracting dollars, not of total contract value. The distinction changes the arithmetic by an order of magnitude.
Take a $40 million contract where the prime plans to subcontract $12 million and negotiates a 32 percent small-business goal. The small-business dollars owed are 32 percent of $12 million, or $3.84 million. If the prime has $2.9 million placed with two incumbent teammates, the gap is $940,000. A workshare priced at $1.1 million does not just fill the gap; it gives the prime headroom for the routine erosion that happens when scopes get descoped during negotiation.
Run that arithmetic before the first call and the conversation changes character. You are no longer asking for work. You are naming the size of the hole and offering something that fits it.
How the plan gets scored before anyone signs anything
Two separate rules put small-business participation into the evaluation itself, and they behave differently.
FAR 15.304(c)(4) applies to solicitations not set aside for small business that involve consolidation or bundling and offer a significant opportunity for subcontracting. In those, the contracting officer includes proposed small-business subcontracting participation in the plan as an evaluation factor. It is conditional, and it does not reach every unrestricted buy.
DFARS 215.304 is broader for defense work. For any DoD acquisition requiring the clause at FAR 52.219-9, except lowest-price-technically-acceptable source selections, the evaluation must address the extent to which offerors identify and commit to small-business performance of the contract, whether as a joint venture, teaming arrangement, or subcontractor. The rule also directs that this be handled separately from the subcontracting plan itself, and that the requirement be structured so offers from small businesses can actually be considered. No dollar threshold appears in the rule. It attaches to the clause, not to the contract size.
What Moves a Small-Business Participation Score
Editorial weighting from public source-selection guidance and practitioner reading. Illustrative, not a measured statistic.
What "identify and commit" looks like on paper
A named firm with identifiers. UEI and CAGE in the text, so the evaluator can look the firm up in SAM.gov during the read. An unnamed "qualified small business to be selected" reads as an intention, and it is scored like one.
A size representation in the NAICS of the work. The prime's plan lives or dies on whether the sub actually counts. SBA size standards run by code, employee-based for research and development, receipts-based for computer systems design. The representation in SAM is what the contracting officer checks.
A workshare with a boundary. "Supports data activities" is not a workshare. "Owns the ingest pipeline, the feature store, the model training and evaluation suite, and the deployment automation, at 9 percent of contract value" is a workshare. It survives a descope negotiation because someone can point at where it starts and stops.
A signed teaming agreement before submission. Signed, not drafted. Primes have been burned by teammates who vanished between submission and award, and the ones who have been burned ask for signatures.
Named people, with the prime's own resume rigor. If the prime formats key-personnel resumes a certain way, match the format. Nothing signals a low-friction teammate faster than a deliverable that arrives already in the right template.
After award, the numbers become reports
FAR 19.704(a)(10) and the clause at FAR 52.219-9 turn the plan into a reporting obligation through the Electronic Subcontracting Reporting System. Two report types, on a fixed calendar.
The Reporting Calendar Under FAR 52.219-9
Reporting hygiene is substantive, not administrative. FAR 19.705-7(b)(2)(iii) lists failure to submit an acceptable ISR or SSR through eSRS by the due dates in 52.219-9 as an indicator that the contractor failed to make a good-faith effort. A prime can hit every dollar goal and still be exposed because someone missed an October 30 filing.
For the subcontractor there is a quiet lesson here. Your dollars count toward the prime's goals only if the prime records them against the right contract. Keep the size representation current in SAM, invoice cleanly, and confirm early which contract number your work is booked under. Teammates who make a prime's small-business administrator's job easy get called again.
The past-performance consequence
Subcontracting performance follows the prime into the next competition. Under FAR subpart 42.15, past-performance evaluations for contracts carrying a subcontracting plan include a small-business subcontracting area, and the record travels through CPARS into every source selection that reads it.
The stakes rise further at FAR 19.705-7(d). When a contracting officer decides the contractor failed to make a good-faith effort, the written notice specifies a material breach, and the rule states plainly that the material breach may be included in the contractor's past-performance information. A capture manager three years and two recompetes downstream inherits that sentence.
Liquidated damages, and how the number is computed
The statutory hook is 15 U.S.C. 637(d)(4)(F), implemented at FAR 19.705-7 and the clause at FAR 52.219-16. The sequence is precise.
First, missing a goal is not by itself a failure of good faith. FAR 19.705-7(b)(1) says so directly: the contracting officer looks to the totality of the contractor's actions, and factors such as unavailability of anticipated sources or unreasonable prices can frustrate a diligent effort. Second, if the contracting officer concludes the effort was not made, the contractor gets written notice specifying the material breach and 15 working days to respond, with the notice stating that failure to respond may be taken as an admission that no valid explanation exists. Third comes a final decision assessing damages, appealable under the Disputes clause.
The amount is the part that concentrates attention. Under FAR 19.705-7(e)(2), damages equal the actual dollar amount by which the contractor failed to achieve each subcontracting goal, summed across every category missed. A shortfall of $940,000 against the small-business line is a $940,000 exposure, not a percentage of it, and any additional category missed adds its own shortfall on top.
For contractors operating under a commercial plan rather than a per-contract plan, FAR 19.705-7(f) prorates. The FAR's own worked example: total sales of $50 million, actual subcontracting of $20 million, government payments under covered contracts of $5 million, so 10 percent of sales, so $2 million of subcontracting attributable to the government. Miss the small-business goal by 1 percent and the liquidated damages are 1 percent of $2 million, which is $20,000. The contracting officer repeats the calculation for each missed category and sums.
Liquidated damages are in addition to other remedies
FAR 19.705-7(e)(3) states that liquidated damages are on top of any other remedy the government has. Combined with the material-breach language at 19.705-7(d) and the past-performance record, a prime facing a goal shortfall is weighing money, reputation, and recompete risk at the same time. That is why a credible teammate who can absorb a scoped workshare late in a capture cycle gets a fast answer.
The good-faith list is really a behavior manual
FAR 19.705-7(b)(1) enumerates what counts as a good-faith effort, and the list reads like instructions to a capture team. Break work into economically feasible units so small businesses can bid it. Conduct market research through SAM, SBA's SUBNet, matchmaking events, and preproposal conferences. Solicit small businesses early enough that they can put a real offer together. Negotiate in good faith. Participate in a formal mentor-protégé program. Exceed one category to offset another.
The mirror list at 19.705-7(b)(2) is just as instructive: no market research, no designated company official administering the program, missed eSRS filings, no records of procedures, policies designed to frustrate the plan, and failure to pay small-business subcontractors according to the terms of the contract.
Read those two lists as a small business and the timing question answers itself. Show up early, findable in SAM, with a unit of work that is already economically feasible to break out. Every one of those is an item the prime needs to document anyway.
What actually moves the answer
Three things change a prime's position, in descending order of impact.
Category fit. Filling a line the prime is short on is worth more than adding another firm to a line that is already covered. Ask which of the six lines is behind before pitching anything. A capture manager who is 40 basis points short on HUBZone and comfortable on overall small business needs a specific thing, and it is not enthusiasm.
Technical centrality. A subcontractor performing a rated technical element reads differently from one performing travel coordination and badging. Under DFARS 215.304 the evaluation asks about the extent of small-business performance of the contract, and evaluators notice whether the small-business dollars sit on the critical path or beside it.
Commitment quality. Signed teaming agreement, named personnel, stated dollars and percentage, and a scope description written in the same technical register as the prime's own volume. This is the cheapest of the three to supply and the one most often skipped.
Where an AI, ML, and data workshare fits cleanly
The easiest goal dollars for a prime to place are the ones it does not want to staff internally. Model development and evaluation, data engineering and pipeline construction, MLOps and deployment automation, cloud build-out and infrastructure-as-code, document and records extraction, and independent test and evaluation suites all break out along boundaries a contracting officer can see. Data in, model artifact and evaluation report out, with acceptance criteria stated in the statement of work. Breaking work into economically feasible units is itself a listed good-faith indicator at FAR 19.705-7(b)(1)(i), so a clean partition helps the prime twice.
That is the work our team does. We are an SBIR and STTR shop building production AI, ML, data, and cloud systems for federal, state, and commercial customers, as prime or subcontractor. Our engineers, licensed professional engineers, and domain specialists work across defense, health, energy, transportation, and public-sector data. Our founder and CTO is a former professor in technology who ranks in the top 200 of more than 200,000 on Kaggle, holds seven cloud certifications, and has twenty years building production systems for federal agencies across five consulting firms, three of them federal.
On the compliance side, the boxes a plan needs are already checked. We qualify as small under SBA's size standards in NAICS 541715 and 541512. SAM.gov registration is active. CAGE is 1AYQ0, UEI is Y2JVCZXT9HP5. We are JCP and DD-2345 certified for controlled technical data. Those are the fields a prime's small-business administrator has to fill in, and they are available today.
Have these ready before the prime asks
- Active SAM.gov registration with UEI, CAGE, and the NAICS codes of the actual work
- Current size representation, since SBA's Dynamic Small Business Search pulls from it
- A one-page scope written as a separable unit of work, not a capability brochure
- A labor mix and rate structure you can defend in a price analysis
- Named key personnel with resumes formatted to the prime's template
- A teaming agreement you can review and sign inside one week
- A point of contact who answers within one business day, every time
That last item matters more than it should. Most primes go looking for teammates after the technical solution stabilizes and before the plan is written, often in the final ten business days of a capture. A firm that returns a scoped one-pager in twenty-four hours gets into the plan. A firm that needs three weeks gets a polite note.
Bottom line
Small-business subcontracting is not a courtesy layer on top of federal contracting. It is a regulated obligation with a trigger at $900,000, six negotiated goal lines, a semiannual reporting calendar, a past-performance record, and a damages formula equal to the dollars missed. Every one of those creates a specific opening for a small firm that arrives early, fills a category the prime is short on, and takes a technically central scope it can defend.
The firms that get called back are the ones who did the arithmetic before the call. Know the denominator, know which line is short, bring a scope that partitions cleanly, and be signable inside a week.
Frequently asked questions
FAR 19.702(a) sets it at contracts expected to exceed $900,000, or $2 million for construction of a public facility, where subcontracting possibilities exist. Small business offerors are exempt, and set-aside acquisitions do not require plans. The requirement also attaches when a modification pushes total value past the threshold.
Of the subcontracted work. FAR 19.704(a)(1) requires goals in dollars and as percentages of total planned subcontracting dollars. On a $40 million contract with $12 million planned in subcontracts, a 32 percent small-business goal means $3.84 million, not 32 percent of $40 million.
Missing a goal is not automatically a violation. Under FAR 19.705-7(b)(1) the contracting officer weighs the totality of the contractor's actions. If the officer finds no good-faith effort, the contractor gets written notice of material breach and 15 working days to respond, then a final decision assessing liquidated damages equal to the actual dollars by which each goal was missed, appealable under the Disputes clause.
Through the Electronic Subcontracting Reporting System. Individual Subcontract Reports cover the periods ending March 31 and September 30 and are due 30 days after each period closes, with a final report within 30 days of contract completion. The Summary Subcontract Report is due October 30 for the twelve months ending September 30. Reports are due whether or not there was subcontracting activity.
It can. DFARS 215.304 directs DoD source selections on acquisitions requiring FAR 52.219-9, other than lowest-price-technically-acceptable, to evaluate the extent to which offerors identify and commit to small-business performance. A named firm with a signed teaming agreement, a stated dollar workshare, and named personnel scores differently from a bare percentage.
The ask
If you are building a subcontracting plan and the AI, ML, data, or cloud line is still open, send three things to [email protected]: the solicitation number, the workshare dollars or percentage you need to place, and the proposal due date. You get a yes or no within 24 hours. If it is a yes, you also get a one-page scope with a labor mix, named key personnel, and a goal-dollar figure you can drop straight into the plan, plus our UEI, CAGE, and size representation for the compliance fields. We count toward small business and we are registered today.