Lesson Overview
A signals NCO runs one net well. A communications planner answers a larger and stranger question: given a whole force that may be scattered across difficult ground, far from infrastructure, made of detachments that must talk to each other and to the commander and sometimes to outside agencies, how do you build a communications system that ties all of it together and keeps working when parts of it fail? This is not the same job as running a net with more radios on it. It is a change in altitude. The operator and the NCO live inside the system and make their part of it work; the planner stands above the system, designs it, and answers for it as a whole. This first lesson is about that change in altitude, where the planner begins, and the mindset the rest of the course builds on.
The course you are beginning, SIG 410, is the planner's tier of the Signals and Communications speciality. It assumes the operator and NCO courses beneath it and that you can work and run a net yourself. What changes now is that you stop thinking about a handset, or even a section's net, and start thinking about the force's communications as one designed thing. You will learn that communications exist to serve command and never the other way round; that the planner starts not from a radio catalogue but from the commander's requirements, who must talk to whom, what must be reported, and how reliable, secure, and far each link must be; that a small, young, non-territorial humanitarian force plans modestly and realistically rather than imitating the signals branch of a large army; and that the planner's true product is a system of well-integrated lawful bearers that is reliable, resilient, secure, and lawful, and that fits alongside the civil agencies the Army serves. The later lessons teach the architecture, the spectrum and licensing, the resilience, the civil integration, and the governance in full. This one frames the problem they all solve.
This is the knowledge layer. Reading about communications planning no more makes you a planner than reading about command makes a force follow you. The real work of the planner, drawing requirements out of a commander, choosing bearers that fail in different ways, writing a plan that a tired operator can follow at three in the morning, and learning from what broke on the last exercise, is practised and signed off in person and on airsoft milsim exercises, where a plan that looks elegant on paper meets the weather, the flat battery, and the dead repeater. Any live transmission is done only by members who hold the proper licence in their jurisdiction, or on licence-free and low-power sets where no licence is required; the planner is the person who designs the system so that this stays true. By the end you will be able to explain why a force-level view of communications differs in kind from running a single net; state that communications serve command and start from the commander's requirements; draw a commander's requirement out as who, what, how reliable, how secure, and how far; describe the responsibility ladder from operator to NCO to planner and what each owns; explain why a small humanitarian force plans modestly and realistically rather than imitating a large army; and describe the whole-system view, reliable, resilient, secure, and lawful, that the rest of the course develops.
Key Terms
- Communications planner: the officer or senior signaller who designs and governs communications for a whole detachment, task, or force, owning the system as a designed whole rather than running any one net within it.
- Communications serve command: the governing principle that communications exist only to let the commander command, so the plan starts from what command needs and is judged by whether it delivers it, never by how clever or complete the radio system is for its own sake.
- Commander's communications requirements: the demand the planner designs against, expressed as who must talk to whom, what must be reported, how reliable each link must be, how secure it must be, and over what distance and terrain.
- Bearer: any means of carrying a message, for example high-frequency radio, line-of-sight VHF or UHF voice, a Meshtastic and LoRa mesh, or the Team Awareness Kit over the internet. The planner's raw material is a set of bearers, chosen and combined.
- Common operating picture: a single shared view of the force, normally the Team Awareness Kit map showing positions, markers, and routes, that ties the force together but depends entirely on the bearers carrying it.
- PACE plan: Primary, Alternate, Contingency, Emergency. The means for a link listed in fall-back order, chosen so they fail in different ways, so that one cause cannot take them all at once.
- Graceful degradation: designing the system so that when a part fails the force loses some capability but not all of it, falling back link by link rather than collapsing all at once.
- Modest and realistic planning: the deliberate choice to field a few well-integrated, lawful bearers that the force can actually crew, license, and sustain, rather than an oversized imitation of a large army's signals branch.
- Whole-system view: the planner's habit of seeing communications as one interacting system of people, bearers, frequencies, plans, power, certificates, and habits, judged by four tests together: reliable, resilient, secure, and lawful.
A change in altitude, not just in scale
Begin by being clear about what is actually different, because it is tempting to think the planner is just an NCO with more radios. That is wrong, and the error is expensive. The operator owns a handset. The NCO owns a section's net as a system, the people and sets and frequencies and habits that make one net hold together. The planner owns something that is not a net at all. The planner owns the whole arrangement by which a force communicates: several nets, several bearers, the way they connect, the way they fail, the way they fall back, the licences that make them lawful, and the plan that governs all of it. Adding radios to a net is more of the same job. Designing a force's communications is a different job.
The clearest way to feel the difference is to notice where each role stands relative to the system. The operator and the NCO stand inside it. They make their part work, and they make it work by hand, by good voice procedure, by checking batteries, by holding a standard. The planner stands above it. The planner does not work any single net by hand; if the planner is holding a handset and running a net, the planning is not being done. The planner's product is not a clean transmission or a well-run net. It is a design and a written plan: this is who talks to whom, on these bearers, in this fall-back order, under these licences, with these procedures, and here is what happens when each part fails. The operator is judged by their own performance, the NCO by the weakest operator on their net, and the planner by whether the system as a whole delivers what the commander needed, even on the day three things broke at once.
That is why it is a change in altitude and not merely in scale. A planner who simply runs a very big net has not changed altitude; they have just taken on a heavier version of the NCO's job, and the force's communications will fail the first time the planner cannot personally hold every part. The planner's real move is to stop holding parts and start designing the system so that the parts hold themselves, and so that when one lets go the others carry on. Everything in this course flows from that move.
THE RESPONSIBILITY LADDER: OPERATOR -> NCO -> PLANNER
+------------------------------------------------------------------+
| PLANNER (SIG 410) ............... stands ABOVE the system |
| owns: the FORCE'S communications as a designed whole |
| product: the architecture, the plan, the governance |
| judged by: does the SYSTEM deliver what command needed? |
+------------------------------------------------------------------+
^ designs the system the NCO runs a part of
|
+------------------------------------------------------------------+
| SIGNALS NCO (SIG 310) .......... stands INSIDE, runs one net |
| owns: a SECTION'S net as a system (people, sets, freqs) |
| product: a net that holds together under pressure |
| judged by: the WEAKEST operator on the net |
+------------------------------------------------------------------+
^ makes one net work within the plan
|
+------------------------------------------------------------------+
| OPERATOR (SIG 201 / 220) ....... stands INSIDE, works one set |
| owns: ONE handset and one operator (me) |
| product: a clean transmission, traffic passed |
| judged by: MY OWN performance on the net |
+------------------------------------------------------------------+
Each rung does NOT replace the one below; it stands on it.
The planner's job is the design, not the doing.
Read that ladder as a stack and not a replacement. The planner does not stop needing clean voice procedure to exist; the planner depends on it utterly, because the whole architecture rides on operators who can pass a message. What the planner adds is the layer above: the design that decides which operators, on which bearers, in which order, under whose licence, talking to whom. You climb the ladder by adding a layer of responsibility, not by leaving the lower layers behind.
Communications serve command
The single most important sentence in this whole course is short and easy to say and easy to forget under the pleasure of good equipment: communications serve command, and never the other way round. The force does not communicate in order to have an impressive radio system. It communicates so that the commander can command, so that the right person knows the right thing in time to decide and act. Every bearer, every net, every certificate, every frequency exists for that and is justified by that. A communications system that is technically magnificent and does not let the commander command has failed completely, and a humble one of two licence-free radios and a runner that does let the commander command has succeeded.
This principle is not a platitude; it is a working test you apply to every decision. When you are tempted to add a bearer, a feature, a clever relay, you ask what command requirement it serves. If the answer is "none, but it is impressive", you do not add it, because every part you add is a part you must crew, license, power, and maintain, and a part that can fail. When you are tempted to leave a requirement unmet because the only solution is unglamorous, you ask the same question and meet it, because the commander's need does not care how elegant the answer is. The planner who keeps this principle in front of them builds small, lawful, sufficient systems. The planner who forgets it builds large, fragile, impressive ones that look like a real army's signals branch and collapse the first time the internet does.
It follows that the planner does not begin with a radio catalogue. The planner begins with the commander. You go to the commander, or to the orders and the task, and you draw out what command actually needs from communications, expressed not in equipment but in requirement. Only when you hold the requirement clearly do you reach for bearers, and then you reach for the smallest set that meets it. Starting from the kit is the classic beginner's error: it produces a system designed around what radios can do rather than around what the commander needs done, and the two are rarely the same shape.
Drawing out the commander's requirements
A commander will almost never hand you a communications requirement in tidy form. They will tell you the task, the ground, who is involved, and what they intend to achieve, and they will assume, reasonably, that you will work out the communications. Your first skill as a planner is to turn that into a clear set of requirements by asking, of the task, five plain questions. Who must be able to talk to whom? What must be reported, and how often? How reliable must each link be, that is, what happens if it fails? How secure must each link be, that is, who must not be able to read or hear it? And how far, over what distance and what terrain, must each link reach? Those five, who, what, how reliable, how secure, how far, are the bones of every communications requirement, and a requirement that answers all five is one you can design against.
The five questions are not equally weighted on every link, and learning to feel which one dominates a given link is much of the art. A link from a forward team to the commander may be dominated by reliability, because if it fails the commander is blind and the team is unsupported, so it must have a strong PACE plan. A link carrying a national's medical detail or a vulnerable person's location may be dominated by security, so it must ride an encrypted internet bearer and never go in clear over a radio. A link from a team working deep in low ground may be dominated by distance and terrain, so it cannot be line-of-sight VHF voice and must be HF or relayed. You answer all five for every link, but you design hardest against the one that, if unmet, breaks the task.
It helps to lay the whole thing out as a flow, from the commander's intent down to the plan, so that you can see that the bearers come at the end and not the beginning. Walk it from the top every time and you will not fall into designing around your favourite radio:
FROM COMMANDER'S REQUIREMENT TO COMMUNICATIONS PLAN
[ COMMANDER'S INTENT / THE TASK ]
the mission, the ground, who is involved, what to achieve
|
v
[ DRAW OUT THE REQUIREMENT ] ask FIVE questions of the task:
WHO must talk to WHOM? .................. the links needed
WHAT must be reported, how often? ....... the traffic
HOW RELIABLE must each link be? ......... consequence of failure
HOW SECURE must each link be? ........... who must not hear/read
HOW FAR / what terrain? ................. distance and ground
|
v
[ CHOOSE BEARERS TO MEET IT ] pick the SMALLEST lawful set:
HF | VHF/UHF voice | Meshtastic mesh | TAK over internet | cellular
chosen so they FAIL IN DIFFERENT WAYS
|
v
[ ORDER THEM: PACE ] Primary -> Alternate -> Contingency -> Emergency
for EACH critical link
|
v
[ WRITE IT DOWN ] the plan: who, what, on which bearer, fall-back,
licences, procedures, governance -> issued and rehearsed
The bearers come at the END. Start from command, not the catalogue.
Notice what the flow protects you from. By forcing the requirement out before the bearers, it stops you choosing a radio and then inventing reasons the force needs it. By making you ask all five questions, it stops you designing a system that is reliable but insecure, or secure but unable to reach. And by putting "write it down" at the bottom, it reminds you that a plan in the planner's head is not a plan the force can use; the planner's product is a written, issued, rehearsed thing, which the governance lesson treats in full.
Why a small humanitarian force plans modestly
Here is a temptation worth naming directly, because it has ruined many a small unit's communications. A new planner, having learned about HF and repeaters and mesh and TAK, wants to build the lot: a full signals branch in miniature, every band covered, every redundancy layered, a system that looks like something a large national army would field. It is an understandable wish and it is wrong, and the planner who indulges it builds something the force cannot crew, cannot license, cannot power, and cannot sustain, which is to say something that does not actually work when it matters.
The Royal Kaharagian Army is small, young, non-territorial, and humanitarian. It has no territory to wire, no standing enemy to out-signal, and no large body of full-time signallers to crew an elaborate system. Its members are volunteers who hold ordinary jobs and ordinary radio licences. Its lawful options are members' amateur licences, licence-free allocations, licensed-no-exam options, and the public internet. Designing against that reality, rather than against a fantasy of a large army, is not a limitation to apologise for; it is the whole point of planning for a small force. A few well-chosen bearers, integrated so they cover each other's weaknesses, crewed by people who actually train on them, and operated within the law, will out-perform a sprawling imitation that nobody can keep running. Modest and realistic is not second best. For a force this size it is the better system, and a planner who understands that builds things that hold.
Modesty also has a lawful and ethical edge that fits the Army's nature. A humanitarian force exists to help and to support the civil authorities, not to supplant them and not to dominate the spectrum. It operates within national law and the international framework, it does not interfere with others' communications, and it does not intercept them. A small, lawful, well-integrated system is exactly the system such a force should want: enough to let it do its job reliably, no more than it can hold lawfully and crew honestly, and built to work alongside the civil agencies it serves rather than to look like something it is not. The later lessons return to each of these threads; here the point is the mindset, plan for the force you actually are.
The whole-system view the course develops
The last idea this lesson plants, and the one the rest of the course grows, is that the planner sees communications as one system judged by four tests at once. An untrained eye sees separate things: some HF radios over here, some handhelds over there, a mesh, a server, a few tablets running TAK. The planner sees one system in which all of those interact, depend on a common floor of power and trained people, and succeed or fail together. And the planner judges that system not by any single virtue but by four tests held together: is it reliable, does the traffic get through when needed; is it resilient, does it degrade gracefully rather than collapse when a part fails; is it secure, can the right people read it and the wrong people not; and is it lawful, does every transmission sit within the law of wherever the member transmits. A system strong on three tests and weak on the fourth is not a strong system; it is a system with a fault line, and the planner's job is to have no fault line they have not seen and decided about.
These four tests map onto the rest of SIG 410, and seeing the map now will make the later lessons cohere. Reliability and the layering of bearers are the architecture, taught in Lesson 02, where you learn to combine HF, VHF and UHF voice, the mesh, and TAK so that no single failure is fatal and the common operating picture rides safely on the bearers beneath it. Lawfulness is the spectrum and licensing strategy of Lesson 03, where you learn to manage frequencies and call signs, to track members' licences, to default to licence-free sets for training, and the firm rule that amateur bands forbid encryption so sensitive traffic must go by an encrypted internet bearer and never over ham RF. Resilience is the continuity of Lesson 04, where you plan for lost power, lost internet, jamming, and disaster with graceful degradation and restoration priorities. Security shades into the interoperability and civil integration of Lesson 05, where you talk to civil agencies in plain language on agreed channels. And all four are held together by the governance of Lesson 10, the signals estimate, the communications annex, the SOPs, and the certificate and key management that turn a design into a governed, rehearsed, living plan.
So this lesson is the frame and the rest of the course is the picture. You begin, always, from the commander's requirement; you remember that communications serve command; you plan modestly and realistically for the small humanitarian force you actually are; and you hold the whole system to four tests at once. Carry those four habits into every lesson that follows and the course will feel like one argument rather than six topics.
In Practice: A Planner Sizes a Two-Team Task
Captain Rava is given a task to plan communications for: two small teams supporting a civil flood-relief effort in difficult ground, working with the local emergency services, over three days, with the commander, a Major, coordinating from a base location. Rava's first instinct, fresh from learning the bearers, is to design the lot: HF for everyone, a repeater, a full mesh, TAK on every device, redundancy everywhere. She catches herself, because she remembers the governing rule. Communications serve command, and she has not yet asked the commander a single thing. She has been designing around her favourite radios.
So she starts again, from the top of the flow. She sits with the Major and the task and draws out the requirement by the five questions. Who must talk to whom: each team to base, the two teams to each other, base to the civil emergency services. What must be reported: routine situation reports twice a day, immediate reports of anyone needing help, and a continuous position picture so the Major can see where both teams are. How reliable: the team-to-base links are critical, because a team that cannot reach base in this ground is a team alone, so each needs a real fall-back. How secure: most traffic is plain civil-support coordination and can go in clear, but any vulnerable person's location or medical detail must not go over open radio, so that traffic must ride the encrypted internet bearer. How far and what terrain: the teams will work low, wet ground where line-of-sight VHF voice will not reliably reach base, which decides the shape of the answer.
Only now does Rava choose bearers, and she chooses the smallest lawful set that meets the requirement, picked to fail in different ways. For each team-to-base link she sets a PACE plan: primary VHF voice via a repeater where it reaches, alternate HF voice which does not care about the hills, contingency the Meshtastic mesh for position and short text when voice is gone, emergency a pre-agreed return to base. The continuous position picture rides TAK over mobile data where there is coverage and over the mesh where there is not, so the Major keeps the common operating picture even when voice drops. For the civil emergency services she agrees a common channel in advance and a plain-language protocol, no internal jargon or codes on the shared net, with contact and frequency plans exchanged before the task. The sensitive traffic she routes only over the encrypted TAK and internet bearer, never over the amateur RF, because the law forbids encryption there. Then, and this is the part that makes her a planner and not just a clever operator, she writes it all down as a short communications plan, who talks to whom on which bearer with what fall-back under whose licence, issues it, and rehearses it on the milsim exercise before the task is real. When the repeater proves useless in the wet low ground on day one, nobody is surprised and nothing collapses, because the HF and the mesh were chosen for exactly that failure, and the system degrades gracefully to its floor. Rava's plan was not impressive. It was small, lawful, and sufficient, and it let the Major command. That is the whole of the planner's job.
Check Your Understanding
- Explain why the communications planner's view differs in kind, not just in scale, from the signals NCO's. Where does each role stand relative to the system, what is each role's product, and what is each judged by? Use the responsibility ladder in your answer.
- State the principle that communications serve command and explain the working test it gives you for every design decision. Then list the five questions you ask of a task to draw out the commander's requirement, and explain why the bearers must be chosen after the requirement and not before it.
- Explain why a small, young, non-territorial humanitarian force should plan modestly and realistically rather than imitate a large army's signals branch. Give at least two reasons rooted in what the Royal Kaharagian Army actually is, and name the four tests the planner holds the whole system to at once.
Reflection (write a short paragraph): You have spent the operator and NCO courses learning to make a net work from inside it, by hand, by skill. The planner is asked to stop holding the parts and instead design a system that holds itself, and to begin not from the radios they know but from a commander's requirement they must draw out. Think honestly about which part of that change you would find hardest: letting go of the hands-on doing you are good at, starting every plan from command rather than from kit, resisting the pull to build an impressive system instead of a sufficient one, or owning a whole system's failure rather than your own. Write, in your own words, what kind of communications planner you intend to be, and how you will keep "communications serve command" in front of you when a clever bearer tempts you to forget it.
Summary
- The move from NCO to communications planner is a change in altitude, not just in scale. The operator and NCO stand inside the system and make their part work by hand; the planner stands above it, designs it, and is judged by whether the whole system delivers what command needed.
- The planner's product is not a clean transmission or a well-run net but a design and a written, issued, rehearsed plan: who talks to whom, on which bearers, in what fall-back order, under whose licence, with what procedures and governance.
- Communications serve command, never the other way round. The system exists only to let the commander command, and every part is justified by a command requirement it meets. This gives a working test: add nothing that serves no requirement, and meet every requirement however unglamorous the answer.
- The planner begins not from a radio catalogue but from the commander's requirements, drawn out by five questions: who must talk to whom, what must be reported, how reliable each link must be, how secure, and how far over what terrain. Bearers are chosen last, as the smallest lawful set that meets the requirement.
- A small, young, non-territorial humanitarian force plans modestly and realistically. A few well-integrated, lawful bearers the force can actually crew, license, power, and sustain out-perform an oversized imitation of a large army's signals branch. Modesty fits the Army's lawful, supporting, humanitarian nature.
- The planner holds the whole system to four tests at once: reliable, resilient, secure, and lawful. A system strong on three and weak on the fourth has a fault line, and the planner's job is to have no unseen fault line.
- This lesson frames the problem the rest of the course solves. Lesson 02 designs the architecture (reliability and layered bearers), Lesson 03 the spectrum and licensing strategy (lawfulness), Lesson 04 resilience and continuity, Lesson 05 interoperability and civil integration (security and plain-language working with civil agencies), Lesson 06 information management and the common operating picture, Lesson 07 cyber defence of the force's communications, Lesson 08 communications capability development and sustainment, Lesson 09 reach-back and strategic communications, and Lesson 10 planning, orders, and governance. SIG 410 builds on the operator and NCO tiers of the Signals speciality and draws on PME 210 · Basic Staff Duties and Written Orders, HCR 220 · Emergency Preparedness and Civil Resilience, and HCR 210 · Aid to the Civil Power. The planner's craft is mastered by rehearsal and certified in person, including on airsoft milsim exercises.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia