Lesson Overview
Lesson 02 taught you to layer complementary bearers so that no single failure is fatal. This lesson takes the next step: planning so that the communications system keeps doing useful work while parts of it fail, and recovers in a sensible order afterwards. A small humanitarian home-defence force is most likely to be tested not by a clever adversary but by a flat battery, a dead mains supply, a saturated cellular network, or a regional disaster that takes the internet with it. The planner who has thought these failures through in advance keeps the force talking when others fall silent.
The central idea is graceful degradation: a system that steps down through useful levels of service rather than collapsing all at once. A force that can no longer share live maps should still be able to send text over the mesh; a force that loses the mesh should still be able to pass voice traffic by radio; a force that loses its repeater should still be able to work simplex. You design the steps, you decide which links come back first when you start to recover, and you make sure the off-grid bearers at the bottom of the ladder are always there as a floor the force never drops below. This lesson links closely to HCR 220 Emergency Preparedness and Civil Resilience.
This is the knowledge layer. It teaches you how to reason about failure and continuity on paper, in the signals estimate and the communications annex. Hands-on operating, charging a battery pack, flipping a net from repeater to simplex, bringing a mesh node up cold, is practised and signed off in person and on airsoft milsim exercises, and radio is actually transmitted only by licensed members or on licence-free and low-power sets. By the end you will be able to identify the failure modes a small force should plan for, design a graceful-degradation ladder from full service to bare minimum, build a power and continuity plan, set restoration priorities for your links, and explain why HF and Meshtastic are the floor the force never drops below.
Key Terms
- Resilience: the ability of the communications system to keep delivering useful service while components fail, and to recover afterwards.
- Continuity: keeping communications going across a disruption, by planned fallback and by sustaining power, people, and equipment over time.
- Graceful degradation: a design in which loss of capability steps the system down through reduced but still useful levels of service, rather than failing completely.
- Failure mode: a specific way the system can stop working (flat batteries, dead mains, lost internet, jamming, a downed repeater, a disaster).
- Single point of failure: one component whose loss takes down a whole capability, for example a single repeater every unit depends on.
- Floor: the lowest, simplest, infrastructure-free level of service the force is built never to drop below; for the RKA this is HF voice and Meshtastic text.
- Restoration priority: the planned order in which links and services are brought back after an outage, most important first.
- Power budget: the planned reckoning of how much electrical energy each radio and device needs against how much you can carry, charge, or generate.
- Solar / charging chain: the kit and plan that keeps batteries topped up off-grid (panels, power banks, vehicle charging, mains when available).
- Jamming: deliberate interference that swamps a frequency; congestion is the same effect caused by too many innocent users.
- PACE plan: Primary, Alternate, Contingency, Emergency; the ordered list of comms means for a link, the practical tool you use to express fallback.
- Off-grid bearer: a means that needs no fixed infrastructure (no mains, no internet, no repeater), such as HF radio or a LoRa mesh.
Why Resilience Is a Planning Problem, Not an Equipment Problem
It is tempting to think resilience is bought: more radios, bigger batteries, a second repeater. Equipment helps, but resilience is decided on paper, by the planner, before anything is bought or switched on. The questions are these. If this fails, what do we use instead? If the power goes, how long do we last, and how do we recharge? If the internet drops, what still works? If we cannot have everything, what comes back first? A force that has answered these questions in its signals annex is resilient even with modest kit. A force that has not is fragile even with expensive kit.
Two habits underpin everything in this lesson. First, assume failure: plan as if every link will fail at some point, because over a long task or a real emergency it will. Second, avoid single points of failure: if every unit routes through one repeater, one internet line, or one charging point, that thing is a single point of failure and the planner's job is to design around it. Lesson 02 gave you the tool for this already, the PACE plan, choosing bearers that fail for different reasons so one cause does not take them all. This lesson uses PACE as the backbone and adds power, degradation, and restoration to it.
The Failure Modes a Small Force Plans For
A planner cannot defend against threats they have not named. For the RKA, the realistic failure modes are few and worth listing plainly, because the humanitarian and home-defence role makes some of them far more likely than the dramatic ones.
Loss of mains power. The most common failure of all. Devices flatten, the charging point goes dead, a generator runs out of fuel. This is a continuity problem more than a comms problem, and it is solved by a power plan, covered below.
Loss of internet and cellular. TAK over the internet, cellular data, and any cloud service all depend on infrastructure that disasters and outages routinely remove. The planned answer is to fall back to RF and mesh: VHF and UHF voice for talk, Meshtastic for text and positions, HF for distance. The common operating picture may go from a live shared map to position reports read out by voice, but the force keeps functioning.
Jamming and congestion. A frequency can be swamped deliberately (jamming) or innocently (congestion, every agency and member of the public crowding the same channel in a crisis). The effect is the same: your primary frequency becomes unusable. The planned answer is alternate frequencies and bands published in advance, changing band so the interference does not follow you, and falling back to a bearer that does not share the congested spectrum, often the mesh or HF.
Loss of a single shared component. A repeater goes down, the one internet line is cut, the charging trailer breaks. If the force depended on it, capability drops sharply. The answer is to have designed it out: simplex fallback when the repeater dies, a second power source, off-grid bearers underneath.
Disaster conditions. Flood, severe weather, or a wide-area outage can hit power, internet, and access roads at once. This is the scenario that justifies the whole lesson, and it is exactly the HCR 220 case: the force may be operating for days, off-grid, supporting civil agencies whose own communications are also degraded. Everything below assumes this can happen.
Graceful Degradation: Designing the Ladder
Graceful degradation means deciding, in advance, the levels of service the force passes through as capability is lost, so that each level is still useful and the drop between levels is small and understood. You design this as a ladder: full service at the top, the floor at the bottom, defined rungs in between. When a failure occurs, the force knows which rung it has dropped to and what it can still do there. This is far better than an all-or-nothing system that works perfectly until the moment it does not work at all.
The ladder below is the RKA's general model. Read it from the top down as capability is lost, and from the bottom up as you recover.
GRACEFUL-DEGRADATION LADDER (full service at top, floor at bottom)
RUNG SERVICE LEVEL BEARERS WORKING WHAT THE FORCE CAN STILL DO
---- -------------------- -------------------- -----------------------------------
5 FULL SERVICE Internet + cellular Live shared map (TAK), voice nets,
(everything up) + repeaters + mesh mesh text/PLI, HF reach-back. The
+ HF full common operating picture.
|
| lose internet / cellular
v
4 RF + MESH Repeaters + simplex No cloud TAK. Local TAK if a server
(no internet) + Meshtastic + HF is reachable by RF; otherwise voice
nets + mesh text and positions.
|
| lose the repeater
v
3 LOCAL SIMPLEX VHF/UHF simplex Direct radio-to-radio voice within
(no repeater) + Meshtastic + HF line of sight, plus mesh text and
HF for distance. Shorter range,
still a working net.
|
| lose VHF/UHF (jamming/congestion/range)
v
2 OFF-GRID DATA + DISTANCE Meshtastic + HF Short text and position reports over
(RF voice gone) (the FLOOR) the mesh; voice and reports over HF
to distant stations. No live map, but
the force is still connected.
|
| worst case
v
1 BARE MINIMUM HF voice only One disciplined HF schedule (set
(the absolute floor) (a single sched) times, set frequency). Slow, but the
force is never truly silent.
Two things make the ladder work. First, every rung is still useful: even rung 1 keeps the force in contact, which is the whole point of never dropping below the floor. Second, the steps are small enough that dropping a rung does not paralyse anyone, because the procedure for the lower rung is already trained and written. Note also that voice procedure (ACP 125 prowords, clear call signs, readback) matters more, not less, as you descend: the data tools that smoothed things over at the top are gone, and clean voice is what carries the force at the bottom.
The Power and Continuity Plan
Of all the failure modes, loss of power is the one most under the planner's control and most often neglected. A radio with a flat battery is not degraded, it is dead, and no PACE plan saves it. Continuity therefore begins with a power budget: for each device the force depends on, how long does it last on a charge, and how do you replace that charge off-grid? The aim is simple. No critical bearer should go dark for want of electricity that could have been planned for.
Build the power side of continuity as a short table, one row per critical device or role, and carry it in the signals annex.
POWER AND CONTINUITY PLAN (worked example, generic figures)
DEVICE / ROLE DRAW ENDURANCE CHARGING CHAIN SPARE / FLOOR
------------------ ----- --------- ---------------------------- -------------------
VHF/UHF handheld Low ~12 h Power bank -> mains/vehicle 1 spare battery per
(per operator) per batt -> solar panel by day set; rotate on sched
------------------ ----- --------- ---------------------------- -------------------
HF set (reach-back) Med ~8 h key Deep-cycle 12 V battery, Second battery; HF
time/day solar-charged; vehicle as sched timed to fit
backup charge source the power budget
------------------ ----- --------- ---------------------------- -------------------
Meshtastic node V.low Days on Small solar + power bank; Designed to run
(off-grid bearer) one charge many nodes self-power longest of all; the
indefinitely on small panels power-loss floor
------------------ ----- --------- ---------------------------- -------------------
TAK device High ~4 to 6 h Power bank -> vehicle/mains; First to be load-
(phone/tablet) heavy use solar slow for this load shed if power is short
------------------ ----- --------- ---------------------------- -------------------
Repeater (if any) Med Mains; on Generator + fuel plan, or Drop to simplex if
UPS/battery battery/solar for outage ride power cannot be held
POWER PRIORITY WHEN SHORT: keep the FLOOR alive first.
1. Meshtastic nodes 2. HF set 3. VHF/UHF handhelds 4. TAK devices (shed first)
CHARGING DISCIPLINE: charge opportunistically whenever mains or vehicle power exists;
never let a critical battery reach empty before its spare is ready; log battery states
on the net like any other readiness item.
Notice the priority line at the bottom. When power is scarce, you do not spread it thinly across everything until all devices die together; you protect the floor first. The high-draw TAK tablet is the first thing you let go, because the force can live without the live map far more easily than without HF and the mesh. This is the power expression of the same principle as the degradation ladder: protect the bottom rungs.
A few continuity habits sit alongside the table. Standardise on as few battery types as you can, so spares are interchangeable. Carry charging that needs no mains: power banks, fold-out solar, and vehicle charging leads. Charge opportunistically, topping up whenever power is available rather than waiting until something is flat. And treat fuel for any generator as a logistics item with its own plan, because a generator with no fuel is just a heavy box.
Setting Restoration Priorities
Degradation is going down the ladder; restoration is coming back up, and it rarely happens all at once. When power returns, or the internet comes back, or you reach a place with mains and signal, you will have more capability than the moment before but perhaps not everything. The planner decides in advance the order in which links and services are restored, so that recovery is deliberate and the most important capability returns first. Without a plan, people restore whatever is easiest or most visible, which is not always what the commander needs.
Restoration priority follows the commander's requirements, the same starting point as the whole communications plan. Command and control links come back before convenience. The order will usually look like this, though you set yours to the task:
- The command link. The means by which the commander reaches subordinate elements and is reached by them. If only one thing works, it is this.
- Safety and casualty reporting. The ability to pass a casualty report and call for help. In a humanitarian task this may rank with or above the command link.
- The off-grid floor, confirmed. Confirm HF and the mesh are up and steady, because they are what you fall back to if the recovery is only partial or stutters.
- Local voice nets. Repeaters and simplex nets that let units run their own areas.
- The common operating picture. TAK and the live shared map. Valuable, but restored after voice, because voice is the bedrock and the map depends on bearers beneath it.
- Convenience and bulk data. Everything else: file sharing, non-urgent reporting, anything the force merely prefers to have.
The discipline is to restore in priority order even when a lower item would be quicker. Bringing the live map back first because it is satisfying, while the command link is still down, is exactly the mistake the priority list prevents.
The Floor: Why HF and Meshtastic Are Always There
The thread running through this lesson is the floor: the level of service the force is built never to drop below. For the RKA that floor is HF voice and Meshtastic text and positions, and it is the floor for one reason. These two bearers need no infrastructure at all. HF radio reaches over the horizon by skipping signals off the ionosphere, with no repeater, no internet, no mains beyond the set's own battery. Meshtastic nodes relay for each other over licence-free LoRa, forming a small off-grid data network that carries position reports and short text with tiny power and no fixed network behind it.
Because they depend on nothing external, they are the bearers that survive when the dramatic failures arrive: the wide-area power cut, the severed internet, the disaster that flattens the local infrastructure. Everything above them on the ladder, cellular, the internet, repeaters, TAK, is a convenience that improves service when it is available and is expected to vanish when it is not. The floor is what is left, and the planner's promise to the commander is that the force will always have at least this. Two rules follow. Keep the floor exercised, so it is trusted and quick when needed and not a cold capability nobody has used. And keep the floor powered first, as the power-priority line in the continuity table requires, because a floor with flat batteries is no floor at all.
One lawful caution carries over from Lesson 03 and matters most exactly when the floor is in use. HF is amateur spectrum: transmitting needs the proper licence, and amateur bands forbid encryption, so the floor is for unencrypted, lawful traffic. Sensitive material rides an encrypted internet or TAK bearer when that bearer exists; when it does not, you simply do not pass that material over the open floor. Resilience never becomes an excuse to break the law the force operates under.
In Practice: A Corporal Holds the Floor Through an Outage
A regional storm has cut mains power across a wide area and taken the cellular network and home internet with it. The RKA is supporting the civil emergency services, and a section under Corporal Adeyemi is checking that an evacuation route is clear and reporting back to the detachment command post.
At full service that morning the section had everything: TAK on a tablet showing the live shared map over cellular data, the repeater net for voice, the mesh running alongside. As the storm worsens the cellular data drops, and with it the live map. Adeyemi does not treat this as a crisis, because the section has trained the degradation ladder. They step to rung 4: the tablet's TAK can no longer reach the cloud, so the section passes its position reports by voice on the repeater net and lets the Meshtastic nodes carry short text and positions to the command post over the mesh. When a power failure later takes the repeater itself, they step to rung 3, working VHF simplex direct to the units within line of sight, with the mesh and HF still beneath them.
Through all of it the floor holds. The mesh nodes, on small power banks and a folding solar panel, have run all day without mains, exactly as the continuity plan intended; the high-draw tablet was the first thing the section stopped using to save power, as the power-priority line says. When the detachment needs to reach a distant element the cellular net would normally have covered, the signaller uses the HF set on the published schedule, in plain unencrypted voice with clean ACP 125 procedure, because HF is amateur spectrum and the traffic is lawful and open. The section's licensed operator keys the HF set; the rest of the section works the licence-free mesh and the low-power simplex net within the law. The shared map is gone for now, but the force is not silent, and a casualty report could still be passed if it were needed. When power and the internet return that evening, the command post restores in priority order: the command link first, then safety reporting, then a confirmed check that HF and the mesh are still steady, and only after all of that does the live TAK map come back. The section never dropped below the floor, and never broke the law it operates under.
Check Your Understanding
- Define graceful degradation and explain why a small force should design a degradation ladder rather than rely on an all-or-nothing system. Give one example of a rung on the RKA ladder and what the force can still do at it.
- Power is short and not every device can be kept charged. List, in order, which the force keeps alive first and which it sheds first, and explain why the live TAK map is shed before HF and the mesh.
- After a wide-area outage, capability is returning but not all at once. State the restoration priority order the planner would follow and explain why the command link is restored before the common operating picture.
Reflection (write a short paragraph): Think about a continuity test you could set for your own section or detachment without any enemy involved: a planned exercise where the mains is "switched off" and the internet "removed" for a fixed period. Which bearers would you expect to survive, where do you think your power plan is weakest, and what one change would most improve the force's ability to hold the floor through a real civil emergency?
Summary
- Resilience and continuity are planning problems decided on paper before kit is bought; assume every link will fail and design out single points of failure.
- The realistic failure modes for a small humanitarian force are loss of mains power, loss of internet and cellular, jamming and congestion, loss of a shared component, and wide-area disaster conditions.
- Graceful degradation means designing a ladder from full service down to a floor, where every rung is still useful and the steps are small and trained; clean voice procedure matters more, not less, as you descend.
- Continuity rests on a power plan: a power budget per device, off-grid charging (batteries, power banks, solar, vehicle), opportunistic charging, and a power priority that protects the floor first and sheds the high-draw TAK device first.
- Restoration priorities set the order capability returns in: command link, then safety and casualty reporting, then a confirmed floor, then local voice nets, then the common operating picture, then convenience.
- HF voice and Meshtastic are the floor the force never drops below, because they need no infrastructure; keep the floor exercised, powered first, and lawful (HF is amateur spectrum, no encryption, licensed operators only).
- Builds on Lesson 02 (Designing the Communications Architecture) and Lesson 03 (Spectrum, Frequencies, and Licensing Strategy); feeds Lesson 10 (Planning, Orders, and Governance) where this becomes the continuity content of the signals annex.
- Cross-references HCR 220 Emergency Preparedness and Civil Resilience (continuity and disaster planning), HCR 210 Aid to the Civil Power (working with civil agencies, see Lesson 05), PME 210 Basic Staff Duties (the signals annex), and FLD 220 Signals and Field Communication (operator-level PACE and voice procedure).
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia