The federal continuity policy framework has been rewritten. The new Federal Continuity Directive series is not a cosmetic update – it redefines what a viable Continuity of Operations program has to do, and most commands have not yet recognized the shift.
Between December 2023 and August 2024, the Federal Emergency Management Agency’s (FEMA) Office of National Continuity Programs (ONCP) published a new series of Federal Continuity Directives (FCDs) that replaced the framework defense and federal organizations had been working against for nearly a decade. The older series — the FCDs many Continuity of Operations (COOP) program practitioners learned the discipline from — is obsolete. It should not be cited, referenced, or relied on.
This is not a minor revision. It is a different framework, built on a different set of assumptions, that produces a different kind of program. Commands still running continuity against the old FCD model are operating against requirements that no longer exist. They may pass inspections under the new framework. They will not satisfy what the new framework actually demands when it is tested by a real disruption.
Three Structural Shifts
Three structural shifts separate the new FCD series from the framework it replaced. Each one has operational consequences that extend well beyond the documentation a program produces.
Continuity is now explicitly a risk management discipline. Under the old framework, continuity was framed primarily as a planning exercise: identify essential functions, write a plan, maintain the plan, exercise the plan. The new series reframes continuity as a risk management discipline that must integrate into enterprise risk management, strategic planning, and budgeting. Essential functions are no longer just things the organization is supposed to continue performing. They are assets that carry specific risks, require specific mitigations, and must be accounted for in the organization’s broader risk posture. A program that produces a plan and an exercise after-action report every year but is never consulted during strategic planning, budget formulation, or risk decisions is not meeting what the new framework expects.
Accountability is clearer — and sits higher than most commands treat it. The new series defines three distinct roles with specific responsibilities. The Continuity Coordinator is the senior accountable official at the organization level, typically at Assistant Secretary equivalent, responsible for integrating continuity risk into enterprise decision-making. The Continuity Program Manager (CPM) executes the day-to-day program. The Mission Owner is the function leader accountable for essential functions within their specific area of operation. At command and component level, the implication is that continuity is no longer a thing the CPM handles quietly in the background. Mission Owners — the directors and department heads responsible for essential functions — are now explicitly part of the accountability structure.
The operating posture has shifted from React and Relocate to Resilience and Distributed Operations.
This is the most operationally consequential shift in the series. The old FCD framework was built around the assumption that disruption arrives with some warning, leadership has time to activate, and essential functions transfer to an alternate facility. The new series rejects that assumption. It expects programs to be built for scenarios where warning is not available, relocation is not possible, and concentration of personnel or functions at any single site is itself a vulnerability to be mitigated in advance rather than a default posture to be protected.
| React and Relocate | Resilience and Distributed Operations |
|---|---|
| Assumes warning before disruption | Assumes no warning may be available |
| Plans for relocation to alternate facility | Plans for sustained operations without relocation |
| Concentrates leadership and staff at primary site | Distributes leadership and staff as a default posture |
| Treats disruption as a discrete event to respond to | Treats disruption as an ongoing condition to operate through |
| Activation triggers the program | The program is the operating model, not the activation |
Figure 1. The posture shift at the heart of the new FCD series. Both columns describe what a continuity program is supposed to be, not just what it does during an event.
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.
What the Policy Tells You — and What It Does Not
The new FCD series is a requirements document. It tells a CPM, a COOP Planner, and a commander what a viable program must produce. It establishes the roles, the elements, the integration expectations, and the outcomes the program is measured against.
It does not tell anyone how to produce those outcomes. It does not teach a CPM how to conduct a Business Impact Analysis (BIA). It does not walk a COOP Planner through how to identify a Mission Essential Function (MEF) or a Primary Mission Essential Function (PMEF), nor how the identification process has evolved with the retirement of the old directive. It does not explain how to build a dependency map, how to design an exercise that stresses the program meaningfully, or how to integrate continuity analysis with enterprise risk management. The methodology is treated as prerequisite knowledge the practitioner brings to the framework. It is not content the framework teaches.
The new framework tells you what a viable program must produce. It does not tell you how to produce it. That is the gap the profession has not yet built the foundation to close — and the reason most CPMs are improvising against a framework that assumes they are not.
Four Gaps in Programs Built for the Old Framework
A program compliant with the old FCD series can be structurally incomplete under the new one in at least four specific ways.
The essential function list was built without explicit risk analysis. Under the old framework, identifying MEFs was largely a cataloging exercise. The new series expects MEF identification to be tied to a risk analysis that accounts for the specific threats and vulnerabilities affecting each function. A program that produced an MEF list without walking through the risk analysis behind it has an MEF list the new framework does not accept as sufficient on its own.
Continuity is isolated from enterprise risk management. If the organization runs an enterprise risk management process and the continuity program is not a contributing input to it, the program is structurally isolated from the framework the new FCDs assume. Continuity risk is enterprise risk under the new series.
The program still assumes relocation as the primary response. A plan built around alternate facility activation, evacuation timelines, and co-located workforce assumptions was appropriate for the old framework. Under the new series, a program that has not considered how essential functions continue to operate without relocation is operating against assumptions the new framework has explicitly rejected. The posture has shifted. A program that has not shifted with it is preparing for contingencies the framework no longer endorses as the default.
Mission Owners are not active participants. Under the old framework, Mission Owner involvement was often nominal. The new series treats Mission Owners as accountable actors whose functions, dependencies, and risks must be documented and maintained with their direct engagement. A program where Mission Owners cannot, unprompted, name their essential functions and describe the dependencies that sustain them has not integrated the role the new framework assigns to them.
The Re-Examination
The question worth asking is not whether your command is compliant with the old FCD framework. That framework is obsolete. The question is whether your program reflects the new series — whether essential functions are tied to risk analysis, whether Mission Owners are actively accountable, whether continuity outputs integrate with enterprise risk and planning, and whether the operating posture assumes distributed sustainment rather than relocation-on-warning.
A command that has not asked those questions since 2023 has not re-examined its program against the current policy framework. The re-examination does not require rebuilding from scratch. It requires an honest assessment of which elements of the existing program still apply, which are obsolete, and which were never built. Each of these is a finite, bounded piece of work. None of them happens without the decision to start.
The new FCD series is not a minor revision to familiar requirements. It is a different framework that expects a different kind of program. Programs that treat it as a cosmetic update will fall short of what it actually requires. Programs that treat it as a call to re-examine will produce something the old framework never demanded and the new framework explicitly expects — a continuity capability built for the conditions disruption actually produces, rather than the conditions the old framework assumed it would announce in advance.
The policy has been rewritten. The question now is whether your program has been.
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.
