Contractor vs Employee: Where the Line Actually Falls

TL;DR

• Core decision: How the work is actually performed beats what any document says, every time, in every jurisdiction in scope.
• When doing nothing is right: When your bench genuinely behaves like a bench, meaning separate engagements, separate invoices, separate tools, and the worker could walk tomorrow with no operational damage.
• What has to be true: A genuinely independent trade, freedom from day-to-day control, and work that sits outside the usual course of your business. Miss any one and the analysis shifts.
• How options split: Stay as contractor, convert to employee, or step outside the relationship entirely through an employer of record or a corporate restructure.
• Decision rule: Run the working relationship through the test, not the contract. If you wouldn't defend the relationship on the facts in front of a regulator, don't call it a contractor relationship in the first place.
• Outcome to expect: Clarity that survives a phone call from the regulator, not just a tidy PDF in your HR folder.

A Tuesday Morning in the People Team

A people director opens a folder on her laptop. It's labelled "Contractors – 2024 archive" and it has not been touched in a while. Inside are fourteen contracts, all signed two years ago when the company was smaller and the work was bursty. Back then each contractor was a specialist hired for a defined piece of work, and the file was a tidy record of who had done what. She scrolls through and recognises names that haven't felt like outside names for a long time. One of them, a senior engineer, has been in the daily standup every morning for eighteen months. Another, a designer, has her own desk, her own laptop and a login that doesn't expire. A third sends invoices for exactly the same amount on exactly the same date each month, with a memo line that reads "monthly retainer."

She closes the folder. But she doesn't feel comfortable. The question isn't whether her contracts are well drafted. They probably are. The real issue isn't what she called these people two years ago. It's what a regulator would see if it opened the same folder today.

When You Can Genuinely Leave This Alone

Not every contractor bench is a problem in waiting. Some are exactly what they look like. The instinct to assume otherwise is itself a kind of risk, because it makes you pull people off real work to clean up files that didn't need cleaning. Before you do anything else, you have to be honest about which of the four stages below you're actually in.

Recommended Tools

Best tools for Global HR

D Deel Global payroll & EOR R Remote Global HR platform P Papaya Global Global workforce management

View all recommended tools

Stage one: your setup is genuinely fine. A small, named project lands, you find a specialist, you agree a fee, the work happens, the invoice is paid, and the person isn't in your standup. You're not in their tools. They hold other clients. If they left tomorrow, you would be annoyed about delivery but you wouldn't be hiring a replacement who needs to learn your codebase. This is the contractor relationship the tests were built to recognise, and you don't have a problem.

Stage two: friction. The work has not changed in scope but the rhythms have. The contractor is in more meetings. They get CC'd on internal updates. The project has drifted from "a defined piece of work" into "an ongoing thing nobody has bothered to renegotiate." The label still says contractor. The working life is starting to look more like a staff pattern. You don't have a crisis yet, but you've the early shape of one, and the longer you leave it the more the relationship calcifies.

Stage three: real risk. The contractor works only for you, sets no hours of their own, uses your equipment, attends your all-hands, and is functionally indistinguishable from a permanent hire except for the absence of benefits and the presence of a monthly invoice. The work is core to your business, not a side project, and the person has no visible trade outside your walls. This is the pattern that fails the regulatory tests, and it's the pattern that triggers the worst conversations you don't want to have.

Stage four: the edge case. A small number of genuinely senior people sit in roles where the line is genuinely arguable, often because they're a founder, a fractional executive, or a specialist whose trade is the work itself. Here the tests can resolve in your favour if the facts are right, but you don't know that without working through it. These are the cases that justify legal review, not the cases that justify a panicked email to your accountant.

Five Questions a Head of People Asks at 11pm

"If the contract says contractor, does that decide it?" No. The contract is one piece of evidence. It can be a strong piece, but no test in any of the jurisdictions in scope treats the label as decisive. If the working relationship looks like employment, the contract won't save you. The label is for the people who already agree with you. The regulator isn't one of them.

