Planning Assumptions: The Most Dangerous Sentence in Emergency Management

Every emergency plan has assumptions.

Some are written clearly in the front of the document. Others are hidden inside procedures, checklists, staffing models, communication plans, vendor agreements, mutual aid expectations, and leadership decisions.

The plan may assume roads will be open.

It may assume employees can report to work.

It may assume the backup generator will start.

It may assume cell phones will work.

It may assume partner agencies will be available.

It may assume leadership can meet quickly.

It may assume one person knows how to operate a critical system.

It may assume vendors can deliver supplies during a regional emergency.

Some of those assumptions may be reasonable.

Some may be dangerous.

The problem is not that organizations make assumptions. Planning would be impossible without them. The problem is when assumptions are treated like facts and never tested against reality.

That is when emergency plans become fragile.

Why Planning Assumptions Matter

Planning assumptions shape the entire emergency management program.

They influence staffing, response times, resource needs, communications, continuity strategies, evacuation planning, sheltering procedures, public messaging, recovery priorities, and leadership expectations.

If the assumptions are wrong, the plan may still look polished while being operationally weak.

For example, a continuity plan may assume that employees can work remotely during a facility closure. That sounds reasonable until a storm causes power outages across the same area where those employees live.

A school emergency plan may assume parents can quickly pick up children during early dismissal. That may not be true if roads are flooded, cell service is down, or parents work outside the community.

A small business may assume its key vendor can provide replacement equipment after a disruption. But if that vendor serves the entire region, the organization may be one of many customers waiting for the same limited support.

A local government may assume neighboring jurisdictions can provide mutual aid. That may work during a localized incident. It may not work during a regional hurricane, wildfire, winter storm, cyber incident, or infrastructure failure affecting everyone at once.

The assumption is not always wrong.

But it has to be examined.

Emergency management is not just about asking, “What is our plan?”

It is also about asking, “What has to be true for this plan to work?”

What Emergency Managers and Leaders Often Get Wrong

One common mistake is writing assumptions because the plan template asks for them, then never using them again.

The assumptions section becomes a formality. It sits near the beginning of the plan, usually after the purpose and scope, and no one revisits it during training, exercises, or updates.

That misses the point.

Planning assumptions are not decoration. They are warnings.

They tell the organization where uncertainty exists.

Another mistake is making assumptions too broad to be useful.

Statements like “resources may be limited” or “communications may be disrupted” are true, but they do not tell leaders enough. They do not explain which resources may be limited, which communications may fail, who is affected, what the consequences are, or what the organization will do about it.

Useful assumptions are specific enough to test.

A third mistake is assuming normal operations will continue around the emergency.

Many plans quietly depend on normal conditions. Normal staffing. Normal supply chains. Normal leadership availability. Normal technology. Normal transportation. Normal vendor response. Normal public behavior.

But emergencies are disruptive because they interrupt normal conditions.

If a plan only works when most things remain normal, it may not be an emergency plan. It may be a standard operating procedure with emergency language added.

The fourth mistake is failing to update assumptions after real events.

Every incident, exercise, near miss, disruption, outage, staffing shortage, storm, cyber concern, or supply chain issue teaches the organization something.

If those lessons do not change the assumptions, the plan does not mature.

A Practical Framework for Testing Planning Assumptions

Planning assumptions should be reviewed like any other part of the emergency management program. The process does not need to be complicated. It does need to be honest.

1. Identify the assumptions already in the plan

Start by reading the plan with one question in mind:

What are we assuming will be true?

Look beyond the formal assumptions section.

Review response procedures, continuity plans, communication methods, evacuation plans, staffing models, call lists, vendor contacts, mutual aid agreements, facility procedures, and recovery processes.

Assumptions often hide in plain sight.

If the plan says a department will notify employees, it may assume that department has a current contact list.

If the plan says leadership will coordinate from a primary location, it may assume that location is accessible.

If the plan says remote work will continue, it may assume systems, power, internet, and employee availability are all intact.

