When your prime contract includes a subcontracting plan, the government expects those obligations to travel down the supply chain. Here is exactly which clauses must appear in your sub agreements and where the thresholds sit.
Why flow-down clauses exist
FAR 52.219-9, the standard subcontracting plan clause, does not just require you to set small business goals. It requires you to push specific obligations onto your subcontractors so the government's small business policy does not stop at the first tier. The SBA and contracting officers audit compliance at both the prime and subcontractor levels. Getting this wrong creates liability: failure to comply in good faith with an approved subcontracting plan is a material breach under FAR 52.219-16, which triggers liquidated damages.
The damages are not symbolic. FAR 52.219-16(b) sets the liquidated damages amount at the dollar difference between the goal and actual small business utilization, multiplied by a factor established in the contract. For a plan with a $5 million small business goal where you hit $2 million, that exposure is real.
The threshold that triggers the requirement
Flow-down obligations under a subcontracting plan apply to subcontracts and purchase orders that exceed $50,000 (for small business programs) or $700,000 (for contracts over the simplified acquisition threshold). The $700,000 threshold is where the full set of clauses applies. Below $50,000, the flow-down requirements largely do not apply.
More precisely: FAR 52.219-9(d)(9) requires primes to include the clause "Utilization of Small Business Concerns" (FAR 52.219-8) in all subcontracts and purchase orders that offer further subcontracting opportunities and that exceed $700,000 ($1.5 million for construction). FAR 52.219-8 is the core clause that obligates the subcontractor to use small businesses, including small disadvantaged, women-owned, veteran-owned, HUBZone, and service-disabled veteran-owned small businesses, to the maximum extent practicable.
The mandatory flow-down clauses
FAR 52.219-8 — Utilization of Small Business Concerns. This is the non-negotiable baseline. Every subcontract above $700,000 (or $1.5 million for construction) must include it verbatim. The clause requires the sub to give small business concerns maximum practicable opportunity to participate in further subcontracting.
FAR 52.219-9 — Small Business Subcontracting Plan. When your prime contract requires a plan, you must also require your first-tier subcontractors to adopt subcontracting plans if their subcontracts exceed $700,000 ($1.5 million for construction) and they are not themselves small businesses. The sub's plan must include the same goal categories yours does: small business, SDB, WOSB, HUBZone, VOSB, SDVOSB.
FAR 52.219-16 — Liquidated Damages — Subcontracting Plan. Flow this down to first-tier subcontractors who are required to have their own plans. It gives the government a contractual remedy against non-compliant subs, and it gives you a contractual remedy against non-compliant lower-tier subs.
FAR 52.244-6 — Subcontracts for Commercial Products and Commercial Services. This clause requires the prime to include FAR 52.219-8 in subcontracts for commercial products or services. It reinforces the flow-down requirement specifically for commercial item acquisitions under FAR Part 12.
Lower-tier subcontracting
The flow-down obligation does not stop at first tier. FAR 52.219-9(d)(9) explicitly says the prime must require each first-tier subcontractor with a subcontracting plan to include FAR 52.219-8 in their subcontracts and purchase orders above $700,000. That obligation cascades. The second-tier sub must also include FAR 52.219-8 in its subcontracts above the threshold.
In practice, this means your subcontracting plan compliance program needs to reach into your supply chain. You should require first-tier subs to certify in writing that they have flowed down FAR 52.219-8 to their own subs. Some primes build this into a standard subcontract exhibit. Others handle it through a supplier code of conduct with a specific FAR clause attachment.
The Electronic Subcontracting Reporting System (eSRS) reflects this structure. When you submit your Individual Subcontract Report (ISR) through eSRS, you are reporting first-tier data. Your subs who have plans submit their own ISRs. The Summary Subcontract Report (SSR) consolidates activity across the contract. A gap at the lower tier shows up in the aggregate and will surface during a compliance review.
DoD-specific requirements
The Department of Defense adds requirements that go beyond the baseline FAR.
DFARS 252.219-7003 — Small Business Subcontracting Plan (DoD Contracts). DoD replaces FAR 52.219-9 with this clause on DoD contracts. It includes additional reporting requirements and specific language about DoD's small business programs. The thresholds remain the same ($700,000 for most contracts, $1.5 million for construction), but the clause text has DoD-specific reporting and compliance language.
DFARS 252.219-7004 — Small Business Subcontracting Plan (Test Program). For contracts covered by the DoD Test Program for Individual Subcontracting Plans, this clause applies instead. Under the test program, a contractor can maintain a single comprehensive plan covering all DoD contracts rather than a contract-by-contract plan. The flow-down requirements remain the same.
DFARS 252.225-7001 and related Buy American clauses. DoD contracts often require additional flow-down of domestic sourcing requirements. If your prime contract includes DFARS 252.225-7001 (Buy American and Balance of Payments Program), you need to assess whether that clause flows down to your subs for items they supply directly. This is separate from small business flow-downs but frequently overlooked in subcontract drafting.
Mentor-Protégé agreements. DoD's Mentor-Protégé Program (10 U.S.C. § 4902) has its own set of obligations that flow through the prime-mentor relationship. If you are a mentor, your approved mentor-protégé agreement imposes developmental assistance obligations that are tracked separately from your subcontracting plan goals, though credit for work performed by your protégé counts toward your plan.
Reporting deadlines
ISRs are due within 30 days after each six-month period of performance and within 30 days after contract completion. SSRs are due twice a year: October 30 (covering April 1 through September 30) and April 30 (covering October 1 through March 31). Missing these deadlines is a compliance finding in its own right, separate from whether you hit your goals.
Your contracting officer has access to eSRS and can pull your reports at any time. Defense Contract Audit Agency (DCAA) audits look at whether reported figures match subcontract records. Discrepancies between what you reported and what your subcontract files show are findings.
Three action steps
Audit your current subcontract templates. Pull every template your BD and contracts team uses. Confirm FAR 52.219-8 is included in the template for awards above $700,000. If DoD work is in your portfolio, confirm your templates include DFARS 252.219-7003 in place of FAR 52.219-9. Gaps in templates are the most common source of non-compliance because they affect every subcontract you execute.
Add a flow-down certification requirement to your subcontracts. Require first-tier subs above the threshold to certify, on an annual basis or with each subcontract modification that adds scope, that they have included FAR 52.219-8 in their own subcontracts above $700,000. File those certifications in your subcontract administration records. When the government audits, that documentation is the difference between a finding and a clean review.
Synchronize your eSRS reporting calendar with your contracts team. Set internal deadlines 10 days before the government deadlines. Late reports trigger compliance notices, and consecutive late reports can affect your past performance ratings. Assign a single owner per contract for eSRS submissions and confirm that owner has system access before performance begins.
