Plan Development and Implementation
What you must understand
Plan development converts strategy into actionable documents. Candidates should know the anatomy of a BC plan: purpose/scope, roles and responsibilities, activation criteria and authority, notification procedures, recovery procedures and sequence, resource requirements, interdependencies, communication plans, and appendices (contact lists, vendor lists, site details). Understand the concept of plan hierarchy: emergency response plan, crisis communication plan, business continuity plans (by function), IT disaster recovery plan, and supplier plans. Know that plans must be usable under stress - clear, concise, role-based, and accessible when systems are down. Understand implementation: assigning owners, acquiring resources, training, and integration with other management systems.
Traps in questions
- Writing plans that are too detailed to use during an incident; usability beats completeness.
- Omitting activation criteria and authority - who declares a disaster and when.
- Assuming one plan covers everything; recognize the plan hierarchy and interfaces.
- Storing the only copy where it is inaccessible during the outage.
Worked example / rule of thumb
A plan lists every procedure but never states who can activate it. That is a defect: without activation authority, recovery stalls. Rule of thumb: every plan must answer Who, What, When (trigger), and How - and be readable by a stressed person at 2 a.m. Keep detailed procedures in annexes; keep the core plan short.