How does Washington's worker classification test actually work?

Priya runs a UX consulting business in Bellevue. She sets her own hours and owns her own tools, so the control part is clean. But she works exclusively for one tech client whose main product is UX design. She has no UBI number registered with the Washington Department of Revenue, and she does not maintain a separate business bank account. On Path 1 she fails the usual-course-of-business part. On Path 2 she fails the UBI and separate-books parts. One failed part on whichever path the employer tries makes her an employee. The 1099 agreement is irrelevant.

The fault line most multi-state employers miss: Washington's no-income-tax status means there is no payroll mismatch to flag a bad classification early, so the file opens at ESD when the worker files for unemployment benefits. By then, the back UI contributions, back L&I premiums, and wage-and-hour liability have already accrued across the full engagement.

Construction work adds a seventh requirement on both paths: the contractor must hold a valid contractor registration under RCW 18.27 or an electrical licence under RCW 19.28. A registered contractor who fails any of the six standard parts is still a covered worker for workers' compensation. Registration is necessary but not enough.

California's ABC test presumes the worker is an employee and puts the burden on the employer to prove all three prongs. Washington does the same thing. The practical difference is the second path. A California software company engaging a contractor developer fails prong B because writing software is the usual course of the business. A Washington software company can try Path 2 instead, skipping the usual-course question entirely. That's the opening.

The closing is the documentary bar. Path 2 requires the worker to have a registered UBI number with the Washington Department of Revenue before the contract is signed, or within a reasonable period after. An overseas contractor or a worker newly in business almost certainly lacks this. The employer who doesn't check is on the hook for the full engagement from day one.

Compare the same engagement in Texas, a pure common-law state. Texas starts neutral and weighs the facts across 20 factors. There is no presumption, no prong B, and no UBI requirement. A developer engaged as a clean 1099 in Texas keeps the same role after the company opens a small Seattle office and re-engages the worker there. Texas was fine. Washington is not, unless the worker holds all the documentation Path 2 requires. Teamed's Contractor Classifier runs the test that matches each engagement's state, so the Washington path analysis and the Texas factor analysis each come from the right rulebook.

Walk a $90,000 contractor through a three-year L&I audit. The tracks stack.

Washington recognises no general good-faith safe harbour for the state classification question. Federal Section 530 can cap the federal payroll-tax piece if you filed 1099s consistently and held a reasonable basis for the contractor call, but it does nothing for the ESD, L&I premium, or wage-and-hour exposure. Compare California, the other West Coast state with heavy workers' comp enforcement, where the ABC prong-B failure triggers a similar stacked bill.

Washington's enforcement posture changed substantially in 2026. The old framework relied on complaints and audits. The new one adds proactive prosecution for industries that routinely use 1099s to avoid employment costs: technology, construction, gig-economy logistics, and professional services. The Worker Rights Unit targets systemic misclassification, not isolated cases, which means a single audit finding across a workforce of contractors can trigger a full-program review.

Construction draws the sharpest scrutiny. A contractor who lacks registration under RCW 18.27 fails the seventh part of the workers' comp test automatically, and L&I coordinates with the Contractor Registration program. A subcontractor on a Washington job site who can't produce a valid registration triggers an assessment that runs up the chain to the general contractor.

The practical read: Washington is not a state where a borderline 1099 arrangement ages well. The documentary requirements of Path 2, the UBI number, the DOR account, and the separate books, exist at the start of the engagement or they don't exist at all. By audit time, you can't paper them in retroactively. The defensible position is the one built into the contract before the first invoice.

Real HR and legal experts handle your Washington classification calls and know both RCW 50.04.140 paths, the L&I workers' comp personal-labour test, and the HB 2479 wilful-penalty rules by heart. An actual person, not a chatbot or a pooled queue. There is no setup fee and no exit fee, and statutory employer cost passes through at cost, itemised on every invoice.

For a role that clears all parts of Path 2, the engagement runs on a Teamed contractor agreement that records the UBI number, the DOR account status, and the separate-books confirmation at the point of hire. For a role that fails either path, Teamed US Inc. is your W-2 employer of record from day one, with Washington UI contributions, L&I workers' comp premium, federal FICA and FUTA, and WA Cares Fund deductions all booked at the correct rate. A quarterly review catches any contractor whose documentary position has lapsed before ESD does.

Contractor onboarding, EOR payroll and entity graduation live on one platform. A Washington contractor who converts to W-2 keeps their record, and that same employee can graduate from EOR to your own US entity without switching systems. Use the Crossover Calculator to see the month the model flips. EOR is the right model for a first Washington hire, until it isn't.