CITYSAFE PODCAST
The CitySafe Podcast explores how retailers, loss prevention teams, and the people responsible for safety navigate theft, incidents, and risk in environments where what you know, and what you do about it, can carry real legal weight.
Co-hosted by Jim Cords, retired from the federal side, whose career spanned the FBI, DHS, and OIG, and Don Carr, who has owned and operated private security guard companies and architected security systems, the CitySafe Podcast focuses on the space between detection and response, where so much of retail security actually plays out.
The CitySafe Podcast reflects the personal views and opinions of its hosts and is a conversation, not professional advice. Rather than offering tactics or prescriptions, it examines how knowledge, duty, documentation, and the choice to act are understood differently across retail environments, and why the same approach does not protect every operator the same way. Listeners should consult their own qualified professionals on questions of legal liability, operational risk, security, and compliance specific to their circumstances and jurisdictions.
Available on Apple Podcasts, Spotify, and YouTube Music.
CITYSAFE PODCAST
Ep. 29: Whose Liability Is It? · Guard Contracts, Indemnification, and Risk Transfer
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
You hired a guard company to transfer the risk — so when a security incident becomes a lawsuit, that's their problem now. Right? In "Whose Liability Is It?", Don Carr and Jim Cords break down why hiring a contractor delegates the task but doesn't automatically move the liability — and why an injured party can still come after the retailer directly. The decider is one clause most operators never read: indemnification. Which direction does yours run? Does it have the guard company covering you, or did you quietly agree to cover them? Why indemnification is only as good as the insurance behind it, why the contractor's standard form is drafted to protect the contractor, and why the org boundary is exactly where duty changes hands — or doesn't. Read the clause before you sign it, not after the lawsuit.
Loss. Liability. Law.
This is the City Safe Podcast, a conversation at the intersection of community safety, technology, and leadership, co-hosted by Don Carr and Jim Kortz. Together, we examine the critical issues facing cities today and the smarter tools that can help reduce crime and protect our communities. From instant communication systems to emerging technology, we break down what works, what doesn't, and what's next for urban safety. Because in today's world, keeping people safe requires more than good intentions. It requires innovation, data, and decisive action. Listen to the City Safe Podcast, available now on Spotify, Apple Podcasts, and YouTube Music. Subscribe today and join the mission to make cities safer for everyone.
SPEAKER_00Welcome back to another episode of the City Safe Podcast. This is episode 29. Whose liability is it? Guard contracts, indemnification, and risk transfer. I'm your co-host, Don Carr. And I'm your co-host, Jim Kords.
SPEAKER_02Alright, so let's start by saying you hire a guard company. And part of why you hire this company, maybe the biggest part, is so the risk isn't all of yours anymore. Something goes wrong on the security side, that's their problem now. That's what you're paying for. You handed off that duty, right? So something goes wrong. There's an incident. Maybe a guard uses too much force or misses something they should have caught, and now there's a lawsuit. And the retailer's reaction is the natural one. Call the guard company. This is on you.
SPEAKER_00And then they actually read the contract. The contract they signed two years ago and never looked at again. And buried in it is one clause. A couple of sentences of dense language nobody parsed at signing. And that clause decides who pays. Sometimes it's the guard company, exactly like the retailer assumed. And sometimes that clause says the retailer is the one holding the bag for the guard's mistake.
SPEAKER_02You thought you transferred the risk, but the contract is where you find out if you actually did.
SPEAKER_00So, Jim, let's start by killing the assumption because the whole episode depends on it being wrong. The retailer thinks I hired an outside company. They're a separate business, their guard, their mistake, their liability. So why isn't that just true?
SPEAKER_02Because the law often doesn't let you off the hook that cleanly when the harm happens on your premises and your operation for your benefit. There's a set of doctrines here, and I won't drown anyone in Latin, but the gist is a property owner or business can be held liable for security failures on its premises, even when it used a contractor. The injured party can frequently come after the retailer directly, regardless of who the guard worked for.
SPEAKER_00So from the victim side, is it fair to say they don't care about your org chart?
SPEAKER_02Yeah, not even a little bit. Someone hurt in your store by a security failure sues whose ever's in reach, right? And that and that very much includes the business that owns the premises and invited them in. We covered that duty to invitees about two episodes ago, and it doesn't evaporate just because you outsource the guarding. You can't always delegate the duty away by hiring a contractor. The duty can stay with you even when the work doesn't.
SPEAKER_00And that's the structural point I want to underline. There's a difference between delegating the task and transferring the liability. You can hand off the task. The guard company does the guarding. That's easy. But whether the legal liability moves with it is a completely separate question. And it doesn't move automatically. It only moves if you deliberately move it in the contract.
SPEAKER_02And if the contract doesn't do it or does it badly, the duty just stays with you. You delegated the work and kept the risk without even realizing it.
SPEAKER_00Which is the worst of both worlds. You paid someone else to do the job, and you're still the one who pays when it goes wrong. So let's talk about the one clause because the risk doesn't transfer on its own. The thing that transfers it or fails to is one clause. And Jim already said it. The word is indemnification. This is the heart of the episode. What is it? In plain English, Jim.
SPEAKER_02All right. So strip away the legaleese and indemnification is a promise about who pays. And indemnification clause is one party agreeing to cover the other party's losses, damages or legal costs if certain things happen. So in a guard contract, the questions and it answers is if there's a claim arising from the security services, who's financially responsible? The clause is where the two companies decide in advance whose problem it is.
SPEAKER_00So this clause is literally the risk transfer mechanism. It's the thing that does the job the retailer assumed was automatic. Exactly.
SPEAKER_02And here's why you have to actually read it because these clauses run in different directions and they aren't standard. A well-drafted contract from the retailer side has a guard company indemnifying the retailer, meaning if a claim arises from the guard's conduct, the guard company covers it. That's the risk transferring the way the retailer assumed.
SPEAKER_00And what's the other direction, Jim?
SPEAKER_02Well, the other direction is the trap. Guard companies write their own contracts too, and a contract drafted to protect them may flip it or water it down or carve out big exceptions or even have the retailer indemnifying the guard company in some scenarios. So, you know, I um we've all heard of contracts where the retailer signed up to cover the contractor, and the retailers' people signing it had no idea because nobody read the indemnification clause. They read the price and the schedule and the term, but not the clause that actually allocated the risk.
SPEAKER_00So the document everyone treats as boilerplate is the single most important thing in the relationship.
SPEAKER_02Yeah, well said. It's the most important paragraph in the contract, and it's the one most likely to go unread. And there's a companion piece that has to be there with it insurance. And indemnification promise is only as good as the ability to actually pay on it. So a sound contract pairs indemnification with insurance requirements. The guard company has to carry adequate coverage at specified limits, and I think this is the detail most people will miss. Name the retailer as an additional insured. A promise to indemnify from a company with no real insurance behind it is a promise that evaporates the moment a serious claim lands.
SPEAKER_00So it's two things working together: the clause that says who pays and the insurance that makes who pays actually mean something. Right.
SPEAKER_02The indemnification says whose problem it is. The insurance is what makes sure the money's actually there when it becomes a problem. You need both. One without the other is a paper shield.
SPEAKER_00A paper shield indeed. So whether you're about to hire a guard company or you've had the same one for years, what do you do?
SPEAKER_02Well, first, and I think most obviously, find the indemnification clause in your current contract and actually read it. Or have someone who understands it read it. Know which direction it runs right now. A lot of operators have generally no idea what their existing contract says about this, and the time to find out is not the week of an incident.
SPEAKER_00Second, and this is the architect in me speaking, understand that the contract is where you engineer the risk transfer. It doesn't happen by hiring, it happens by drafting. So treat the indemnification and insurance terms as the most important part of the negotiation. Not the fine print that everybody likes to skim. If you're the retailer, you want the guard company indemnifying you for claims arising from their conduct, backed by real insurance, with you named as an additional insured.
SPEAKER_02Third, don't sign the guard company's standard form without scrutiny. Their standard contract is drafted to protect them. That's their job. The risk allocation that's good for them is often the opposite of what's good for you. This is a genuine uh get counsel moment, right? The cost of having a lawyer review a guard contract is trivial next to the cost of discovering mid-lawsuit that you indemnified the wrong party.
SPEAKER_00And the through line of the whole season applied here: the duty doesn't disappear when it crosses an organizational boundary. It moves only if you deliberately move it. Structured and in writing before the incident. Same lesson as the response doctrine, same lesson as retention. Structure it in advance on purpose with intention, or live with whatever the default turns out to be.
SPEAKER_02And the default is almost never in your favor. So, in closing, here's where it all lands. Hiring a guard company delegates the task. It does not automatically transfer the liability. When something goes wrong on your premises, the injured party can frequently still come after you. And whether you're truly covered comes down to one clause you probably haven't read. Indemnification backed by real insurance.
SPEAKER_00You can hand off the work, but the risk only moves if you deliberately move it. In the contract, before anything happens. The org boundary between you and your contractor is exactly where duty quietly changes hands, or quietly doesn't. And you find out which one two years later. The hard way.
SPEAKER_02Yeah, so read the clause before you sign it, not after the lawsuit. It's the most expensive paragraph you'll ever skim past.
SPEAKER_00Well said, Jim. And next week, the season turns to the asset every loss prevention program forgets to protect. The employee. And why the person at the register is the one you owed all along. I'm Don Carr. I'm Jim Cords. Stay well, stay aware. And stay city safe.
SPEAKER_01That wraps up this episode of the City Safe Podcast. Thanks for joining us in the conversation about smarter strategies for safer cities. If you found today's discussion valuable, share it with your network and help us spread awareness about the tools and technology making a real impact. Be sure to subscribe on Spotify, Apple Podcasts, and YouTube Music so you never miss an episode. Until next time, stay informed, stay connected, and stay city safe.