"Can the worker just agree to be a contractor?" In a limited sense, yes, and that's part of the trap. Both sides can sign a document that says "I am self-employed" and mean it. The tests ask what the facts of the working relationship look like, not what the parties agreed to call themselves. A signed declaration is helpful evidence but it isn't a shield. The reason this matters is that the worker often agrees, sometimes enthusiastically, because the contractor structure pays them more in the short term. That doesn't make the structure right.

"What happens if our US test and the California test disagree?" This isn't a hypothetical. A company can satisfy the IRS common-law test in full and still fail the ABC test under California AB5, and there's no way to reconcile the two by averaging. In practice, the stricter test governs, so if you've people working in California you run the ABC analysis first and let the answer dictate the structure. If you would fail ABC for someone, you don't get to call them a contractor anywhere in your US operation on the basis that they would pass the federal test.

"Does paying through an agency or umbrella company solve it?" It changes the paperwork. It doesn't change the underlying relationship. The UK has specifically legislated for the situation where an umbrella runs the payroll but the working pattern remains one of employment, and from 6 April 2026 agencies and end clients can become liable for PAYE underpayments even where the umbrella runs payroll. Agencies are a useful layer, not an answer.

"How long does the exposure last?" Long enough to worry about. Misclassification isn't an event with a clean ending. It runs through every pay cycle that happened under the wrong structure, and it runs through obligations you didn't know you had, such as back-tax, back-pensions, back-notice, and a working paper trail you now have to produce under pressure. The exposure gets heavier the longer the relationship runs in the wrong shape.

The Three Honest Categories the Options Split Into

Stay as a contractor, but earn it. You keep the label and the structure, and you change the working life so the facts match the label. The person sets their own hours. They use their own tools. They hold other clients. Their work is genuinely outside your usual course of business or sits in a defined piece that ends. This is the right answer for a defined project, a specialist brought in for a known problem, and a senior advisor whose trade is the work itself. It fails when the work has quietly turned into a permanent role and the documents haven't caught up. A tell: if the contractor has a desk, a laptop, a login, an all-hands invite, and a pattern of work that looks like a permanent role, the structure isn't earning itself, the documents are lying.

Convert to employee, and accept the cost. You make the person a hire, in the right jurisdiction, on the right terms, with the right statutory protections. You give up the flex of the contractor model and take on the obligations of an employer. This is right when the work is core, ongoing, and integrated, and when the cost of misclassification is higher than the cost of doing it properly. It fails when the work is genuinely project-based and the conversion is a paper move rather than an operating one. A tell: if you convert a person to employee and then keep them in the same project for the same period with the same pattern, you've moved the label, not changed the exposure. Real conversion changes the rhythm, the entitlements, and the way the role is described to the rest of the company.

Step outside the relationship, through a formal layer. You bring in a structure that sits between you and the worker, such as an employer of record, or you move the engagement to a separate company the worker owns. The EOR employs the worker through its own local entity and runs local payroll, statutory filings and employee-level obligations, which removes the need for you to incorporate. It substantially reduces but doesn't eliminate permanent establishment exposure, because activity beyond employing staff, such as concluding contracts locally, maintaining a fixed office or holding inventory, can still create one, and an EOR doesn't answer corporate tax. This route is right when the work genuinely sits outside your usual course and you want the operational lift taken off your plate. It fails when the working relationship is so deeply integrated that no formal layer can describe the reality, or when the formal layer is used to dress up a relationship the regulator would still see as employment. A tell: if the worker still attends your standup, on your equipment, with your processes, and the only thing that has changed is the name on the payslip, the layer is cosmetic.

Five Diagnostic Questions You Can Answer About Your Own Organisation

These aren't legal questions. They're observational questions, and the point of asking them is to find out what a regulator would see if it opened the same folder the people director opened earlier.

