Lock Down the I-9 Audit Trail Before the Jan. 8 E-Verify Cutoff
Older E-Verify accounts need a preservation step before the agency removes historical case records.
| By | The Petition File — Newsroom |
|---|---|
| Filed | 31 October 2026 |
| Read | 3 MIN |

The deadline is January 8, 2027. If your E-Verify account predates 2017, that date is the last moment to pull the old case records before USCIS, the immigration agency, removes them. The rule is simple: records last touched on or before December 31, 2016 are in the current disposal cycle. The workaround is preservation: download, reconcile, archive, and confirm vendor copies.
The deadline is the trigger
USCIS will permanently dispose of those records after the cutoff. The disposal cycle follows a National Archives and Records Administration retention schedule that directs removal of E-Verify records at least 10 years old. That schedule is the reason the agency is removing the oldest cases now. If your enrollment began in 2017 or later, the current cycle does not reach your account. You are not exempt from future cycles, but this one is aimed at older records.
Treat the account, not the employee, as the unit of work. A single employer may have multiple accounts, and each account can hold cases for different entities. If the company has gone through acquisitions, rebrands, or payroll changes, the oldest accounts are the ones most likely to be overlooked. The download is only useful if the team can say which account produced it, which entity it covered, and which I-9 files depend on it.
The rule turns a download into an audit trail
A downloaded file is not enough if it cannot be matched to the Form I-9 it supports. For each related Form I-9, you must record the E-Verify case verification number or attach the E-Verify case details page. That link is what makes the onboarding file defensible. Without it, the I-9 has no linked verification evidence.
The records can surface in a Department of Homeland Security audit, a Department of Justice Immigrant and Employee Rights Section investigation, a Department of Labor request, or a state inspection. In a worksite enforcement matter, the file should show who was verified, when, and how the result tied to the employee record.
The case details page is the exhibit that ties the employee to the verification result. If the I-9 is paper, the attachment should be physically or electronically linked to the same employee file. If the I-9 is electronic, the metadata should show the association. A case number written on the form is useful, but the details page is stronger because it preserves the content of the verification record, not just a reference to it.
The checklist keeps the file defensible
Use this list as the preservation checklist. Each item is testable in a minute, and the order matters because the download must exist before reconciliation can begin. The record retention step is the part that turns a download into a defensible I-9 compliance file.
- Confirm the account list names every E-Verify account and entity that enrolled before 2017. Mark each one as in scope or out of scope.
- Confirm a historical case report exists for records created or updated on or before December 31, 2016. Save the report metadata, including the date and time of the download.
- Confirm each retained Form I-9 has the case verification number or the attached case details page. Flag any I-9 that lacks the link.
- Confirm the downloads are stored in a read-only location with access controls and a retention label. Keep the archive separate from active case files.
- Confirm any vendor or outside counsel copy matches the downloaded case details page. Note the custodian, the date, and the storage location.
The list is short because the failure mode is simple: a missing file, a mismatched case number, or an archive that no one can find. If a regulator asks for the verification record, you should be able to produce the I-9 and the matching E-Verify evidence in the same review. A clean audit file is the standard.
Keep a short index of what was downloaded, where it is stored, and who can retrieve it. The index should name the account, the entity, the report date, the archive location, and the person responsible for production. If a request arrives, the team should be able to pull the I-9 and the matching verification evidence without reconstructing the file from memory. That index is the difference between a retrieval task and a reconstruction task, and it is the part of the file that makes the archive usable when needed.