Federal subcontracting plans are not a checkbox you file once and forget. Under FAR 52.219-9, any prime contractor with a contract above $750,000 (or $1.5 million for construction) that has subcontracting opportunities must negotiate a plan, then report performance against it twice a year and summarize it once a year. The reporting vehicle is eSRS — the Electronic Subcontracting Reporting System at esrs.gov.
Most compliance failures happen not from bad intent but from confusion about which form goes where and when. This guide walks through both reports field by field.
The two reports and when they are due
The Individual Subcontract Report (ISR) covers a single contract. You file it semiannually: once for the period ending March 31 (due by April 30) and once for the period ending September 30 (due by October 30). For contracts that close mid-year, you also file a final ISR within 30 days of contract completion.
The Summary Subcontract Report (SSR) is an agency-level rollup. It consolidates all your active subcontracting plans under one contracting agency for the full federal fiscal year (October 1 through September 30). The SSR is due October 30 each year.
One source of confusion: contractors with commercial plans file only one SSR per agency rather than per-contract ISRs. If you are on a commercial plan, skip the ISR section below.
ISR: field-by-field
Log into esrs.gov, select your contract, and open a new ISR for the applicable reporting period.
Period covered. Enter the start and end dates of the reporting period. For the April filing, this is October 1 through March 31. For the October filing, it runs April 1 through September 30.
Dollars subcontracted to each socioeconomic category. eSRS has separate line items for: Small Business (SB), Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), HUBZone Small Business, Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), and Historically Black Colleges and Universities / Minority Institutions (HBCU/MI). Enter cumulative dollars, not period-over-period deltas.
Total subcontracted dollars. Enter the total you have paid to all subcontractors during the reporting period, then the cumulative contract-to-date figure. The system calculates your percentage goals against your plan automatically.
Compliance certification. A senior company official must electronically certify the report. This is not a formality. A false certification can expose the company to False Claims Act liability.
After you submit, the contracting officer receives a system notification and reviews the report. If your actuals fall materially short of plan goals, expect a written explanation request.
Handling subcontractors with multiple certifications
A single subcontractor often holds more than one certification. An SDVOSB with HUBZone status counts in both columns. eSRS does not prevent double-counting across socioeconomic categories, but each dollar you pay that firm can only be counted once in the SB total and once in each applicable category column.
Practically: if you pay an SDVOSB/HUBZone firm $100,000, you enter $100,000 in the SDVOSB column and $100,000 in the HUBZone column. The total subcontracted dollars line stays at $100,000. This is consistent with how SBA defines credit under 13 CFR Part 125.
Verify all certifications through SAM.gov before you enter data. If a subcontractor's certification lapsed before the work was performed, that spend does not count toward the applicable goal even if the firm was certified when you originally selected them.
SSR: what it adds
The SSR consolidates performance across all your active subcontracting plans under a single agency. If you have five contracts at the Department of Defense, one SSR covers all five.
Agency identification. Select the agency from the eSRS dropdown. The system links your registered contracts automatically once you confirm which plans roll up.
Prime contract list. eSRS pre-populates the ISRs you filed during the year. Review the list for completeness before submitting.
Cumulative dollars by category. The SSR asks for fiscal-year-to-date actuals, not just one semiannual slice. Reconcile these numbers against your internal subcontract payment ledger before submission. Discrepancies between your ISR figures and the SSR rollup are a common cause of corrective action requests.
Goals versus actuals. Enter your plan goals as negotiated, then your actual performance. If actuals fall below goals, document the reason in the narrative field. Contracting officers look at the narrative first when performance is under goal.
Consequences of late or inaccurate filing
The SBA reviews eSRS data when evaluating contractor responsibility for future set-aside work. A pattern of late ISRs or SSRs can surface during a responsibility determination.
OFCCP does not directly regulate subcontracting plan reporting, but DOD and civilian agencies have authority under FAR 52.219-9(d) to assess liquidated damages for failure to comply with a subcontracting plan. The standard rate is $500 per day for each day the report is late.
Repeat failures or material misrepresentations go to the agency's suspension and debarment official. Debarment is rare but not theoretical; the Government Accountability Office has cited eSRS non-compliance as a contributing factor in past suspension proceedings.
Contracting officers can also withhold final payment on a contract until all required ISRs are filed and accepted. If your billing team is chasing a payment delay, check eSRS before assuming the problem is in the payment system.
Three actions to take before the next deadline
1. Build the eSRS deadlines into your contract calendar now. April 30 and October 30 are fixed. The October filing covers both the second semiannual ISR and the SSR, which makes that date genuinely high-pressure. Set internal due dates at least two weeks earlier so you have time to reconcile your subcontract ledger.
2. Verify every subcontractor's SAM.gov status before you enter data. Pull a current SAM extract for each firm on your subcontract register. A lapsed registration or expired certification discovered post-submission requires an amended report and a written explanation to the contracting officer.
3. Assign one person as the eSRS administrator with system-level access. eSRS logins are role-based. Staff turnover is the most common reason reports are filed late or filed by someone who does not understand the data. The eSRS administrator role should live in your subcontract management group, not in the BD team.
The reporting itself is straightforward once you know the structure. The real work is keeping your subcontract payment data clean and your certification verifications current so that filing day is a confirmation exercise, not an audit.
