How does Arizona’s worker classification test work in 2026?

California presumes a worker is an employee until you prove three independent factors. Arizona does the opposite: facts and circumstances, weighted across behavioural control, financial control, and the nature of the relationship, per the IRS Rev. Rul. 87-41 twenty-factor test.

David is a software developer in Phoenix. He has three clients, sets his own hours, works from a co-working space he pays for himself, and bills by deliverable. He passes the IRS common-law test for Arizona purposes, passes the right-of-control test for workers’ comp, and passes the federal economic-reality test. One worker, three answers, all consistent.

Sofia is a sales rep in Tucson. Same paperwork as David. But she takes weekly direction from a manager, uses a company laptop, sells only the hiring party’s product, and is paid a recoverable draw against commission. The same three tests can reach three different answers on Sofia, and the conservative call is employee on all of them.

Pick the answer with the broadest coverage when the tests disagree. That is the only safe default.

The declaration is voluntary. Not signing one does not create any negative presumption. Signing one without acting on it is worse than not signing at all.

David, the Phoenix developer, signed a DIBS at the start of his engagement. He files quarterly estimated tax, carries his own laptop, declines work when he wants to, and bills three other clients on the same form. The hiring party never schedules him for a Monday morning standup or requests exclusive availability. At audit, the DIBS holds. The auditor has to overcome a presumption built on six of ten enumerated factors that are visibly true.

Sofia, the Tucson sales rep, also signed a DIBS. Her hiring party has a copy in the file. But the day-to-day looks like employment: weekly one-to-ones with a manager, an assigned territory, a company-owned CRM login, and a draw she has to repay if commissions fall short. The DIBS is in the file but the practice voids the presumption. Worse than no DIBS at all, because the form documents the intent and the practice proves the intent was inconsistent.

What the declaration must affirm

The contractor signs that they:

1. Operate their own independent business
2. Are not an employee and have no right to unemployment benefits from the hiring party
3. Are responsible for all tax liability on payments received
4. Are responsible for obtaining and maintaining their own registrations and licenses
5. Meet at least six of ten enumerated factors

The ten DIBS factors

Three limits worth knowing

• State-law only. The presumption has no effect on a federal IRS, DOL, or NLRB classification challenge.
• Substantial consistency required. The hiring party has to actually run the engagement like the declaration describes. Paper plus opposite practice equals voided presumption.
• Does not cover workers’ comp. That sits on its own separate written-agreement safe-harbour. See the next section.

Jordan runs a small construction crew in Tempe. He hires three trades on 1099, signs a DIBS with each, but does not sign the parallel workers’ comp agreement. Eight months in, one of the trades falls from a roof and breaks his pelvis. The injury runs to six figures. Jordan is personally liable for the medical and lost-wage cost because no premium was paid and the workers’ comp bargain, premium for tort immunity, was never made.

Construction has its own rules on top. Arizona’s statute reaches up the chain to the general contractor when a sub fails to carry coverage. The risk is not limited to the immediate hiring party.

What the workers’ comp written agreement must contain

What it costs to get workers’ comp classification wrong

• Missed premium plus penalty and interest, calculated back to the start of the engagement
• Personal liability for the injury if the worker was hurt on the job and never carried under a policy
• Loss of statutory immunity from civil suit, because the premium-for-immunity trade was never made

A single uncovered head injury can blow past six figures, even for a small Arizona firm. The workers’ comp claim arrives at a judge who applies a different rulebook than the Department of Economic Security auditor. Both can be live on the same worker at the same time.

The state-level numbers look smaller than they would in California or New York because Arizona’s flat 2.5% income tax and $8,000 SUTA wage base are both low. The federal floor dominates the stack. State exposure adds 5 to 15% on top.

The criminal track is separate from the civil-and-tax audit. The threshold is wilful misrepresentation, not honest error. But in an aggressive audit the line between optimistic adviser language and wilful conduct can look uncomfortably thin.

If the proposed rule lands later in 2026, the federal threshold for finding a worker is an employee for FLSA overtime tightens slightly. The state-level Arizona analysis under the common-law test runs on its own track.

David, the Phoenix developer, passes both tests today. He still passes both tests on the day the new federal rule lands, because his profile is unambiguous on every factor. The change matters for the consultant who works exclusively for one client on a deliverable basis, with their own tools and schedule. That profile sits closer to the line under both rules, and the line moves slightly under the new federal rule.

When the tests disagree on a borderline role, take the conservative answer: employee. Re-running the analysis after the rule lands is cheaper than re-running it after an audit.

• Day 0. The role goes through the Contractor Classifier. The tool walks the IRS common-law factors and the ten DIBS factors, produces an informational risk indicator (not a legal determination), and flags any factor that pushes the role toward employee. David would land high-confidence contractor. Sofia would land flagged.
• Day 1, EOR path. Teamed’s US entity is the legal employer of record. We onboard with Arizona Form A-4, federal W-4, Form I-9, and the Arizona Joint Tax Application registration if not already in place. Workers’ comp premium gets booked automatically at the right risk class. Paid leave and sick-leave accruals are calculated from day one; state income tax and UI contributions run on cadence.
• Day 1, contractor path. The engagement runs on a Teamed contractor agreement that captures the DIBS analysis and the workers’ comp written agreement on the same signing flow. The contractor receives a 1099-NEC at year-end; the hiring party never touches Arizona withholding for that worker.
• Ongoing. All federal and state filings run on cadence. Multi-state day ledger maintained for any worker who travels. Quarterly classification review surfaces any role that has drifted toward employee since hire, before the auditor does.
• If a role changes. A contractor who needs to convert to W-2 keeps their record. The same platform onboards them as an EOR employee on the right test from day one. If the engagement ends, Arizona termination law and at-will exceptions governs the separation.

Behind the platform sit real HR and legal experts with deep local employment-law expertise who track Arizona DES audit patterns and Industrial Commission case law. When something looks borderline on the common-law test or on the DIBS factor count, you message an actual person, not a chatbot or a pooled queue. No support tickets.

When EOR is the right call (and when it isn’t)

EOR works while you’re testing the Arizona market, ramping a small remote team in Phoenix or Tucson, or running a few W-2 hires alongside contractor relationships you want to preserve. Once you have six or more Arizona employees and predictable hiring ahead, the maths of your own US entity starts to win. Teamed’s Crossover Calculator shows you the month it flips. We graduate clients to their own entity when the spreadsheet says it’s time. The conversation is built into the relationship. EOR is the right hiring model, until it isn’t.

Statutory employer cost (FICA, FUTA, Arizona SUTA, workers’ comp premium) passes through at cost, itemised on every invoice. No markup on statutory cost. No setup fees. No exit fees.