Defense organizations are required to have Continuity of Operations plans. Most commands have the instruction that requires one. Fewer have the plan itself. And the gap between those two facts is where defense continuity starts to fail.
Why the Plan on the Shelf Isn’t the Program You Think It Is
Ask a defense Continuity Program Manager (CPM) a simple question: can I see your command’s current Continuity of Operations (COOP) plan? The answer, more often than it should be, reveals something the inspection process was not designed to catch.
At some commands, the answer is the plan itself — a current, maintained document that reflects the command’s mission, people, and dependencies as they exist today. At many others, the answer is different. It may be the policy directive or the local instruction that requires a plan to exist, handed over in place of the plan itself. It may be an older version, written under a previous commander, against a mission that has since changed. It may be a binder on a shelf that nobody has opened in two years, with contents so generic they could describe any command. Sometimes the answer is that nobody is sure where the plan is, or who owns it, or whether it was ever actually produced.
Each of these is a different failure mode, but they share a common feature. The documentation chain that policy requires has been partially satisfied. The instruction exists. The designation letter exists. The annual review memorandum exists. What is missing is the document those other documents are supposed to be about — and the program that document is supposed to describe. This is the gap between plans and execution, and it is the first and most foundational problem in defense continuity.
What a Plan Actually Is
A COOP plan captures what leadership agreed to on the day it was written. It names the essential functions, the alternate facilities, the succession order, the communications paths, the resources required. It reflects the best thinking of the people who built it, working from the information they had, under the assumptions that applied at the time. That is not nothing. A command with no plan at all is worse off than a command with a plan that needs updating. The plan is the starting point.
The starting point is not the finish line. Federal Continuity Directives (FCDs) require plans. Department of Defense (DoD) policy requires plans. Inspection regimes verify that plans exist. None of this guarantees that the plan reflects current reality, that the assumptions still hold, or that the people named in it are still in the roles the plan assigned them. A fully compliant plan can be completely inaccurate by the time an actual disruption tests it. Compliance measures whether the document was produced. It does not measure whether the document is still true.
The Difference That Matters
A continuity plan and a continuity program are not the same thing, and conflating the two is the single most common mistake commanders and CPMs make when they assess where their command stands.
| The Plan | The Program |
|---|---|
| A snapshot of intentions on the day it was written | An ongoing discipline that keeps intentions aligned with reality |
| Static — ages between reviews whether or not anyone notices | Dynamic — updated as people, missions, and dependencies change |
| Satisfies inspection requirements when current | Satisfies execution when it is tested by a real disruption |
| Describes what the command intended under stress | Delivers what the command actually does under stress |
| The document the program is supposed to produce | The discipline that keeps the document accurate |
A plan is a snapshot of intentions at a point in time. A program is the discipline that keeps those intentions aligned with reality as the command changes — people rotate, missions shift, contracts recompete, facilities change, dependencies appear and disappear. When conditions are stable, the plan and the program look identical, and the distinction feels academic. The distinction becomes visible the moment reality stops matching the assumptions the plan was built on — which is exactly the moment a continuity program is supposed to matter. Most defense organizations have built the plan. Few have built the program.
Three Structural Forces That Widen the Gap
Three forces push defense continuity programs toward the plan-as-artifact failure mode.
Compliance metrics reward documents, not capability. Inspectors check whether the plan exists, whether the annual review was completed, whether training records are on file, whether the last tabletop exercise produced an after-action report. These are verifiable outputs. They are not capability measurements. An inspector cannot, in a two-day visit, determine whether personnel would actually execute under stress, whether alternate facilities have current credentials, whether succession would function if the first two names on the roster were unavailable. The audit stops at documentation. Commands optimize for what they are measured on, and when measurement stops at the document, the program stops there too.
Continuity competes with primary mission tempo. In every defense organization, continuity is a secondary discipline that shares time and attention with the command’s primary mission. Operational requirements win that competition because they have to. Training time, exercise resources, leadership attention, and staff cycles flow toward whatever the command is currently measured on — and the command is rarely measured on continuity until something fails. Capability requires sustained engagement. Sustained engagement does not happen on residual time.
The role is under-resourced and under-defined. The person responsible for the continuity program at most commands is performing the role as a collateral duty alongside one or two primary jobs. Current federal continuity policy and Department of Defense Instruction (DoDI) 3020.26 require that a CPM be designated. Neither document specifies prerequisite training, certification, or experience for the role. The policy mandates the position without defining what qualifies someone to fill it. This is not the fault of the people filling those billets. It is a structural choice that guarantees the program will be sustained only as far as the individual’s capacity allows — and individual capacity, against two or three competing duties, is rarely enough.
What Execution Actually Requires
A continuity program that functions when tested is the product of five things a plan alone does not provide. A commander reading this list should be able to walk it over to their CPM and ask which of the five currently exists at the command in a current, defensible form.
The policy tells you what your program must produce. It does not tell you how to produce it. That gap is not the policy’s fault. It is the gap the
profession has not yet built the foundation to close.
Five Elements That Distinguish a Program from a Plan
- Current MEF analysis. Priority-ordered, with dependencies mapped. Reflects the command as it exists today, not as it existed when the plan was last written.
- Validated dependencies. Personnel, systems, contracts, vendors, facilities, communications — checked regularly, not assumed. Each dependency verified to still hold under current conditions.
- Execution-focused exercises. Scenarios that stress the program against realistic constraints and expose gaps before an actual disruption does. Not compliance events. Not demonstrations.
- Leader integration. The commander knows the program in more than an administrative sense. Can name the top-priority essential functions. Asks continuity questions in operational contexts.
- Sustainment discipline. The MEF analysis is updated. The dependency map is validated. The exercise schedule is populated. The program is maintained between inspections, not rebuilt before them
Figure 2. The five elements that distinguish a continuity program from a continuity plan. A plan may satisfy inspection. Only the program survives execution.
Why the Gap Matters Now
The gap between plans and programs has always mattered. What is changing is the visibility of the gap. Federal efficiency reviews are moving faster. Disruption events are arriving more frequently and from more directions. Commands are being asked questions about their operational resilience that plans alone cannot answer.
A command that can demonstrate a working continuity program — current analysis, validated dependencies, realistic exercises, integrated leadership, sustained discipline — can answer those questions with specifics. A command with a plan and nothing else can answer them with generalities, and generalities do not hold up when the question is what specifically will continue to function if a named event occurs. The gap that used to be invisible is becoming visible.
The first step toward closing the gap between documentation and execution is naming it. Not in an inspection brief. Not in an annual review memorandum. In the command’s own internal assessment of where it stands. A command that can say plainly “we have the instruction but not the plan” or “we have the plan but not the program” is further along than a command that still believes the binder on the shelf is a working capability.
The plan is the snapshot. The program is the discipline. Your command needs both. Most commands have only one.
About Vision Continuity
Vision Continuity is a Service-Disabled Veteran-Owned Small Business (SDVOSB) that specializes in providing defense continuity expertise and leadership advisory services. With a team of certified defense continuity experts, Vision Continuity helps elevate client continuity programs from compliance-focused to establishing a culture of resilience that translates into durable readiness.
