← University
Testing and Exercising Your Continuity Plan
0 of 4

A business continuity plan dated 18 months earlier sits in a 3-ring binder on a shelf in the operations manager's office at a regional food processing facility in southern Alberta. The document runs to 47 pages and includes emergency contact trees, supplier backup arrangements, IT recovery procedures, and protocols for relocating production to a secondary site if the main facility becomes unusable. The plan was developed over 6 months by a cross-functional team that included the operations manager, the plant supervisor, the IT coordinator, and a consultant retained for the project. When completed, the chief executive signed off on it and the board of directors received a summary at their quarterly meeting. Since then, the plan has remained untouched.

The facility processes and packages agricultural products for distribution to grocery chains across western Canada. It employs 83 full-time staff and operates 2 production shifts, 5 days per week. The organization's primary risks include equipment failure, supply chain disruption, food safety incidents requiring product recall, and loss of access to the facility due to fire, flood, or severe weather. The continuity plan addresses each of these scenarios in varying levels of detail, with the most comprehensive section devoted to IT system recovery and the least developed section covering manual workarounds for production equipment failure.

In the months since the plan was finalized, several changes have occurred that the document does not reflect. The IT coordinator who helped develop the plan left the organization 8 months ago and was replaced by a new hire who has never seen the continuity documentation. 3 of the 12 suppliers listed in the backup arrangements have changed their terms or ceased operations. The secondary production site identified in the plan, a partner facility 140 kilometres away, underwent a change in ownership and the informal agreement that underpinned the relocation protocol was never formalized in writing. The emergency contact tree includes direct phone numbers for 4 employees who have since departed.

The operations manager has begun raising concerns with senior leadership about the plan's reliability. A near-miss incident 2 weeks ago, when a power surge caused a 4-hour production stoppage, revealed that staff were uncertain about escalation procedures and that the documented backup generator startup sequence did not match the actual equipment configuration. No formal exercise or test of the continuity plan has ever been conducted. The chief executive has asked the operations manager to propose a testing approach that can be completed within the current fiscal quarter without disrupting production schedules or requiring significant additional budget allocation.

Why Untested Plans Fail: The Gap Between Paper and Practice

Every organization that creates a business continuity plan does so with the sincere intention of using it when disaster strikes. The document represents countless hours of analysis, consultation, and careful drafting. It sits in a binder on a shelf or exists as a PDF in a shared drive, ready to guide the organization through fire, flood, cyberattack, or any of the other disruptions that threaten operational survival. Yet when the moment arrives and the plan must transform from document to action, many organizations discover a troubling truth: the plan that looked so comprehensive on paper fails to function in reality. This gap between documentation and execution represents one of the most significant and least understood vulnerabilities in organizational risk management, and it affects Canadian businesses of every size and sector with remarkable consistency.

The phenomenon of plan failure is not primarily about poor planning. Many failed plans were thoughtfully constructed by competent professionals who understood their organizations well. The failure lies instead in the absence of validation, the missing step between creating a plan and trusting that plan with the organization's survival. A continuity plan that has never been tested exists in a state of theoretical perfection, untouched by the messy realities of human behaviour, technological interdependency, and organizational change. It assumes that contact information remains current, that backup systems function as specified, that employees remember procedures they read months or years ago, and that the scenarios imagined during planning bear sufficient resemblance to actual emergencies. Each of these assumptions represents a potential point of failure, and untested plans accumulate these failure points silently over time.

That’s the free preview

You’ve reached the end of what’s open to read. The rest of this lesson is part of a $79 course — purchasing unlocks it, or sign in if you already have access.