Before the Training Gap Steals the 9-1-1 Call Surge, Capture It and Return

Listen to Direct Action Briefings on Spotify, Apple Podcasts, Amazon Music, or YouTube.

The training gap was real. It still could not be allowed to steal the live call floor.

That is the part public-sector leaders have to control.

The storm is active.

Calls are stacking.

Call-takers are answering back-to-back.

Dispatchers are working active incidents.

Supervisors are watching abandoned calls, emergency priority, non-emergency overflow, call-taker fatigue, and radio coordination.

The current objective is clear.

Keep the emergency call flow moving.

Protect life-safety triage.

Support dispatch.

Keep the floor from losing control.

Then a real secondary issue appears.

Several non-emergency storm-damage calls are coming into 9-1-1 because residents do not know which number to use.

A newer call-taker shows a training gap on separating urgent life-safety calls from lower-priority storm reports.

A supervisor notices the pattern.

A training lead wants to correct it.

A communications manager wants a new public message pushed immediately.

The issue is real.

It matters.

It could create future risk.

But if the center stops the live call floor to redesign the public message, rewrite the script, conduct training, or rebuild the non-emergency routing process during the surge, the main objective can lose control.

That is where Identify and Postpone matters.

Identify and Postpone is not ignoring the issue.

It is not saying the training gap does not matter.

It is not dismissing the public messaging problem.

It is controlled deferral.

The leader captures the issue, protects the current objective, assigns ownership, sets the return point, and defines the trigger that brings the issue forward if it becomes urgent.

The current objective is not to rebuild the training program.

The current objective is to keep emergency call flow moving during the surge.

The side issue matters.

It just may not belong in the right-now window unless it is actively damaging the live emergency call objective.

Current emergency communications pressure makes this more than a hypothetical. NENA’s 2025 Pulse of 9-1-1 report describes the public safety communications environment across staffing, technology and operations, training, wellness, and mental health, while noting rising outage rates and burnout concerns.  

That matters because a 9-1-1 center does not need extra distraction during a live surge.

It needs priority discipline.

━━━━━━━━━━━━━━━━━━━━

The Leadership Trap

The trap is treating every real issue like an immediate issue.

That trap feels reasonable because the training gap is not fake.

The newer call-taker really did need help.

The non-emergency storm reports really were entering the wrong channel.

The public message really may have been unclear.

The call script really may need refinement.

The training program really may need adjustment before the next storm.

The issue deserves attention.

So people want to fix it now.

Pull the training lead to the floor.

Stop and brief the call-takers.

Rewrite the non-emergency script.

Ask the P I O for a new public post.

Change the call classification guidance.

Discuss the difference between life-safety calls and storm-damage reports.

Review what should be transferred, held, documented, or redirected.

All of those may be valid actions.

They just may not belong in the live call surge.

That is the leadership trap.

The leader sees a legitimate issue and lets it hijack the current objective because the issue is visible, serious, and easier to define than the pressure already in motion.

The training gap needs correction.

But the call floor needs control first.

The public message needs improvement.

But emergency calls need to be answered now.

The non-emergency routing process needs review.

But the live surge cannot become a process-redesign meeting unless the issue is actively damaging life-safety triage.

That is the distinction.

Identify and Postpone protects the main effort without letting the issue disappear.

A real issue is not always the right-now issue.

━━━━━━━━━━━━━━━━━━━━

What Usually Happens Under Pressure

The pressure starts with a storm surge in the call center.

Wind damage is being reported.

Trees are down.

Power is out in pockets of the county.

Water is crossing a few low roads.

Residents are calling with different levels of need.

Some calls are true emergencies.

Some are urgent but not life-threatening.

Some are non-emergency storm-damage reports.

Some residents are scared and do not know which number to use.

The 9-1-1 center absorbs it.

Call-takers move from call to call.

Dispatchers are coordinating active units.

Supervisors are watching the board.

The floor has no extra attention to waste.

Then the secondary issue appears.

A newer call-taker hesitates on a storm-damage call.

A supervisor hears inconsistent classification language.

Another call-taker asks whether a tree across a neighborhood road is an emergency, non-emergency, public works issue, or law enforcement assist.

Resident services reports that people are confused about which number to call.

Someone says the public messaging should have been clearer.

Someone else says the training packet needs updating.

Now the room starts to shift.

The conversation can move away from the live call flow and toward the side issue.

Who trained the new call-taker?

Why is the script unclear?

Why do residents keep calling 9-1-1 for non-emergency storm damage?

Should the public message be rewritten now?

Should all call-takers be briefed immediately?

