Primary Alternate COntingency and Emergency

Emergency Planning is like an Ogre or an Onion. It needs to have layers. The PACE methodology gives us guidance to adding layers to our contingency plans. This tool walks you through setting up a PACE plan for communications

PACE Planning (Primary, Alternate, Contingency, Emergency) PACE planning is a structured method used to ensure reliable communication and operational continuity when systems fail. It is widely used in emergency management, public safety, the military, and incident response organizations—but it is just as valuable for businesses, nonprofits, families, and volunteer groups.

The core idea is simple: Never rely on a single method of communication. Instead, plan multiple layers that can be used as conditions degrade. PACE stands for:

• Primary – Your normal, everyday system
  
• Alternate – A secondary option if the primary fails
  
• Contingency – A resilient, independent option when normal infrastructure is degraded
  
• Emergency – Last-resort methods when most systems are unavailable
  
• 
  
• Each level should be:
  
• 
  
• Clearly defined
  
• Tested regularly
  
• Known by all participants
  
• 
  
• ⸻
  
• 
  
• Why PACE Planning Matters
  
• 
  
• Modern communication systems are highly interconnected. Power outages, cyber incidents, severe weather, infrastructure damage, or provider outages can quickly cascade into total communication failure.
  
• 
  
• PACE planning:
  
• • Reduces downtime
  
• • Improves coordination during incidents
  
• • Enables faster decision-making
  
• • Prevents single points of failure A good PACE plan assumes failure will happen and prepares for it in advance.
  
• 
  
• ⸻
  
• 
  
• Communications-Focused PACE Example
  
• 
  
• Below is an example PACE plan focused specifically on communications continuity.
  
• 
  
• Primary –
  
• 
  
• Normal Operations
  
• 
  
• These are the systems used during day-to-day operations. Examples:
  
• • Primary internet service provider (ISP)
  
• • Office or home broadband
  
• • Cellular voice and SMS
  
• • Primary email provider
  
• • Cloud-based collaboration tools (Teams, Slack, Google Workspace, etc.) Assumption: Infrastructure is stable and fully operational.
  
• 
  
• ⸻
  
• 
  
• Alternate –
  
• 
  
• Backup Services Alternate systems are used when the primary system is unavailable or unreliable but infrastructure is still mostly intact. Examples:
  
• 
  
• • Secondary ISP or mobile hotspot
  
• • Backup cellular carrier or eSIM
  
• • Web-based communication tools (Zoom, Signal, WhatsApp, webmail)
  
• • Loaner phones or laptops
  
• • Backup power for networking equipment Assumption: Internet and cellular networks still exist, but primary providers are impaired.
  
• 
  
• ⸻
  
• 
  
• Contingency –
  
• 
  
• Independent Connectivity Contingency options are used when traditional internet or cellular service is significantly degraded or unavailable. Examples:
  
• 
  
• • Starlink or other satellite internet services
  
• • Portable satellite terminals
  
• • Fixed or mobile satellite phones
  
• • Pre-positioned communication kits
  
• • Dedicated incident communications devices Assumption: Local or regional infrastructure is disrupted, but satellite systems remain functional.
  
• 
  
• ⸻
  
• 
  
• Emergency –
  
• 
  
• Infrastructure-Independent Communications Emergency systems are used when most modern infrastructure is unavailable. Examples:
• • Amateur (Ham) radio (VHF/UHF/HF)
  
• • Local repeater networks
  
• • Simplex radio operations
  
• • Emergency nets and scheduled check-ins
  
• • Pre-defined radio frequencies and call signs Assumption: Power, internet, and cellular services may be unavailable or unreliable.
  
• 
  
• Ham radio is especially valuable at this level because it:
  
• • Does not rely on the internet or phone networks
  
• • Can operate on generator, battery, or solar power
  
• • Enables long-distance and local communication
  
• • Integrates with emergency management and volunteer networks
  
• 
  
• ⸻
  
• 
  
• Best Practices for PACE Planning
  
• 
  
• • Document the plan and make it accessible
  
• • Train and practice using alternate and emergency systems
  
• • Assign roles and responsibilities
  
• • Test regularly (especially contingency and emergency layers)
  
• • Update after incidents or technology changes PACE plans should be living documents, not one-time checklists.
  
• 
  
• ⸻
  
• 
  
• Final Thought PACE planning is not about preparing for the worst—it’s about ensuring communication never becomes the failure point. When one system fails, another is already waiting.