1. Who decides how, when and where the work is done? If you set the hours, the location, the tooling, and the workflow, the relationship is leaning employee. If the person decides these things and you only see the outcome, the relationship is leaning contractor. To answer it properly, pick one contractor on your bench and ask your line manager, not HR, how that person's week is structured. If the manager talks about standups, sprint planning and tickets, you've your answer.

2. Could the worker substitute another person to do the work? Genuine contractors can often send a colleague or subcontractor when they're unavailable. Employees, by definition, send themselves. If the worker is the only person who can do the job, and that's by design rather than accident, the relationship is leaning employee. To answer it, ask the worker directly whether they have ever sent a substitute and whether your contract permits it.

3. Does the worker have a visible trade outside your walls? Look at their website, their other clients, their marketing, their company. A genuine contractor has a footprint. A misclassified contractor has a name on a contract and not much else. To answer it, search for the person online and see whether the public story is consistent with someone running an independent business.

4. Is the work inside or outside the usual course of your business? A bakery hiring an accountant is straightforward. A bakery hiring a baker isn't. If the work is what your business does, the relationship is leaning employee. To answer it, write a one-sentence description of what your business does, then a one-sentence description of what the contractor does. If the two sentences rhyme, the work is integrated.

5. Does the relationship have a defined end, or does it drift? A genuine contractor engagement has a deliverable and a finish line. A misclassified contractor relationship has a start date and a sense that it will go on. To answer it, pull the latest contract and ask whether it has a clear end date tied to a piece of work. If the answer is "well, it sort of continues" you've found your risk.

The Tests, Compared

The IRS common-law test

The IRS weighs a body of factors together as a totality of the circumstances. No single factor is decisive. There's no presumption either way at the federal level. The factors cover behavioural control, financial control, and the type of relationship itself. The test earns a place because it's the US federal default and because it's the test most companies have heard of. Where it falls short is in producing a clean answer when the factors point in different directions, which is most of the time, and in leaving room for genuine disagreement between advisors. The test is the floor. It isn't the ceiling.

The California ABC test under AB5

AB5, codified at Labor Code sections 2775 to 2787, applies the ABC test to most California engagements. The test presumes a worker is an employee unless the hiring entity proves all three prongs: A, freedom from control in performance and in fact; B, work outside the usual course of the hiring entity's business; C, the worker is engaged in an independently established trade. Failing any one prong means employee. The test earns a place because it's the strictest in scope and because it's the test most likely to surprise companies that assumed the federal standard was enough. Where it falls short is in being almost impossible to satisfy for workers who are doing the work your business does, regardless of how the contract is structured. If your core business is the work the contractor does, the test answers itself.

The US Department of Labor economic realities rule

The department adopted a 2024 regulation setting out its own economic realities test. As of July 2026, however, the department isn't enforcing that rule and has proposed rescinding and replacing it. The test earns a place because it's the rule the federal wage-and-hour agencies would otherwise apply, and because the state of play changes what your compliance posture should look like right now. Where it falls short is that a rule you can't rely on, because the regulator has said it isn't enforcing it, is a hard rule to design your working practices around. Until the rule is settled, the safest course is to satisfy the more demanding standard you can find, which is the IRS common-law test in practice, while watching the federal rule for movement.

UK off-payroll working (IR35)

IR35 is the UK's framework for determining whether an off-payroll worker should be taxed as an employee. The test looks at substitution, control, mutuality of obligation, and the financial arrangements. The end-user is responsible for determining the worker's status where the end user meets the size threshold. From 6 April 2026 the turnover threshold rises from 10.2 million pounds to 15 million pounds, with the employee headcount threshold remaining at 50, so some companies leave the regime and responsibility for status determination moves back to the contractor. Separately, from 6 April 2026 agencies and end clients can become liable for PAYE underpayments where workers are supplied through umbrella companies, even where the umbrella runs the payroll. The test earns a place because it's the only one in scope with a hard cutover date and a hard size test. Where it falls short is in producing a status determination that's treated as definitive, and in leaving genuine room for disagreement between a contractor and an end client on what the working relationship looks like.

