Independent, not SAM.gov

SAM.gov IAE migration, week five

Updated 18 October 2026

ZeroGov covers the independent lane of US federal contracting, and we are not affiliated with SAM.gov or the General Services Administration. Five weeks into the IAE migration, the bottleneck is no longer uptime, it is the Entity Validation queue, and that is the only story that matters this week.

What changed in week five of the SAM.gov IAE migration

The first three weeks of the SAM.gov move to the Integrated Award Environment were an infrastructure story. The fourth week was a backlog story. Week five, the one that opened on Monday the twelfth of October and runs through this weekend, is a process story, and it is the most important shift so far for anyone whose SAM record is the gate to a bid, a payment, or a set aside decision.

Uptime has stabilised. The read only weekend of the third and fourth of October is now two weeks behind contractors, and the early week one glitches that had people refreshing ticket pages are gone. The five things contractors learned in week one still hold, and the read only recovery checklist we published at the end of week three is still the cleanest field manual we have for cleaning a corrupted record after the cutover.

What is new is that the queue has narrowed. The migration waves that pulled in legacy records with old CAGE values, old address strings, and old DUNS style identifiers are largely drained. What is left is harder, and it is concentrated in Entity Validation, the gating step that decides whether a SAM record is real, reachable, and tied to a taxpayer identifier that the Internal Revenue Service will vouch for. We covered the week four pattern, where the Entity Validation queue was shrinking in headline terms but was in practice redistributing itself across three review paths. Week five is the week those three paths became the whole game.

Independent contractors watching the SAM.gov IAE migration tracker and the IAE status page have started to notice something that mirrors what we are hearing in the FBO comment threads and on the small business subreddit. New SAM registrations and address changes are sitting in Entity Validation for longer than the historical forty eight hour median. Tickets that used to close in three business days are closing in eight. The Internal Revenue Service validation step, which is supposed to be near instant for entities with a clean Employer Identification Number, is now the single longest pole in the tent for the majority of new entries.

This is a process story, not a system story. The pipes are working. The reviewers are working. The math just no longer fits, and the math is what we are going to walk through below.

Who is in the Entity Validation queue right now, and why

If your SAM record is in Entity Validation today, you are almost certainly in one of three buckets. The three buckets line up with the three review paths that GSA stood up during the pre migration hardening push in August and September, and the three paths are now visible through ticket subject lines and case notes that contractors have started sharing in the SAM.gov community board and in the r/federalcontracting weekly thread.

The first bucket is brand new entities. These are contractors and nonprofits that started a SAM.gov registration for the first time after the IAE cutover on the sixth of October. Before the migration, a clean new registration with a matching IRS TIN match and a working mailing address typically cleared Entity Validation inside one business day. In week five, the median for this bucket is sitting at six business days, with a long tail that stretches past ten. The reason is procedural. The IRS validation service that SAM.gov calls behind the scenes is rate limited, and the rate limit was set against the pre migration volume forecast. The IAE migration pushed a one time registration surge on top of the normal new entity flow, and the IRS side of the handshake is the choke point.

The second bucket is address changes. Any contractor who updated a mailing address, a physical address, or a country code on an existing active record after the sixth of October is in this bucket. Address changes used to clear Entity Validation in a single automated pass because the IRS does not need to be consulted for a US to US address move. Under the IAE, address changes now route through a human review path that checks the address against the USPS AMS snapshot, the Census Bureau geographic identifiers, and a few other reference tables that were folded into the new schema. That human review path has a single digit headcount and a queue that is measured in days rather than hours.

The third bucket is the one that surprised us. It is the NAICS code review path. We have covered how to find your NAICS code before, and we have covered how SBA's proposed new size standards would change small business status, but neither of those pieces prepared us for the way the IAE is treating NAICS assignments. When a contractor selects a NAICS code that maps to a size standard that is currently under SBA review, or that maps to an industry category that intersects with a HUBZone certification map, the record is being routed into a secondary validation queue. We are tracking at least three NAICS ranges that are triggering this path: the 5415xx computer systems design family, the 56111x office administrative services family, and the 238xxx specialty trade contractors family.

Across all three buckets, the pattern is the same. The system is working as designed, the queue is just bigger than the reviewers, and the only lever a contractor has is the quality of the data on the record before it enters the queue. That is the part we can help with, and it is the part we are going to dig into next.

What contractors can do about the new Entity Validation reality

There is no way to skip Entity Validation, and there is no way to pay for an expedite. The banking screen is not a paid product, and neither is the validation queue. The only thing that moves a record out of the queue faster is a record that does not need a human reviewer to interpret it. Here is the playbook that has worked for the contractors we have been talking to this week, in the order the steps should be taken.

