complianceworkforcepayroll

Employee vs. Independent Contractor in the Guard Industry

CGuardPro

The pitch is always the same, and it always arrives at the same moment. Margins are thin, a new account needs bodies next week, and someone suggests running the officers as 1099 contractors. No payroll taxes, no workers’ compensation premium, no overtime, no unemployment. Just a rate and an invoice. Employee vs contractor security guards looks, on a spreadsheet, like the easiest cost reduction in the business.

It is also, in most guard operations, the least defensible one. Not because contractor relationships are illegitimate — they are, in the right circumstances — but because almost everything that makes a security company a security company is evidence of an employment relationship. The uniform, the post orders, the schedule, the supervision, the required training, the equipment, the standards of conduct. Every one of those is a control you cannot give up without ceasing to deliver the service you sold.

This post is general orientation, not legal, tax or payroll advice. Worker classification is assessed differently by different authorities — the federal wage and hour agency, the tax authority, state unemployment and workers’ compensation agencies, and the courts — and the tests they apply vary, have changed over time, and continue to change. Some states apply notably stricter standards than the federal baseline. State security licensing rules may also speak to whether officers must be employees of the licensed company. Verify with employment counsel, your payroll advisor and your state regulator before making any classification decision; in Texas, the Texas Department of Licensing and Regulation (TDLR) is the licensing authority to raise the security-specific question with.

Why the answer is usually “employee”

Different agencies use different frameworks, but they tend to circle the same underlying question: how much control does the hiring party exercise over how the work is done, and to what degree is the worker genuinely running an independent business rather than depending economically on this one relationship?

Walk that against a contract security post.

You set the schedule. Not “we need coverage sometime this week” but a specific post, at a specific site, from 1800 to 0600, on named days. The officer cannot decide to show up at 2000 instead. Coverage is the product.

You dictate the method. Post orders are, by definition, detailed instructions on how to perform the work: what to check, when to check it, what to write down, who to call, what to say, what not to do. That is the opposite of engaging an independent professional for a result and leaving the method to them.

You supply the identity. Your uniform, your patch, your badge, your vehicle, often your radio and your phone. The client believes they are receiving your company’s service, because that is what you sold them.

You supervise. Field supervisors conduct site checks. Dispatch monitors check-ins. Somebody reviews the DAR. Somebody counsels an officer whose appearance slipped.

You require training. Orientation, use of force, report writing, site-specific instruction, and whatever the client mandates.

The relationship is continuous and exclusive in practice. An officer working four twelves a week at your account is not simultaneously operating a business serving multiple clients. They are economically dependent on you, which is precisely what most frameworks look at.

There is no realistic opportunity for profit or loss. A genuine contractor can make more by working more efficiently, or lose money by mismanaging a job. An officer paid hourly to stand a post cannot. Their earnings vary only with hours, which is a wage.

Any one of these might be survivable. All of them together describe employment in almost any framework anyone applies.

Officer profile screen in the guard mobile app showing personal details and current assignment

The labels that do not help

Owners consistently overestimate the protective value of paperwork. A few things that carry far less weight than people expect:

A signed agreement calling the worker a contractor. Classification is assessed on the substance of the relationship. Parties cannot contract out of a worker protection regime by agreeing on a label.

Issuing a 1099 instead of a W-2. That is a consequence of the classification, not a determinant of it.

The worker preferring it. Common, understandable, and irrelevant. The protections at issue are not the worker’s to waive by preference, and the same worker will file for unemployment or a workers’ compensation claim when circumstances change — which is one of the most common ways misclassification comes to light.

The worker having an LLC. Helpful evidence of independence, but not dispositive on its own if the actual working relationship looks like employment.

“Everyone in our market does it.” Industry practice is not a defense, and enforcement in low-wage, high-turnover sectors tends to arrive in waves.

Where the exposure actually lands

The reason to take this seriously is that the consequences are not a single fine from a single agency. Misclassification tends to unravel across several fronts at once, often triggered by a single event.

An injured officer with no workers’ compensation coverage behind them is the classic trigger. They seek treatment, someone asks who the employer is, and the question reaches a state agency. A separated officer filing for unemployment is another; the agency contacts you, and its own classification determination follows. Once one agency has made a finding, others tend to follow, and findings for one worker tend to be applied across everyone in the same role.

The exposure typically includes back taxes and withholding, unpaid overtime and the remedies that attach to wage claims, unemployment contributions, workers’ compensation premium and potentially direct liability for the injury itself, plus penalties and interest. Because it applies across a class of workers over a look-back period rather than to one person, the number scales with your headcount and your history.

There is a second exposure specific to our industry that owners often miss entirely. Your insurance is written on the basis of your stated operations and payroll. Your client contract almost certainly represents that officers assigned to the site are your employees, properly screened, trained, supervised and covered. A classification finding can put you in breach of that representation and can complicate coverage at the worst possible moment. And your state security license may itself assume an employment relationship between the licensed company and the registered officers.

The narrow cases that can work

There are legitimate contractor relationships adjacent to guard work. A consultant who performs a security assessment and delivers a report. A trainer engaged to run a specific course. An installer who mounts hardware. A firm engaged as a subcontractor — which is a company-to-company relationship with its own licensing, insurance and employees, and is a fundamentally different arrangement from putting an individual on a 1099.

What these share is the shape of genuine independence: a defined deliverable rather than ongoing hours, the contractor’s own method, their own tools, their own workers, real exposure to profit and loss, and other clients. If you find yourself writing post orders for someone, you have left that territory.

Officer schedule screen in the guard mobile app showing assigned shifts across the week

The real problem underneath

Almost every owner who seriously considers 1099 officers is trying to solve one of two problems: overtime cost on a coverage model that generates it structurally, or the administrative weight of onboarding and paying a workforce that turns over quickly.

Both have legitimate solutions. The overtime problem is a scheduling design problem — rotations built without visibility into the hours they generate, and callouts concentrated on the same handful of reliable officers. Making projected hours visible while the schedule is being built, and spreading open shifts across a wider pool, addresses the cost at its source rather than by reclassifying the people working it.

The administrative problem is a systems problem. If onboarding an officer, tracking their credentials, capturing their hours and paying them correctly takes hours of manual work per person, high turnover becomes unaffordable. Accurate time and attendance that captures the real in and out at the post, feeding a single officer record, removes most of that weight without touching classification at all.

Neither solution is as fast as changing a form. Both are still available to you in five years, which is the relevant comparison.

Get the classification question answered by counsel for your specific operation, in writing, before you need the answer. Then go fix the schedule.

If you want to see how scheduling and time records reduce the administrative load of a real guard force, explore CGuardPro or get in touch.

Run the whole operation in one place

Shifts, attendance, patrols, incident logs and clients on one platform — with the guard app on site and the client portal on the other side.

  • Attendance with selfie and GPS
  • QR patrols and a digital logbook
  • Client portal included

Keep reading