The EU Platform Work Directive presumption

The Platform Work Directive, 2024/2831, must be transposed by member states by 2 December 2026. It introduces a legal presumption of employment for platform workers in defined circumstances, shifting the burden of proof from the worker to the platform. It doesn't apply directly in the UK after Brexit, though a UK-based platform operating in EU member states must comply with how each member state implements it. The framework earns a place because it's the most recent structural shift in scope and because it sets a direction of travel for similar regimes outside the platform sector. Where it falls short is in applying narrowly to platform work and in being a presumption, not a determination, so a determined platform can still defend an independent relationship on the facts, but the burden of proof has moved.

The contract itself

The written agreement is the thing most companies reach for first and the thing the tests care about least. The contract earns a place on the list because it's the artefact in the file and the one a regulator will read first. Where it falls short is precisely there: a contract is a piece of evidence, not a determination. A working relationship that fails the tests on the facts won't be rescued by clauses that say "the parties agree this is a contractor relationship." The contract is for setting the working relationship up correctly. It isn't for papering over one that's set up wrongly.

The Decision Table

A Self-Audit You Can Run This Week

The point of the audit is to test the working relationship, not the contract. The order matters: don't read the contract first. The contract will colour what you see. Look at the working life first, then read the contract, then see whether the two match.

Pick five people from your contractor bench. For each, spend two hours observing the working pattern, not the paperwork. Watch a standup they're in. Look at the tools they use. Look at the calendar. Look at the invoice history. Then walk through the sequence below.

If the answers to most of these point at employee, the structure is wrong and the documents aren't the problem. The operating pattern is. Change the pattern, or change the structure. Don't change only the documents.

Contract Terms That Help, and Terms That Hurt

Some clauses support a genuine contractor relationship. Some quietly undermine it. The list below isn't a drafting guide, because drafting is for your lawyer. It's a way of seeing the contract as evidence.

The contract won't save a working relationship that fails the tests on the facts. But the contract can quietly pull a working relationship towards employee, even when the parties meant otherwise. If you see more rows in the right-hand column than the left, you've your answer.

The Cost of Getting This Wrong

The first cost is the one people plan for: back-tax, back-pensions, back-notice, the financial settlement. It's large. It's also the cost you can see. The costs you can't see are heavier.

The second cost is operational. The week the regulator opens the file is the week your senior people stop building product and start building a paper trail. Every contractor engagement becomes a project. Every line manager becomes a witness. Every calendar entry for the last three years becomes discoverable. The opportunity cost of the time your people lose during that period is rarely recorded anywhere, but it's the cost that hits hardest.

The third cost is reputational and personal. The head of people whose name is on the folder carries the conversation with the regulator, the board, and the affected workers. The workers themselves, many of whom preferred the contractor structure, are suddenly owed protections they didn't ask for, and the relationship with each of them has to be rebuilt under pressure. None of that's on the invoice.

So when you sit with the folder on a Tuesday morning, the question isn't whether the contracts are tidy. The question is whether the working life behind them would survive the phone call.

When You Are Ready to Go Further

If the self-audit gives you a clean answer, you can take it from here. If the self-audit gives you a muddled one, the next step is independent comparison rather than another vendor call. At HROpsLab, we are a review publication, not a vendor, and we sell nothing. Our job is to test the claims made by the people selling the solutions, and to publish what we find. When you're ready to compare employer-of-record providers, contractor management platforms, and the advisors who specialise in cross-border classification, we've done the work already, and the comparison is free to read.

The right next move depends on what your audit found. If the answer is "this is messier than I thought," the comparison work is the place to start, because the structure you pick has to fit the working life, not the other way round.

Frequently Asked Questions

HROpsLab helps you compare the people operations tools, advisors, and structures that real companies are using, so the next decision you make is informed by someone else's hard-won lesson, not just your own.