CONFIDENTIAL

[Department Name]

BUSINESS CONTINUITY PLAN

This plan will be reviewed once annually and immediately after any major changes to the working of the department, or the products and services provided.

Owner
Version
Date last reviewed
File location


Contents

1. Key Contacts 3

1.1 Department Incident Management Team 3

1.2 Location of the Department Call Cascade 3

1.3 Useful Internal [e.g. departments you usually interact with] Contacts 4

1.4 Useful External Contacts [e.g. could be key suppliers] 4

2. Department Incident Management Team Information 5

2.1 Plan purpose and scope 5

2.2 Products and services timescales for resumption 5

2.3 Triggers for invoking the plan 5

2.4 Incident flow chart 6

2.5 Meeting venues 7

2.6 Teleconference details 7

3. Roles & Responsibilities 8

4. Workarounds 9

4.1 Workarounds for [name of product or service] if [insert resource e.g. building] is unavailable 9

4.2 Workarounds for [name of product or service] if [insert resource e.g. IT application] is unavailable 9

4.3 Workarounds for [name of product or service] if [insert resource e.g. telephones] are unavailable 9

5. Procedures 10

5.1 Insert procedure 10

5.2 Insert procedure 10

5.3 Insert Procedure 10

6. Minimum Resource Requirements 11

6.1 [insert name of key product or service] resource requirements 11

6.2 [insert name of key product or service] resource requirements 11

6.3 [insert name of key product or service] resource requirements 11

Appendices 12

A) Incident information management log 12

B) Map & location for meeting venues 13

C) Staff with laptops and VPN 14

D) Useful URL links 15

E) [insert useful information e.g. manual forms] 16

F) Document control & plan distribution list 17

1.  Key Contacts

1.1 Department Incident Management Team

Ref / Name / Incident Role / Contact Numbers
(O) Office
(M1) Work Mobile
(M2) Personal Mobile
(H) Home
1.  / (O)
(M1)
(M2)
(H)
2.  / (O)
(M1)
(M2)
(H)
3.  / (O)
(M1)
(M2)
(H)
4.  / (O)
(M1)
(M2)
(H)

1.2 Location of the Department Call Cascade

Electronic file path
Location of hard copies (securely stored)

1.3 Useful Internal [e.g. departments you usually interact with] Contacts

Ref / Name / Purpose / Contact Numbers
(O) Office
(M1) Work Mobile
(M2) Personal Mobile
1.  / (O)
(M1)
(M2)
2.  / (O)
(M1)
(M2)
3.  / (O)
(M1)
(M2)
4.  / (O)
(M1)
(M2)
5.  / (O)
(M1)
(M2)

1.4 Useful External Contacts [e.g. could be key suppliers]

Ref / Name / Company / Contact Numbers
(O) Office
(M1) Work Mobile
(M2) Personal Mobile
1.  / (O)
(M1)
(M2)
2.  / (O)
(M1)
(M2)
3.  / (O)
(M1)
(M2)
4.  / (O)
(M1)
(M2)
5.  / (O)
(M1)
(M2)

2.  Department Incident Management Team Information

2.1 Plan purpose and scope

[insert purpose & scope of plan – reference interested parties]

Objectives

[insert plan objectives]

2.2 Products and services timescales for resumption

Ref / Product and/or Service / Maximum Acceptable Outage / Recovery Time Objective
1. 
2. 
3. 

2.3 Triggers for invoking the plan

The Department Incident Management Team will be informed of an operational disruption and liaise as agreed:

Type / Trigger
Operations / [disruption to...]
Information Security / [disruption to...]
Data protection

2.4 Incident flow chart

2.5 Meeting venues

Location / Facilities
Within the building
[Room number] / E.g. capacity of room, video conferencing
External close by
[Room number]
[Address]
External further away
[Room number]
[Address]

2.6 Teleconference details

Conference Telephone Number / [insert]
Moderator Passcode / [insert]
Participant Passcode / [insert]

3.  Roles & Responsibilities

Ref / Incident Role / Responsibility
1.  / Department Incident Management Team Leader / ·  Liaising the department Incident Management Team when trigger reached.
·  Informing the Corporate Business Continuity Team of the incident and updating them as necessary.
·  Chairing department incident meetings.
·  Overseeing the implementation of the Business Continuity Plan.
2.  / Department Communications Lead / ·  Completing and maintaining the incident information management template from discussions in department Incident Management Team meetings and circulating to the agreed distribution list.
3.  / Department Operations Team member / ·  Resolving the actual issue.

4.  Workarounds

Below are the workarounds which detail how the product or service will be continued during an incident (e.g. denial of access to work premises, loss of IT, telephony, key supplier).

4.1 Workarounds for [name of product or service] if [insert resource e.g. building] is unavailable

Ref / Actions / Responsible
1. 
2. 
3. 
4. 
5. 

4.2 Workarounds for [name of product or service] if [insert resource e.g. IT application] is unavailable

Ref / Actions / Responsible
6. 
7. 
8. 
9. 
10. 

4.3 Workarounds for [name of product or service] if [insert resource e.g. telephones] are unavailable

Ref / Actions / Responsible
11. 
12. 
13. 
14. 
15. 

5.  Procedures

Below are the procedures to help implement complex actions in the Workarounds section.

5.1 Insert procedure

5.2 Insert procedure

5.3 Insert Procedure

6.  Minimum Resource Requirements

Below are the minimum resources required to continue the delivery of agreed products and/or services during disruption.

6.1 [insert name of key product or service] resource requirements

Timescale / Staff / Mac / PC / IT applications / Telephone / Supplier
4 hours
1 day
2 days
1 week
1 month
Total

6.2 [insert name of key product or service] resource requirements

Timescale / Staff / Mac / PC / IT applications / Telephone / Supplier
4 hours
1 day
2 days
1 week
1 month
Total

6.3 [insert name of key product or service] resource requirements

Timescale / Staff / Mac / PC / IT applications / Telephone / Supplier
4 hours
1 day
2 days
1 week
1 month
Total

Appendices

A)  Incident information management log

[insert the file path of where the log template is stored electronically and where hard copies of the log template can be found]

B)  Map & location for meeting venues

Address

Room number

1st line of address

2nd line of address

Town/City

Postcode

Map

Additional Information

C)  Staff with laptops and VPN

Ref / Name / Laptop (Yes / No) / VPN (Yes / No)
1. 
2. 
3. 
4. 
5. 
6. 
7. 
8. 
9. 
10. 
11. 
12. 
13. 
14. 
15. 

D)  Useful URL links

These are helpful if you are working on a different computer and do not have access to ‘My Favourites’ on the internet browser.

Ref / URL
1. 
2. 
3. 
4. 
5. 
6. 
7. 
8. 

E)  [insert useful information e.g. manual forms]

F)  Document control & plan distribution list

To ensure the implementation of this plan is effective and efficient, the plan is subject to the following review schedule:

·  All contact details contained within the plan will be reviewed bi-monthly;

·  Plan sections will be reviewed immediately after every exercise;

·  The whole plan will be reviewed by the department Incident Management Team Leader once annually;

·  The plan will be reviewed immediately after any major changes to the working of the department, or the products and services provided.

Change control history

Plan Version / Date of Change / Change Made / Responsible

This plan is distributed to the following staff

Ref / Full Name / Job title
1. 
2. 
3. 
4. 
5. 

[Name of department] Business Continuity Plan Page 2 of 17