Typical Business Continuity Plan Content - BBC

1 Document title [ ] Version [ ] Issue date [ ] plan holder [ ] plan authorizer [ ] Next review [ ] Page 1 of 9 Business Continuity TOOLKIT 6. Business Continuity plan [DIVISION/DEPARTMENT] Data Protection The data contained in this plan document are reproduced for Business Continuity and Disaster Recovery purposes only. In order to comply with the Data Protection Act, the Storage, Distribution, use and disposal of this plan document must be controlled by the plan holder as part of a plan Holding Procedure (PHP).

2 Your PHP must be reviewed regularly to ensure contact details are accurate and up to date and to securely delete and/or destroy old contact information. The PHP also should advise staff members to keep the contact information safe and secure and safely destroy old versions when revised details are issued. Your PHP should ideally form part of your Business Continuity and Disaster Recovery Maintenance plan . Failure to adhere to your PHP may constitute a contravention of the Data Protection Act. Next review date for this plan : [ ] Document title [ ] Version [ ] Issue date [ ] plan holder [ ] plan authorizer [ ] Next review [ ] Page 2 of 9 CONTENTS PAGE.

3 Section CONTENTS PAGE 1 Purpose 2 plan activation 3 Scope 4 Assumptions 5 Objectives 6 Priorities 7 Roles and responsibilities 8 Locations 9 Communications 10 Document contact Appendices A HR Support in a major incident B Action Plans/maps/checklists C Contact lists Document title [ ] Version [ ] Issue date [ ] plan holder [ ] plan authorizer [ ] Next review [ ] Page 3 of 9 1. PURPOSE OF plan How will this plan be used? In what situations can the plan be used? Who will use this plan ?

4 2. plan ACTIVATION How the plan can be activated? Which individuals have authority to invoke the plan and under what circumstances? How to mobilize the team Include a process for standing down the incident and returning to Business as usual 3. SCOPE This plan covers the work, people and resources of the [ ] team/area/department/event In developing this plan the following types of situations have been considered: Lack of people Lack of access to/use of work space Lack of Technology / IT infrastructure Lack of suppliers (incl. utilities) You should reference any other relevant plans or documents and where you can find them.

5 4. ASSUMPTIONS In developing this plan the following assumptions have been made: The safety and welfare of staff is paramount at all times All people with a responsibility in this plan have knowledge of this plan Assumptions about the maximum scale of the incident in terms of extent, duration or staff impact should be included here. 5. OBJECTIVES The objectives of the BBC during any incident or interruption to Business as usual are: 1. Ensure the safety of staff and others at the BBC 2. Maintain output 3. Maintain Business as determined by Divisional Priorities 4. Preserve our assets 5. Return to Business as usual The objectives of the team in an incident are as follows: 1.

6 2. 3. Document title [ ] Version [ ] Issue date [ ] plan holder [ ] plan authorizer [ ] Next review [ ] Page 4 of 9 6. PRIORITIES Note your Critical activities to be recovered Timescales in which they should be recovered The level you want to restore the activity to When Business as usual is not possible, the key priorities are: 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] 7. ROLES AND RESPONSIBILITIES plan ownership Who is the plan owner?

7 Who is responsible for maintaining and updating the plan ? Responsibilities This should explain the roles and responsibilities of the people and teams who have authority during and following an incident Who will manage the response of your team? Who is in charge? . It may be better to use job titles rather than names as they change less frequently All people with a role and responsibility in this plan should be aware of the details of the plan . Administrative support Technical support 8. LOCATIONS The usual workplace of the team is [ ] In the event of unavailability of the office, the default meeting locations for the team are as follows: 1.

8 [ ] 2. [ ] 3. [ ] If the office is unavailable for a sustained period of time, the pre-arranged recovery locations are as follows. 1. [ ] 2. [ ] Document title [ ] Version [ ] Issue date [ ] plan holder [ ] plan authorizer [ ] Next review [ ] Page 5 of 9 9. COMMUNICATIONS How the team will communicate Who outside the team you need to communicate with eg suppliers, public, other parts of the BBC Conference bridge details Telephone cascade details How to account for staff You should consider how the team will communicate if there is no access to mobile phones or IT network.

9 Will you all aim to meet at the default meeting location or on a conference bridge? For information on incidents affecting the BBC, staff should check BBC Emergency Information. This can be found on the following channels: Telephone: 0800 0688 159 Twitter: @BBC159 Ceefax: Page 159 Internet: 10. DOCUMENT CONTROL Change made By Date Note Distribution list: [ ] Document title [ ] Version [ ] Issue date [ ] plan holder [ ] plan authorizer [ ] Next review [ ] Page 6 of 9 APPENDIX A.

10 HR SUPPORT DURING MAJOR INCIDENTS Version 5, issued June 2012. Issued by BBC People This document outlines the following information: 1. Line manager HR responsibilities during a major incident 2. Emergency HR support during Business -as-usual 3. HR support during a major incident 1. LINE MANAGER HR RESPONSIBILITIES DURING A MAJOR INCIDENT Line managers are reminded that they have a duty of care with regard to being able to safely account for those working for them during a major incident, and have communications procedures in place for emergencies: Accounting for People: Line managers must have arrangements in place to enable them to account for the safety of people working for them (including staff, casuals, freelancers, temps, contractors, on-air talent and those doing work experience) in the event of an incident.