Ep. 25: Detection's Dilemma, Part 2 · Building the Response Doctrine

Last week, Store B's AI caught the theft, logged it, and nobody moved — leaving the store that saw the crime more exposed than the one that stayed blind. In Part 2 of Detection's Dilemma, Don Carr and Jim Cords resolve the paradox by rebuilding Store B without changing a single piece of hardware. The fix isn't less detection — it's the half of the system the vendor doesn't sell you: a response doctrine. A defined recipient, a defined response, a logged outcome — three lines that convert timestamped liability into a documented legal defense. Detection sees; doctrine answers; you need both. Plus the version-one response doctrine you can write this afternoon. Loss. Liability. Law.

Transcript

0:02

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. Thanks for joining us for another episode on the City Safe Podcast. This is episode 25. I'm your co-host, Don. And I'm your co-host, Jim. And last week, Jim and I left you with a store and a problem. Store B. The AI saw the theft, flagged it, timestamped it, logged it, and nothing else moved. And we said that store, the one that saw it, is in a worse legal shape than the store that stayed blind. And we stopped there on purpose. I cut you off, and you walk and go back and hear me do it. You did, Jim. So today we finish it. Same store, same technology, same camera, same AI, same alert. We don't change a single piece of hardware. And we're going to turn store B from the most exposed operation in the chain into the most defensible one. Same detection, opposite outcome. The difference isn't what the system sees, it's what the organization does in the next 90 seconds. So let's restate the paradox, Jim, in one sentence. So anyone joining today is caught up. Detection manufactures knowledge. Knowledge creates legal duty. And a duty you don't discharge becomes liability. So the danger was never the camera. The danger was the alert that fires into a void. Yeah, it fires into a dashboard that nobody's watching, or to a phone in a back office that's empty. The alert isn't the problem, the void is the problem. Right. And here's the reframe that resolves everything. People hear detection creates liability and conclude that the detection is the risk. It isn't. The detection is just half a system. Every detection system ships with a built-in question. Now what? And the box doesn't answer it. The vendor sells you the question. They don't sell you the answer. And legally, the void is the worst possible place to be. We said it last week. Awareness plus an action timestamped side by side. That's not a gap in your security, but that's a gap a plaintiff's attorney drives a verdict through. So the fix isn't less detection. It's never less detection. The fix is to build the other half of the system. The half that answers, now what? I call that response doctrine. And doctrine just means the answer is decided in advance. Written down and the same every time. So it doesn't depend on who happened to be looking at the screen in that moment. Yeah, that's well said, Don. It's decided before the incident, not during it. Because during the incident, it's too late and too chaotic to invent a response. And that's the whole game, Jim. Structure before urgency. You build the response when you're calm, so the system can execute when you're not. So let's actually build it. Same store B. The alert fires, concealment detected, aisle seven, timestamped. In the broken version, it lands in a void. Watch what we change. Okay, walk us through it. What's the first thing that has to be true? First, the alert has to go to a defined person, not to a dashboard, but to a role. The closing manager, the on-duty LP associate. Somebody whose job description includes you receive this. If the answer to who gets the alert is the system, you haven't assigned it yet. A system isn't a person. Notice has to land on a human who's accountable for it. And in legal terms, that single step changes the story. Now there's not just a record that the company knew, there's a record that a responsible person was tasked, and the organization had a plan for that knowledge. You've converted raw notice into a managed process. Well articulated, Jim. Second, that person has a defined response. Not use your judgment, a predecided set of reasonable steps. Maybe it's an approach and offer service, which, by the way, deters as well as anything. Maybe it's notify a supervisor. Maybe in some cases it's simply observe and document and let them go. Because we'll get to detention in a later episode. And that's its own minefield. The point isn't which step. The point is the step exists before the alert. And I think the important thing you said there was reasonable steps, right? So that's the legal standard from episode 23. The law asks for reasonableness, not perfection, not crime solving. A defined reasonable, repeatable response is the discharge of the duty. And third, and this is the part that makes the lawyer smile, the response gets logged. The alert fired at 7.42 a.m. Manager acknowledged at 7.43 a.m. Action taken, documented, 7.44 a.m. Now your record doesn't say we knew and did nothing. It says we knew. And here's the timestamped chain of exactly what we did about it. And that record is the entire ball game in litigation. The plaintiff wants to show notice plus in action, but you hand them you hand them notice plus a documented reasonable response. So you've taken their whole theory of the case and structurally dismantled it. The detection that was your exposure is now your defense. That's right, Jim. Same camera, same AI, same alert. We added three things: a defined recipient, a defined response, a logged outcome. And store B went from the most exposed store in the chain to the most defensible. The technology didn't change. The doctrine around it did. So I want to pull up to the principle because this isn't really about cameras. It's the thing that runs under both of these episodes. The capability to detect and the duty to respond have to be engineered together. Detection without response isn't a half-built system. It's a full-built liability system. And most operations buy them in the wrong order. They buy the detection because that's what gets sold and that's what's exciting. The response structure, the boring part, the who gets it and the what do they do with it and where is it logged part? That's an afterthought, if it even happens at all. Which is exactly backwards. The response doctrine should be designed before you turn the detection on. Because the moment you switch that system on, it starts manufacturing notice, and the clock on your duty starts running, whether you've built the answer or not. Don't energize a knowledge machine. You're not structured to answer. That's it. That's the whole thing. And here's the part I find genuinely encouraging. After two weeks of what sounds like bad news, this is buildable. It's not expensive. A response doctrine is mostly decisions and documentation, deciding who, deciding what, deciding where it's recorded. You can write the core of it in an afternoon. The hard part isn't cost, it's just remembering to do it before instead of after. And the operators who do it simply sleep better. Not because nothing will ever happen, things happen, but because when it does, they already know what the record will say. They built it on purpose. So last week's homework was diagnostic. Go find your void. This week's is constructive. Take one detection system you run, write the three lines, who receives the alert, what they're required to do, where it gets logged. That's a response doctrine, version one. You can refine it forever, but version one closes the void. So, in closing, here's where the two parts land. Detection isn't the danger, and it isn't the savior. It's half a system. It manufactures the knowledge, and knowledge creates the duty. What you build to answer it decides whether that duty becomes your defense or your downfall. Your defense or your downfall. Well said, Jim. Same camera, same alert, opposite outcome. And the only variable was the doctrine standing behind it. The technology doesn't make you safe or expose you. The structure around the technology does. Detection, well, that sees. Doctrine, that answers. And you need both. So build the answer before you turn on the question. Next week, we change gears from the systems that watch to the moment a human being physically steps in. The detention, where the lawful stop ends and false imprisonment begins, and how a $40 loss becomes a six-figure claim. I'm Don Carr. And I'm Jim Kords. Stay well, stay aware. And stay city safe. That 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.