Royal Army College

Lesson Overview

The nine lessons before this one made you a designer. You learned to start from the commander's requirements, layer complementary bearers so no single failure is fatal, manage spectrum and licensing lawfully, plan for power loss and lost infrastructure with graceful degradation, integrate with the civil agencies the Army serves, manage the information and common picture that ride on the network, defend the force's communications from cyber attack, develop and sustain the communications capability, and reach back to higher and partner networks. All of that is the communications plan held in the planner's head. This lesson is about getting it out of your head and into the force: writing it down, issuing it as orders, rehearsing it, governing who may operate it, controlling the keys and certificates that secure it, and revising it after every task. A plan that lives only in the planner is not a plan; it is a single point of failure who can be tired, busy, off the net, or simply absent on the day it is needed.

This is the lesson that pulls the whole course together. A small force's communications are only as good as the plan that is written, issued, rehearsed, and revised. The cleverest architecture is worthless if the operators never received it, never practised it, or are working last month's frequency list. So this lesson covers the signals estimate, the disciplined way you reason from requirement to plan; the communications annex to orders, the plan written down and issued in a form everyone in the force already knows how to read; communications standing operating procedures, the steady rules that do not change task to task; training and qualification governance, who may operate and who may instruct; certificate and key management policy, issuing and revoking TAK certificates and Meshtastic keys; and review and learning, the discipline of debriefing every exercise and task and feeding what you find back into the plan. It draws throughout on PME 210 · Basic Staff Duties and Written Orders, which owns the orders process and the service-writing craft this lesson applies to communications.

This is the knowledge layer. Reading it makes you ready to plan and govern communications on paper, but it does not make you a planner: planning, writing orders, and governing keys are practised and signed off in person and on airsoft milsim exercises, watched by someone already qualified, and any real transmitting in your exercises is done only by licensed members or on licence-free and low-power sets. By the end you will be able to work a signals estimate from the commander's requirements through to a chosen plan, write a clear communications annex to orders with a frequency and call-sign plan and a PACE table, draft a small set of communications SOPs that govern how the force operates regardless of task, set the governance of who may operate and who may instruct, write a certificate and key management policy that issues and revokes TAK certificates and Meshtastic keys lawfully and tie it to the Information Systems and Cyber Security speciality, and run an honest after-action review that turns each task into an improvement to the plan.

Key Terms

Signals estimate: the disciplined reasoning that takes you from the commander's requirements to a chosen communications plan. It is the staff estimate of PME 210 applied to communications: state the mission, study the factors, work out and compare the ways of meeting the need, and decide. The plan is the output; the estimate is how you reach it defensibly.
Communications annex: the part of a set of orders that tells everyone how the force will communicate for this task. Also called the signals annex or signals paragraph. It carries the frequency and call-sign plan, the PACE plan, the common operating picture details, and the rules for the task. It is the plan written down and issued.
Frequency and call-sign plan: the published table that says which channel or frequency each net uses and what each station is called, so units do not interfere with one another and everyone can find everyone else. The "who is on what, and what are they called" of the task.
PACE plan: Primary, Alternate, Contingency, Emergency. The ordered list of communications means for a link, so the force knows what to fall back to when the first means fails, with the means chosen to fail in different ways so one cause does not take them all.
Standing operating procedure (SOP): a steady rule that does not change task to task: how a radio check is done, how the log is kept, what the no-comms drill is, how a lost or compromised radio is reported. SOPs are written once and assumed; the annex only states what is different for this task.
Qualification governance: the written rules for who is allowed to operate which bearers and who is allowed to instruct others, so that competence is held to a known standard and not assumed. It records who is qualified, on what, and until when.
Certificate: the cryptographic identity that lets a person or device onto the TAK server, issued per user, proving the holder is who they say and authorising their access. Issued when someone joins or is cleared, revoked the moment they leave or are compromised.
Key: the shared secret that secures a Meshtastic channel (and, more broadly, any encrypted bearer), so that only holders can read the traffic on it. Like a certificate, it is issued under control and changed when a holder leaves or it may be exposed.
Revocation: the act of withdrawing a certificate or key so the holder can no longer use it. The other half of issuing, and the half most often neglected: a force that issues but never revokes leaks access with every departure.
After-action review (AAR): the honest, structured debrief held after every exercise and task to establish what was supposed to happen, what actually happened, why, and what to change. Its purpose is to feed lessons back into the plan, not to assign blame.

The signals estimate: reasoning to a plan

