Employee or 1099? Why the Real Answer Is "It Depends"- Blog by Shanna Chambers & Brianna Capps

A two-person take on a topic that deserves one.

This month's post is a bit of a departure for us. Instead of one voice, you're getting two, because honestly, this topic earned it.

It started as a draft on employee versus independent contractor classification, and the more we talked it through together, the clearer it became that this isn't a subject that holds up to a single, tidy take. One of us lives in the day-to-day of client relationships — the calls where this question comes up in the middle of a real hiring decision, before it's had time to become a "situation." The other spends more time in the higher-level view, pulled in once something's gotten complicated enough to need a wider lens and the pattern across clients and industries that any one relationship on its own won't show you. Put those two vantage points together and you get a more complete answer, plus a few "wait, that actually happened?" stories along the way.

That's really the whole point of this post. Any resource that hands you a checklist for this — a list of absolutes, a "just don't do X" — is doing you a disservice. It's a judgment call built on a lot of moving pieces. So we sat down together, compared notes, and landed in the same place: this is more nuanced than it looks, and that's exactly what makes it worth getting right.

If you've Googled "employee vs. independent contractor," you've probably found a list of hard rules: don't set their hours, don't give them a company email, don't make them come to staff meetings. Check the boxes, you're safe. We wish it were that easy. 😬

Here's the problem: no such list actually holds up with the IRS, the Department of Labor, or a court. The test they use is the "economic reality" test — looking at everything together, does this person function like they run their own business, or like they're part of yours?

Start with the real distinction

An employee works for you. An independent contractor works with you. Easy peezy lemon squeezy — except we're not making a classic lemonade from a tried-and-true recipe here.

Employees are typically integrated into day-to-day operations — you direct how the work gets done, not just what it should look like when it's finished. Contractors bring their own expertise and are hired for an outcome; they control the "how." Nobody's telling a plumber which wrench to use.

That difference in control runs through everything below, but how much control is "too much" isn't a fixed line drawn in permanent marker. It shifts with the industry, the nature of the work, and — this one tends to raise eyebrows in client meetings — the political climate at the moment you're making the call.

Questions to weigh, not rules to follow

Think of these as signals rather than prohibitions. None of them alone makes someone an employee, but the more that stack up, the more the picture looks like employment — whatever the paperwork says.

• Their availability. Are you setting a deadline and letting them get there their way, or requiring specific hours? "Must be logged in by 8:00 sharp" does a lot of quiet talking.

• Equipment and process. Are you staying out of the "how," or handing them a laptop and a step-by-step SOP? Standing over their shoulder explaining exactly how you like it done is basically hiring an employee with extra steps.

• Other clients. Do they work with other businesses, or are you effectively their only income? Exclusivity isn't automatically disqualifying, but it's worth asking honestly why it exists.

• Integration into the team. Are they brought in only when their expertise is needed, or attending your trainings as a condition of the work — birthday cake in the break room and all?

• How they present externally. A company email, business cards, a uniform — none are deal-breakers alone, but they add up. Hard to argue "contractor" when the email signature says otherwise.

• Duration and repetition. Is this a defined project, or has "the project" quietly become "the job" for a couple of years running? Longevity alone doesn't reclassify someone, but it's often the piece that tips a close case — the house guest who's been "just staying a few days" since spring.

Most business owners want a rule they can rely on. We'd love one too. But pretending there's a solid line when there isn't is what actually gets businesses in trouble, and "I had a checklist" has never once worked as a defense.

Why there's no one-size-fits-all answer

The totality-of-circumstances approach means the same facts can land differently depending on:

• The nature of the work. A specialist brought in for a discrete project reads very differently than someone doing the same ongoing work as your employees, even if both technically "consult."
• The industry. What's normal in construction, creative freelance work, or healthcare staffing looks nothing like what's normal in a professional office. A film crew and a front desk don't play by the same unwritten rules.
• The regulatory and political climate. The legal standard itself doesn't sit still. Different administrations have taken meaningfully different positions on how employee- or business-friendly the Department of Labor's test should be, and enforcement priorities shift with them. A classification that was defensible under one administration's guidance can draw more scrutiny under the next — even though the actual working relationship never changed. Fun, right? 🤣

That's exactly why we don't hand clients a checklist and walk away. We weigh your industry, the role, how the relationship actually functions day to day, and the current enforcement environment, and help you land on the most defensible position for your situation — not a generic one from a quick search.

What's actually at stake

We're not saying this to be alarmist, just realistic: misclassification can mean back taxes, penalties, and interest; unpaid overtime; unpaid employer payroll taxes; and liability for benefits a worker should have received. Workers can also request an official determination from the IRS using Form SS-8 — yes, there's a form for this too — and that process doesn't usually favor the employer when the relationship looked like employment, regardless of what the contract said.

Your intent doesn't factor in, which feels unfair but is just how it works. Genuinely believing someone is a contractor, in good faith, with a signed agreement and a 1099 every January, doesn't change the analysis if the day-to-day tells a different story. You can label it a duck on paper, but if it's clocking in, taking direction on every task, and sitting through the same trainings as your employees, it's walking and quacking like an employee — and the law goes with the walk and the quack, not the label.

The bottom line

This isn't about memorizing a list of don'ts. It's about honestly looking at how a working relationship functions and weighing that against a standard that shifts with your industry, the role, and the regulatory climate. We know that's less satisfying than a checklist. We promise we're not just saying that to keep ourselves employed.

If you're thinking through a 1099 relationship and something about it feels a little gray, trust that instinct — that's usually the moment worth a quick conversation with an HR professional (😉 we happen to know a few). It's a lot easier to structure the relationship correctly from day one than to unwind it later, and considerably less fun to do it with an auditor in the room.