Ever find yourself in that gray area at work? You know, that space where it’s not totally clear who’s in charge? It happens all the time on job sites, especially when you bring in contractors or outside help. It’s usually fine… until it’s not.
When someone gets hurt, that blurry line of command suddenly becomes a huge, expensive problem. The big question becomes: who is legally the employer? And more importantly, whose workers’ compensation insurance has to pay the claim?
A recent North Carolina Supreme Court decision just drew a much clearer line in the sand on this very issue, and it’s something anyone in business or insurance needs to pay attention to. The case, Lassiter vs. Robeson County Sheriff’s Department, gives us a real-world lesson on what it truly means to be an employer in the eyes of the law.
Let’s break down what happened and, more importantly, what it means for you.
The Scene: A Roadside Accident and a Legal Showdown
Here’s the story. Stephen Lassiter, a deputy with the Robeson County Sheriff’s Office (RCSO), was working an approved off-duty gig. A highway contractor, Truesdell Corporation, was doing bridge repairs on I-95 and needed uniformed officers to direct traffic. Lassiter was one of those officers.
Tragically, he was seriously injured when a vehicle struck him on the worksite.
This is where things get complicated. Lassiter filed a workers' comp claim against both his primary employer, the Sheriff's Office, and the contractor, Truesdell. This kicked off a major dispute between the two organizations and their insurance carriers.
The core of the argument was about something called “joint employment.” Lassiter and the Sheriff’s Office argued that Truesdell was a joint employer, meaning both companies were on the hook for the workers’ comp claim.
Their reasoning seemed solid on the surface:
- Truesdell’s contract required them to have a traffic control plan.
- Truesdell determined where the officers were needed.
- Truesdell paid the officers directly for their off-duty hours.
From their perspective, this looked a lot like an employer-employee relationship. If you’re paying someone and telling them where to be, you’re their boss, right? Well, not so fast.
Truesdell’s Defense: We Hired the Expertise, Not the Employee
Truesdell and its insurer, The Phoenix Insurance Co., saw things very differently. They argued that they lacked the one thing that truly defines an employer: control.
Think of it like this. If you hire a professional plumber to fix a leak, you tell them which pipe is broken. You don't stand over their shoulder telling them which wrench to use or how to solder a joint. You’re hiring their expertise to achieve a result.
That was Truesdell’s argument. They said they simply outlined the goal—safe traffic flow around their construction site. But the how was left entirely to the Sheriff’s Office.
Here’s what they pointed out:
- RCSO supervisors managed all the staffing and scheduling.
- An RCSO supervisor assigned Lassiter to his specific post.
- RCSO supervisors were on-site, overseeing the officers.
- Lassiter was using his law enforcement training and judgment to direct traffic, not following a script from Truesdell.
Truesdell basically said, "We needed a job done, and we hired the experts at RCSO to manage it. We didn't direct the details of their police work."
The Supreme Court's Ruling: It’s All About the "How"
This disagreement worked its way up to the North Carolina Supreme Court, which had to make the final call. And their decision hinged on that one critical word: control.
The court didn’t just look at who wrote the paycheck or who set the general location. They drilled down to a much more fundamental question: Who had the right to control the manner and method of the work being performed?
In the court’s own words, the key test is whether the worker "passes under the [alleged employer]’s right of control with regard not only to the work to be done but also to the manner of performing it.”
When they applied that test, the answer was clear. Truesdell controlled the "what" (we need traffic control here), but the Sheriff's Office controlled the "how." RCSO leaders chose the officers, told them where to stand, managed their hours, and had the power to pull them off the job. Deputy Lassiter was acting as a law enforcement officer, using his professional skills—skills Truesdell’s team didn’t have.
Because Truesdell didn’t control the nitty-gritty details of how Lassiter did his job, the court said they couldn't be considered a joint employer.
The final verdict? The Robeson County Sheriff’s Department was Lassiter’s sole employer at the time of the accident. That means their insurer, Synergy Coverage Solutions, is the one solely responsible for the workers' compensation benefits.
What This Means for Businesses and Insurers
So, why does this legal battle matter to the rest of us? Because it provides some much-needed clarity on a really murky issue.
For any business that hires subcontractors, freelancers, or off-duty specialists, this case is a powerful reminder that control is the dividing line between being a client and being an employer.
If you simply define the outcome you want but leave the "how" to the experts you've hired, you're likely in the clear. But the more you start directing the specific methods, tools, and moment-to-moment activities of that person, the more you look like an employer in the eyes of the law—and the more likely your workers' comp policy could be on the line.
This ruling narrows the scope of joint employment in North Carolina, which is generally good news for general contractors and companies that rely on specialized outside help. It helps prevent them from being held liable for injuries to workers they don't directly supervise.
But it’s also a warning. You need to be very intentional in your contracts and on your job sites. Make sure it's crystal clear who is responsible for supervision and the "manner and method" of the work. Blurring those lines isn't just confusing—it can be an incredibly costly mistake when something goes wrong.