Before you write a single line of orders you must decide what the plan is, and you reach that decision the same disciplined way PME 210 teaches for any staff problem: by an estimate. The signals estimate is the staff estimate applied to communications, and its value is that it makes your reasoning visible and defensible rather than a hunch. You do not skip it because the task is small; you shorten it. Even a half-page estimate forces you to ask the questions a good plan answers, and it leaves a trail so that when something is questioned, on the day or at the review, you can show why you chose as you did.

Start where every estimate starts, with the mission and the requirements, which on a communications problem come straight from the commander, as Lesson 01 taught: who must be able to talk to whom, what must be reported and how often, how reliable each link must be, how secure, and over what distance and terrain. Communications serve command, so the requirement is the commander's, not the signaller's, and your first job is to be sure you have it right. Then study the factors, the things that shape what is possible: the ground and how far the bearers must reach across it, the infrastructure that is and is not present, the power available, the licences your members actually hold, the sets the force owns, and the law of wherever the force will transmit. Each factor narrows the field of workable plans.

From the factors you work out the ways of meeting the need and compare them honestly. Usually this is a question of which bearers to layer and how, because Lesson 02 taught that the answer for a small force is rarely one bearer but a sensible combination: HF for range without infrastructure, VHF or UHF voice for local work and repeaters, Meshtastic for off-grid text and position, TAK over the internet or mobile data for the common operating picture, cellular where it exists. You weigh each candidate plan against the requirement and the factors: does it meet the reliability and security the commander asked for, does it fail gracefully, does it stay within the law and the licences held, can the force actually operate and sustain it. Then you decide, and the output of the decision is the plan you are about to write down: the bearers, the PACE order for each critical link, the frequency and call-sign scheme, the security boundary, and the governance that holds it together. The plan is the answer; the estimate is the working that justifies it.

The communications annex to orders

A decision that stays in your head reaches no one. The plan becomes the force's plan only when it is issued as orders, and the right place for it is the communications annex to the orders for the task, what PME 210 also calls the signals annex or, for a short order, the signals paragraph. Issuing it as a recognised part of orders matters for two reasons. First, it reaches everyone through the chain in the form they already expect, alongside the rest of the orders, so no one is left guessing. Second, it puts the plan in the standard service-writing form PME 210 teaches, clear, correct, and brief, so it can be read fast and acted on without interpretation. Write the annex in plain, ordered prose and tables, not in your own shorthand, because the soldier reading it under a poncho in the rain has only the paper, not you.

Keep the annex disciplined. State only what this task needs and lean on the SOPs for everything that does not change, so the annex stays short and the reader is not made to re-read the permanent rules every time. The core of it is always the frequency and call-sign plan and the PACE table, because those are the two things a station needs to get on the net and to know what to do when a link drops. Add the common operating picture details, which TAK server, which channels, who is on it; the security boundary, restated plainly so it cannot be missed (sensitive traffic on the encrypted internet or TAK bearer, never on the amateur RF that forbids encryption); any liaison or shared channel with a civil agency, in plain language as Lesson 05 taught; and the report formats and timings the commander wants. Then issue it, confirm it has been received and understood, and rehearse it, because an annex that is filed unread is no better than a plan in your head.

   COMMUNICATIONS ANNEX TO ORDERS  (signals annex outline)
   Annex to: Orders for <task>          DTG: <ddhhmmZ mon yy>
   Issued by: Signals planner            Classification: <as set>

   1. SITUATION (comms-relevant)
      Bearers and infrastructure available; known dead ground;
      power and charging situation; civil agencies present.

   2. MISSION (the comms task)
      Provide reliable, lawful comms for <task>: who must reach
      whom, what must be reported, how secure, over what distance.

   3. EXECUTION
      a. Concept: how the bearers layer; the common operating
         picture (TAK server / channels); the security boundary.
      b. Frequency & call-sign plan  ........ (table, para 5)
      c. PACE plan, per critical link ....... (table, para 6)
      d. Reports & timings: SITREP every <n>; CONTACT immediate;
         formats per SOP. Civil liaison channel: <plain language>.

   4. SERVICE SUPPORT
      Power/charging/solar; spare sets & batteries; who holds keys
      and certificates; fault reporting; lost/compromised-set drill.

   5. FREQUENCY & CALL-SIGN PLAN
      NET        BEARER        CHANNEL/FREQ      STATIONS / CALL SIGNS
      Command    VHF simplex   <ch / MHz>        HQ "Zero"; c/s ...
      Admin      PMR446        <ch>              ...
      Data/posn  Meshtastic    <ISM channel/key> all; TAK gateway
      COP        TAK/internet  tak.kaharagia.org per-user cert

   6. PACE  (example: command link)
      P  VHF/UHF voice (repeater)     A  VHF simplex
      C  Meshtastic text             E  HF voice / SMS / runner

   7. ACKNOWLEDGE: each sub-unit confirms receipt and understanding.

