A shoplifter bolts for the parking lot. The officer on post gives chase, tackles him at the curb, and holds him down until police arrive. Everyone on the property manager’s side calls it a win — right up until the arrestee’s attorney points out that the takedown happened well past the point where the officer had any legal basis to detain, force was used beyond what the situation required, and now the property owner and the guard company are named in a civil suit. This scenario plays out somewhere in the country on a fairly regular basis, and it almost always traces back to the same root cause: the officer believed the uniform gave them police-like arrest authority. It doesn’t — what actually governs the stop are citizen’s arrest laws for security guards by state, and most officers have never been told that plainly.
In nearly every state, a private security officer’s power to detain someone rests on the same citizen’s-arrest framework available to any private person — not on a separate, elevated authority that comes with the job. Wearing a uniform, carrying a radio, or having “security” printed on a shirt changes nothing about the underlying legal basis for a detention. What changes, state by state, is exactly what a private citizen is permitted to do: under what circumstances a detention is legally justified, how much force is proportionate, how long someone can be held, and what happens if the person turns out not to have committed the offense the officer suspected. Those rules vary significantly across states, they get revised, and getting the details wrong here is not a paperwork mistake — it’s the kind of error that turns into a personal-injury or false-imprisonment claim against both the officer and the company.
Nothing here is legal advice, and nothing here should be read as a summary of any specific state’s statute. The point of this post is the gap itself — what officers assume versus what the law actually authorizes — not a citation of what any particular state permits. Confirm the current rules for every state you operate in with counsel licensed in that state, and build your training around that guidance, not around industry folklore passed down from a previous employer.
Where the gap actually shows up
The failure mode is rarely a guard who doesn’t know the law exists. It’s a guard who’s confident they know it, based on what a prior supervisor told them, or what felt reasonable in the moment. Three patterns account for most of the incidents that turn into claims:
Detaining based on suspicion alone, not observed conduct. Citizen’s-arrest frameworks typically require some direct basis — witnessing the act, or a comparably solid ground — not a hunch that someone “looks like” they’re shoplifting or “seems off.” An officer who stops someone purely on a gut read, and turns out to be wrong, has exposed the company to a claim with essentially no defense.
Using force disproportionate to the situation. Even where a detention itself is legally justified, the force used to accomplish it has its own separate standard, and that standard doesn’t scale up just because the person is resisting or the officer is frustrated. A shove to prevent someone from leaving is a different legal event than a takedown, and the line between them is exactly where most excessive-force claims against contract guards originate.
Holding someone too long, or in the wrong way, while waiting for police. A citizen’s arrest generally contemplates a short detention for the purpose of turning the person over to law enforcement — not an extended hold, and not conditions that could themselves be characterized as false imprisonment. An officer who locks a detainee in a back office for forty-five minutes because dispatch is slow to answer has created a second problem independent of whatever the original stop was about.
Building the guardrails into training and post orders
The fix isn’t a poster in the break room — it’s making the boundary explicit in post orders for any site where detention is even a plausible scenario, retail and similar accounts especially, and reinforcing it during onboarding rather than assuming common sense covers it. Post orders should state plainly what an officer is and isn’t authorized to do on that specific site, because “observe and report” is a legitimate, defensible posture for a huge share of accounts, and a company should be explicit about which sites actually call for anything beyond it.
When a detention does happen, what protects the company afterward is the same thing that protects the officer: a complete, contemporaneous incident report — what was observed, what was said, exactly when the detention started and ended, and what force, if any, was used. An account written from memory two days later, after the company already has a demand letter in hand, is worth far less than one logged with photos and a timestamp while the details are still fresh. That record is often the difference between a claim that gets dismissed early and one that drags on because nobody can establish what actually happened on the ground.
Citizen’s arrest laws for security guards by state: why they vary so much
A company running sites in one state has one set of rules to train against, which is hard enough. A company operating across several states is training officers on a legal framework that changes depending on which property they’re posted at that week — and a supervisor who transfers an officer from one state’s account to another’s without re-briefing them on that state’s specific limits has created a real liability exposure, not a theoretical one. This is a place where a generic, one-size-fits-all training module actually creates risk rather than reducing it, because it teaches officers a false sense of a single national standard that doesn’t exist.
The operational answer is to tie post orders and onboarding checklists to the specific site and state, not to a company-wide template that gets copy-pasted across every account. An officer picking up a shift at an unfamiliar site should have access to that site’s specific post orders before they’re posted there, not a generalized handbook they read once during initial hiring months earlier. That’s a workflow problem as much as a legal one — the right information needs to reach the officer at the moment they need it, not sit in a binder in a back office they’ve never seen.
What a supervisor should actually check after any detention
However clear the post orders were beforehand, a detention that happens is a moment for a field supervisor to actively verify what occurred, not just file whatever the officer submits. That means confirming the report was completed the same shift, checking that it describes specific observed conduct rather than a conclusion (“he was stealing”), and following up directly with the officer if the account is vague about force used or duration. A supervisor who treats incident reports as a formality to collect, rather than a record to actually read and question, misses exactly the pattern that would flag an officer operating outside the boundaries the law actually allows.
Review your citizen’s-arrest exposure state by state with counsel, build it into post orders and onboarding rather than leaving it to instinct, and make sure every detention — however minor — gets documented the same day. If you want a closer look at how documentation like this fits your operation, explore CGuardPro or get in touch.