Most states leave E-Verify optional for private employers. Arizona does not.
Under the Legal Arizona Workers Act, every employer in the state is required to verify the employment eligibility of new hires through E-Verify. For a manufacturer hiring forty people a year, that is a small addition to onboarding. For a staffing agency that might onboard forty people in a week, it is a process design problem.
This is general information about how the requirement interacts with staffing operations, not legal advice. Employment verification law changes and the penalties are serious — talk to your employment counsel about your specific obligations.
What the requirement actually is
E-Verify is a federal system that checks the information from an employee’s Form I-9 against Social Security Administration and Department of Homeland Security records.
Two things are worth being precise about, because they are commonly confused:
E-Verify does not replace the I-9. You still complete Form I-9 for every new hire, within the federal deadlines. E-Verify is an additional check run against the information the I-9 captured.
It applies to new hires, not to your existing workforce. Running E-Verify retroactively on current employees is not what the system is for and creates its own problems.
Arizona’s enforcement mechanism is what makes it bite: the state can suspend or revoke the business licences of employers found to have knowingly employed unauthorised workers. That is a materially different risk profile from a federal fine.
Why staffing agencies feel this differently
Three structural facts about staffing collide with employment verification.
Volume. You are the employer of record for everyone you place. A branch filling a warehouse account through peak season onboards more people in ten weeks than most businesses do in a decade. Every one needs an I-9 and an E-Verify case.
Speed. A customer calls Thursday needing fifteen people Monday. The verification step sits directly in that path, and the pressure to start someone before it completes is real and constant. It is also exactly where agencies get into trouble.
Multi-state operations. Arizona agencies rarely stay inside Arizona. Alabama, Georgia, Mississippi, North Carolina, South Carolina, Tennessee, and Utah also have mandatory E-Verify requirements for private employers, each with its own scope, and other states have partial requirements covering public contractors. If you place workers across state lines you are managing several regimes at once, and the answer to “do we have to E-Verify this person” depends on where they are working.
Where it belongs in the process
The workable arrangement is to make verification part of onboarding rather than a separate step somebody performs afterwards.
That means:
- Capture the I-9 data digitally at onboarding, validated at the point of entry rather than corrected later. The most common cause of an E-Verify mismatch is a transcription error in a name, a date of birth, or a Social Security number — not an actual eligibility problem.
- Run the E-Verify case within the required window, tracked against the person.
- Hold the result on the personnel record, so it can be produced during an audit without anyone searching an email archive.
- Do not dispatch before the process is complete. This is a scheduling discipline as much as a compliance one, and it needs to be enforced by the system rather than by memory.
In Staffing Complete, this is the reason onboarding, screening, and the personnel record sit together. Digital onboarding through Able collects and validates the data and handles SSN verification, background screening runs through Asurint against the same record, and the documents stay attached to the person rather than to a process.
Tentative non-confirmations
A tentative non-confirmation is not a finding that someone is unauthorised to work. It means the data did not match, and very often the cause is clerical — a name changed after marriage and never updated with the SSA, a hyphenated surname entered inconsistently, a transposed digit.
The employee has the right to contest it, and there is a defined process and timeframe for doing so. Taking adverse action against someone while a TNC is being contested is itself a violation.
For an agency, the practical requirement is that somebody owns TNC follow-up as a named responsibility with a deadline, rather than it sitting in a queue nobody watches. This is ordinary reminder-and-checklist work, which is what those tools are for.
Keeping the records
Retention rules for I-9s are specific: keep them for three years after the date of hire or one year after employment ends, whichever is later.
In staffing, “whichever is later” does a lot of work, because a large share of your employees work briefly. Practically, you are keeping most I-9s for the full three years from hire, for a population that turns over continuously.
The only sustainable approach is documents held against the personnel record digitally, so producing them during an audit is a query rather than an excavation of a filing cabinet in a branch that has since closed.
Why we care about this
Carvin Software is in Gilbert, Arizona, and a meaningful share of the agencies we work with are Arizona employers dealing with this requirement every week. It is one of the reasons employment eligibility handling is built into the onboarding flow rather than treated as a bolt-on — in this state it was never optional.
If you are working out how to run verification at volume without slowing down dispatch, we are happy to talk it through.