When you hear the phrase "P.A.C.E. planning," you likely think of radios.
Embedded Files
Step 1: Define Your Scope and Audience
Separate your networks: Build distinct PACE plans depending on who you need to reach (e.g., internal family vs. external emergency services, or local team vs. remote command).
Identify operational functions: Apply P.A.C.E. not just to voice communications, but also to data, power, logistics, or transportation.
Step 2: Establish the 4 Tiers (P.A.C.E.)
Design each tier so that it is distinguishable (no shared single points of failure with the level above it) and feasible with equipment and skills you actually possess:
Primary (P): The ideal, most convenient, everyday method you use under normal "blue sky" conditions.
Examples: Commercial cell phone calls, standard text messages, or office VoIP/Microsoft Teams.
Alternate (A): The first backup method to use when the primary system is degraded, congested, or unavailable.
Examples: Mobile data terminals switching to two-way radio, encrypted messaging apps, or email/social media.
Contingency (C): A more robust or independent technology used when both primary and alternate systems fail.
Examples: Local conventional radio channels, backup generators, or independent satellite hotspots.
Emergency (E): The last-ditch method of last resort. It is often slow, manual, expensive, or inconvenient, and used only when all else fails.
Examples: Direct radio "talkaround" (no repeater/tower needed), satellite PTT devices (like Iridium), pre-designated physical meet-up spots, or physical message runners.
Step 3: Define Clear Triggers
Set transition rules: Establish explicit conditions for when to drop from Primary to Alternate, Alternate to Contingency, and Contingency to Emergency (e.g., "If no cellular signal or text goes through for 15 minutes, switch to...").
Account for duration: Plan for extended outages (weeks instead of hours) and factor in secondary requirements like backup battery power, fuel, and equipment maintenance.
Step 4: Test, Train, and Document
Print and distribute: Put the plan on wallet-sized physical cards or post it where everyone involved can see it (digital-only plans fail if the device dies).
Rehearse regularly: Practice executing each tier during drills or simulated outages so users know how to operate the hardware under stress.
SAMPLE P.A.C.E. PLANS
An Amateur Radio Emergency Service (ARES) Team operates in an environment where secondary systems are just as critical as the radios themselves. To build an effective operational framework, you must establish three distinct, non-interdependent PACE plans (one for Communications, one for Power, and one for Transportation).
Because a single point of failure in one tier cannot overlap with the tier above it, your technical assets must be distinctly segregated.
1. Communications PACE Plan (Internal & Served Agencies)
This plan governs how your ARES team maintains contact with local Net Control, county EOCs, served agencies (like the Red Cross or hospitals), and field units.
Primary (P): Local VHF/UHF Repeater Networks
The Setup: Daily or standardized emergency operations utilizing local, high-elevation coordinated repeaters (e.g., 2-meter or 70-centimeter bands).
Trigger to Drop: Repeater infrastructure goes offline due to structural damage, power grid failure at the tower, or severe RF jamming.
Alternate (A): VHF/UHF Simplex & Tactical Frequencies
The Setup: Direct, peer-to-peer radio contact bypassing repeaters altogether. Teams shift to pre-designated simplex frequencies (e.g., 146.520 MHz or localized tactical channels).
Trigger to Drop: Terrain obstructions, long-distance requirements, or localized structural interference drops signal readability below a readability score of QRK 2 (unreadable).
Contingency (C): HF NVIS (Near Vertical Incidence Skywave)
The Setup: Regional HF networks (typically 40-meter or 80-meter bands) utilizing NVIS antennas to bounce signals over mountains and terrain bottlenecks without infrastructure. This layer incorporates Winlink global radio email for data transmission.
Trigger to Drop: Massive solar flare/geomagnetic storm (EMP or severe HF blackout) renders ionospheric propagation impossible.
Emergency (E): Commercial Sat-Comms or Physical Runners
The Setup: Off-grid commercial satellite messengers (such as Garmin inReach or Iridium PTT devices). If satellite constellations are unavailable or blocked, drop down to physical dispatch runners using printed ICS-213 forms to hand-deliver critical data.
2. Power PACE Plan (Station Continuity)
Radio equipment has high amperage demands during transmission. Your field deployments require a rigorous energy fallback strategy. [1, 2]
Primary (P): Grid AC Power with Inline Smart Charging
The Setup: Commercial utility power feeding the station's main power supplies while simultaneously maintaining a float charge on backup batteries.
Trigger to Drop: Local or regional grid blackout. [1]
Alternate (A): High-Capacity LiFePO4 Battery Banks
The Setup: Deep-cycle Lithium Iron Phosphate (LiFePO4) batteries connected via automated low-voltage disconnects to power 12V DC radio gear instantly without rebooting.
Trigger to Drop: Battery banks deplete to critical thresholds (e.g., below 11.5V) during extended 48+ hour deployments.
Contingency (C): Portable Inverter Generators
Emergency (E): Solar Array Recharging & Manual Crank Systems
The Setup: Portable, foldable solar panels (100W–200W) paired with MPPT solar charge controllers to slowly rebuild battery capacity using solar index windows. Ultra-low power QRP (5-watt) radio operations are enforced to maximize efficiency. [1]
3. Transportation PACE Plan (Logistics & Deployment)
An ARES team must physically move personnel, mobile command trailers, and repeaters into disaster zones regardless of road conditions. [1]
Primary (P): POV (Privately Owned Vehicles) via Main Arteries
The Setup: Standard member sedans, SUVs, and trucks navigating primary highways and local paved routes to report to the EOC or staging areas.
Trigger to Drop: Debris fields, severe structural road damage, or gridlocked evacuation routes blocking standard transit.
Alternate (A): High-Clearance 4x4 & Off-Road Fleet
The Setup: Pre-arranged team members with dedicated 4WD trucks, winches, and off-road capability utilizing secondary dirt roads, bypasses, or driving over minor debris field clearings.
Trigger to Drop: Flash flooding, total road washouts, structural bridge collapses, or fuel rationing mandates.
Contingency (C): Mutual Aid, Public Safety, or Foot Mobilization
The Setup: Requesting logistical transport assistance directly from your served agencies (e.g., riding inside a Sheriff’s high-water vehicle, National Guard transport, or official EMA vehicles).
Trigger to Drop: Emergency services assets are entirely committed to search-and-rescue and cannot spare transport resources.
Emergency (E): Foot March with "Go-Kits" / Backpacking
The Setup: Deployment via foot. Operators strip down their gear to lightweight, wearable "Go-Kits" (handheld transceivers, roll-up J-pole antennas, and compact batteries) to hike directly into the disaster site or shelter location.
Building Your Operational PACE Plan
Your PACE plan must reflect realistic operational conditions and team capabilities. For law enforcement applications, this might progress from encrypted radio (Primary) to cellular communication (Alternate) to verbal commands at distance (Contingency) to physical movement for face-to-face communication (Emergency). Military applications might substitute satellite communications or alternative frequency bands in the alternate or contingency tiers.
The critical element is documentation and validation through training. A PACE plan exists on paper initially, but its true value emerges through stress testing under realistic conditions. Training iterations will reveal gaps in your planning—perhaps your alternate method lacks sufficient range, or your contingency protocol proves too time-intensive during dynamic situations. These discoveries allow you to refine your approach, potentially eliminating ineffective tiers or introducing entirely new methods that better serve your operational requirements.
Family and Civilian Applications
PACE planning transcends professional applications. Prepared civilians maintaining a protector mindset should develop communication redundancies for family emergency protocols. When primary cellular networks become congested during regional emergencies, having pre-established alternate methods—whether ham radio, designated rally points, or neighbor networks—ensures family cohesion during crisis scenarios.
The Bottom Line
Communication redundancy isn't optional—it's foundational to tactical success. Your PACE plan represents a living document that evolves through training and operational experience. Document your communication tiers, validate them through realistic training scenarios, and remain willing to modify based on discovered limitations. For specialized communication training and advanced radio operations, resources like Mojave Repeater offer professional-grade instruction that can elevate your communication capabilities beyond basic PACE implementation.
Effective communication wins fights. Plan accordingly.
P.A.C.E. Planning Worksheet
Page updated
Google Sites
Report abuse