Communications SOPs: the rules that do not change

If every order had to restate how a radio check is done, what the log looks like, and what to do when a link drops, orders would be long, slow, and inconsistent, and the force would relearn the basics every task. The cure is the standing operating procedure: the set of rules that do not change task to task, written down once, taught, and thereafter assumed. SOPs are what let the communications annex stay short, because the annex only has to say what is different this time; everything permanent lives in the SOPs and is simply taken as read. A force with good SOPs operates the same way whoever is on the radio and whatever the task, which is exactly the consistency a scattered small force needs.

Keep the SOP set small and genuinely standing. Good candidates are the things that should never vary: how a radio check is initiated and answered and how a signal report is given; how the log is kept, time, stations, gist of each message, with the date-time group in Zulu; the no-comms drill worked before any link is declared dead, power, volume and squelch, channel, antenna and its connection, position, relay; how a fault or a lost or compromised set is reported and what happens next; the standard report formats the force uses, SITREP, CONTACT, the SALUTE or SALTR sighting, the casualty report; the plain-language rule for shared nets with civil agencies; and the security boundary as a standing rule, that no sensitive traffic goes over amateur RF because amateur bands forbid encryption, and that such traffic rides the encrypted internet or TAK bearer instead. Write them in the same clear service-writing form as orders, review them on a fixed cycle so they do not drift out of date, and govern changes so the SOP set is one trusted document and not a dozen contradictory memories. The SOPs and the annex divide the work cleanly: SOPs say how the force always operates, the annex says what is special about today.

Governing who may operate and who may instruct

A plan assumes competent operators, and competence cannot be assumed into existence; it has to be governed. Qualification governance is the written answer to two questions the planner owns: who is allowed to operate which bearers, and who is allowed to instruct others. Without it, the force drifts into letting whoever is keen pick up whatever set is to hand, which is how unlicensed transmission, broken procedure, and mishandled keys creep in. With it, every bearer has a known standard, every operator is recorded against the standards they hold, and the planner can look at a task and know the force has the qualified people to run it.

Tie the governance to the standards the speciality already sets and to the law. An operator cleared for the common net has met the voice-procedure and message-handling standard of the operator and NCO courses, assessed by watching them work, as Lesson 05 of the Signals NCO course teaches, not by asking what they know. An operator who will transmit on amateur bands must additionally hold the amateur licence the law requires for those bands, Technician, General, or Amateur Extra in the US example, or the local equivalent; for general training and exercises the force defaults to licence-free sets, FRS, PMR446, MURS, LoRa ISM, or licensed-no-exam options such as GMRS, so that being unlicensed never stops a member training. An operator trusted with TAK or keyed bearers has been issued a certificate or key under the policy below and understands the discipline that goes with it. And instruction is governed separately: coaching your own people in a skill you hold is within an NCO's role, but formal instructor qualification, certifying others, and unit-wide training belong to the Training and Instruction speciality and are escalated there, never improvised. Record all of this so it can be checked: who is qualified, on what, and until when, with re-qualification on a cycle so a competence signed off two years ago is not assumed to be current today.

Certificate and key management policy

The force's most capable bearers are the secured ones, the TAK common operating picture reached by per-user certificate on the RKA's OpenTAKServer, and the Meshtastic channels secured by a shared key. That security is only real if the certificates and keys are governed, and governing them is a policy the planner writes and the Information Systems and Cyber Security speciality runs. The principle is simple and is the one most often half-done: issuing and revoking are equal halves of the same job. A force that issues certificates and keys eagerly but never revokes them accumulates active access in the hands of everyone who has ever left, which is exactly how a lost device or a departed member becomes an open door into the common operating picture.

