How does Tennessee worker classification actually work?

Marcus is a software developer in Nashville on a 1099. He sets his own schedule and works from home on his own kit, but he joins the sprint planning call every Monday, follows the product backlog the VP of Engineering manages, and invoices only this one client. Run those facts through the Tennessee Department of Labor's 20-factor guide for unemployment and he reads as an employee. The IRS reaches the same answer for federal payroll. There was never one test to get right.

The practical split that trips out-of-state employers: the 20-factor unemployment test and the 7-factor workers' comp test are not the same test and can reach different answers on the same set of facts. There is no state income-tax withholding track to flag a bad classification early. The unemployment-tax track usually opens the file, commonly when the worker files for benefits after the engagement ends.

Latoya is a marketing consultant in Memphis, paid on project fees as a 1099. She uses the company content-management platform, attends the weekly editorial meeting, and works exclusively for this client. She owns a laptop and sets her own hours, but she earns nothing from any other client. She clears only a handful of the 20 factors, and the behavioural-control bucket points almost entirely at employee. The contract calling her a contractor changes none of that. The Tennessee DOL applies the same factors the IRS does for unemployment tax.

A genuine contractor reads the opposite way on most of these: own hours, own tools, several clients, paid by deliverable, free to subcontract. The role that fails on the first ten, the behavioural-control bucket, is the one the TN DOL reclassifies first. Teamed's Contractor Classifier walks the same 20 factors the auditor uses and records the rationale in your file.

The contrast is clearest in tech and professional services. A Tennessee software company that engages a developer on a 1099 can score the 20-factor test and find a clean contractor result if the arrangement genuinely looks like one: own tools, own hours, several clients, paid by the sprint. Under the old ABC test, prong B would have asked whether software development falls outside the company's usual business. For a software company, it plainly does not, and the contractor classification would have failed at prong B regardless of everything else.

This divergence between the unemployment test and the workers' comp test is the conversion trap for construction and staffing employers. A worker cleared on the 20-factor unemployment test can still be an employee for workers' comp under the 7-factor analysis if the right-to-control facts point that way. Construction employers face the sharper end: North Carolina is another common-law state where the workers' comp and UI tracks split, and many employers learned the hard way that passing one was not passing both. Teamed's Contractor Classifier runs the analysis the auditor will actually use, state by state.

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

Tennessee gives no state safe harbour of its own, because there's no state income-tax track and the unemployment-tax track carries no reasonable-basis shield. The federal Section 530 safe harbour can still cap the federal payroll-tax piece if you filed 1099s consistently and had a reasonable basis. It does nothing for the FLSA back wages or a worker's own lawsuit. Compare the same federal stack in Texas, another no-income-tax state where the unemployment test also runs alongside the federal tracks.

Three conditions carry Section 530, all required: a reasonable basis for the contractor treatment (a prior audit, a court ruling, industry practice, or written advice from a qualified adviser), consistent 1099 filing every year, and consistent treatment of every worker in the same role. Miss one and the shield drops.

Tennessee's 2020 switch from the ABC test to the 20-factor test matters for one reason: any employer who treated workers as contractors under the old ABC test and got that call right at the time now uses the IRS test on every new engagement. The transition did not invalidate prior correct classifications, but it changed the analysis going forward. An engagement that cleared the ABC test's prong B (work outside the usual business) does not automatically clear the 20-factor test. Run the current test on every engagement, not the pre-2020 rulebook.

The honest read for most knowledge-work roles is the same on every test: employee. The divergence sits in the genuine edge cases, the specialist who works from home on their own kit, sets their own hours, bills by deliverable, and serves several clients. That worker clears the common-law 20-factor test and the FLSA economic-reality test together. The role that fails one usually fails the others.

Real HR and legal experts handle your Tennessee classification calls and know the TN DOL 20-factor test, the 7-factor workers' comp test, and the FLSA economic-reality line 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 genuine contractor, the engagement runs on a Teamed agreement that records the common-law analysis at the point of hire. For a role that fails it, Teamed US Inc. is your W-2 employer of record from day one, with Tennessee unemployment tax, federal FICA and FUTA, and workers' comp premium all booked at the correct rate. A quarterly review catches any contractor whose role has drifted toward employee before the TN DOL does.

Contractor onboarding, EOR payroll and entity graduation live on one platform. A Tennessee 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 Tennessee hire, until it isn't.