Ask the BattleTested Lawyer: Is My Contractor Actually an Employee?

Is my contractor actually an employee? A founder asked me this after his "1099 contractor" — who worked 40 hours a week, only for him, on his schedule, for two years — filed a claim. He'd called her a contractor. The law didn't care what he called her. After 20 years litigating, I can tell you that worker misclassification is one of the most expensive mistakes a growing business makes, precisely because it feels like paperwork until it becomes back taxes, penalties, and a lawsuit all at once. Here's how that conversation went.

Does it matter what we agreed to call the relationship?

Barely. This is the first thing founders get wrong: they think a signed agreement that says "independent contractor" settles the question. It doesn't. Whether someone is an employee or a contractor is determined by the actual substance of the working relationship, not the label on the contract. Agencies and courts look through the paperwork to how the work really happens. You can write "contractor" at the top of the page in bold, but if you treat the person like an employee day to day, the law treats them like an employee too — and now you have a document that contradicts reality, which is worse than having nothing. The contract is a starting point, not a shield.

So what actually decides it?

Control and independence — that's the heart of every test, even though the specific standards vary by agency and by state, and some states use notably strict versions. The core question is: whose business is this, and who controls how the work gets done? A genuine independent contractor runs their own business, sets their own hours, uses their own tools, works for multiple clients, can profit or lose based on how they manage the work, and decides how to accomplish the result you hired them for. An employee shows up when you say, does the work how you direct, uses your systems, and depends on you. The more control you exert over the how — not just the what — and the more the person is economically dependent on you alone, the more they look like an employee no matter what the contract says. Some states go further and essentially presume employee status unless you can prove the worker is truly independent.

What does getting it wrong actually cost?

Far more than people expect, because the liabilities stack from several directions at once. Misclassification can mean unpaid payroll taxes you should have withheld, the employer share you never paid, unpaid overtime and minimum-wage exposure, missed benefits, unemployment and workers'-comp gaps, and penalties layered on top — often reaching back across the entire period the person worked for you. And it doesn't take a government audit to trigger it; a single disgruntled worker filing for unemployment or overtime can open the whole thing up. This is why I call it a sleeper. It sits quietly while the business grows, and the longer it sits, the bigger the number gets when it finally wakes up.

How do I structure a real contractor relationship?

Make the independence real, not just recited. Give the contractor genuine control over how they do the work and when, within the bounds of the deliverable. Don't require them to work only for you, don't put them on your internal schedule as if they're staff, don't hand them a company email and a seat in the daily standup and then call them a vendor. Use a real independent-contractor agreement that reflects how the relationship actually operates — scope, deliverables, payment tied to work rather than hours clocked, their control over method, and clean IP-assignment terms so you actually own what they produce. The agreement matters, but it has to match reality. A contract describing independence you don't actually give them just documents your own violation.

What should I do if I think I've already misclassified someone?

Take it seriously now, while it's still cheap, because this only gets more expensive with time. Look honestly at your working relationships against the control-and-independence factors, not against the label you've been using. Where someone really functions as an employee, fix the classification going forward rather than hoping nobody notices. Where the relationship is genuinely independent, tighten the structure and the paperwork so it actually looks that way in practice. And get the agreements right for every contractor you bring on next — customized to how you truly work with them, not a generic template that describes a relationship you don't have. Partnerships and hiring are a legal danger zone for exactly this reason: the cheapest time to fix classification is before anyone has a reason to challenge it.

Bottom line

Calling someone a contractor doesn't make them one. The law looks at control and independence — who runs the business, who directs the work, and whether the person depends on you alone — and it reads through whatever label your contract uses. Get it wrong and you're exposed to back taxes, wage claims, and penalties reaching across the entire relationship, triggered by nothing more than one unhappy worker. Get it right by making the independence real and matching your paperwork to reality. The Contract Library has the independent-contractor agreements and IP-assignment terms to structure this properly — customized for you, not a generic template — each one built by a 20-year litigator and paired with training. Defense wins championships.

Frequently asked questions

Does a signed contractor agreement make someone a contractor?

No. Classification turns on the actual substance of the relationship — control and independence — not the label in the contract. An agreement helps only if it matches how the work truly operates.

What's the main factor in classification?

Control over how the work is done and the worker's economic independence. A true contractor runs their own business, sets their own methods, and typically serves multiple clients; an employee works under your direction and depends on you. Specific tests vary by agency and state, and some states are especially strict.

What are the risks of misclassifying a worker?

Back payroll taxes, unpaid overtime and wage exposure, missed benefits, unemployment and workers'-comp gaps, and penalties — often reaching across the full period of the relationship. A single worker complaint can trigger it.

Can I fix a misclassification I've already made?

Yes, and sooner is cheaper. Reassess each relationship against the real factors, correct the classification going forward where needed, and align your agreements with how the work actually happens. This is educational information, not legal advice for your specific situation.

Want to legally bulletproof your business, for free? Start with the free Legal Risk Report and find your blind spots in minutes.

About the Author — Karam Nahas, The BattleTested Lawyer. A 20-year courtroom veteran who has handled over $1 billion in deals and real litigation, Karam founded Legally Bulletproof to give entrepreneurs the same legal defense systems big companies use — without big-law prices.

Ready to lock it down? Visit the Contract Library — every contract comes with the training and a 20-year lawyer inside your business, starting as low as $197, and it's constantly updated and customized.

Educational content, not legal advice.