Single point of failure
Read the full after-action account
A domestic disturbance call led to a suspect fleeing across state lines, crossing three separate jurisdictions in a single incident. During a traffic stop, the responding officer was dragged by the fleeing vehicle. The suspect eluded a second stop before ties to a third state were identified.
What followed was coordination across four-plus agencies: the originating state, the state where the officer was injured, the state with the suspect's ties, local municipal detectives, and federal partners who joined as the case developed. The primary coordination tool was a single, sprawling email thread.
As more agencies joined, updates got buried in reply-alls. Time-sensitive leads sat unread or got lost in a thread organized around whoever replied last, not the incident itself.
This wasn't a training failure, it was structural. There was no shared, real-time channel built for the specific incident, accessible to exactly the people working it, with a subject record that updated in one place instead of a new PDF attached to every email.
“As new information on the suspect came in, someone had to compile it, format it into a PDF, and email it out to everyone on the case. Agencies working off an outdated PDF wasn't a hypothetical risk, it was the default condition.”From the after-action review