Before the Call — The Decker Manhunt — Chelan County, Washington

The failure-to-return call is one of the more ambiguous call types in a dispatch center's inventory. It sits at the intersection of family law, welfare concerns, and potential criminal investigation. Most failure-to-return calls resolve without incident — a miscommunication, a late return, a parent who lost track of time. The Decker case is the version where the worst-case interpretation was true from the beginning, even though nothing in the initial call made that obvious.

• The initial call determines the investigation's starting point. The information Whitney Decker provided on May 30 — who the children were, who had them, where the visitation was, what the custody order said, when contact was last made, what was unusual about the situation — became the foundation for everything that followed. Call-takers on missing children reports need to understand that they are building an investigative record, not just routing a welfare check. The questions you ask, the information you capture, and the specificity of what you document shape whether investigators can move quickly in the first hours.
• Failure-to-return calls require early escalation triggers. Most jurisdictions have protocols that distinguish between a custodial dispute (civil matter, limited law enforcement role) and a missing child (immediate law enforcement response). The indicators that push a call from the former to the latter — the age of the children, the absence of contact, any prior history of concern, the calling parent's assessment of risk — are call-taking questions, not investigative questions. A dispatcher who asks the right questions in the first five minutes may be the one who triggers the escalation that gets units to the campground while there's still something to find.
• The 48-hour window is where the call type changed — and that shift has dispatch implications. When Decker's vehicle was found and the children's bodies were located on June 2, the incident type changed from missing children to homicide and manhunt simultaneously. That transition — from welfare/missing persons protocols to homicide protocols to fugitive protocols — each carries different resource implications, different notification chains, and different public information postures. Dispatch centers need to be able to pivot across those frameworks without losing continuity of the information record from the original call.
• Document everything, especially what seems routine. The May 27 traffic stop — three days before the girls were killed — was a routine citation. Decker was documented, photographed, and released. That interaction became significant evidence. Call-takers and dispatchers working routine contacts in the days and hours before a major incident are building records they don't know they're building. Complete, accurate documentation of ordinary contacts is the same skill as complete documentation of emergencies — the difference is that you don't know which ordinary contact will matter later.

Chelan County is not a large jurisdiction. Its dispatch center handles the day-to-day communications of a rural mountain county — traffic, SAR, fire, law enforcement. The Decker case brought a tip volume and a public attention footprint that dwarfed anything in its recent history. The operational challenge of managing incoming tips while simultaneously coordinating an active multi-agency manhunt and maintaining baseline county services is a real resource stress that small centers face in high-profile cases.

• Tip management is a distinct function that should not run through 911. When a high-profile case generates public tip volume, routing those calls through the primary PSAP degrades 911 availability for actual emergencies. Chelan County eventually transitioned tip management to the U.S. Marshals and FBI, who have dedicated infrastructure for it. The earlier that dedicated tip line is established and publicized, the less that volume pressures the 911 system. Establishing a separate tip line — and getting that number into media releases and public communications quickly — is an operational decision that dispatch supervisors should be positioned to recommend.
• Tips require triage, not just logging. A tip from England that Decker was spotted near London is a different priority than a tip from a hiker who saw someone matching his description near Ingalls Creek the same morning. The volume of low-credibility tips in a high-profile manhunt can bury the high-credibility ones if there's no triage framework. Dispatch doesn't usually adjudicate tip credibility — but if dispatch is receiving tips before a dedicated line is established, having a clear protocol for what information to capture and where to route it prevents the record from becoming an undifferentiated pile.
• The federal transition is a resource, not a handoff. When the U.S. Marshals deployed their Rapid Manhunt Program and the FBI took an increasing role, Chelan County didn't exit the case — it transitioned from primary operator to coordinating partner. Dispatch was still the local 911 system. Understanding how your center's role changes when federal agencies assume primary operations — what information flows continue, what new communication channels are established, how you route resources that arrive through different chains of command — is an interoperability question that's worth working through before a major case, not during one.
• Declining tips are an operational signal. When CCSO announced the scale-back on July 25 because tips had dried up, that decision was based in part on an observable change in information flow. The tip volume that had been generating leads had dropped below a threshold where the search posture was sustainable. Dispatch centers that have visibility into tip volume trends — not just individual tips but the overall pattern — can provide investigators with that signal earlier. "We're getting 200 calls a day and now we're getting 20" is useful operational intelligence.

The viral custody hoax during the Decker manhunt is a version of a problem that now recurs in every high-profile law enforcement case: false information circulates faster than corrections, and some portion of the public acts on the false information by calling 911. Dispatchers were fielding calls from people who believed the case was over, asking for confirmation, asking about the children, asking what happened — when the case was very much not over and Decker was still at large.

• Dispatch is not the public information office — but it is the public's first contact. When misinformation is active, dispatchers will receive calls from people acting on it before any correction has been issued. The call might be someone reporting they saw the viral video and want to confirm it's real. It might be a journalist. It might be a family member. It might be someone who wants to know if it's safe to hike in the search area. Dispatch needs a clear, consistent, short answer that doesn't confirm or expand the false information, doesn't engage with its details, and routes the caller to the correct public information source. "That is not accurate — for official updates on the case, please check the Chelan County Sheriff's Office website" is a complete answer.
• Misinformation generates safety-relevant behavior. If people believe a fugitive is in custody, they may relax precautions that were appropriate while he was at large. In the Decker case, the public had been told not to pick up hitchhikers, to report unusual activity in the wilderness, and to avoid flying drones in search areas. If a portion of the public believed those precautions were no longer necessary based on a false video, that created a real operational gap. Dispatch was in a position to correct that — briefly, consistently, without elaboration.
• The debunking itself generated call volume. When CCSO issued the formal statement that the viral video was false, that generated a second wave of calls — people who had seen the correction and wanted to understand what was real. Each wave of public information activity, accurate or not, creates a corresponding wave of public inquiry that arrives at 911. Anticipating that wave — and having a briefed, consistent answer ready before it hits — is a dispatch supervisor function, not an individual dispatcher improvisation.
• Document misinformation contacts. Calls driven by false information should be logged with a notation that the caller was acting on inaccurate public information, what that information was, and when. That record helps investigators understand the scope of the misinformation's spread, helps public information officers calibrate their correction efforts, and protects dispatchers whose call record might otherwise look like they were receiving unusual call types for reasons that aren't explained.

