Most organizations have thought about emergencies.
Where are the exits?
Who calls 911?
What happens if there is a fire?
Those are important questions.
But there is another question that receives far less attention:
What happens to the work after the immediate emergency?
Who can make decisions if the owner or executive director is unavailable?
Can employees access the records they need if the office is closed?
What happens if email, banking, payroll, a CRM, or another essential technology platform is unavailable?
Can customers still reach the organization?
Which services have to continue immediately, and which can wait?
Who knows how to perform the work if the person who normally handles it cannot?
Those questions are at the heart of Continuity of Operations Planning, commonly called COOP planning.
Continuity is not only about major disasters
It is easy to associate continuity planning with earthquakes, wildfires, floods, or other large-scale emergencies.
Those risks matter. But organizations can lose normal operating capacity for many other reasons.
In November 2026, a series of separate technology failures disrupted major U.S. systems over the course of several days. The disruptions affected Microsoft email services, air travel, banking transactions, United Airlines operations, Apple services including iCloud and Apple Pay, and even an internal National Security Agency network. Federal officials said the incidents were separate technical or maintenance failures rather than evidence of a coordinated cyberattack.[1]
That distinction is important.
An organization does not need to experience a cyberattack or declared disaster to lose access to something essential.
A software update can fail.
A bank can experience an outage.
A telecommunications provider can go down.
A critical employee can become unavailable.
A vendor can stop operating.
A building can become inaccessible.
A storm can take out electricity or internet service.
Operations can be interrupted even when nothing is physically wrong with the organization itself.
Washington businesses saw the other side of continuity risk during the summer of 2026. Severe wildfires across Central and Eastern Washington damaged homes, businesses, roads, utilities, agricultural operations, and public infrastructure. The fires forced evacuations, caused widespread power outages, and disrupted essential services. By October, Washington had requested more than $133 million in federal Public Assistance associated with wildfire damage and recovery.[2]
The lesson from both situations is similar:
Organizations cannot control every disruption. They can control how prepared they are to operate through one.
What is COOP planning?
FEMA describes Continuity of Operations as an organization’s effort to ensure that essential functions continue during a disruption of normal operations.[3]
For a business, nonprofit, or public-serving organization, that usually means identifying:
- What absolutely has to continue
- How long each function can reasonably be unavailable
- Who has authority to make decisions
- Which employees or contractors are essential
- What information and systems are required
- What outside vendors or partners the organization depends on
- How customers, employees, funders, regulators, and partners will be contacted
- Where work can occur if the normal workplace is unavailable
- How operations will eventually return to normal
The Washington Emergency Management Division maintains its own Continuity Program and encourages businesses to use an all-hazards approach to continuity planning rather than planning for only one specific type of emergency.[4]
That is an important distinction.
A useful COOP plan should still help if the disruption is a wildfire, a technology failure, an extended power outage, a building closure, a cyber incident, a key-person absence, or something leadership never anticipated.
Emergency planning and continuity planning are related—but they are not the same thing
An emergency plan generally focuses first on life safety and immediate response.
A continuity plan focuses on keeping essential operations functioning during and after the disruption.
For example:
An emergency plan may tell employees how to evacuate the office.
A COOP plan answers:
Where will we work tomorrow?
An emergency plan may establish who calls emergency services.
A COOP plan asks:
Who has authority to approve payroll if the owner is unavailable?
An IT disaster-recovery plan may explain how servers and data are restored.
A COOP plan asks:
What will employees do while those systems are unavailable?
A succession plan may identify who assumes leadership.
A COOP plan asks:
What information, authority, processes, contacts, and resources will that person need to keep the organization functioning?
These plans work together, but they solve different operational problems.
Start with essential functions
One of the most useful exercises in continuity planning is deciding what is truly essential.
During normal operations, almost everything can feel important.
During a disruption, priorities become clearer.
For each major function, leadership should ask:
How long could we stop doing this before there is serious harm?
Some functions may need to continue almost immediately.
Others might tolerate a day.
Some may wait a week.
Others can be temporarily suspended.
Consider functions such as:
- Customer or client communication
- Payroll
- Accounts payable and receivable
- Scheduling
- Contract or grant deliverables
- Regulatory reporting
- Service delivery
- Purchasing
- Records access
- IT systems
- Vendor coordination
- Employee communication
- Insurance reporting
- Banking
- Leadership approvals
Once those functions are prioritized, the organization can identify what each one depends on.
Look for single points of failure
Many continuity problems are not caused by the emergency itself.
They are caused by dependence on one person, one system, one vendor, one location, or one set of records.
Ask:
What happens if the employee who knows the process is unavailable?
Who else knows the password?
Who can authorize a payment?
Where is the vendor contract?
Is the current contact list accessible outside the office?
Can anyone else run payroll?
What happens if the CRM is unavailable?
Does a critical spreadsheet live only on one person’s computer?
Is there a manual process if the online system stops working?
Can employees work from another location?
Does more than one person know how to contact major customers?
These are operational questions, not disaster-management questions.
And that is precisely why COOP planning belongs in everyday operations.
Technology deserves particular attention
Organizations increasingly depend on interconnected technology.
Email may depend on one provider.
Payments on another.
Payroll on another.
Customer records on another.
Scheduling, document storage, communications, accounting, and banking may each involve separate platforms.
A continuity plan should identify which technologies support essential functions and what happens when one becomes unavailable.
That might mean establishing:
- Alternate communication methods
- Offline contact information
- Backup copies of essential records
- Clearly assigned system administrators
- Documented recovery procedures
- Manual workarounds
- Alternate payment processes
- Vendor escalation contacts
- Secure remote-access procedures
Technology redundancy does not mean maintaining two versions of everything.
It means knowing where the organization is vulnerable and what the next step is when something stops working.
People are part of the continuity system
COOP planning also exposes knowledge risk.
Sometimes the most important operational system in an organization is a person.
That person knows:
where the records are,
which vendor to call,
how a complicated report is prepared,
what the client expects,
how the software is configured,
or which workaround keeps a process moving.
If that knowledge is not documented or shared, the organization has a continuity vulnerability even if every piece of technology works perfectly.
Cross-training, procedure documentation, role clarity, and delegated authority are therefore fundamental continuity tools.
Communication should be planned before it is needed
During a disruption, people want information quickly.
Employees want to know whether to report to work.
Customers want to know whether services are available.
Vendors need instructions.
Board members may need updates.
Funders or regulators may need notification.
Trying to determine who should communicate what—and to whom—during the disruption wastes valuable time.
A continuity plan should establish:
- Who communicates externally
- Who communicates with employees
- Where contact information is maintained
- What channels are available
- Who has authority to speak for the organization
- Which stakeholders have priority
- What circumstances require notification to regulators, funders, insurers, or contracting agencies
Prepared communication does not require predicting every possible message.
It requires deciding who owns the communication process.
There can also be legal and regulatory requirements
Not every business is legally required to maintain a formal COOP plan.
However, emergency preparedness and continuity requirements appear in several federal and state regulatory frameworks, and organizations should understand which rules apply to their industry.
For example, OSHA’s Emergency Action Plan standard, 29 CFR 1910.38, requires an emergency action plan when another OSHA standard requires one. Covered plans must address items such as emergency reporting, evacuation, accounting for employees, critical operations, rescue or medical duties, and responsible contacts. Employers with ten or fewer employees may communicate the plan orally when the standard applies.[5]
Washington has corresponding workplace emergency-planning requirements through the Department of Labor & Industries. WAC 296-24-567, for example, establishes required elements for emergency action plans when a particular Washington workplace-safety standard requires one.[6]
Health care organizations may face additional requirements. The HIPAA Security Rule’s contingency-planning standard, 45 CFR §164.308(a)(7), requires covered entities to establish and implement procedures addressing emergencies or other occurrences that damage systems containing electronic protected health information. Required elements include data backup, disaster recovery, and emergency-mode operations.[7]
CMS also requires Medicare- and Medicaid-participating provider and supplier types covered by its Emergency Preparedness Rule to maintain emergency preparedness programs based on an all-hazards approach. CMS identifies four core elements: risk assessment and emergency planning, policies and procedures, a communication plan, and training and testing.[8]
Washington provides another particularly clear business example. State-registered investment advisers are subject to WAC 460-24A-126, which requires written business continuity and succession procedures covering records protection and recovery, alternate communications, office relocation, assignment of duties when key personnel are unavailable, and measures to minimize service disruption and client harm. Washington has also adopted investment-adviser rule amendments effective November 21, 2026, including a requirement to file a copy of the business continuity and succession plan with the Securities Division.[9]
These examples do not mean every organization has the same legal obligations.
They demonstrate something more important:
Continuity is increasingly treated as part of responsible organizational management.
Contract terms, grants, insurance policies, professional licensing requirements, privacy laws, industry standards, and funding agreements may create additional obligations.
Organizations should confirm applicable requirements with the appropriate legal, compliance, insurance, IT, or regulatory professionals.
A COOP plan does not need to begin as a hundred-page binder
For many small businesses and nonprofits, a practical first version can be surprisingly straightforward.
Start with a table.
For each essential function, identify:
Function — What must continue?
Maximum interruption — How long can it reasonably stop?
Primary owner — Who normally performs or oversees it?
Backup — Who can step in?
Systems and records — What information or technology is required?
Dependencies — Which vendors, employees, facilities, or outside partners are needed?
Workaround — What happens if the normal method is unavailable?
Communication — Who needs to know?
Then ask one additional question:
If the organization had to operate differently tomorrow morning, could someone actually follow this plan?
That question often reveals the difference between a document that exists and a continuity plan that works.
Test the plan
A plan that has never been tested contains assumptions.
A simple tabletop exercise can uncover them.
Consider a scenario:
It is 8:00 Monday morning.
The office cannot be accessed for five days.
Email is working, but the shared drive is unavailable.
The person who normally approves payments is unreachable.
Payroll is due Wednesday.
Three clients have active deadlines.
A major vendor needs authorization before noon.
What happens next?
Walking through that scenario with the people who actually perform the work can quickly expose missing contact information, unclear authority, inaccessible records, undocumented procedures, and technology dependencies.
Washington Emergency Management emphasizes planning, training, exercises, evaluation, and improvement as a continuous preparedness cycle—not a one-time document-development exercise.[10]
The purpose is not to prove the organization planned perfectly.
It is to find the weaknesses before a real disruption does.
Continuity is an operational discipline
The U.S. Small Business Administration has continued to emphasize proactive disaster preparation for small businesses, including understanding local hazards, protecting records, reviewing insurance, and developing plans before disruption occurs.[11]
But continuity planning can go further.
It can help an organization understand:
who holds essential knowledge,
where authority sits,
which systems are truly critical,
which vendors represent risk,
which processes lack documentation,
and which functions cannot tolerate prolonged interruption.
Those are valuable findings even if an emergency never happens.
In that sense, COOP planning is not simply preparing for the worst.
It is another way of understanding how the organization actually works.
How BERIDIAN can help
At BERIDIAN, continuity planning begins with operations.
We can work alongside businesses, nonprofits, and public-serving organizations to identify essential functions, understand operational dependencies, document critical processes, and organize the information teams need to continue working when normal operations are disrupted.
Depending on the organization, that may include:
- Essential-function identification
- Process and workflow documentation
- Roles and responsibility mapping
- Delegation and backup planning
- Key contact and vendor documentation
- Records and document organization
- Operational dependency reviews
- Alternate-work process development
- Continuity checklists and tools
- Communication planning
- Tabletop exercises
- After-action reviews and plan updates
BERIDIAN does not replace legal counsel, cybersecurity professionals, insurance advisers, accountants, or emergency-management specialists where their expertise is required.
Our role is to help connect those requirements to the way work actually gets done.
Because a continuity plan should not simply describe what an organization hopes will happen.
It should give the people responsible for the work a practical way to keep moving when business as usual is no longer available.
Sources and Legal References
[1] Reuters, November 18, 2026. U.S. officials reported that the recent disruptions affecting Microsoft services, aviation, banking, government networks and other systems were separate technical incidents, not a coordinated attack.
[2] Office of Washington Governor Bob Ferguson. Washington’s 2026 wildfires damaged homes, businesses, utilities and infrastructure, caused power outages and disrupted essential services; the state subsequently sought more than $133 million in FEMA Public Assistance associated with the disaster.
[3] Federal Emergency Management Agency, Continuity Guidance Circular. FEMA defines continuity around maintaining essential functions during disruption and identifying people, systems, records, authorities and dependencies required to perform them.
[4] Washington Emergency Management Division, Continuity Program and Business Preparedness Resources. Washington provides continuity-planning guidance and encourages an all-hazards approach for government and private-sector partners.
[5] Occupational Safety and Health Administration, 29 CFR 1910.38 — Emergency Action Plans.
[8] Centers for Medicare & Medicaid Services, Emergency Preparedness Rule.
[9] Washington Department of Financial Institutions and WAC 460-24A-126 — Business Continuity and Succession Plan. Existing Washington rules require registered investment advisers to maintain continuity and succession procedures. Adopted amendments effective November 21, 2026 add a continuity-plan filing requirement.
[10] Washington Emergency Management Division, Integrated Preparedness Process.
This article provides general operational information and is not legal, regulatory, cybersecurity, accounting, or insurance advice. Organizations should confirm requirements applicable to their industry and circumstances with the appropriate professional or regulatory authority.
