Business guides – contracts, HR, AI & compliance

Continuity plan – what should it contain and how is it developed?

A business continuity plan describes how critical operations should continue or be restored in the event of disruptions. See what the plan should include, how it is developed, and how it is tested.
Published Mallbutiken
Continuity plan – what should it contain and how is it developed?

By Mallbutiken · Fact-checked September 30, 2026 · Approx. 9 minutes reading time

A continuity plan describes how an organization will maintain or restore priority activities when normal operations are disrupted. The plan should be concrete enough to be used under time pressure: who activates it, what contingency routines exist, what resources are needed, who should be contacted, and how does the return to normal operations take place?

The most important thing: A continuity plan should not be a general list of risks. It should be based on the organization's critical activities and describe actual measures to continue delivering at an acceptable level during a disruption.

Continuity plan, crisis plan, and incident plan – what is the difference?

Document Primary focus
Continuity plan How priority activities continue or are restored when normal resources are unavailable.
Crisis plan Management, coordination, communication, and decision-making during a major disruption or crisis.
Incident response plan How a specific incident is detected, analyzed, contained, escalated, and closed.

These documents often overlap. For example, a cyber incident may trigger incident response, crisis management, and the continuity plan simultaneously. Therefore, roles and communication channels must be coordinated.

What should a continuity plan contain?

1. Purpose, scope, and owner

Describe which operations the plan covers, who is responsible for it, and the assumptions it is based on. If there are multiple plans, it should be clear how they relate to one another.

2. Activation criteria

Specify when the plan should be used. This could be when a critical activity is judged to exceed its maximum tolerable downtime, when a key facility becomes inaccessible, or when a central system cannot be restored within the standard incident process.

3. Priority activities and recovery objectives

The plan should be based on a Business Impact Analysis (BIA). List the activities that must be prioritized and the relevant recovery objectives. Read how to conduct a Business Impact Analysis before setting time targets without an operational basis.

4. Roles and decision pathways

Specify who makes the decision to activate the plan, which function owners lead the recovery, who communicates, and who documents the course of events. Use roles rather than just personal names, and supplement with an up-to-date contact list.

5. Contingency routines

Describe how work can continue at a lower but acceptable level when the normal solution is unavailable. A contingency routine must be practically feasible, not just the phrase "work manually."

6. Critical resources and dependencies

  • Personnel and backups.
  • Systems, data, and access permissions.
  • Facilities and workstations.
  • Communication and networks.
  • Suppliers and external services.
  • Equipment, spare parts, and inventory.
  • Documentation and contact details.

7. Communication plan

Determine which groups need information, who approves messages, and what alternative communication channels exist if normal email or telephony is down.

8. Return to normal operations

Do not just plan for the initial state. Describe how temporary manual registers will be synchronized, how backlogs will be managed, who approves the return to normal, and how lessons learned are processed afterwards.

How to develop a useful continuity plan

  1. Perform a BIA/impact analysis. Identify what is critical and how long downtime can be tolerated.
  2. Assess risks and existing capabilities. Which scenarios and vulnerabilities could disrupt critical dependencies?
  3. Choose continuity strategies. Contingency facilities, redundancy, alternative suppliers, manual work methods, or other solutions.
  4. Write the plan for use under stress. Short instructions, clear roles, checklists, and communication channels.
  5. Test. Verify that the plan works with realistic scenarios.
  6. Address gaps. Document what is missing and who is to solve it.
  7. Maintain. Update following changes and exercises.

Contingency routines must work even when the dependency is gone

A common mistake is for the contingency routine to use the same resource that the disruption has knocked out. If the instructions are only stored in the system that is down, or the backup contact is in the same identity platform that no one can access, the plan has a built-in dependency.

For every critical contingency routine, you should therefore verify:

  • Where can the instructions be found if the standard system is inaccessible?
  • Can access be granted without the standard identity solution?
  • Is there an offline or alternative communication path?
  • What information must be available locally?
  • Can the supplier deliver during the same disruption?
  • How long can the contingency solution be used?

Suppliers are part of the plan

If critical operations rely on SaaS, managed service providers, payment providers, or other external services, contractual terms and continuity capabilities must align with your own goals. Read which cybersecurity requirements may need to be regulated in supplier contracts.

Test the plan – otherwise, you won't know if it works

Exercises do not need to start with an expensive full-scale test. A tabletop exercise can reveal unclear roles, missing phone numbers, or unrealistic time targets. Subsequently, more technical tests can be carried out for, for example, backups, restoration, standby environments, or alternative communication.

Test What it can reveal
Document review Outdated contact details, unclear instructions, and missing dependencies.
Tabletop exercise Decision-making problems, role conflicts, and communication gaps.
Technical restoration test Whether backups, RTO/RPO, and technical dependencies work in practice.
Simulated disruption exercise Whether multiple functions can work together using contingency routines.

After the test, observations should be turned into actionable items with an owner and a deadline. Otherwise, the exercise just becomes documentation of known flaws.

Continuity and the Cybersecurity Act/NIS2

For operators covered by the Cybersecurity Act, operational continuity and crisis management are among the areas that security measures must at least address. The law requires appropriate and proportionate measures based on the risk profile; it does not stipulate that all organizations must use an identical continuity template.

This means that documentation needs to be tied to the actual operation. A finished document without an established BIA, clearly defined responsibilities, tests, and actual contingency solutions is not the same as having functional continuity capabilities.

Checklist before finalization

  • Are the scope and owner of the plan clear?
  • Is the prioritization based on a current BIA?
  • Are there clear activation criteria?
  • Are roles, backups, and communication channels up to date?
  • Are there realistic contingency routines for the most important activities?
  • Are external suppliers and subcontractors included?
  • Can the plan be accessed if the standard IT environment is down?
  • Is the return to normal operations described?
  • Has the plan been tested and are there documented improvement measures?
  • Is there a date and owner for the next review?
Continuity plan and BIA template package for companies

Combine analysis, plan, and measures into one workflow

Mallbutiken's Continuity Plan + BIA package contains templates in Word, PDF, and Excel for impact analysis, dependencies, recovery objectives, contingency routines, and action planning. Store price: 249 SEK.

See Continuity Plan + BIA

Frequently asked questions

Must the continuity plan cover every conceivable crisis?

No. A robust plan is better off focusing on the loss of critical resources and operational needs rather than a long list of specific scenarios.

Is backup the same as continuity?

No. Backup is an important control for data and restoration, but continuity also includes people, processes, facilities, suppliers, communication, and decision-making capabilities.

How detailed should the plan be?

Detailed enough that a prepared person can act during a disruption without having to reinvent the workflow. At the same time, too much background text can make the plan difficult to use.

Templates in this article

Explore the topic

Back to blog
Customers rate us 4.6/5 based on 10261 reviews.