State RFP subcontracting requirements, decoded
Five states, six clauses, and how they score. A research teardown of state-level subcontracting and small-business participation requirements with citations to each procurement code.
State RFPs in the United States vary in structure but converge on a small set of subcontracting requirements that trip up vendors who treat them as boilerplate. This teardown walks through five states and six recurring clause types, with citations to each state’s procurement code, and notes how the clauses score in evaluation.
The post is structured-research, not advocacy. We make no claim about whether the policies are good or bad — we describe what they require and what compliance looks like.
The five states and the basic shape
We picked California, Texas, New York, Illinois, and Florida for two reasons: they collectively account for a meaningful fraction of state-level procurement spend, and their codes are publicly accessible and well-documented enough to compare cleanly.
| State | Anchor program | Code reference |
|---|---|---|
| California | Small Business / DVBE | Public Contract Code §10115 |
| Texas | HUB (Historically Underutilized Business) | Government Code Ch. 2161 |
| New York | MWBE (Minority/Women-Owned Business Enterprise) | Executive Law §313 |
| Illinois | BEP (Business Enterprise Program) | 30 ILCS 575 |
| Florida | OSD (Office of Supplier Diversity) certified | Statutes §287.09451 |
Each state has its own taxonomy of qualifying subcontractor types, its own certification process, and its own goal-setting and reporting framework. A vendor that responds to one state cannot copy-paste subcontracting language to another state without missing structural differences.
The six recurring clauses
1. Subcontracting goal as a stated percentage
Every state in this set sets a subcontracting goal as a percentage of contract value. California’s Public Contract Code §10115 sets a 25% small business participation goal for state agencies; the goal is solicitation-specific and can be higher. Texas’s HUB program sets goals that vary by category — special trade construction is 32.7%, professional services is 23.7%, other services is 26%. New York’s MWBE goal is 30% statewide.
How it scores. Most solicitations include the goal as a stated requirement, sometimes with a “good faith effort” exception. Bidders who meet or exceed the goal get the full points. Bidders below the goal must document a good-faith effort or be marked non-responsive on this criterion.
2. Certified subcontractor identification
Every state requires the subcontractors counted toward the goal to be certified — by the state’s own program or by an accepted reciprocal agency. California recognizes its own Small Business and Disabled Veteran Business Enterprise (DVBE) certifications. Texas requires HUB certification through the Comptroller’s office. New York’s certification flows through Empire State Development.
How it scores. Listing an uncertified subcontractor against the goal results in disqualification of those dollars. A bidder who hits the percentage with non-certified subs scores zero on this criterion.
3. Subcontracting plan format and content
States vary on the document the bidder must submit. California requires a Bidder Declaration (Std. 843) form. Texas requires HUB Subcontracting Plan (HSP). Florida requires identification of certified Office of Supplier Diversity subcontractors. The form requirements are not uniform.
How it scores. Submitting the wrong form, or an incomplete form, is a non-responsiveness flag. Some agencies will request a correction; others will mark the bid non-responsive without an opportunity to cure.
4. Good-faith effort documentation
When a bidder cannot meet the stated goal, every state requires documented good-faith effort. The contents vary but the recurring elements: solicitation outreach to certified vendors, response from those vendors, justifications for not selecting responsive vendors, and certification of the effort.
How it scores. Good-faith effort documentation is reviewed against the state’s specific checklist. Submitting solicitation logs that show only one outreach round, or that show no response to the bidder’s emails, typically does not satisfy the requirement. Good-faith effort is the most-litigated clause in state procurement; bidders who lose protests in this area generally lose because their documentation was thin.
5. Subcontractor performance reporting
After award, states require ongoing reporting of subcontractor utilization. Quarterly is common. Some states require a final reconciliation showing the dollars actually paid to certified subs versus the dollars in the original plan.
How it scores. This clause does not score at proposal time — it scores at performance time. Vendors who fail to meet their stated subcontracting plan in execution can face contract penalties, debarment, or non-renewal. The compliance burden lives on the vendor’s accounting team after award.
6. Sub-tier compliance
Some states extend subcontracting requirements past the prime-sub relationship to lower tiers. Texas’s HUB program counts second-tier subcontracting in some categories. California’s DVBE program does not count third-tier participation toward the goal. The variations matter for vendors who use intermediary primes or specialized tier structures.
How it scores. Misclassifying a third-tier vendor as a directly counted subcontractor is a non-responsiveness flag at audit. The mistake is invisible at proposal time and surfaces at performance review.
Where vendors get hurt
Three patterns we see consistently in bid post-mortems.
Goal slippage between solicitations. A vendor who responded to a Texas HUB solicitation last year reuses the subcontracting plan in a California small-business solicitation this year. The percentages don’t transfer, the certifications don’t transfer, the form template doesn’t transfer. The reused plan is non-responsive on every clause.
Certification expirations. Subcontractor certifications expire. A vendor who listed a certified sub on a multi-year contract may discover at year three that the sub’s certification has lapsed and the dollars no longer count toward the contract goal.
Good-faith effort that isn’t. A vendor below the goal submits a one-page narrative claiming “extensive outreach” without attached solicitation logs, dated correspondence, or vendor responses. The claim is not the documentation. The bid is marked non-responsive.
What good response looks like
For each state in the response: identify the specific anchor program, the specific form, the specific goal applicable to this solicitation, and the specific certified subs you intend to use. Verify each sub’s certification is current as of the bid submission date. Document outreach if the goal is missed. File the right form template. Cite the specific state code provision in any narrative.
This is not heroic work. It is checklist work, and most subcontracting non-responsiveness flags come from teams that did not run the checklist because they assumed boilerplate from a prior bid would carry. Boilerplate does not carry across state lines.
For vendors responding to multiple states, the structural answer is a state-level compliance matrix at the bid-prep stage — for each state, which form, which goal, which certifications, which language. We covered the general compliance-matrix discipline in the compliance-matrix-thirty-minutes post; the state-subcontracting layer is an extension of the same pattern.
What this teardown does not cover
This teardown is a research note, not a legal opinion. It also does not cover federal subcontracting (FAR 52.219-9 and the federal small-business program), municipal procurement variations within these states, or industry-specific subcontracting carve-outs (transportation, federally funded transit, etc.). Each of those would be its own teardown.
For vendors who want to go deeper on a specific state, we recommend pulling the state’s most recent Bidder’s Library or solicitation template and reading the actual subcontracting clause language, not summary documentation. The variations are in the language, not in the summaries.