How does Ohio worker classification actually work?

Priya writes software for a Columbus startup on a 1099. She sets her own hours and uses her own laptop, but she is in the daily standup, follows the sprint board, and bills only this one client. Run those facts through the ODJFS 20-factor guide and she is an employee for unemployment tax. Run the same facts through the IRS common-law test and you reach the same answer. Ohio also requires BWC registration for every employer with workers on site, so the startup is already exposed on workers' comp for any injury Priya suffers. There was never one question to get right.

The fault line out-of-state employers miss is the BWC column. In Texas a company can engage a 1099 and carry no workers' comp exposure because coverage is elective. In Ohio, every employer with at least one worker on payroll must register with the BWC state fund. A misclassified 1099 who suffers a workplace injury can file a BWC claim, and the bureau can retroactively assess premium on the unreported payroll. The Ohio income-tax track is a second distinction: a 1099 who should be on W-2 creates an Ohio withholding shortfall that the Department of Taxation can recover independently of any ODJFS audit.

Marcus writes software for an Akron firm on a 1099. He uses the company CRM, joins the Monday planning call, and works the project backlog the engineering director sets. He bills only this one client. He clears only a handful of the 20 factors, and the direction-and-control bucket points almost entirely at employee. The written contract calling him a contractor changes none of that, because Ohio law looks at the actual relationship, not the label on the agreement.

A genuine contractor reads the opposite way on most of these: own hours, own tools, multiple clients, paid per project, free to subcontract. The role that fails on the first ten, the behavioural-control bucket, is the one ODJFS reclassifies first. For construction work, the bar is harder: ten or more of the twenty factors pointing toward control creates a statutory presumption of employment under ORC 4141.01(B)(2)(k). Teamed's Contractor Classifier walks the same 20 factors the auditor uses and records the rationale in your file.

The common-law test reflects a balance. A contractor who scores most of the 20 factors toward independence is usually a contractor. Add facts that point to direction and control and the answer shifts. There is no single fact that ends the conversation, and no presumption to overcome.

This is the multi-state trap employers walk into. A developer engaged as a clean 1099 in Texas keeps the same role after the company opens an office in Ohio. In Ohio, the same engagement now creates four tracks instead of three, because Ohio has state income tax and mandatory BWC. In a strict ABC state the prong-that-asks-about-your-usual-business fails from day one, no matter how the Texas engagement looked. The test changed because the worker's location changed. Teamed's Contractor Classifier runs the test that matches each engagement's state, so the Ohio answer and the Texas answer each come from the right rulebook.

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

Ohio gives no state safe harbour of its own for the UI or withholding tracks. The federal Section 530 safe harbour can cap the federal payroll-tax piece if you filed 1099s consistently and had a reasonable basis for the contractor call. It does nothing for the FLSA back wages, the Ohio withholding, the BWC premium, or a worker's own lawsuit. Compare the route in Texas, where there is no state income-tax track, workers' comp is elective, and the overall exposure is narrower on the same set of facts. Ohio's four tracks mean the cleanest version of this bill is the one you never trigger.

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. Under IRS Rev. Proc. 2025-10 (in force for 2026), the IRS can now consider whether you treated the same worker as an employee for state unemployment purposes while claiming contractor status for federal tax, and use that inconsistency against you.

The BWC question is separate and more concrete. Ohio law requires every employer with at least one worker on payroll to register with the BWC state fund or qualify as a self-insurer. A 1099 labelled as a contractor is not automatically exempt. If the BWC audits the payroll and concludes the worker was an employee under the right-to-control test in ORC 4123.01, it can assess back premium on the full unreported payroll going back to when the engagement began. For a knowledge-work role that lasted two or three years, that retroactive assessment can exceed the cost of BWC cover paid prospectively from day one.

The honest read for most knowledge-work roles is the same on every track: 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, serves multiple clients, and carries their own professional liability cover. That worker clears the ODJFS 20-factor test and the FLSA economic-reality test together. The role that fails one usually fails the others, including the BWC right-to-control test.

Real HR and legal experts handle your Ohio classification calls and know the ODJFS 20-factor test, the BWC state-fund registration requirement, 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 Ohio unemployment tax, state income-tax withholding, federal FICA and FUTA, and BWC state-fund premium all booked at the correct rate. A quarterly review catches any contractor whose role has drifted toward employee before the ODJFS does.

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