The program nobody runs full-time is the one that has to work under the worst conditions.
In most federal and defense Continuity of Operations (COOP) programs, the person responsible has a different primary job.
At the GS-13 level, the Continuity Program Manager (CPM) is an analyst, a program officer, or an operations coordinator who inherited the binder when the last person rotated out. At the Senior Executive Service (SES) or flag level, the Continuity Coordinator (CC) is an Assistant Secretary or a general officer who gets briefed on the program once a year and signs the plan. The Emergency Relocation Group (ERG) members are functional staff from across the organization who are nominally designated, occasionally trained, and largely unaware of what they would actually be expected to do if the plan activated tomorrow.
This is not a failure of any individual organization. It is the structural reality of how continuity programs are staffed across the federal civilian executive branch, across Department of Defense (DoD) components, across defense agencies, and at the combatant command level. Continuity is a collateral duty. Even at the four-star level, it is a collateral duty. The Commanding Officer who inherited a program at change of command, the newly appointed CPM who was handed the role as an additional responsibility, the Operations Officer asked to coordinate continuity into the command’s battle rhythm, and the COOP Planner trying to produce a plan against framework guidance — all of them are looking at the same structural condition from different angles. This article names it.
A small number of organizations do assign the CPM role full-time, and the people who hold those billets run genuine programs. But staffing model is not the common denominator. The common denominator is training. CPMs arrive in the role — full-time and collateral duty alike — without structured training in continuity as a discipline and without the certifications that would validate methodology rather than inherited practice. The Certified Public Sector Continuity Professional credential from DRI International, the Master Business Continuity Professional (MBCP) credential, and elated certifications are held by a small fraction of the practitioner workforce. Programs are run by people doing their honest best against a framework they were handed and a methodology they were never taught.
The policy framework does not name it clearly. The current Federal Continuity Directive (FCD) series describes Continuity Coordinators, Mission Owners, Continuity Program Managers, and Emergency Relocation Groups as if these are roles that people hold in any meaningful functional sense. In most organizations, they are designations on a roster that get reviewed annually and updated when people change permanent duty stations or separate from service. The roster is current. The capability is not.
Any honest conversation about improving federal and defense continuity programs has to start here. Programs that do not acknowledge this constraint fail when they are actually tested.
What Incident Management Actually Is in Most Federal Organizations
There is a persistent assumption in continuity doctrine that federal organizations have a functioning incident management capability that a COOP program activates alongside. This assumption is wrong in most cases.
The Incident Command System (ICS) and the National Incident Management System (NIMS) exist in federal policy. They do not exist as standing operational capabilities in most federal civilian agencies. What most agencies have is an Occupant Emergency Plan — a building evacuation procedure — and an information technology service desk that tracks system outages in a ticketing tool. Some have emergency operations centers on paper. Few have trained, exercised, standing incident management teams ready to activate.
Incident management in most federal agencies means something specific and unglamorous. A senior official convenes a meeting. People report what they know. Someone takes notes. Decisions get made through normal chains of command under abnormal conditions. That is not ICS. It is management under stress, which organizations do whether they have a plan or not.
The military operates differently. DoD components with operational missions have genuine command and control structures that function under degraded conditions. Operations directorates exist specifically to manage operations in contested environments. But even in defense organizations, the COOP program is typically separate from the operations structure — maintained by a small staff element that is not integrated into the battle rhythm of the command. The gap is not between incident management and COOP as parallel programs. The gap is between what disruption actually demands and what organizations have actually built.
What Disruption Actually Demands
When a significant disruption hits a federal organization — a facility loss, a cyber incident that takes down mission systems, a pandemic that eliminates normal staffing patterns, a leadership succession event — several things have to happen simultaneously, executed by the same people.
The people managing the disruption and the people sustaining the mission are the same people. There is no separate incident management team to hand off to. The deputy coordinating the organizational response is also the deputy whose office is responsible for sustaining three of the organization’s six Mission Essential Functions (MEFs). The information technology director managing the cyber incident is also the Mission Owner for two systems-dependent MEFs. The program manager handling personnel accountability is also the person who knows where the vital records are stored and whether the alternate facility credentials are current.
The doctrine imagines a clean separation between these roles. The organization does not have enough people to maintain that separation, and the doctrine has no realistic answer for organizations operating at the staffing levels that characterize most of the federal government today.
What disruption actually demands is not two programs running in parallel. It is a single organizational capability that embeds continuity requirements into normal operations, so that when disruption occurs, the response is a natural extension of how the organization already operates — not the activation of a separate program that nobody has rehearsed.
| The Framework | The Organization |
|---|---|
| Continuity Coordinator as senior accountable official | Assistant Secretary signs the plan, briefed annually |
| CPM as dedicated role | CPM holds the role as collateral duty |
| Mission Owners accountable for essential functions | Mission Owners unaware of their designation |
| Emergency Relocation Group trained and ready | ERG members nominally assigned, rarely trained |
| All roles functional and integrated | All roles exist on a roster, not in the organization |
The Collateral Duty Problem and What It Actually Means
The collateral duty reality is not a deficiency to fix. It is the operating constraint that shapes the design of most continuity programs. An organization that does not have dedicated continuity staff is not a broken organization. It is the standard federal organization. The program design has to fit that reality, or it will not function.
Continuity capability has to live in the organization’s existing structure, not alongside it. Orders of succession documented but not understood by the successors produce no capability. ERG designations assigned but not trained produce no capability. Vital records identified but not accessible to the people who would need them during a disruption produce no capability. Each continuity requirement must be embedded in a role that someone actually holds and actually exercises — not added to a list of responsibilities that nobody has bandwidth to execute.
The trigger for continuity operations cannot be a separate activation event. The moment a significant disruption begins, the people in the organization are simultaneously managing their normal responsibilities, managing the disruption, and potentially needing to execute continuity procedures. There is no margin in that environment for consulting a plan they have seen once. The procedures that matter under disruption are the ones simple enough to execute from memory, embedded in systems and workflows that are already in daily use, and practiced frequently enough that they do not require a crisis to activate.
None of this is possible without trained practitioners running the program. A CPM without methodology is not a CPM — they are an administrator of a binder. The training gap is not a professional development concern to be addressed when the budget allows. It is the condition that determines whether the program is capable of the design the framework expects. A collateral duty CPM with training can build a program that works within the constraint. A full-time CPM without training cannot build a program that works at any level of resourcing. Staffing model is the visible condition. Training is the load-bearing one.
Continuity capability has to live in the organization’s existing structure,
not alongside it. Orders of succession documented but not understood by
the successors produce no capability. ERG designations assigned but not
trained produce no capability.
The Integration Point That Actually Matters
The real integration needed in federal and defense continuity programs is not between two separate programs. It is between continuity requirements and the normal operational cycle of the organization.
Federal organizations of any size operate on some version of a battle rhythm: planning cycles, budget cycles, operational reviews, leadership transitions, exercise programs, reporting requirements. Continuity requirements embedded in that rhythm survive. Continuity requirements that exist outside it atrophy.
Succession orders should be reviewed when leadership transitions occur — not annually on a compliance calendar. Vital records accessibility should be verified when systems change — not when the plan is updated. ERG readiness should be confirmed when personnel rotate — not at the annual COOP training brief. Alternate facility access credentials should be validated when credentials expire — not when a disruption reveals they do not work.
This is not a sophisticated program design. It is a recognition that continuity capability cannot be maintained as a separate track parallel to normal operations. It has to be integrated into the decisions, transitions, and reviews that already govern how the organization functions.
For Defense Organizations: Continuity Is a Readiness Requirement
The defense context adds a dimension that civilian frameworks do not adequately address. In defense organizations, continuity of operations is not just an organizational survival requirement. It is a readiness requirement — a direct input to the command’s ability to generate, project, and sustain military capability.
A defense logistics organization that cannot sustain its essential functions through a disruption is not just organizationally impaired. It degrades the readiness of the forces it supports. A defense finance organization that loses the ability to process payments and execute contracts is not just having an administrative problem. It is constraining operational options at the command level. A defense communications organization that loses mission-critical systems during a continuity event is not just down on capability. It is creating an information advantage for an adversary who may have caused the disruption deliberately.
These are not continuity outcomes. They are operational readiness outcomes. They require that continuity be treated as a component of unit readiness — assessed, trained, and reported with the same discipline applied to personnel readiness, equipment readiness, and training readiness. Most defense COOP programs are not built this way. They are built as compliance programs: maintained by a small staff element, reported through administrative channels, assessed on documentation metrics, and disconnected from the command’s operational readiness framework.
What a Realistic Program Looks Like
A continuity program designed for the collateral duty reality is simpler, not more complex. It concentrates requirements on the capabilities that actually matter under disruption — the ones that cannot be improvised and cannot be reconstructed in real time.
Each position in the succession order knows they hold it, knows their first actions, and has practiced them at least once. Essential records are accessible to the people who need them from the locations where those people will be when the disruption occurs. Alternate facility access works for the personnel currently assigned, not the personnel who were assigned when the facility agreement was last reviewed. Communications systems have been tested by the people who will use them, not by the information technology team who installed them.
Leadership is engaged not through compliance briefings, but through honest assessment of what the organization can actually do under the conditions that matter — degraded communications, absent personnel, disrupted systems, time pressure — and what it cannot. The program is documented, but the documentation follows the capability. It does not substitute for it.
Defense continuity is a collateral duty. At most organizations, the staffing stack from the GS-13 analyst holding the binder to the flag officer who signs the annual plan is operating under that constraint. The policy framework describes roles the organization cannot actually staff. The doctrine assumes capabilities the organization does not actually have. The programs that result are structured for an organization that does not exist, and they fail for that reason alone.
The answer is not to pretend the constraint is not there. It is not to demand more resources that the department will not provide. It is to build programs for the organization as it actually is, not as the framework assumes it to be. Continuity capability that survives has to be embedded in the work the organization already does, owned by the leaders who already hold the mission risk, and practiced by the people who will actually be present when disruption arrives. Anything else is a program on paper.
The constraint is not the problem to solve. The constraint is the starting point. Programs built from it can work. Programs built around it cannot.
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.
