Building a PACE Communication Plan

A PACE plan is the minimum communication planning standard for any operation. No unit should move without one. This guide walks through building a PACE plan from scratch for a ground element operating in a degraded communications environment.

Why PACE Matters

Radio communications fail. Terrain blocks signals, batteries die, equipment gets damaged, frequencies get jammed. The PACE plan ensures that losing one communication method doesn't mean losing command and control. Each tier activates automatically when the tier above it fails — no confusion, no debate.

Step 1: Define Your Communication Requirements

Before picking methods, answer these questions:

• Who do you need to communicate with? (higher HQ, adjacent units, subordinate elements)
• What information needs to move? (SITREPs, fire requests, CCIR triggers, CASEVAC)
• What range does communication need to cover?
• What are the terrain and weather constraints?

Step 2: Select Communication Methods

For each relationship (unit → higher HQ, unit → adjacent), select four methods:

Tier	Common Methods
Primary	FM tactical radio (secure, assigned frequency from SOI)
Alternate	UHF/VHF radio on alternate frequency, or SATCOM
Contingency	Messenger (runner), relay through adjacent unit
Emergency	Pre-arranged visual signals (VS-17 panel, IR strobe, pyro)

Step 3: Document the Plan

For each tier, specify:

• Method: What means of communication
• Frequency / Channel: Exact frequency or net from SOI
• Call signs: Per SOI
• Authentication: Authentication table entry from SOI
• Trigger: What condition switches you to this tier

Tier	Method	Freq/Channel	Trigger
Primary	FM Radio	46.500	Primary goes down
Alternate	FM Radio	38.750 (alt freq)	Alt net jammed
Contingency	Runner	N/A	Both radio nets unavailable
Emergency	IR strobe + VS-17 panel	N/A	No comms for 15 min

Step 4: Brief and Rehearse

The PACE plan is briefed in OPORD Paragraph 5: Command and Signal. Every leader and radio operator must know it by heart. Rehearse switching tiers — call the alternate frequency, verify comms, switch back. Never assume a backup works until you've tested it.

Step 5: Trigger Conditions

Define exact triggers for switching. Avoid vague language ("when radio fails"). Use observable, unambiguous conditions:

• "If no radio contact with TOC for 10 minutes, switch to alternate frequency."
• "If alternate frequency is compromised or jammed, send runner to CP."
• "If runner cannot reach CP within 30 minutes, initiate emergency signal IAW SOI."

Common Mistakes

• Untested alternates: The alternate frequency was never checked and is out of range
• Forgotten at rehearsal: PACE plan exists on paper but was never briefed to subordinate RTO
• No trigger discipline: Units stay on a failed primary net hoping it recovers instead of switching
• SOI reference missing: Call signs and frequencies not cross-referenced to current SOI cycle