911 Dispatch: Still on Shift - When the Job Won't go "Not Ready"
- Whitney B.
- Apr 1
- 4 min read
Updated: 5 days ago
If you’ve ever found yourself irritated by other people’s decision-making, mentally noting license plates “just in case,” or standing in your kitchen unable to decide what to eat for dinner—you’re not alone.
For many 911 dispatchers, these aren’t random quirks. They’re patterns.
In most communications centers, going “not ready” means you’re temporarily unavailable for calls—even if it’s just for a moment to reset, regroup, or catch your breath.
The challenge is, that option doesn’t exist off the console.
The calls stop. The headset comes off. But the mental state that made you effective on shift doesn’t automatically power down.
Patterns that make you highly effective at work can be the same ones that make it surprisingly difficult to transition out of it.
What It Looks Like (From the Dispatcher Seat)
Hypervigilance, in the dispatch environment, isn’t just “being aware.” It’s a constant state of scanning, processing, and anticipating.
You might recognize it as:
Always tracking details—descriptions, behaviors, exits—without trying
Becoming an “expert eavesdropper” in public spaces
Feeling mentally exhausted, but unable to relax
Experiencing decision fatigue over even minor choices
Irritability over small inconveniences
Unwinding by mentally checking out into someone else’s chaos (hello, reality TV)
And sometimes, it looks like this:
You use the word “overstimulated” to your spouse, and it doesn’t quite land—because how do you explain the constant layering of input?
Callers in crisis
Radios transmitting simultaneously
A coworker trying to slip in a quick piece of gossip
The immediate need to drop everything when the tone of a call changes

Then you go home:
Your partner wants to unload their day on you
A toddler is climbing on you
Your older kid needs brownies for the bake sale tomorrow
The laundry chimes
The cat is demanding food
It doesn’t turn off. It just… follows you.
What’s Actually Happening
This pattern is well-documented by Kevin Gilmartin, who describes hypervigilance as a necessary, job-related state.
The critical point:
The issue isn’t going into hypervigilance—it’s coming out of it.
For dispatchers, the cycle is predictable:
On-duty: focused, alert, high-performing
Off-duty: fatigue, irritability, withdrawal
Days off: partial recovery
Return to work: the cycle repeats
By the time you start to feel like yourself again, it’s often late in the evening—and while the rest of your household is winding down, you’re preparing to ramp back up.
Where It Gets Misunderstood
From an organizational standpoint, these behaviors are often misread as:
Burnout
Disengagement
Performance issues
In reality, they are predictable physiological responses to the demands of the job.
That distinction matters.
Because when the response is misunderstood, the solution often misses the mark.
The Operational Impact
Unchecked, this cycle doesn’t just affect the individual—it affects the organization:
Retention challenges
Fluctuating morale
Strain on team dynamics
Supervisors addressing behavior without understanding the cause
A common leadership blind spot is focusing only on the outward behavior—irritability, withdrawal, lack of engagement—without addressing the underlying pattern.
Correction may be necessary in the moment. But it cannot be the only strategy.
Sustainable change requires:
Ongoing engagement
Follow-up
Supportive structures
A willingness to invest time, not just policy
The Disconnect (Where Problems Grow)
At its core, the issue is simple:
There is no built-in transition from “on” to “off.”
The brain does not distinguish well between:
Active emergencies
Residual stress carried after the shift
And that creates a disconnect.
For example, like many dispatchers, when people find out what I do, I often become the “party trick”—asked to recall my worst or most memorable call.
What surprises people is that I often can’t.
Some of the most tragic calls felt routine in the moment. The outcome came later.
At the same time, an irate caller—over something minor—can leave a lasting imprint. Not because of the issue itself, but because of the intensity.
That stress doesn’t always resolve when the call ends. Sometimes, it lingers for years.
What Actually Helps
Addressing hypervigilance isn’t about quick fixes. It’s about awareness and intentional action.
At the individual level:
Physical movement after shift to help regulate stress
Simple transition routines between work and home
Maintaining connection, even when withdrawal feels easier
At the leadership level:
Normalizing the conversation around hypervigilance
Training supervisors to recognize patterns, not just behavior
Creating space for decompression within the culture
And realistically—this isn’t easy.
Leadership is often understaffed and overextended. Supporting irritable, disengaged employees can feel like being asked to cuddle a piranha.
But what doesn’t work is just as important to recognize.
One-time, generalized debriefs
Surface-level wellness initiatives
Interaction limited to evaluation or correction
What does work takes more effort:
Regular, meaningful check-ins
One-on-one conversations that aren’t tied to discipline
Building rapport through consistency and honesty
Leaders modeling vulnerability and reliability
Trust isn’t built overnight. Culture isn’t built in a training.
It’s built in moments—repeated over time.
Inspiration comes first. Motivation follows.
Perspective
Hypervigilance isn’t a flaw. It’s a trained, adaptive response that makes dispatchers exceptionally good at what they do.
But the same skill set that drives performance on shift can create friction off shift—if it goes unrecognized and unmanaged.
For agencies, understanding this isn’t just about wellness.
It’s about performance, retention, and the long-term sustainability of the workforce.
And for dispatchers, it may explain something you’ve felt for a long time:
You’re not overreacting. You’re not disengaged.
You might just still be on shift.
— shift/change
For the part of the job that doesn’t stay at the console



Comments