Latest / HOTELLIGENCE PODCAST / Ep. 11: The Incident Report Is Not the Incident
Transcript
- speaker-0: Welcome to the Hotelegents Podcast, your strategic vantage point on the changing landscape of hotel safety. Hosted by Jim Courts, a retired FBI DHS investigator and Don Carr, a former frontline security owner-operator with years of first-hand incident response experience on hotel properties. Every episode brings you closer to understanding the full picture and what the future may hold. Let's begin. speaker-1: Welcome back to the Hoteligence podcast. This is episode 11, the incident report mirage, why hotels document problems, but rarely capture the truth. I'm Don. During the years I operated on-site security teams in hotels and multifamily environments, I wrote and reviewed a lot of incident reports. And over time, something became very clear. Incident reports feel authoritative. but they rarely function the way people think they do. speaker-0: And I'm Jim. So yeah, Don, I spent my career in federal law enforcement, wrote my Shaharif reports, but documentation in the government is treated as evidence. But in hospitality, incident reports play a very different role. So today, we're unpacking why hotels document incidents consistently, yet still struggle to build meaningful operational understanding from those reports. speaker-1: Well said, Jim. And this episode is not about bad reporting. speaker-0: It's about what incident reports are designed to do and what they're not designed to do. So first, what incident reports are built for? Well, in hospitality, incident reports are primarily legal instruments. In hospitality, incident reports are primarily legal instruments. They exist to create a contemporaneous record that can be referenced later if questions arise. speaker-1: Right, they're written to establish that something was noticed, acknowledged, and handled within policy, not to reconstruct every detail of what occurred. speaker-0: Yeah, and that purpose shapes everything, tone, language, and structure. speaker-1: So when people expect incident reports to function as safety analysis tools, they're asking them to do work that they weren't designed to do. So let's talk about why language gets so careful. With incident reports, they're usually written by people who understand that their words may be reviewed later by managers, attorneys, insurers, or corporate teams. speaker-0: And that awareness naturally pushes language toward caution. Descriptions become narrow, verbs soften, interpretation disappears. speaker-1: Not because staff are hiding information, but because interpretation creates exposure. speaker-0: And the safest sentence is often the least descriptive one. So let's talk about incentives shape documentation. So it's important to understand incentives, right? So staff are not rewarded for depth or narrative clarity. speaker-1: They're rewarded for compliance, for completing the report, for not escalating risk unnecessarily. speaker-0: Over time, reporting behavior adapts to what the system reinforces. speaker-1: And the result is documentation that satisfies legal requirements without capturing operational nuance. Let's talk about how the timing degrades accuracy. Another structural issue here is timing. Incident reports are often written after the immediate situation has passed. speaker-0: Yeah, sometimes hours later and sometimes after a shift change. speaker-1: and memory fades quickly, especially under stress. speaker-0: details blur, sequence collapses, what felt clear in the moment becomes harder to reconstruct later. speaker-1: And that isn't a failure of effort. It's a human limitation. speaker-0: Shift changes fragment context. Hotels operate continuously, but incident reports don't always capture continuity across shifts. speaker-1: Right, one team documents what they observed, another team documents something else, neither sees the full picture. speaker-0: So reports exist more as snapshots, not narratives. speaker-1: And without narrative continuity, patterns are very difficult to see. Which brings us into how reports are actually read. Many staff assume incident reports are read carefully and holistically. speaker-0: In reality, managers are often scanning for exposure, claims risk, or policy compliance. speaker-1: They're triaging, not necessarily analyzing. speaker-0: And that's not negligence, it's workload reality. speaker-1: But what it means is that reports are rarely used as raw material for deeper understanding. speaker-0: what happens at the corporate level. While one reports reach corporate, they're usually abstracted further. speaker-1: Right, converted into categories, counts, and dashboards. speaker-0: Volume matters. Trends at a higher level matter. speaker-1: but story, sequence, and context are stripped away. speaker-0: Yeah, the system favors aggregation over interpretation. speaker-1: And that explains the mirage because this is why incident reports feel so solid, yet often fail to drive operational insight. speaker-0: They create the appearance of clarity without producing any understanding. speaker-1: And that's not because anyone's lying or withholding information. speaker-0: No, it's because the system incentivizes defensibility over death. speaker-1: So in closing, incident reports are not broken. They're doing exactly what they were designed to do. speaker-0: The problem arises when we expect them to function as something they're not. speaker-1: and understanding that limitation is essential before asking hotels to rely on reports for prevention or pattern recognition. speaker-0: In the next episode, we'll look at another overlooked operational environment that quietly carries risk, the hotel business center. speaker-1: And remember, we're in this together. speaker-0: And together, we make hospitality stronger. speaker-1: We publish a short written insider briefing alongside each episode. It goes out on Wednesdays when the episode drops. If that's useful, the link is in the show notes. speaker-0: Thank you for joining the Hotelegents Podcast, where experience informs smarter, safer hotel operations and prepares you for what comes next. Stay informed, stay confident, and stay connected. As the conversation evolves, Jim Cords and Don Carr will highlight developments that help hotels strengthen their approach to safety and risk management. See you next episode.