First, pull your own ticket before you call the help desk. The SAM.gov ticket tracker reads your case before you call, and that has not changed under the IAE. If your ticket is in the IRS validation bucket, the case notes will say so in plain language. If your ticket is in the address review bucket, the case notes will name the field that is under review. Reading the ticket first means the call to the help desk is a confirmation call, not a status request, and confirmation calls close faster than status calls. We have heard anecdotally of contractors getting an answer on the first call this week when they opened with the case notes verbatim, and we have heard of contractors waiting on hold for over an hour when they opened with a generic where is my record question.

Second, audit your address strings. The IAE normalises addresses against a stricter schema than the legacy SAM.gov did, and an address that was valid under the old rules can fail the new rules. The two most common failures are apartment numbers that are in the wrong field, and suite numbers that are concatenated into the street line instead of living in their own field. The USPS AMS snapshot that the address review path is checking against is unforgiving on this, and a one character fix on the record can drop a ticket out of the human review queue and into the automated path.

Third, do not change your NAICS code while you are in Entity Validation. We have heard from three different contractors this week who tried to swap a NAICS code to align with a specific solicitation while their record was in the validation queue, and in all three cases the swap kicked the record to the back of the queue. The IAE treats a NAICS change on a record that is under validation as a new submission, and the new submission starts the timer again. If you have a solicitation in front of you that is asking for a different NAICS, wait until the record is active and then file the change as a separate update, not as a mid queue edit.

Fourth, do not confuse the entity validation queue with the entity registration queue. They are not the same thing. The entity registration queue is the queue that decides whether a new entity can start a registration at all, and that queue has been near empty for most of week five. The Entity Validation queue is the queue that decides whether a registration, once started, is allowed to become active. If you are in the Entity Validation queue you are past the registration queue, and the work to do is on the record, not on the entry point.

Fifth, keep an eye on the small business status fields. The SBA certification statuses, the 8(a) status, the HUBZone status, the women owned small business status, and the veteran owned small business status, are all derived from the entity record. If the entity record is in the validation queue, those derived statuses are also paused. SBA certifications are not SAM.gov, and the SBA side of the data flow is still working, but the SBA system is reading a paused SAM record, and the read is showing nothing. Do not read the absence of a status on SBA's side as a cancellation, read it as a pause.

What this page is not

This page is not affiliated with SAM.gov, with the General Services Administration, with the Integrated Award Environment, with the Small Business Administration, or with the Internal Revenue Service. ZeroGov is an independent publication that covers US federal contracting, and we do not speak for any federal system. Nothing on this page is legal advice, and nothing on this page is a substitute for reading your own ticket, your own record, and your own contract.

This page is not a promise that any of the timelines above will hold for your specific record. Queue times are medians, not guarantees, and the bucket you are in changes the math. A new entity in the IRS validation bucket is on a different clock from a legacy record in the address review bucket, and we are reporting what we are seeing across the contractors we are in contact with, not what any individual contractor will see.

This page is not a how to guide for fixing Entity Validation Failed errors. We have a separate piece on that, and the two are intentionally distinct. The what is the new bottleneck story is process level, and the how to fix the error story is record level. Read both.

This page is not a substitute for the federal contracting calendar we maintain, which is the right place to look for SAM renewal deadlines and other dates that matter this month.

What to watch in week six

Week six opens on Monday the nineteenth of October. Three things are worth watching.

The first is whether the IRS rate limit on the validation handshake gets raised. GSA and IRS have been in conversation about this for two weeks, and there is reason to expect a change before the end of the month. If the rate limit goes up, the new entity bucket will drain quickly, and the address review bucket will become the dominant share of the queue by the end of week six.

The second is whether the NAICS review path expands. The three NAICS ranges we named above are the ones we have direct evidence for. If the path expands, expect to see the specialty trade contractors bucket in particular get longer, because the 238xxx range overlaps with the SBA size standard review that is still in proposed rule.

The third is the shutdown ripple. The October 2026 federal shutdown is now in its recovery phase, and the after the shutdown ripple for federal contracts is still working through the payment system. Stop work orders issued during the shutdown are being lifted in tranches, and the contractors who were paid on a SAM.gov linked schedule are the ones most exposed to a delayed Entity Validation. We are tracking the intersection of the two stories and we will report on it as soon as the data firms up.

Independent information, not legal advice. Confirm status and rules on sam.gov and the current FAR text.