Should emergency management push a new notification?

Should the non-emergency line be highlighted again?

Those are not bad questions.

They just may not be the questions that protect the call floor right now.

If the supervisor chases the issue immediately, the live surge loses attention.

If the supervisor ignores the issue completely, the same problem returns during the next storm.

Both moves are weak.

The better move is controlled capture.

Name the issue.

Keep the call flow moving.

Assign ownership.

Set the return point.

Define what would make the issue urgent enough to move forward now.

That is the Identify and Postpone moment.

━━━━━━━━━━━━━━━━━━━━

Field Note: Do Not Let the Side Fix Steal the Main Effort

A side issue can be real and still be mistimed.

That is hard in emergency communications because real issues deserve respect.

Training matters.

Call classification matters.

Public messaging matters.

Non-emergency routing matters.

Resident confusion matters.

Call-taker confidence matters.

Supervisor burden matters.

None of that should be dismissed.

But the leader still has to protect the active objective.

During a live 9-1-1 surge, the main effort is emergency call flow.

The side issue is the training gap, public messaging gap, or non-emergency routing improvement that surfaced during the surge.

Those are connected, but they are not always the same action window.

If the training gap is actively damaging emergency call triage, it moves into the current action path.

If the public messaging issue is causing immediate call-floor failure, the center may need a narrow live correction.

If the issue is real but not currently blocking life-safety call flow, it needs capture, ownership, return timing, and a trigger.

That is the field note.

Do not ignore it.

Do not chase it.

Bring it back on purpose.

━━━━━━━━━━━━━━━━━━━━

Scenario: The Communications Supervisor and the Training Gap That Tried to Take Over the Surge

Elena is a shift supervisor in a county 9-1-1 emergency communications center.

A severe storm line has moved through the county.

The weather alert went out earlier in the day.

Now the calls are coming in.

One area has downed trees.

Another has traffic lights out.

Several neighborhoods have power loss.

A creek is rising near a low-water crossing.

A few callers are reporting wires down.

Others are reporting branches, blocked driveways, fence damage, minor flooding, and debris in the road.

The floor is active.

Call-takers are working fast.

Dispatchers are coordinating fire, law enforcement, E M S, utilities, and public works notifications.

Supervisors are watching emergency priority, abandoned calls, call-taker fatigue, unit availability, and non-emergency overflow.

The current objective is clear.

Keep the emergency call flow moving.

Protect life-safety triage.

Support dispatch.

Keep the floor controlled.

Then the side issue appears.

A newer call-taker struggles with a storm-damage call.

The caller reports a large tree across a residential road.

No one is injured.

No wires are visible.

No vehicle is trapped.

The caller is upset because they cannot leave the neighborhood.

The call-taker hesitates.

Is this a police call?

Public works?

Non-emergency?

Emergency dispatch?

Supervisor review?

At the same time, several similar calls are entering 9-1-1.

Some are serious.

Some are not.

Some should be directed to non-emergency reporting or public works.

Some need dispatch.

Some need immediate escalation because wires, trapped people, medical issues, or road hazards are involved.

Elena sees the pattern.

The training issue is real.

The public messaging issue is real.

The call classification issue is real.

A training lead on duty says they need to correct the gap now before more calls come in.

A communications manager suggests pushing a new public message about the non-emergency line.

Another supervisor wants to pause and brief the floor.

All of that makes sense.

The issue is visible.

The floor is feeling it.

No one wants a life-safety call mishandled.

No one wants residents sent to the wrong place.

No one wants a new call-taker guessing under pressure.

But Elena has to decide whether the correction belongs inside the live surge or after the floor is stabilized.

The first instinct is to fix the training gap now.

That instinct is understandable.

The risk feels serious.

The newer call-taker needs support.

The public is confused.

The supervisor does not want to look like she is dismissing an operational weakness.

But if Elena turns the live surge into a training correction, the call floor loses attention.

The call-takers get new direction while they are already overloaded.

The training lead gets pulled into a process conversation instead of supporting the floor.

The P I O starts adjusting public messaging while the center still needs immediate call control.

Dispatch coordination may weaken.

The active objective starts drifting.

That is the failure pattern.

The side issue is real.

The timing has to be tested.

━━━━━━━━━━━━━━━━━━━━

The Problem Path

The current path should be controlled.

Answer emergency calls.

Protect life-safety triage.

Support dispatch.

Keep call-takers moving.

Use supervisor support for immediate classification questions.

Handle the calls that need action now.

Capture the training gap and public messaging problem.

Return to them after the surge or at the next operational review.

That path protects the current objective and keeps the issue visible.

