The short version
| What we counted | Number |
|---|---|
| Primes screened | 160 |
| Subcontractor relationships (a prime and one of its reported subs) | 5,987 |
| Distinct subcontractors, by UEI | 5,000 |
| Relationships with a registration we could read in SAM.gov's public data | 5,532 |
| Of those, with an active exclusion linked to the sub | 0 |
| Relationships with a subaward reported in the last 12 months ("recent") | 2,040 |
| Recent relationships where the sub's registration had lapsed | 50 |
| Recent relationships where it would lapse within 30 days | 63 |
| Primes with at least one of those 113 | 53 of 160 (33%) |
A relationship is one prime and one sub. A sub that works for three of these primes is three relationships and one distinct subcontractor; 584 subs appeared under more than one prime. Read how we counted and what this doesn't show before quoting any of it.
No active exclusions
Of the 5,987 relationships, 5,532 were with a company whose registration is in SAM.gov's public data, so we could look for exclusions linked to it. We found none that were active on the day of the screen. The other 455 (7.6%) weren't in the public data, and we didn't check them: see below.
That is the result you would hope for. These are primes that file subaward reports, about subs they have already chosen, and FAR 52.209-6 already tells them not to subcontract above the threshold in FAR 9.405-2(b) (currently $45,000) with a party that is debarred, suspended or proposed for debarment, unless there is a compelling reason. Exclusions of firms are also rare: we counted 341 taking effect against firms across the whole government from January to September 2026.
Three limits on that zero:
- It is one day's answer. An exclusion that ended before November 2026 wouldn't show, and one added afterwards wouldn't either.
- We matched by UEI only. We ran no name search, so an excluded party listed under a name with no UEI or CAGE that links it to the sub's registration would not have been found.
- We didn't screen sanctions or export-control lists. Those are separate from SAM.gov exclusions: see the Consolidated Screening List.
One prime in three had a lapsed or lapsing registration among recent subs
We looked at registration dates only for subs with a subaward reported in the 12 months before the screen: 2,040 relationships, about a third of the total. Among those:
- 50 (2.5%) had lapsed. Forty-five registrations were past their expiry date and five were no longer active in SAM.gov's data (status "deleted"). They were spread over 31 primes, 19% of the 160.
- 63 (3.1%) would lapse within 30 days unless renewed, spread over 38 primes (24%).
- 53 primes (33%) had at least one of either. Counting only the 135 primes with any recent sub, that is 39%.
The lapses were mostly recent. Half of the 50 had an expiry date within about seven weeks before the screen, 20 within 30 days, and 6 more than 180 days back. Nor were they only the smallest subs: the median lapsed relationship had about $247,000 of subawards reported by that prime on contracts active in fiscal years 2025 and 2026.
One caution on timing. Our registration dates come from SAM.gov's public extract dated November 1, 2026, and the screens ran on November 8 and 9. Of the 50 lapsed registrations, 41 had an expiry date on or before November 1. The other 9 had an expiry date in the week between, and the 63 lapsing dates are later still: any of those 72 may have been renewed after November 1 without our data showing it. Confirm a date at SAM.gov before acting on it.
Longer lists, more lapses
| Reported subs | Primes | With a lapsed or lapsing recent sub | Share |
|---|---|---|---|
| 5 to 19 | 64 | 7 | 11% |
| 20 to 49 | 53 | 19 | 36% |
| 50 to 99 | 35 | 21 | 60% |
| 100 or more | 8 | 6 | 75% |
The rate per sub hardly moves: in the three larger bands, between 5.7% and 5.8% of recent relationships had a lapsed or lapsing registration (3.8% in the smallest band, on few cases). A longer list simply gives more chances for one renewal to be missed. Half of these primes reported fewer than 28 subs, and half had 6 or fewer recent ones.
Among the 53 primes with something to check, 26 had one such sub, 13 had two and 14 had three or more.
What a lapsed registration does and doesn't mean
It is not an exclusion, and it is not evidence of wrongdoing by the sub or the prime. Companies that do business with the federal government register in SAM.gov and renew at least every 365 days; an expired registration is still listed, but it is no longer active.
It may not even be a problem. Registration is required of offerors and prime contractors (FAR 52.204-7, and 52.204-13 during performance). The clauses don't generally ask it of subs, and SAM.gov offers subs a Unique Entity ID on its own. A prime does need a first-tier sub's UEI to report the subcontract under FAR 52.204-10, and the UEI remains when a registration lapses.
So each of the 113 is a question, not a finding against anyone. A lapse matters when your subcontract or policy requires active registration, when the sub also holds prime awards of its own, or as a sign that nobody at a small supplier is minding its federal paperwork. What to do when a sub's registration lapses covers the steps.
Subs we couldn't read, and integrity records
455 relationships (7.6%) were with a UEI that isn't in SAM.gov's public extract. That is not a finding. The extract lists registered entities, and leaves out companies that hold a UEI without a registration and those that opted out of public display. For these we checked neither registration nor exclusions, so the zero above says nothing about them. A prime screening its own list would look each one up at SAM.gov.
Integrity records. Where our data had them, we also read the responsibility records agencies post about a contractor (the records formerly in FAPIIS). We saw 13 such records on 7 subs, under 3 primes: terminations for cause or default, and failures to comply with closeout requirements. A record isn't an exclusion; it is information a responsibility decision takes into account (FAR 9.104-6). We did not have these records for every sub, so 7 is a floor and not a rate. See FAPIIS and integrity records.
What this doesn't show
- It is not a random sample. We started from USAspending's recipients by fiscal year 2026 contract obligations at twelve agencies, Defense first, and dropped the largest companies, universities and laboratories by name. Of the 160 screened, 107 (67%) came from the Defense list and 32 from eleven civilian agencies, each with $43 million to $150 million obligated by that agency in the year. For the other 21, from an earlier list, we recorded no agency.
- It covers only primes that report subawards. We looked up 768 primes. For 608 of them USAspending showed fewer than five subcontractors (for 570, none) on the contracts we pulled, and we didn't screen those. Subcontracts below the reporting threshold in FAR 52.204-10, lower-tier subs and anything a prime didn't report are absent.
- "Recent" is a reported date, not a payment. It means the prime reported a subaward to that sub dated within 365 days before the screen. The relationship may have ended since.
- It is a snapshot. Registration facts are as of the November 1, 2026 extract. A sub that renewed after that date still counts as lapsed or lapsing here.
- It says nothing about any prime's compliance. We can't see a prime's own checks, its subcontract terms or the written disclosures FAR 52.209-6 asks it to collect. These counts describe public records, not conduct.
How we counted
- Primes: for each one, its contracts (award types A to D) with activity from October 1, 2024 to September 30, 2026 on USAspending, matched by the prime's UEI, up to its 300 largest by award amount. Ten primes reached that cap.
- Subs: every subaward reported on exactly those contracts in the same period, grouped by the sub's UEI. Rows without a valid 12-character UEI were dropped, as was the prime itself. A prime with fewer than five such subs was not screened.
- Screens ran on November 8, 2026 (136 primes) and November 9 (24 primes). Each sub's UEI was looked up in SAM.gov's public entity extract dated November 1, 2026, together with the exclusions linked to that registration by UEI or CAGE. Nothing was matched by name.
- Active exclusion: one with no termination date, or a termination date after the screen date.
- Lapsed: a recent sub whose registration status was not active, or whose expiry date was before the screen date. Lapsing: expiry date within 30 days after the screen date. Registration dates were not examined for subs with no subaward in the prior 365 days.
- Relationships are counted per prime. The 113 lapsed or lapsing relationships involve 110 distinct subs; the 2,040 recent relationships involve 1,894.
- Percentages are rounded. No prime and no subcontractor is named here, on purpose.
You are welcome to quote these numbers. Please link back to this page, and keep the limits with them.
Run the same check on your own subs
Everything here uses public data. For one company, the supplier check takes a UEI or CAGE code and shows its SAM.gov registration status and expiry, whether an active exclusion is linked, and any possible screening-list match, with no account. For a list, the pre-award screening checklist has the steps in order, and how to check if a company is debarred covers the search at SAM.gov itself.
The registration result is the argument for a calendar rather than a one-time check: a registration that was active at onboarding has an expiry date within the year. Watch re-checks each confirmed supplier daily and warns before the date; so does a reminder in your own tracker, if someone keeps it.