Govern the whole lifecycle. Issue a certificate or key only to a person who has been cleared and qualified, recorded against their name, with the least access the role needs and no more, so a member who only needs the data net does not also hold the keys to everything. Hold them under control: certificates and keys are protected, not shared around, not pasted into chat, not left on an unlocked device; each person holds their own so that access can be traced and withdrawn person by person. Rotate keys on a sensible cycle and whenever the membership of a keyed channel changes, because a shared key is only as trustworthy as the smallest circle that still holds the old one. Revoke the moment a person leaves, a role ends, or a device is lost, stolen, or compromised: a certificate is revoked on the TAK server so the identity no longer authenticates, and a key is changed and the new one redistributed only to those who should still have it, so the departed holder's copy secures nothing. And keep a record of every issue, rotation, and revocation, the who, what, and when, so the planner can answer at any moment who currently holds access to what. Tie all of this explicitly to the CIS speciality, which owns the servers and the cryptographic craft: the planner sets the policy of who gets access and when it is withdrawn, and CIS executes it on the systems, the two working as one so that the governance written on paper is actually true on the server.

   CERTIFICATE / KEY LIFECYCLE AND GOVERNANCE FLOW

      [ Member cleared & qualified ]
                 |
                 v
        +------------------+      decided by: Signals planner
        |  ISSUE  (least   |      executed by: CIS speciality
        |  access needed)  |      recorded: who / what / when
        +------------------+
                 |
                 v
        +------------------+   <-- protected; per-user; never
        |   HOLD & USE     |       shared, pasted, or left on
        |  (under control) |       an unlocked device
        +------------------+
            |          |
   role/    |          |  membership of a keyed
   device   |          |  channel changes, or
   ends or  |          |  cycle reached
   is lost  |          v
   /comp-   |     +------------------+
   romised  |     |  ROTATE key /    |
            |     |  re-issue to     |
            |     |  current holders |
            |     +------------------+
            v                |
        +------------------+ |
        |  REVOKE          |<+   cert revoked on TAK server;
        |  (cert + key)    |     key changed, redistributed
        +------------------+     only to those who keep access
                 |
                 v
        [ Record updated; access no longer valid ]

   RULE: issuing and revoking are equal halves. Every departure,
   every lost device, triggers revocation the same day.

Review and learning: turning tasks into a better plan

A plan written, issued, and governed is still only your best guess until reality tests it, and reality always finds the gaps: the repeater that did not reach where the map said it would, the PACE fallback nobody had actually rehearsed, the civil channel that was agreed but never confirmed, the key that one departed member still held. The discipline that closes those gaps is review, the after-action review held after every exercise and every task, without exception. Its purpose is to feed lessons back into the plan, so the plan you carry into the next task is better than the one you carried into the last. A force that plans but never reviews keeps the same faults forever; a force that reviews honestly improves with every outing, which is how a small force makes its modest means reliable.

Run the review the plain, honest way. Establish what was supposed to happen, the plan and the annex as issued; establish what actually happened on the net, drawn from the log, the operators, and the common operating picture; work out why the difference arose; and decide what to change. Keep it about the procedure and the plan and never about the person, exactly as fault correction is kept in Lesson 05, because a review that hunts for blame teaches people to hide the very faults it needs to find. Then, and this is the step most often dropped, close the loop: turn each lesson into an actual change, a corrected frequency in the plan, a PACE fallback that will now be rehearsed because it failed, an SOP tightened, a key rotated because it should have been already, a member's qualification refreshed, and record that the change was made. The output of a review is not a list of complaints; it is an updated plan, set of SOPs, and governance record. That is the loop that makes this whole course work: estimate, write, issue, rehearse, operate, review, revise, and round again, each turn leaving the force's communications a little more reliable, resilient, secure, and lawful than before.

In Practice: Planning Communications for a Search Support Task

A Captain of the Signals speciality is given a humanitarian task: support a civil search and rescue effort across an area of low hills and patchy mobile coverage, with two RKA sections out on the ground, a small headquarters, and a liaison with the civil emergency services who own the operation. She does not reach for a radio; she works a signals estimate. The commander's requirement is clear once she draws it out: the headquarters must reach both sections reliably, both sections must be able to report a find or a casualty at once, the headquarters must hold a common picture of where everyone is, and the force must be able to talk to the civil controller in plain language. The factors narrow it fast: the hills create dead ground, mobile coverage is patchy, only three members hold amateur licences, and the force will be transmitting under national law alongside a civil agency.

From that she decides the plan and writes it as a communications annex. Command and section nets run on VHF, simplex where a repeater does not reach, with a PACE for the command link of repeater voice as primary, simplex as alternate, Meshtastic text as contingency, and HF or a runner as emergency. Position reporting and the headquarters' common picture run on TAK over mobile data where it exists, fed by a Meshtastic and TAK gateway so that the off-grid sections still show on the map when their phones lose signal, the light position and chat messages riding the mesh while anything heavier waits for data. The liaison with the civil controller is a single agreed channel worked in plain language, no internal call signs or codes, with frequency and contact details exchanged beforehand. She leans on the SOPs for everything standing, the radio check, the log in Zulu, the no-comms drill, the report formats, so the annex stays short, and she restates the one security rule that must not be missed: nothing sensitive over the amateur RF, because it forbids encryption; sensitive coordination rides the TAK bearer.