Write these assumptions down.

Do not judge them yet. First, identify them.

2. Separate reasonable assumptions from fragile assumptions

Not every assumption is a problem.

Some assumptions are necessary and reasonable. Others are fragile because they depend on one person, one system, one facility, one vendor, one communication tool, or one outside partner.

Fragile assumptions deserve more attention.

Examples include:

Only one person knows how to complete a critical process.
The plan depends on a single communication method.
The organization has no backup location.
The vendor is assumed to respond immediately.
Staff are expected to report even if their families are affected.
Mutual aid is expected during a regional event.
The backup system has not been tested recently.
Leadership authority is unclear if the primary decision-maker is unavailable.

These assumptions may not make the plan fail every time.

But they create risk.

3. Ask what happens if the assumption is wrong

This is the most important step.

For each major assumption, ask:

What if this is not true?

What if staff cannot report?
What if the generator fails?
What if the phones are down?
What if the vendor is unavailable?
What if the building cannot be accessed?
What if the incident affects the whole region?
What if the person named in the plan is on leave?
What if the public needs information before we have full confirmation?

This question turns an assumption into a planning discussion.

The purpose is not to create fear. The purpose is to create options.

4. Test assumptions through exercises

Exercises are one of the best ways to test assumptions.

A tabletop exercise does not need to be dramatic to be useful. In fact, ordinary scenarios often reveal the most practical gaps.

Use scenarios that affect real operations:

A power outage during business hours.
A severe weather warning during a public event.
A network outage during payroll processing.
A facility closure on a Monday morning.
A water outage at a healthcare or school facility.
A staffing shortage during a regional emergency.
A delayed vendor response after storm damage.

During the exercise, pay attention to moments where someone says, “We assumed…”

Those moments are valuable.

They show where the plan needs more detail, more training, more resources, or a better backup option.

5. Assign ownership for the fix

Finding a bad assumption is not enough.

Someone has to own the correction.

If the employee contact list is outdated, who updates it?

If the backup communication method has not been tested, who tests it?

If the continuity plan depends on a single person, who cross-trains another employee?

If the vendor agreement is vague, who reviews it?

If leadership succession is unclear, who clarifies authority?

Assumptions become safer when they turn into assigned actions.

Without ownership, they remain interesting observations.

6. Revisit assumptions on a schedule

Assumptions age quickly.

A plan written two years ago may reflect a different organization. Staff may have changed. Facilities may have changed. Technology may have changed. Vendors may have changed. Community risks may have changed. Leadership priorities may have changed.

Assumptions should be reviewed at least annually and after major incidents, exercises, organizational changes, or operational disruptions.

The plan should not only ask, “Is this section still accurate?”

It should ask, “Are we still assuming the right things?”

That question keeps the planning process alive.

Leadership Takeaway

Leaders should treat planning assumptions as decision points, not background text.

Every major assumption is a place where the organization may need a backup plan, a clearer procedure, a training conversation, a vendor review, a communication test, or a leadership decision.

The value is not in pretending every risk can be eliminated.

It cannot.

The value is in knowing where the plan is strong, where it is fragile, and where the organization is depending on conditions that may not exist during a real disruption.

That awareness improves decision-making.

It also helps leaders avoid false confidence.

A plan can be well-written and still depend on weak assumptions.

Test the Assumptions Before the Incident Does

Planning assumptions are not the enemy.

Untested assumptions are.

Every emergency management plan depends on some version of “we assume.” The responsibility of the planning process is to challenge that sentence before reality does it for you.

That means asking direct questions, testing ordinary disruptions, identifying fragile dependencies, and updating the plan when experience proves something wrong.

The strongest organizations are not the ones that assume nothing will fail.

They are the ones that know what might fail and have already thought through what comes next.

Emergency management planning improves when assumptions are made visible, tested honestly, and corrected before they become operational problems.

Closing Thought

Open one emergency plan, continuity plan, or department procedure and identify three assumptions it depends on. Then ask what happens if each one turns out to be wrong.