The weak path is different.

The training gap appears.

The supervisor starts correcting the full issue in real time.

The training lead gets pulled into rewriting guidance.

The P I O is asked to adjust public language before the floor has a stable read.

The communications manager starts discussing non-emergency routing.

Call-takers receive extra explanation while calls are stacking.

Supervisors start solving the next training cycle while the current call surge is still active.

Everyone is trying to help.

But the main effort has drifted.

The center is busy, but less controlled.

That is the problem path.

The 9-1-1 center does not lose control because a training gap appeared.

It loses control when the training gap becomes the priority before the live call objective is protected.

━━━━━━━━━━━━━━━━━━━━

The Blockage

The blockage is priority confusion.

Not the new call-taker.

Not the resident.

Not the public message.

Priority confusion.

A real issue has appeared during an active objective.

The issue matters enough to capture.

It does not automatically matter enough to take over the floor.

That is where leaders get caught.

They know the issue matters, so they feel pressure to act immediately.

They know the call-taker needs support.

They know public messaging is weak.

They know non-emergency routing needs improvement.

They worry that postponing it will sound like neglect.

But concern is not the priority test.

Visibility is not the priority test.

Embarrassment is not the priority test.

The priority test is whether the issue deserves action before the current objective is protected.

In Elena’s case, the current objective still matters more.

Emergency calls are stacking.

Dispatch is active.

The floor needs supervisor attention.

The training gap can be captured and returned to unless it is actively damaging live emergency call handling.

That is the blockage.

The issue is real.

The timing is wrong.

The leader needs controlled deferral, not neglect.

━━━━━━━━━━━━━━━━━━━━

The Decision Point

Elena has two weak choices and one stronger choice.

The first weak choice is to chase the issue now.

That may make the team feel supported, but it risks the live call floor.

The second weak choice is to brush it off.

That may keep the floor moving for the moment, but it lets the same issue return in the next storm.

The stronger choice is to capture the issue and protect the objective.

Elena can say:

The classification issue is real.

We are not rebuilding the training guidance during the surge.

The current objective is emergency call flow.

Supervisors will support live classification questions now.

The training lead owns the post-surge training correction.

The communications manager and P I O own the non-emergency public message review.

We return to this after the surge in the operational review.

If repeated classification errors begin affecting emergency response, abandoned calls rise, or supervisors cannot maintain floor control, we move the issue forward immediately.

That is not the full tool.

That is not the full worksheet.

But it is the correct recognition.

The issue is not ignored.

The issue is not allowed to steal the main effort.

It is captured, owned, scheduled, and monitored.

That is Identify and Postpone.

━━━━━━━━━━━━━━━━━━━━

The Next Movement

The next movement is controlled.

Elena keeps the call floor focused.

She tells the newer call-taker to use supervisor escalation for uncertain storm-damage classification during the surge.

She gives the floor one narrow live instruction:

When life safety, wires down, trapped people, medical impact, active hazard, or immediate road danger is present, escalate through the emergency path.

When the call is storm damage without immediate danger, use the current non-emergency routing guidance and flag uncertainty to the supervisor.

That is enough for the live objective.

It is not the full training correction.

It is not the full public messaging fix.

Then Elena captures the broader issue.

Training gap: assigned to the training lead.

Public message: assigned to the communications manager and P I O.

Return point: post-surge operational review.

Trigger: repeated classification errors affecting emergency response, rising abandoned calls tied to confusion, or supervisors losing floor control.

That keeps the main effort intact.

The live surge stays the focus.

The training gap stays controlled.

The team sees that Elena is not ignoring the problem.

They also see that she is not letting a real side issue steal the call floor.

That is the leadership move.

━━━━━━━━━━━━━━━━━━━━

Consequence Chain

If Elena chases the training issue now, the immediate consequence is attention loss.

Supervisors shift from floor control to process correction.

The second consequence is call-taker overload.

People already handling back-to-back calls receive extra instruction while their decision bandwidth is low.

The third consequence is dispatch friction.

If classification guidance changes mid-surge without tight control, dispatch can receive inconsistent inputs.

The fourth consequence is abandoned-call pressure.

If supervisors and trainers get pulled away from live support, call flow can suffer.

The fifth consequence is public-safety risk.

The center may spend too much attention correcting the side issue while the live emergency objective still needs protection.

But if Elena ignores the issue completely, the cost also grows.

The same classification gap returns during the next storm.

New call-takers remain unsure.

Non-emergency storm reports keep entering 9-1-1.

Resident confusion continues.

Supervisors carry the same burden again.

Training loses credibility because the issue was seen and not returned to.