Before the task she checks the governance. The three licensed members are the ones who will work any amateur frequencies; the rest operate on licence-free sets, so being unlicensed stops no one. Two new members were issued TAK certificates last week against their names with only the data-net access they need, and she has the CIS speciality confirm that a member who left the section a month ago has had his certificate revoked on the server and the Meshtastic channel key rotated, because issuing without revoking is exactly the leak this policy exists to stop. The task runs; a repeater turns out not to reach one valley, and the section there falls back down the PACE to Meshtastic text and stays on the map throughout. Afterwards she runs the after-action review: what was supposed to happen, what did, why the repeater fell short, what to change. The plan gains a corrected note about that valley and a standing instruction to rehearse the Meshtastic fallback, the SOP for confirming the civil channel is tightened, and the qualification record is updated. The next task starts from a better plan than this one did.

Check Your Understanding

What is a signals estimate, and what are its main steps from the commander's requirements to a chosen plan? Why work an estimate even on a small task rather than going straight to a frequency list, and what is the relationship between the estimate and the communications annex you then write?
The communications annex carries a frequency and call-sign plan and a PACE table but leans on the SOPs for much else. Explain the division of work between the annex and the standing operating procedures, and give three things that properly belong in the SOPs because they do not change task to task.
Why are issuing and revoking described as equal halves of certificate and key management, and what specifically must happen to a TAK certificate and to a Meshtastic channel key when a member leaves the force or a device is lost? How does the planner's role here divide from the role of the Information Systems and Cyber Security speciality?

Reflection (write a short paragraph): This lesson argues that a plan which lives only in the planner's head is a single point of failure, and that a small force's communications are only as good as the plan that is written, issued, rehearsed, and revised. Think about the difference between knowing how something should work and having written it down so that others can run it without you. Where, in your own experience, has knowledge that stayed in one person's head failed a group when that person was absent? As a planner, how will you make yourself replaceable, getting the plan out of your head and into orders, SOPs, and an honest review loop, so that the force's communications survive your worst day rather than depending on your best?

Summary

A communications plan that lives only in the planner is a single point of failure. The work of this lesson is to get it out of your head and into the force: written, issued, rehearsed, governed, and revised. A small force's communications are only as good as that plan.
Reason from the commander's requirements to a chosen plan by a signals estimate: mission and requirements, factors, ways of meeting the need, decision. Even a short estimate makes your reasoning visible and defensible. The plan is the output; the estimate is the working.
Issue the plan as a communications annex to orders, in the standard service-writing form of PME 210, so it reaches everyone through the chain and can be acted on without interpretation. Its core is always the frequency and call-sign plan and the PACE table; confirm receipt and rehearse it.
Keep the rules that do not change in a small set of standing operating procedures, the radio check, the log, the no-comms drill, the report formats, the lost-set drill, the plain-language rule, the security boundary, so the annex can stay short and the force operates the same way every task.
Govern who may operate and who may instruct: known standards per bearer, the amateur licence where the law requires it, licence-free sets as the training default, and instruction escalated to the Training and Instruction speciality. Record who is qualified, on what, and until when.
Write a certificate and key management policy in which issuing and revoking are equal halves: issue with least access to cleared and qualified people, hold under control, rotate keys on change of membership, and revoke certificates and keys the same day a member leaves or a device is lost. Set the policy with, and run it through, the Information Systems and Cyber Security speciality.
Review after every exercise and task: what was supposed to happen, what did, why, and what to change, kept on the procedure and never on the person. Close the loop by turning each lesson into an actual change to the plan, SOPs, and governance record. Estimate, write, issue, rehearse, operate, review, revise, and round again.
Cross-references: PME 210 (the estimate, the orders process, and the service writing this lesson applies to communications), SIG 410 Lessons 01 to 05 (the requirements, architecture, licensing, resilience, and civil integration this lesson commits to paper and governs), HCR 220 (the continuity the resilience plan serves), HCR 210 (the civil integration the annex provides for), and the Information Systems and Cyber Security speciality (the servers and cryptographic craft behind the certificate and key policy).

Planning, Orders, and Governance