Misclassification is decided on how the working relationship runs day to day, not on what the contract calls it.
You signed an agreement with an independent contractor. However, that agreement doesn't decide how they're classified - a tax authority or a court can look past it and rule they were an employee all along. What matters is how the work actually happens, not what is on paper. Set working hours, provided equipment, or exclusivity are just a few factors that can lead to reclassification and consequently backpay, penalties and legal trouble. This isn't rare or theoretical. It's one of the most common compliance issues companies run into once they start hiring contractors abroad, precisely because it's easy to drift into without anyone deciding to.
The checker below scores the nine factors that decide it.
There's no single global test. Every country has its own, and in the US, every state does
too. The US common-law test looks at three things: who controls the work, who bears the
financial risk, and what kind of relationship the two sides have. Some US states use a
stricter ABC test instead, which assumes employment unless the company can prove otherwise.
Europe and Latin America use their own statutory tests, built on similar ideas but with
different thresholds.
The same factors keep showing up everywhere: who controls the work, exclusivity, how
integrated someone is, and how they're paid. That's why one nine-factor check works as a
directional read no matter where you're hiring.
Misclassification is judged on how the working relationship actually runs day to day, not on what the contract calls it. Answer nine questions about one typical contractor and see where you stand.
With Contractor of Record, EliteBrains becomes the contracting party and takes on the employment-status exposure - you keep working with the same people, on compliant contracts, with timesheets and global payouts handled in one place.
If a contractor you work with gets reclassified, here's what you could owe:
This adds up fast. Misclassification is usually not about one person. It's a pattern in how a company treats its contractors. If you manage five contractors the same way, a review doesn't produce one claim. It produces five, each counted on its own. That's why our checker asks how many contractors you have.
Reviews don't happen at random. They're usually triggered by an event outside your control:
The contractor who quietly became full-time. Someone starts on a three-month project. It gets extended, then extended again. Eighteen months later, they're on every team call, have a company email, and work the same hours as everyone else. But they're still paid as a contractor, because no one ever decided to change that.
The offshore team managed like staff. A company hires contractors abroad to cut employment costs, then manages them exactly like employees: set hours, daily standups, a manager assigning and reviewing their work. The idea was to save money, but in practice the company ends up carrying the exact risk this checker is built to catch.
The contractor who's always available but never scoped. A contractor is paid a flat amount every month for a set number of hours, but with no clear scope for what those hours actually cover. Defining the hours isn't the same as defining the work - without project-based terms, it starts to look like a salary paid to someone who's just on call. That's one of the clearest red flags reviewers look for.
There are two ways to go about this: manage it yourself, or hand the exposure off to a Contractor of Record.
Managing it yourself. You can change how the engagement works: stop setting deadlines, let the contractor take other clients, pay per project instead of a fixed amount, and put real contract terms in place. This can't just be a paperwork change - the whole working relationship has to change with it. You can no longer treat them like part of the team: no more day-to-day control, standing meetings, or assigning tasks directly. The work has to get done through deliverables and outcomes, not direction. This can help, but it's fragile. One manager slipping back into old habits can undo it. It's not a one-time fix. It has to hold up every day, for every contractor, forever - and most companies aren't able to keep that up.
Handing it off to a Contractor of Record. With EliteBrains as the contracting party, the exposure sits with EliteBrains, not with you. Your team keeps working with the same people, the same way - but the contract, classification, and compliance are kept correct on EliteBrains's side, on an ongoing basis. Contracts, timesheets, and global payouts all run through the same platform, so nothing about the day-to-day relationship has to change for the risk to go away.
No, not on its own. A written agreement matters, but every test used to determine employment status looks past what the contract says and examines how the relationship actually works day to day.
Yes. Their country's rules apply, not yours. In the US, it's their state's rules. Hiring abroad can also affect visa status, local taxes, and social security in that country.
There's no set limit, but the longer it goes on, the riskier it looks. Passing the one-year mark is a common warning sign in many countries.
Mainly you, the hiring company. These rules exist to protect the contractor, so the costs and consequences usually land on whoever hired them.
The form doesn't decide anything. It just reflects how you're already paying someone. If the work itself looks like a job, sending a 1099 instead of a W-2 won't protect you.
It's an older checklist the IRS used to use, looking at things like control, risk, and the type of relationship. Today the IRS uses a simpler version with three main categories, but the old list is still a handy way to spot risk.
Some US states, like California, New Jersey, and Massachusetts, use a tougher rule. They assume someone is an employee unless the company can prove all three specific conditions, including that the work isn't part of the company's normal business.
Auditors usually ask for records showing how the work really ran: schedules, messages, equipment, whether the person worked for anyone else. If someone gets reclassified, you may owe back taxes, missed benefits, and penalties, sometimes for several years back.
Yes, and it's often the simplest fix for a long or risky engagement. It stops the risk going forward, but it doesn't erase any liability from the time they were misclassified.
Not on its own. If you're still controlling the day-to-day work, the platform doesn't take on the legal risk, unless it's set up as a real Contractor of Record or Employer of Record.