The Decker manhunt is the series' first exercise built around an incident without a clean resolution point — or rather, one whose resolution took four months and ended not with an arrest but with the discovery that the suspect had been dead near the crime scene the entire time. For dispatchers, the sustained nature of the incident is itself the operational challenge. This isn't a 12-hour MCI that you work and then debrief. It's an incident that outlasts shift cycles, supervisor rotations, and normal operational rhythms — for months.

• Multi-phase incidents require explicit phase transitions. The Decker manhunt moved through at least four distinct phases: active pursuit (June 2 – ~week 3), scaled aerial operations with targeted ground search (~week 3 – July 25), reduced footprint with recovery orientation (July 25 – September), and remains recovery/confirmation (September). Each transition changed the resource picture, the tip management posture, the public communication framework, and the day-to-day dispatch coordination requirements. Those transitions need to be documented and briefed across shifts — not assumed to be understood because they happened. A dispatcher coming on shift in August needed to know the current operational posture, not the June posture.
• Shift handoffs carry the institutional memory of a long incident. In a four-month operation, no individual dispatcher worked the entire thing. The collective understanding of the case — what had been searched, what leads were active, what the current inter-agency structure was, what the public communication protocol was — lived in the handoff process. When handoffs are rushed or incomplete, the institutional knowledge degrades shift by shift. Long-duration incidents require a more structured briefing document than a normal shift change — a living operational summary that gets updated as the case evolves.
• Baseline county services don't pause for a major case. While the Decker manhunt was ongoing, Chelan County dispatch was still handling every other call in the county — traffic accidents, medical calls, fire responses, the normal daily volume. The manhunt didn't replace the job; it was added to it. For the dispatchers working during that period, the Decker case was a sustained background pressure running alongside their regular workload. That kind of chronic operational stress — not the acute stress of a single bad call, but the accumulative weight of weeks and months — is a dispatcher wellness issue that gets less attention than critical incident stress.
• The answer "we don't know yet" is a valid and important dispatch posture. For four months, the honest answer to most questions about Decker's whereabouts was "we don't know." The sheriff said publicly that Decker might be found in a week or two years. That uncertainty — sustained over months, with periodic sightings that proved false, with a scale-back that looked like giving up even though it wasn't — is genuinely difficult to hold. Dispatchers who received calls asking whether the fugitive had been found, whether the area was safe, whether the case was being actively worked, needed to hold that uncertainty accurately without either inflating hope or projecting defeat. "The investigation is ongoing, and official updates are available through the sheriff's office" is honest, complete, and sustainable.

This question sits outside the tactical dispatch skill set — and that's exactly why it belongs in this series. Every other question in Before the Call is about what to do. This one is about what it costs to do it, and whether your center has the infrastructure to support the people carrying that cost.

• Dispatchers are community members first. The dispatchers at Chelan County CCSO live in the Wenatchee Valley. Some of them knew the Decker family, or knew people who did. They attended the same community events, drove past the same landmarks that now had significance. The professional requirement to maintain composure and function during a shift doesn't erase the fact that they were also community members experiencing the same grief as everyone else — they were just experiencing it while working a console.
• Repeat exposure to case details is cumulative. Over four months of the Decker manhunt, dispatchers received hundreds of calls related to the case — tips, welfare checks, media inquiries, misinformation calls, calls from people who were frightened, calls from people who were grieving. Each call re-engaged the details of the case. Unlike a critical incident that ends and can be debriefed, a four-month sustained exposure doesn't have a clean endpoint for the debrief process. Standard CISM (Critical Incident Stress Management) protocols are designed around discrete events; they are less well-suited to cumulative, chronic exposure. Centers with long-duration cases need to check in with staff proactively, not just after a single acute incident.
• The scale-back announcement on July 25 was emotionally complex for everyone. Publicly, the scale-back read as an acknowledgment that the search might not end with a capture. For dispatchers who had been routing resources, fielding tips, and holding the operational complexity of the manhunt for nearly two months, the transition to a reduced-footprint posture carried its own psychological weight. "We're shifting to recovery mode" is a meaningful sentence for a dispatcher who has spent weeks working a pursuit. It's worth acknowledging explicitly in shift briefings and supervisor check-ins — not because dispatchers can't handle the transition, but because pretending it's just a routine operational change isn't honest.
• Closure doesn't always close things. The confirmation of Decker's remains on September 26 ended the legal uncertainty but didn't erase four months of community grief or the operational weight the center had been carrying. Sheriff Morrison acknowledged that many questions would likely remain unanswered. For dispatchers, "the case is closed" doesn't mean the processing is complete. Post-incident peer support conversations — not just formal CISM — offered weeks after confirmation, not just the day after, reflect a more accurate understanding of how people process sustained trauma.