Most governments discover the gaps in their continuity planning at the worst possible moment: mid-crisis, when a ministry realizes it has no protocol for keeping essential services running, no clear chain of decision-making, and no shared template with the ministry next door. Grenada faced this problem directly, and the way it solved it offers a practical model for any government serious about disaster risk management.
The Challenge
Before this work began, Grenada’s government ministries and schools each handled disaster risk and operational continuity in their own way, if they handled it at all. There was no standardized framework, no shared vocabulary for risk, and no consistent expectation of what a ministry should do in the first 72 hours after a disruptive event. That inconsistency is common across small and mid-sized governments, and it has a real cost: when a hurricane, flood, or health emergency hits, the ministries that improvise lose critical time, and the ones without a plan often lose services entirely.
The deeper issue wasn’t a lack of willingness. Ministry staff understood the risks their institutions faced. What was missing was a common structure: a way to translate that awareness into a plan that could survive staff turnover, budget cycles, and the pressure of an actual emergency.
The Solution
Working with the World Bank, I led the development of Comprehensive Disaster Risk Management Plans (CDMPs) designed to give every ministry and school a common starting point: a shared template that could be adapted to each institution’s specific mandate without losing the core structure that makes continuity planning work under pressure.
The approach rested on three principles. First, standardization without rigidity: every ministry used the same planning architecture, but the content, risk profile, and operational priorities were tailored to each institution’s actual function. Second, ownership at the ministry level: plans were developed with the people who would have to execute them, not handed down as a compliance exercise. Third, plans had to be usable, not just approvable. A continuity plan that lives in a binder no one has read is not a continuity plan.
The Grenada Template
The CDMP template built for Grenada covers the elements that determine whether a ministry keeps functioning during a crisis or stalls out:
- Risk and vulnerability assessment specific to the ministry’s facilities, staff, and services.
- Essential functions mapping — identifying which services cannot stop, even temporarily, and which can be paused.
- Chain of command and delegation of authority, so decisions don’t stall if key personnel are unreachable.
- Communication protocols, both internal (staff, leadership) and external (public, other agencies).
- Resource and logistics planning, covering alternate work sites, equipment, and supply continuity.
- Recovery procedures that define how the ministry returns to normal operations, not just how it survives the initial event.
What made this template work wasn’t any single component. It was that every ministry could point to the same six elements and know exactly what “done” looked like, which is what standardization is supposed to deliver and rarely does in practice.
Implementation
Implementation was carried out through structured workshops with ministry staff and school administrators, rather than top-down documentation. Each session walked participants through their own institution’s risk profile and essential functions, then built the plan section by section with the people who would be responsible for activating it. This is slower than simply issuing a template and asking for a completed plan back, but it’s the difference between a document that exists and a plan that gets used.
Coordination across ministries was built in from the start. A shared template made it possible for the Ministry of Health and the Ministry of Education, for example, to understand how their plans intersected — where one institution’s continuity depended on another’s, and where response efforts needed to be sequenced rather than duplicated.
Lessons
A few things from this process apply well beyond Grenada:
- A shared template beats a customized one nobody finishes. Ministries with a common structure to adapt moved faster than institutions asked to build a plan from a blank page.
- Ownership determines whether a plan survives contact with a real crisis. Plans built with the people who’ll execute them get used. Plans imposed on them get filed away.
- Continuity planning is a governance exercise, not just a technical one. Chain of command and delegation of authority matter as much as risk assessment.
- Cross-ministry visibility reduces duplicated effort during an actual response. When ministries know each other’s plans, coordination during a crisis is no longer improvised.
None of this requires a government as large as Grenada’s to be relevant. The same standardize-then-adapt logic applies whether you’re planning continuity for six ministries or sixty, and it applies to any organization, public or private, that has more than one operational unit and no shared plan for keeping them running when something goes wrong.
If your organization is working through government continuity planning and needs a framework that ministries and departments can actually adopt, not just file, let’s talk about what that would look like for your context.