That is the consequence chain.

Chasing it now damages the main effort.

Ignoring it completely damages future execution.

Identify and Postpone protects both.

━━━━━━━━━━━━━━━━━━━━

Better Read

The better read is not:

“The call-taker showed a training gap, so we need to fix the training right now.”

The better read is:

“The training gap is real, but the live call surge still owns the current window unless the gap is actively damaging emergency triage.”

The better read is not:

“We do not have time for this.”

The better read is:

“We will not lose this issue, but we will not let it steal the emergency call objective.”

The better read is not:

“We will handle it later.”

The better read is:

“Assign it, schedule the return point, and define the trigger that brings it forward.”

That is the shift.

Identify and Postpone separates recognition from immediate action.

The leader can respect the issue without surrendering the objective.

━━━━━━━━━━━━━━━━━━━━

How This Fits the Direct Action System

C S A helps the leader read what is happening before action.

In this scenario, C S A helps Elena see more than a call-taker mistake.

She sees the storm surge, the emergency call objective, the non-emergency overflow, resident confusion, supervisor load, training gap, public messaging issue, call classification pressure, abandoned-call risk, and dispatch consequence.

That cleaner read feeds DEPN.

DEPN helps leaders move through the problem once the situation is clearer.

Identify and Postpone is the DEPN move here because a real secondary issue appears while the main effort is already in motion.

The 9-1-1 center is not asking Elena to ignore the training gap.

It is asking her to protect emergency call flow while controlling the training issue for the right window.

Pro may later help Elena check what the decision could damage if handled poorly: call-taker confidence, supervisor control, public trust, emergency response, staff fatigue, and future storm readiness.

T M C may later help protect ownership, return timing, communication method, and follow-through so the postponed issue does not drift.

A L C may help capture what changed after the surge and feed the next training cycle.

The current tool stays central.

Identify and Postpone is the controlled deferral move.

The larger Direct Action System shows why timing, ownership, and return discipline matter after the issue is captured.

━━━━━━━━━━━━━━━━━━━━

The Point

The call floor did not lose control because a training gap appeared.

The call floor would lose control if the training gap became the priority before the emergency call objective was protected.

That is the point.

Training matters.

Call classification matters.

Non-emergency routing matters.

Public messaging matters.

Resident understanding matters.

Call-taker confidence matters.

Supervisor support matters.

But the leader still has to protect the main effort.

The issue must be captured.

The owner must be clear.

The return point must be real.

The trigger must be known.

Otherwise, one of two failures happens.

The team chases the side issue and loses the current objective.

Or the team postpones the issue vaguely and loses it completely.

Identify and Postpone prevents both failures.

Postponed does not mean forgotten.

It means the issue has been controlled until the right action window.

━━━━━━━━━━━━━━━━━━━━

A Practical Field Exercise

Use this before the next side issue steals a live public-safety operation.

This is not the full paid worksheet.

It is a recognition-level field check to help leaders protect the main effort while keeping real issues visible.

1. Name the Current Objective

Start with the work already in motion.

What are we protecting right now?

Emergency call flow?

Life-safety triage?

Dispatch coordination?

Reduced abandoned calls?

Floor control?

Call-taker support?

If the current objective is unclear, every side issue can sound urgent.

━━━━━━━━━━━━━━━━━━━━

2. Name the Side Issue

Do not dismiss it.

Name it clearly.

What did we identify?

Where did it show up?

Who noticed it?

How did it affect the current work?

Is it a training gap, public messaging issue, non-emergency routing issue, script issue, or call classification issue?

A vague issue cannot be controlled.

━━━━━━━━━━━━━━━━━━━━

3. Test the Timing

Ask whether the issue deserves action before the current objective is protected.

Is it damaging emergency triage right now?

Is it increasing abandoned calls?

Is it confusing dispatch inputs?

Is it pulling supervisors away from floor control?

Or can it be safely captured and returned to after the surge?

This is the core timing decision.

━━━━━━━━━━━━━━━━━━━━

4. Assign the Return Owner

Do not say “we will fix it later” unless someone owns later.

Who owns the training correction?

Who owns the public message review?

Who updates the routing guidance?

Who confirms the correction happened?

Who reports back after the surge?

If no one owns it, it is not postponed.

It is lost.

━━━━━━━━━━━━━━━━━━━━

5. Define the Trigger

A postponed issue still needs a trigger.

What would make this issue urgent?

Repeated classification errors?

Rising abandoned calls?

Supervisor overload?

Dispatch confusion?

A resident safety signal?

A call-taker unable to apply the current guidance?

