Running a security guard company means operating in a constant state of flux. Headcounts shift when you win or lose a client contract. Guards rotate across sites. Licensing requirements vary by state, and in some cases by county. Workers’ comp classifications are complicated by whether your guards are armed, unarmed, mobile, or stationary. It’s a demanding operational environment, and most PEO contracts are not designed for it.
That’s the core problem. PEO agreements are written by PEO legal teams, and their primary purpose is to protect the PEO. For most industries, the standard boilerplate is manageable. For security companies, it can be genuinely costly. The clauses that create the most exposure aren’t the obvious ones — they’re buried in workers’ comp provisions, rate adjustment language, licensing definitions, and termination terms that look routine until something goes wrong.
This article isn’t a primer on what a PEO is or how co-employment works in general. If you need that foundation, it’s worth reviewing a broader PEO service agreement guide first. What follows is specific: the contract provisions that carry real operational and financial risk for security guard operators, and what to look for before you sign.
Why Security Guard Operations Break Standard PEO Contracts
Most PEO contracts are built around a relatively stable employment model — consistent headcount, predictable payroll, and workers in standard occupational classifications. Security guard companies don’t fit that mold, and the mismatch shows up in three specific ways.
The first is workers’ comp classification. Security work typically falls under high-risk class codes, with the specific code depending on the nature of the work. Armed guards, unarmed guards, mobile patrol, and static post assignments can all carry different classifications, and the premium rates attached to those codes vary significantly. The problem is that many PEO contracts use vague language around risk classification, grouping all security personnel into a single bucket or defaulting to a worst-case code. If the contract doesn’t explicitly address how your specific guard types will be classified, you may end up rated on assumptions that don’t reflect your actual workforce.
The armed versus unarmed distinction deserves particular attention. These aren’t just operational categories — they represent real underwriting differences that affect coverage scope and premium calculation. A contract that doesn’t explicitly define which guard types fall within the scope of services is a contract that leaves room for coverage disputes. If an armed guard files a claim and the PEO’s underwriter argues that armed personnel weren’t contemplated in the original risk profile, you have a problem. Get the scope of services language specific.
The second issue is variable headcount. Security companies win and lose client contracts regularly. A single large contract loss can drop your headcount by thirty or forty people overnight. Many PEO contracts include minimum billing guarantees or minimum employee thresholds — meaning you owe fees based on a floor, not your actual count. If your contract has a minimum of fifty employees and you drop to thirty-five, you’re paying for fifteen people who don’t exist. In an industry where headcount fluctuates as a normal course of business, this clause can quietly drain margin during slow periods.
The third structural problem is that security operations often span multiple states, which compounds every other complexity in the contract. Governing law clauses, workers’ comp coverage territory, and licensing obligations all behave differently across state lines. A contract written with a single-state operator in mind may have serious gaps for a company running sites in four or five states simultaneously. Understanding how common PEO contract loopholes apply to multi-state operations is essential before you commit to any agreement.
Workers’ Comp Provisions That Carry Real Weight in Security
Workers’ compensation is where most of the financial risk lives in a security PEO contract, and the provisions that matter most are often the ones operators spend the least time reading.
The first question to answer is whether the PEO is offering coverage under a master policy or a dedicated policy. A master policy pools your workers’ comp risk with other PEO clients. That can work in your favor if your loss history is clean and you benefit from the pool’s overall experience. It can work against you if other clients in the pool have poor loss histories that inflate the rate you’re effectively paying. More importantly, in a pooled arrangement, your individual claims experience may not be tracked in a way that carries forward cleanly if you leave the PEO. A dedicated policy keeps your experience separate, which matters if you’ve built a good loss history and want that to follow you.
The experience modification factor — your e-mod — is a direct multiplier on your workers’ comp premium. Some PEO contracts include language that effectively shields your e-mod from developing during the contract period, because the claims are reported under the PEO’s FEIN rather than yours. When you leave, you may find yourself starting fresh with no established e-mod, which defaults to 1.0. That’s not necessarily bad, but it’s not necessarily good either, depending on what your history would have looked like. The contract should be explicit about how your loss history is tracked and what data you’re entitled to take with you when the relationship ends.
Claims management authority is a clause that frequently gets overlooked. Who has the right to make decisions about how a workers’ comp claim is handled — including whether to settle? Some PEO contracts give the PEO or its carrier broad unilateral authority to settle claims, even over the client’s objection. In a high-claim-frequency industry like security, that matters. A claim that gets settled without your input can affect your loss runs, your e-mod trajectory, and your ability to argue for better rates when you renew or switch providers. If the contract gives the PEO full settlement authority, push back on that language or at minimum get a notification requirement added.
One more provision to locate: how claims that occur during the contract period are handled after you leave. This is the tail coverage question, and it’s addressed in more detail in the termination section below. But it starts here, in the workers’ comp provisions, where the contract defines whose policy covers what and for how long. Security operators should also review the PEO contract liability risks that most commonly surface in high-incident industries before finalizing any workers’ comp terms.
Licensing, Compliance, and the Co-Employment Gray Area
Co-employment creates a genuine legal complication for security companies that doesn’t exist in most other industries: the question of who is the licensed employer.
In most states, private security contractors must hold a state-issued license to operate, and individual guards must hold their own licenses as well. The licensing requirement typically attaches to the employer — the entity that employs the guards. Under a co-employment arrangement, both the PEO and the client company share employer status in some legal sense. But many state security regulatory agencies don’t recognize that shared structure. They want a single licensed employer of record, and they expect that entity to be the company with the security contractor license — not the PEO.
The contract must be explicit about who holds employer-of-record status for licensing purposes. If the PEO’s standard agreement positions them as the employer of record across the board, you may have a conflict with your state’s licensing requirements. This isn’t theoretical — it’s the kind of gap that surfaces during a state audit or a licensing renewal and creates real operational disruption. Reviewing how the best PEOs for security companies handle enterprise compliance can help you benchmark what good contract language looks like in this area.
Multi-state operators face this problem multiplied. Each state has its own private security regulatory framework, and they don’t all treat co-employment the same way. Some states are more permissive about how employer-of-record status is defined for licensing purposes; others are strict. A PEO contract that defaults to a single governing state’s law and doesn’t address the regulatory requirements of the other states where you operate is leaving compliance gaps that you’ll be responsible for filling.
Background check and drug screening obligations are another area where the contract needs to be specific. State security licensing boards frequently mandate pre-employment background checks and ongoing drug testing. The contract should define who owns that compliance obligation — the PEO or the client — and what the process is when a guard fails a check mid-assignment. If a guard is on-site and fails a random drug test, who terminates the assignment? Who handles the documentation? Who is liable if the guard was working in a state with specific requirements that weren’t met? Vague contract language on this creates operational risk that lands on you.
Pricing Structure and the Costs That Don’t Show Up in the Pitch
The pricing structure in a security PEO contract is rarely as simple as the sales presentation makes it look. There are a few specific mechanisms worth understanding before you sign.
Workers’ comp premium markups are common in PEO pricing for high-risk industries. The PEO typically charges a percentage of payroll that includes their markup on the underlying workers’ comp cost. The way this is expressed in the contract matters: a flat rate per employee per month behaves differently than a percentage of payroll when overtime is involved. Security companies run heavy overtime — guards covering shifts, filling in for callouts, working extended hours at special events. If your pricing is expressed as a percentage of gross payroll, your effective cost per hour of overtime is higher than it looks in the base rate. Run the math on your actual overtime exposure before you sign.
Annual rate adjustment clauses tied to loss ratios are a significant risk for security operators. Some contracts allow the PEO to reprice mid-term or at renewal based on your claims experience. If your loss ratio worsens — which can happen quickly in security after a single serious incident — the PEO can increase your rates. The contract may frame this as a standard adjustment mechanism, but the practical effect is that your cost assumption for the contract year can change after you’ve already committed. Look for whether the contract specifies a cap on mid-term adjustments, and what triggers them. Conducting financial due diligence on PEO contracts before signing is the most reliable way to surface these hidden repricing risks.
Minimum premium guarantees and minimum employee counts are worth locating in the contract before you’re surprised by them. These provisions require you to pay as if you have a certain number of employees or a certain payroll level, regardless of your actual figures. For a security company that loses a major client contract and drops headcount by twenty-five percent, the minimum guarantee means you’re paying for a workforce size you no longer have. Understand what your floor obligation is, and model what it costs you in a downside scenario.
Administrative fee structures can also have layered components — base admin fees, per-employee charges, technology fees, and compliance fees that aren’t always itemized clearly in the contract. Ask for a full fee schedule as an exhibit to the contract, not just a summary in the proposal.
Exit Terms, Termination, and What Happens to Open Claims
How a PEO contract ends is just as important as how it begins, and this is an area where security operators consistently underestimate their exposure.
Termination notice periods in security PEO contracts typically run sixty to ninety days. That’s a meaningful lead time when you’re trying to transition to a new provider or bring coverage in-house, and it affects your planning timeline. But the notice period itself isn’t the most important exit provision. The more consequential question is what happens to workers’ comp claims that were filed during the contract period but are still open when you leave.
Workers’ comp claims in security don’t always resolve quickly. Injuries involving cumulative trauma, hearing loss from prolonged exposure, or stress-related conditions can have long development periods. A claim filed six months before you exit the PEO may still be active two years after you’ve moved on. The contract needs to define who is responsible for those open claims — specifically, whether the PEO’s policy continues to cover them (and at what cost to you) or whether you’re expected to pick up tail coverage through another mechanism.
Some PEO contracts include runoff liability provisions that allow the PEO to bill you for claims that develop or worsen after the contract ends. This clause is often buried in the termination section and is easy to miss in a first read. In a high-claim-frequency industry like security, the financial exposure here can be substantial. If the contract includes runoff liability language, understand the scope of it — is it capped? Does it have a time limit? What triggers it?
Transition assistance language is the other exit provision that matters operationally. When you leave a PEO, you need loss run reports, payroll data exports, benefits enrollment records, and HR documentation. If the contract doesn’t specify what the PEO is obligated to provide, on what timeline, and in what format, you may find yourself negotiating for your own data while trying to stand up a new provider. A practical PEO transition guide can help you understand what a well-structured handoff should look like. Get transition deliverables defined in the contract as a specific obligation, not a courtesy.
What’s Actually Worth Negotiating Before You Sign
Most security operators assume PEO contracts are take-it-or-leave-it. They’re not. PEOs want your business, especially if you’re bringing a meaningful payroll, and there’s more room to negotiate than the standard pitch implies. Following a structured PEO contract negotiation process gives you a framework for identifying which terms have real flexibility and which are genuinely fixed.
Rate lock provisions: Push for a defined period — typically twelve months — during which workers’ comp rates and administrative fees cannot increase. If the PEO insists on including an adjustment mechanism, negotiate for a defined cap on any mid-term change and a clear trigger definition. “Loss ratio deterioration” is too vague; get specific thresholds in writing.
Dedicated loss control services: Security is a high-incident industry, and generic online safety portals don’t move the needle on claims frequency. Negotiate for named loss control support — a specific person or team assigned to your account, with defined service commitments. If the PEO can’t offer this, that tells you something about how they’re pricing your risk and how much attention your account will actually get.
Claims management notification rights: Even if you can’t negotiate full joint authority over claim settlements, push for a notification requirement before the PEO or its carrier settles any claim above a defined threshold. This gives you visibility into decisions that affect your loss runs.
Carve-out rights for alternative risk structures: Larger security operators sometimes benefit from captive insurance arrangements or self-insured retention structures. If your operation is growing toward that scale, make sure the contract doesn’t prohibit or penalize participation in those structures. A contract that locks you into the PEO’s workers’ comp arrangement indefinitely limits your options as your risk profile matures.
The Bottom Line Before You Sign
Security guard operators who treat a PEO contract as administrative paperwork tend to find out where the gaps are at the worst possible moment — when a major claim hits, when headcount drops after a contract loss, or when they try to exit and discover they’re on the hook for runoff costs they didn’t know existed.
The provisions covered here aren’t edge cases. They’re the standard contract terms that have direct financial and operational consequences specific to this industry. Workers’ comp classification language, claims management authority, minimum guarantees, licensing definitions, and exit terms all behave differently in security than they do in most other industries. A contract that works fine for a staffing company or a professional services firm may create real exposure for a security operation.
The best way to evaluate these provisions isn’t to review one PEO’s contract in isolation. It’s to compare how multiple providers structure the same terms side by side. Different PEOs take meaningfully different approaches to risk classification, pricing mechanisms, and exit obligations, and those differences aren’t visible until you look at them together.
Don’t auto-renew. Make an informed, confident decision. PEO Metrics provides side-by-side comparisons of PEO providers on the contract terms and pricing structures that matter most for security operations — so you can evaluate your options with real data before you commit.
Before you sign that PEO renewal, make sure you’re not leaving money on the table.
Many businesses unknowingly overpay because of bundled fees, hidden administrative markups, and contracts designed to limit flexibility. We give you a clear, side-by-side breakdown of pricing, services, and contract terms—so you can see exactly what you’re paying for and choose the option that truly fits your business.
