A single PACE plan is not enough. Every operation—whether a military patrol, a community security rotation, or a neighborhood disaster response—moves through distinct phases, and each phase changes what communication methods are available, who you need to talk to, and what can go wrong. A PACE plan built for your rally point will fail during movement. A plan designed for vehicle insertion will be useless once you’re dismounted and stationary. The solution is to build separate PACE plans for each phase of the mission, then explicitly plan the transitions between them.
Why One PACE Plan Fails
The PACE framework (Primary, Alternate, Contingency, Emergency) is a hierarchy of communication methods ranked by reliability and capability. But communication conditions are not static. During a movement phase—driving to a location, patrolling through terrain—you may be limited to handheld radios, hand signals, or vehicle-mounted systems. Once you reach a stationary position, you can deploy directional antennas, establish relay points, or use digital networking tools that would be impractical on the move. The frequencies, the equipment, the people you need to reach, and even the physical environment all shift when the mission transitions from one phase to the next.
A common failure mode is building a single PACE plan during pre-mission preparation and assuming it covers the entire operation. It does not. What works during the deliberate observation phase—say, an HF radio as Primary with a satellite messenger as Alternate—may be completely unavailable during an emergency withdrawal when the team is mobile, dispersed, and under stress. Phase-specific planning forces you to confront these realities before they become crises.
Breaking Operations into Phases
Military doctrine typically divides operations into three or more phases:
-
Insertion / Movement to Objective — The team is mobile, communication windows are compressed, and antenna performance is degraded by vehicle enclosures, terrain masking, or simple lack of time to set up equipment. PACE plans for this phase lean on mobile-friendly methods: vehicle-mounted radios, handheld VHF/UHF, pre-arranged visual signals, or brief scheduled check-ins.
-
Actions on Objective / Deliberate Operations — The team is stationary or semi-stationary. This is where communication capability peaks: field antennas can be deployed, digital networking tools like ATAK become practical, and longer transmissions are feasible. PACE plans for this phase typically expand to include methods that require setup time—HF radio with a wire antenna, satellite communication, or mesh networking.
-
Extraction / Withdrawal — Often the most dangerous phase, because the team is again mobile but may also be fatigued, carrying casualties, or operating under degraded conditions. PACE plans here must be the most robust and the simplest to execute, because cognitive load is highest and equipment may have been lost or damaged.
A complex operation may require five to eight or more distinct PACE plans when you account for communications with internal team elements, partner or adjacent forces, external support (medical evacuation, quick reaction forces), and higher headquarters across each phase. This is not bureaucratic overhead—it is the difference between coordinated action and chaos.
Internal vs. External PACE Plans
Within each phase, a further distinction must be made between internal and external communications:
- Internal PACE covers how team members communicate with each other—hand signals at close range, intra-squad radio nets, visual signals, or simple proximity. These methods are optimized for speed and simplicity.
- External PACE covers how the team reaches entities outside itself—a community coordination net, a quick reaction force, medical assets, or adjacent friendly elements working in a different area. External methods typically require more powerful equipment, longer transmission windows, or relay infrastructure.
Both internal and external PACE plans must be built for each phase. During insertion, internal communication may rely on vehicle intercom or hand-and-arm signals, while external communication runs through a vehicle-mounted radio. During actions on objective, internal shifts to whispered radio traffic, while external shifts to a field-deployed HF set or satellite link. For more on the structural framework that governs these layers, see PACE Planning Framework and Communication Precedence and Phase-Specific Communication Requirements and Role Assignment.
Transition Points: Where Plans Break
The most dangerous moments in any operation are the transitions between phases. A team moving from insertion to actions on objective must switch from mobile communication methods to stationary ones—and there is a window during that switch where neither plan is fully active. Casualties or emergencies occurring during transitions happen in degraded conditions: team members may not be able to hear or see each other, equipment may be in the process of being set up or broken down, and the communication hierarchy is momentarily undefined.
Pre-planned contingencies for transitions are essential. These might include:
- Time-based triggers: “If no communication is established within 15 minutes of arrival at the objective, execute the Contingency method.”
- Event-based triggers: “If contact occurs during movement, revert to the movement-phase Emergency method.”
- Default rally protocols: Pre-designated frequencies, times, and locations that every team member knows, so that even if all electronic communication fails, the team can reconstitute.
This is where pre-mission preparation becomes non-negotiable. Frequency coordination, cryptographic key loading, radio programming, and equipment checks cannot be done during the operation—they require the connectivity and deliberate focus of the preparation phase. As a practical matter, HF radio setup in particular demands internet access for propagation prediction and frequency coordination that will simply not be available in a crisis. Every piece of equipment must be assembled, licensed, programmed, and distributed before the need arises.
Civilian Application: Community Communication Schedules
For the prepared citizen, phase-specific planning translates directly into community communication protocols. A recommended approach is to establish a scheduled communication window—for example, activating radios for three minutes every three hours on a designated channel. This allows news and coordination to flow without draining batteries through continuous monitoring. The only equipment required is a pre-programmed radio and a functioning wristwatch, making the protocol accessible to non-technical community members.
Different groups within a community may warrant separate schedules and frequencies: immediate neighbors on one net, extended community members on another, and tactical partners on a third. The designated radio operator tracks and bridges these clusters. This layered schedule is itself a phase-specific plan—the “steady state” phase has one communication rhythm, while an emergency activation phase would collapse to continuous monitoring on a priority frequency.
Building this kind of structure is part of the broader work of community preparedness and local disaster response, and it depends on the communication infrastructure decisions covered in handheld radio hardware and configuration. The terrain you live in will shape which methods are viable for each phase—see Terrain Impact on Communication Method Selection and PACE Planning for that analysis.
Integration with Mission Planning
Phase-specific PACE planning does not exist in isolation. It is one output of the broader METT-TC planning framework, where Mission, Enemy, Terrain, Troops, Time, and Civilian considerations all feed into communication decisions. The enemy’s electronic warfare capability—their ability to intercept, jam, or direction-find your transmissions—directly shapes which methods you can use in each phase, a topic addressed in Enemy Electronic Warfare Threats and Communication Vulnerability Assessment. And the commander’s intent, established through mission analysis, determines which communications are mission-critical and which are merely useful.
The core principle is simple: plan the communication for the phase, not for the operation. Build the plan before the crisis. Test it in training. And when the transition comes, know exactly what you are switching to—because that is the moment when communication fails kill.