The trigger protects the team from delaying too long.

━━━━━━━━━━━━━━━━━━━━

What Leaders Should Watch For

The Phrase “We Need to Fix This Right Now” Appears During Live Operations

Sometimes that is correct.

Sometimes it is the side issue trying to take the floor.

Test it against the current objective.

━━━━━━━━━━━━━━━━━━━━

The Issue Is Real, Visible, and Frustrating

That combination pulls attention fast.

Real does not automatically mean right now.

━━━━━━━━━━━━━━━━━━━━

Supervisors Start Solving Training While Calls Are Still Stacking

Training correction matters.

But if the call floor is active, the leader has to protect the live objective first.

━━━━━━━━━━━━━━━━━━━━

Public Messaging Becomes the New Meeting During the Surge

The message may need correction.

But broad message redesign during live surge can steal attention unless it is blocking the current response.

━━━━━━━━━━━━━━━━━━━━

The Phrase “We’ll Handle It Later” Has No Owner

That is not controlled deferral.

That is drift.

A postponed issue needs ownership, timing, and a trigger.

━━━━━━━━━━━━━━━━━━━━

The Same Classification Gap Returns Next Storm

If the issue returns, the postponement failed or the return point was not honored.

That is a signal for stronger ownership.

━━━━━━━━━━━━━━━━━━━━

Why This Matters for Public-Sector Leaders

Public-sector leaders operate where public trust, limited resources, staff capacity, and live consequence meet.

In emergency communications, that pressure is sharper.

The call floor does not get to pause because a side issue appeared.

Residents keep calling.

Call-takers keep answering.

Dispatchers keep coordinating.

Supervisors keep making priority decisions.

The public does not see the training gap, the routing weakness, or the message confusion.

The public feels whether the system answers, understands, prioritizes, and routes the call correctly.

That is why side issues are dangerous during live operations.

They can look responsible.

They can feel urgent.

They can be serious enough to deserve action.

But if the leader lets every real issue become the right-now issue, the floor loses sequence.

Emergency call flow weakens.

Supervisors split attention.

Call-takers get mixed signals.

Dispatch coordination can suffer.

The best public-sector leaders do not ignore real side issues.

They control them.

They protect the main effort and make sure the side issue returns when it belongs.

That is Identify and Postpone.

━━━━━━━━━━━━━━━━━━━━

Where Identify and Postpone Fits

This is where Identify and Postpone fits.

It helps leaders control real issues that appear at the wrong time.

It does not replace judgment.

It protects judgment from being pulled away from the main effort too early.

It does not tell leaders to ignore the issue.

It tells them to capture the issue, protect the current objective, assign ownership, set the return point, and watch the trigger.

In this case, the objective is emergency call flow, life-safety triage, dispatch support, abandoned-call control, and floor stability.

The training gap matters.

It just does not automatically outrank the live call surge.

A full Identify and Postpone application goes deeper than this blog.

Inside the DEPN training path, leaders learn how to control timing, ownership, return points, triggers, fallback options, and communication so postponed issues do not become forgotten issues.

This article is the recognition layer.

The course teaches the execution layer.

━━━━━━━━━━━━━━━━━━━━

What to Practice This Week

During the next live operation, watch for the first side issue that tries to take over the room.

Then write five lines:

The current objective is:

The side issue is:

If we chase it now, we risk:

If we ignore it completely, we risk:

The return owner and trigger are:

Then decide whether the issue belongs now or later.

Do not let visibility set priority.

Do not let frustration set priority.

Do not let concern set priority.

Protect the main effort and bring the issue back on purpose.

━━━━━━━━━━━━━━━━━━━━

Final Thought

The training gap does not have to steal the 9-1-1 call surge.

The leader has to separate the current objective from the side issue before the floor drifts.

A training issue matters.

A public message issue matters.

A non-emergency routing issue matters.

A call classification issue matters.

But timing matters too.

If the issue damages live emergency triage, act.

If it does not, capture it, assign it, schedule it, and track the trigger.

That is not ignoring.

That is operating discipline.

The call floor needs control.

The issue needs ownership.

Both can be true.

The leader’s job is to protect the main effort without losing the problem.

Capture the issue.

Protect the surge.

Bring it back on purpose.

━━━━━━━━━━━━━━━━━━━━

Start where you are.

Use the Public Sector Direct Action Starter Sheet before you react, correct, delegate, escalate, promise a public answer, or make the next public-service call under pressure.

Identify and Postpone sits inside Decision Execution and Problem Navigation.

DEPN helps leaders move through the problem once the situation is clearer and the next decision needs structure.