If your contract carries FAR 52.219-9, the Individual Subcontracting Report is the document that proves whether your small-business subcontracting plan was a real commitment or a paragraph you wrote to win the award. Contracting officers read it that way, and so does SBA. File it clean and you move on. File it sloppy and it bounces back, with a 30-day clock to fix it.
One thing changed for everyone who files in 2026: eSRS.gov is gone. The Electronic Subcontracting Reporting System decommissioned on February 20, 2026, and all subcontracting reporting now lives inside SAM.gov. The terms ISR and SSR are unchanged, the FAR clauses are unchanged, but the portal, the login, and the access model are not. If you bookmarked eSRS.gov, that habit will cost you time this cycle.
Here's how the report works, what goes where, and the rejections that actually send filers back to the start.
When the ISR applies, and when it doesn'tThe subcontracting plan requirement attaches to negotiated contracts expected to exceed $750,000, or $1.5 million for construction, that have subcontracting possibilities (FAR 19.702). Small businesses are exempt from the plan requirement. If you're an other-than-small prime with a plan approved under FAR 52.219-9, you owe reports.
There are two reports, and people conflate them:
- The Individual Subcontracting Report (ISR) covers one contract (or one order, depending on how the plan is structured). It reports cumulative subcontracting dollars against the goals in that specific plan.
- The Summary Subcontract Report (SSR) rolls up all your subcontracting with a given agency for the fiscal year. It's filed once a year, by October 30.
This guide is about the ISR. If you only file the SSR, the mechanics below still mostly apply, but the data and timing differ.
Timing and frequencyThe ISR is semi-annual during performance. The reporting periods end March 31 and September 30, and the report is due within 30 days of each period close, so April 30 and October 30 in a normal year. A final ISR is also due within 30 days of contract completion, covering everything since the last report.
Two dated specifics worth holding onto for this cycle. eSRS retired February 20, 2026, mid-reporting-season. To absorb the migration, SBA granted a 30-day extension on the mid-year ISR, moving the FY2026 mid-year due date to June 14, 2026. Treat that as a one-time accommodation tied to the system move, not a new standing deadline. Verify the current cycle's date in SAM.gov before you rely on it.
What goes where on the reportThe ISR is a comparison: your approved plan goals against your actual cumulative subcontracting dollars. You report both a dollar figure and the resulting percentage for each socioeconomic category your plan covers:
- Total small business (the headline number behind the government's 23% small-business goal)
- Small disadvantaged business (SDB)
- Women-owned small business (WOSB)
- HUBZone small business
- Veteran-owned small business (VOSB)
- Service-disabled veteran-owned small business (SDVOSB)
- Alaska Native Corporations and Indian tribes, where applicable
A few fields are not yours to edit. Contract value, UEI, and other identifiers feed from the federal procurement record (historically FPDS), and the system pulls them in. If those look wrong, the fix is upstream in the contract action data, not in the ISR form. In the SAM.gov environment, a Contract Action Report has to exist for the contract before subcontracting reporting can proceed, and only one report is permitted per PIID. NAICS and PSC codes are no longer required on the ISR, though you can now record a subcontract NAICS that differs from the prime's.
The remarks field is no longer a formality. SAM.gov added a "Validate Remarks" review that uses an automated mechanism to assess your goals, actuals, and narrative, and flags weak or boilerplate explanations. If you're under a goal, generic language like "market conditions" will get flagged. Write specific, evidence-backed remarks tied to the actual category and the corrective action you're taking. That is also exactly what a contracting officer wants to see before acknowledging.
How the counting rules now workThe single biggest source of overstated numbers is counting subcontractors who don't qualify. Since the rules tightened, a subcontractor only counts toward a socioeconomic goal if it holds the certification that category requires.
SDVOSB and SDB self-certification is gone. As of December 22, 2024, only firms certified through SBA's Veteran Small Business Certification (VetCert) program count toward SDVOSB goals, and SDB credit follows formal certification rather than a vendor's say-so. WOSB and HUBZone have required formal certification through SBA for some time. If you've been crediting a self-described SDVOSB or WOSB toward your goals, that dollar figure may not survive review, and it can resurface as a rejection.
Confirm status before you count it. SBA's certification records and the certifying-body listings are the authoritative sources. Our certifying body directory is a fast way to verify which organization issues a given certification and to check a supplier's standing before you book the credit.
The rejections that cost you 30 daysA contracting officer either acknowledges your ISR or rejects it. A rejection starts a 30-day clock to resubmit under FAR 52.219-9(l), and you generally cannot amend a submitted ISR unless the CO rejects it first. The recurring reasons:
- Goals don't match the approved plan. The goals you type into the ISR have to match the goals in your approved subcontracting plan exactly. If you entered different percentages, the report is rejected and you resubmit with the approved figures. Pull your signed plan before you start; don't reconstruct the numbers from memory.
- A zero with no explanation. Entering 0 in a small-business category without a remark explaining why reads as either a miss or a data error. Both get rejected. If a category is genuinely zero this period, say why in remarks.
- Actuals that don't reconcile. Cumulative figures that drop from one period to the next, or percentages that don't compute from the dollars entered, get questioned. Check your math before submitting.
- Weak remarks on a shortfall. With the automated remarks review now in the loop, thin justifications on missed goals draw flags before a human even looks.
If you spot your own error after submitting, the only path is to ask the CO to reject the report so you can resubmit inside the 30-day window. Responsive contracting officers will do this, but you depend on their timing, so catch errors before you hit submit.
Tie it back to the plan, then close the gapThe ISR is a scorecard for the subcontracting plan you negotiated. If your actuals trail your goals, the report documents it in writing, and a pattern of shortfalls without a credible good-faith-effort record is what FAR 52.219-9 treats as a compliance problem, not a rounding issue. The fix is not better narrative writing. It's more qualified subcontract dollars in the categories where you're short, sourced before the period closes rather than explained after.
That's a sourcing problem, and it's solvable ahead of the deadline. Build a pipeline of certified suppliers in the NAICS codes your contract actually buys, verify their certifications so the dollars count, and route real scopes of work to them. SBA's SUBNet and the Small Business Search (the tool formerly known as DSBS) are the federal starting points for identifying certified small businesses.
Our supplier directory lets you search certified diverse and small suppliers by capability and certification, so you can find qualified subcontractors in the categories where your plan is light before the next ISR comes due rather than after it bounces. If you also report Tier-2 spend to corporate customers or run a voluntary supplier-inclusion program, the same verified pipeline feeds both obligations.
A note on the corporate side. The 2025 rollback of Executive Order 11246 changed the rules for voluntary, federally-influenced corporate programs. It did not touch the statutory small-business subcontracting obligations in FAR 19.7 and 52.219-9. If your contract carries the clause, the ISR is still due, the goals still count, and good-faith effort is still the standard. For the wider read on what's required versus what's discretionary right now, see our breakdown of the cheapest path into federal contracts.
File the ISR on time, match it to the approved plan, count only what's certified, and write remarks a contracting officer can actually act on. Do that and acknowledgment is routine. The harder work, hitting the goals, happens months earlier, in who you put on contract.
