Business continuity programme Gantt chart template with exercises

What the business continuity programme gantt chart template with exercises process is

A continuity programme looks like one big document, but it is a chain of decisions that each depend on the one before. You cannot choose how fast a process must recover until you know how much damage an outage does. You cannot test a plan nobody has read. Teams that start by writing plans tend to rewrite them once the impact analysis says the priorities were wrong. A timeline makes those dependencies visible before the work starts.

This template has four groups: Scope and impact analysis, Risk and recovery strategy, Plans and awareness, and Exercise, review and upkeep. "Secure executive sponsorship" (3 working days) and "Agree programme scope and policy" (4) come first, because every later task needs someone with authority to pull in process owners. "Run business impact analysis" (10) is the longest early task. "Map critical processes and dependencies" (6) starts 4 days into it, so the mapping follows the interviews as they produce lists. "Impact analysis signed off" is a milestone that waits for both.

The plan has two gates that are easy to skip when time is short. "Set recovery time and point objectives" (3) waits for "Impact analysis signed off", so targets come from the analysis and not from guesses. "Complete risk assessment" (6) waits for the mapping, and "Evaluate recovery strategies" (7) waits for both the objectives and the risk assessment. "Recovery strategies approved" is the milestone before any plan is written. "Write continuity plans" (10) then starts, and "Prepare training and awareness material" (5) starts 5 days into it so training is drafted while the plans take shape.

"Review plans with process owners" (4) leads to the milestone "Plans approved". "Deliver training and awareness sessions" (6) waits for the approval and for the material. Exercises come in order of cost: "Run tabletop exercise" (2) first, then "Run technical recovery test" (4). "Record exercise findings" (3) feeds "Fix gaps and update plans" (8), and "Retest corrected recovery steps" (3) checks the fixes before "Hold management review" (1). "Schedule maintenance and exercise cycle" (2) leads to "Maintenance cycle running". Remediation is the task that slips most, because it depends on what the exercise finds. All durations are illustrative.

A timeline schedules the work. It does not make an organisation resilient, and it does not certify or prove conformity to any standard. For the process steps behind this plan, see the business continuity process at /templates/business-continuity-process and the disaster recovery process at /templates/disaster-recovery-process. For a management-system rollout with the same gate structure, see /templates/qms-implementation-gantt.

What this flowchart covers

In this template

• Four groups, Scope and impact analysis, Risk and recovery strategy, Plans and awareness and Exercise, review and upkeep, with 22 tasks, four of them milestones: "Impact analysis signed off", "Recovery strategies approved", "Plans approved" and "Maintenance cycle running".
• A gate in front of strategy: "Set recovery time and point objectives" waits for "Impact analysis signed off", and "Evaluate recovery strategies" also waits for "Complete risk assessment".
• Overlapping early work: "Map critical processes and dependencies" starts 4 days after "Run business impact analysis" starts, and "Prepare training and awareness material" starts 5 days after "Write continuity plans" starts.
• Exercises in order: "Run tabletop exercise" before "Run technical recovery test", both after "Deliver training and awareness sessions".
• A remediation loop: "Record exercise findings" leads to "Fix gaps and update plans", then "Retest corrected recovery steps", "Hold management review" and "Schedule maintenance and exercise cycle".

When to use this template

• You are starting a continuity programme and need to agree who does what, and in which order, with operations, IT, facilities and the executive sponsor.
• You want to see which gate decides the date, for example the sign-off of the impact analysis or the fixes after the technical test.
• Leadership needs a continuity capability by a date and you want to compare the finish date with the date you need.
• You want a repeatable skeleton to adapt for each site or business unit.

The plan, task by task

Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.

How it works

1. Fix the sponsor and scope first

   Keep "Secure executive sponsorship" and "Agree programme scope and policy" ahead of everything else, and replace the durations with how long your own approvals take.

2. Let mapping follow the analysis

   "Map critical processes and dependencies" is linked start-to-start with a lag of 4 days to "Run business impact analysis". Change the lag if your interviews produce usable lists sooner or later.

3. Keep the strategy gate

   "Set recovery time and point objectives" waits for "Impact analysis signed off". Add tasks for the sites, suppliers or systems your scope includes.

4. Draft training beside the plans

   "Prepare training and awareness material" starts 5 days into "Write continuity plans". Move the lag if your plans change too much for early drafting to pay off.

5. Size the exercises and the fixes

   Set the length of "Run tabletop exercise" and "Run technical recovery test" from the scenarios you will use, and leave real room for "Fix gaps and update plans", since you cannot know its size in advance.

6. Add owners, share and export

   Put the responsible person in People, share the chart with the teams involved, and export a PDF or CSV for the programme file when you need a copy.

Frequently asked questions

How long does a business continuity programme take?

It depends on scope, the number of sites and how quickly process owners respond. The template uses illustrative working-day lengths. Replace them with your own and read the finish date from the chart.

Does the chart make us resilient or certified?

No. It schedules the work. Whether your plans work is shown by your exercises, and any certification or standards conformity is decided by your own assessment, not by a timeline.

Why does the strategy wait for the impact analysis?

Because recovery targets and the money behind them should come from how much an outage costs each process. Starting strategies earlier means choosing solutions before you know what they must achieve.

Why are there two exercises?

A tabletop is cheap and finds gaps in decisions and contacts. A technical test is costlier and finds gaps in systems and recovery steps. Running them in that order puts the cheap findings first.

What happens after the first cycle?

The last tasks set up a repeating cycle. Copy the exercise and review tasks for each round. For the process logic behind the plan, see /templates/disaster-recovery-process, and for the method see /guides/gantt-chart-dependencies.

Related processes

• QMS implementation Gantt chart template for an ISO 9001 style project

  An editable Gantt chart for implementing a quality management system: gap analysis, policy, process mapping, procedures, training, internal audit, management review and the external audit as waits.

  Related

• CAPA Gantt chart template for corrective and preventive action plans

  An editable CAPA Gantt chart: containment, evidence and root cause, an approved action plan, corrective and preventive actions, an effectiveness check window and closure review, with dependencies and milestones.

  Related

• Business continuity process flowchart: invoke to stand-down

  A business continuity process flowchart covering continuity thresholds, the decision to invoke the BCP, BIA-led prioritisation, workarounds and stand-down.

  Related

• Disaster recovery process flowchart (IT systems)

  A swimlane flowchart of the IT disaster recovery process: invocation criteria, RTO and RPO prioritisation, failover, data restore, validation and failback.

  Related

• Medical device development Gantt chart with design reviews and V&V

  An editable medical device development Gantt chart: design inputs, design and development, verification, validation and design transfer, with a risk file kept in step and milestones for each gate.

  Same family

• Regulatory submission Gantt chart template with response window

  An editable regulatory submission Gantt chart: gap analysis, parallel module authoring, internal review, publishing, submission and a window for answering questions, with dependencies and milestones.

  Same family

Part of

• Gantt charts

QueryChart features for this process

• Spreadsheet editor
• Export
• Collaboration