What Does a Legal Hold Mean for a Security Company?

What a legal hold means for a security guard company: what to preserve, spoliation risk, and a practical hold workflow. Get the operator's guide.

Yonah Nathan — Co-founder & Head of Product

Published July 12, 2026 Updated July 23, 2026 6 min read

I run a guard company with 400+ employees across four markets — Houston, Corpus Christi, Las Vegas, and Florida. In this business, the question is never if a claim will touch one of your sites. It's when, and whether your records will still exist by the time the demand letter arrives. This guide is how I think about legal holds as an operator, not a lawyer.

What is a legal hold in plain English?

A legal hold (also called a litigation hold) is a freeze order you place on your own records. When your company reasonably anticipates a lawsuit, claim, or government investigation, you must suspend any routine deletion — automatic purges, retention-schedule cleanups, employees clearing phones — for records that could be relevant.

Two things trip up guard company owners:

1. The trigger is anticipation, not filing. A slip-and-fall on a client site, an injury involving your officer, a termination that ends badly, or a preservation letter from an attorney can all start the clock. The duty commonly attaches months or years before a complaint is ever filed.
2. The duty covers electronic records. The federal courts made this explicit in the Zubulake v. UBS Warburg line of decisions, and Rule 37(e) of the Federal Rules of Civil Procedure now spells out sanctions for lost electronically stored information. GPS pings, checkpoint scans, and app-captured photos are all "records."

When do guard companies actually get legal holds?

In practice, three scenarios generate most litigation holds in contract security:

• Premises liability. Someone is assaulted, injured, or robbed at a property you guard, and the property owner gets sued for negligent security. Your patrol records become Exhibit A — for or against you. Personal injury statutes of limitation commonly run two to four years depending on the state, so the incident that matters may be one nobody remembers.
• Injury claims. Your own officer is hurt on post — a workers' comp dispute, an OSHA inquiry, or a third-party claim. Schedules, post orders, and training records get demanded.
• Employment disputes. Wage-and-hour claims, wrongful termination, discrimination. Clock-in data and shift schedules are the battleground; timekeeping records are exactly what plaintiffs' attorneys subpoena first.

If any of these lands on your desk, assume a hold obligation exists and act the same day.

What records must a security company preserve under a hold?

Cast the net wider than the incident itself. A defensible hold typically covers:

Preserve everything for the relevant site and time window — commonly the incident date plus a surrounding period — not just the single report.

Why is auto-deletion the biggest spoliation risk?

Spoliation is the destruction or loss of evidence you had a duty to preserve. Under Rule 37(e), consequences range from paying the other side's costs to an adverse-inference instruction — the judge telling the jury it may assume the missing records were bad for you. In a negligent-security case, "the guard company deleted the patrol logs" is close to a lost case.

The dangerous part: nobody has to decide to destroy anything. Deletion happens by default —

• Software that purges GPS data after 90 days or media after 12 months.
• Officers' personal phones holding the only copy of incident photos.
• A guard quits (industry turnover is commonly cited at 100%+ annually) and their device, texts, and photos walk out the door.
• Paper DARs in a site binder that gets tossed at contract end.

A hold means finding every one of those default deletion paths and shutting them off — provably.

What does a practical legal hold workflow look like?

1. Recognize the trigger. Train supervisors: serious injury, preservation letter, attorney contact, or agency inquiry → notify management the same day.
2. Issue a written hold notice. Identify the matter, the sites, the date range, and the record types. Send it to everyone who touches those records — and get acknowledgments.
3. Suspend auto-deletion for the covered scope in every system: guard management platform, email, dispatch, video storage.
4. Collect the fragile stuff first. Photos on personal phones, texts, paper logs — copy them to controlled storage before people or devices disappear.
5. Document everything. When the hold issued, who acknowledged, what was suspended. The record of the hold is your defense if something still slips.
6. Release the hold in writing when your attorney confirms the matter is closed, then resume your normal retention schedule.

How do platform-level holds beat manual ones?

A manual hold is a stack of emails and crossed fingers. It depends on every supervisor remembering, every officer complying, and every system's purge settings being found and changed. One missed checkbox is spoliation.

A platform-level hold flips the default. When your reports, photos and video, GPS clock-ins, checkpoint scans, and schedules already live in one system — captured from the field, timestamped, and centrally stored — preserving them is a scope decision, not a scavenger hunt. Because SNTNL runs Ranger Guard's daily operations, more than a year of records — 150+ GB of live operational data — sits in one place, exportable on demand; when counsel asks for a site's history, pulling it is a query, not an archaeology project. That's the difference between proving what your guards did and explaining why you can't. And because SNTNL includes free data export always, your records stay yours even if you leave.

If you'd rather have holds be a settings change than a fire drill, take a look at how we run it — book a demo and I'll show you how Ranger Guard's records are kept litigation-ready by default.

This is general information, not legal advice — verify current requirements with your attorney.