Royal Army College

Lesson Overview

There is a quiet but total change that happens when a trained operator is given a stripe and made responsible for a section's communications. The operator's job was honest and bounded: keep my radio working, speak well, pass my traffic, and play my part on the net. The signals non-commissioned officer's job is larger and never quite finished. It is not "keep my radio working" but "keep the section's communications working", and those are not the same sentence with one word changed. The first is about a handset; the second is about a system of people, sets, frequencies, plans, and habits that must hold together when the weather turns, the repeater drops, and the youngest operator on the net has forgotten everything they were taught. This first lesson is about that change, what it asks of you, and why it is a step up in kind and not just in rank.

The course you are beginning, SIG 310, is the NCO tier of the Signals and Communications speciality. It assumes the operator courses, SIG 201 on radio communications and message handling and SIG 220 on communications security and digital discipline, and that you can work a net well yourself. What changes now is that you become responsible for whether other people can. You own the section's communications as a system; you set and enforce the standard; you train and assess the operators under you; you manage the kit, the frequencies, and the certificates; you advise the commander on what is and is not possible by radio; and you are the net authority who keeps a cool head when the net goes quiet and everyone looks to you. The later lessons teach the planning, the radio physics, the running of a detachment, and the training of operators in full. This one frames the role those skills serve.

This is the knowledge layer. Reading about responsibility does not make you responsible any more than reading about leadership makes a section follow you. The real work of the signals NCO, planning a link that gets through, holding a faltering net, correcting a tired operator without crushing them, calling the moment a means has failed and the next must take over, is practised and signed off in person and on airsoft milsim exercises, where a collapsed net has a visible cost and a watching section. Live transmission is done only by members who hold the proper licence, or on licence-free and low-power sets where no licence is required; the NCO is the person who makes sure of that. What you learn here is the shape of the job. By the end you will be able to describe the change from operator to leader of communications and why it is a change in kind; state the signals NCO's core responsibilities and own the section's communications as a system rather than a set of tasks; explain what it means to set and enforce the standard in voice procedure, security, and EMCON; describe your duty to train and assess operators and to manage kit, frequencies, and certificates; advise a commander honestly on what radio can and cannot do; and act as the net authority who stays calm and decides when the net goes quiet.

Key Terms

Signals NCO: a Corporal or Sergeant who runs and supervises a section or detachment's communications, responsible not for one radio but for the whole communications system the section depends on.
Net authority: the person who holds responsibility for a net, sets its standard, settles disputes on it, and decides what happens to it. On a section net this is normally the signals NCO or the commander.
Communications as a system: the view that a section's communications are not a pile of radios but an interacting whole, people, training, sets, antennas, batteries, frequencies, plans, and habits, that succeeds or fails together.
The standard: the agreed, enforced level of voice procedure, security, and discipline the section operates to, held the same whether anyone is watching or not.
EMCON (emission control): deliberate control of what the section transmits and when, to deny information to a listener and to save battery, ranging from free use down to listening silence.
PACE plan: Primary, Alternate, Contingency, Emergency. The comms means listed in fall-back order so the section knows what to switch to when the first fails.
Communications check: the drill, done before any task, of confirming every link by radio check, confirming the PACE plan is understood, and confirming the shared map is current. Comms not checked before moving are assumed broken.
Certificate (TAK): the per-user credential that lets a member's device connect to the Army's TAK server. The NCO controls who holds one and withdraws it when a member leaves the role.
Channel key (Meshtastic): the shared secret that admits a radio to the section's Meshtastic channel. Whoever holds the key can read and send on the mesh, so the NCO controls it.
Frequency and call sign card: the simple card listing who talks to whom, on what frequency or channel, with what call signs, on what schedule, and what the fallback is. The working summary of the signals plan.
Signals log: the running written record of the net, time, stations, and the gist of each message, kept so that what was passed can be proven and reconstructed.

From operator to leader of communications

Begin by being honest about what you are leaving behind, because it is comfortable. As an operator you had a clean, finishable job. Your radio was your responsibility and only yours. You knew at any moment whether you were doing it well: your set worked or it did not, your voice procedure was clean or it was not, your traffic got through or it was repeated. The boundary of the job was the edge of your own performance, a satisfying place to stand. You could be the best operator on the net and know it, and nothing outside your own handset was yours to answer for.

The signals NCO loses that clean boundary on the first day. Your performance is no longer the measure; the section's is. You can speak flawless voice procedure into a net that is collapsing because the operator three positions away cannot, and the net is still failing, and it is now your failure, not theirs. Most new NCOs feel this as a loss before they feel it as a promotion. The skill you spent two courses perfecting, working a radio, is now the floor you stand on, not the job you do. The job is making other people able to do what you can do, and keeping the whole arrangement working when several parts of it are tired, broken, or frightened at once.

That is why this is a change in kind and not merely in degree. A more senior operator is still an operator; a signals NCO is something different. The mental shift can be put in one line, and everything in this course flows from it. The operator's question is "is my radio working?" The NCO's question is "are the section's communications working?", and that question has no off switch. It is being asked when a battery you did not check goes flat, when an operator you did not train freezes on the net, when a frequency you did not deconflict clashes with another callsign. You cannot answer it by being good yourself. You answer it by building a system that is good without you having to hold every part of it by hand.

   THE OPERATOR (SIG 201 / 220)          THE SIGNALS NCO (SIG 310)
   --------------------------------      --------------------------------
   "Is MY radio working?"                "Are the SECTION'S comms working?"

   Responsible for one handset           Responsible for the whole system:
   and one operator (me)                 people, sets, freqs, plans, habits

   Measured by my own                    Measured by the WEAKEST operator
   performance on the net                on my net, not the best

   Job is bounded and finishable:        Job is open-ended: it is being
   send my traffic, then done            asked even when nothing is keyed

   I keep my voice procedure clean       I set the standard others keep,
                                         and enforce it fairly

   When my set fails, I fix my set       When ANY link fails, I diagnose
                                         it, fall back, and keep the net up

   I trust the plan I was given          I MAKE the plan, and answer for it

Read that table as a description of a promotion that is also a burden, because it is both. You are being trusted with the section's nervous system. The reward is real influence over whether the section can act at all. The price is that "communications failed" now ends, somewhere, with your name.

Owning the section's communications as a system

The most useful single idea in this whole course is that a section's communications are a system, not a heap of equipment. A heap of equipment is what an untrained eye sees: some radios, some batteries, a tablet running TAK, a few Meshtastic nodes in pouches. A system is what the NCO must see: those things plus the people who work them, the training that makes the people reliable, the antennas that decide whether a signal gets out, the batteries that decide whether it gets out for long, the frequencies and call signs that keep the traffic untangled, the PACE plan that decides what happens when a part fails, and the habits that hold the whole thing to a standard. The radios are the least interesting part. The system is everything around them that makes the radios useful.

Seeing communications as a system changes what you worry about. An operator worries about their handset. The NCO worries about the part most likely to fail next, which is almost never the handset. It is the half-charged battery nobody logged, the operator who has not touched a radio since the last exercise, the antenna lashed against a vehicle so it radiates into metal, the frequency never deconflicted with the other detachment, the expired TAK certificate, the PACE plan that lives only in your own head. None of these is a broken radio. All of them break the section's communications. The NCO's eye is trained to look past the working handset to the weak joint, because a system fails at its weakest joint, not its strongest set.

It helps to map the system out, so you can see all of it at once and ask of each part, who owns this, what is its state, and what happens when it fails. Lay your responsibilities out as a map and very little can hide:

                 THE SIGNALS NCO'S COMMUNICATIONS RESPONSIBILITIES

                          +---------------------------+
                          |   SECTION COMMUNICATIONS  |
                          |       ( the system )      |
                          +-------------+-------------+
                                        |
        +----------------+--------------+--------------+----------------+
        |                |              |              |                |
   +---------+    +-------------+  +----------+  +-------------+  +-------------+
   | PEOPLE  |    |  STANDARD   |  |   KIT    |  |    PLAN     |  |  NET        |
   |         |    |             |  |          |  |             |  |  AUTHORITY  |
   | train   |    | voice proc  |  | radios   |  | PACE plan   |  | settle the  |
   | assess  |    | security    |  | antennas |  | freq/CS card| | net, decide |
   | correct |    | EMCON       |  | batteries|  | comms check |  | when quiet  |
   | keep    |    | net         |  | freqs    |  | signals     |  | advise the  |
   | calm    |    | discipline  |  | certs/keys| | paragraph   |  | commander   |
   +---------+    +-------------+  +----------+  +-------------+  +-------------+

   Ask of EACH box:  Who owns it?   What state is it in?   What if it fails?
   The system fails at its WEAKEST box, not its strongest radio.

You are not expected to do all of this personally and at once; that is impossible and the next sections explain how the load is shared through training and delegation. You are expected to own it. Owning a thing means you know its state, you know who is holding it, and you know what happens when it breaks, even when someone else is doing the holding. The operator holds a radio. The NCO holds the whole map and knows, at any moment, which box on it is the one most likely to let the section down.

Setting and enforcing the standard

A section communicates to a standard, and the standard is whatever the NCO actually enforces, not whatever is written in a manual nobody is held to. This is worth stating bluntly because new NCOs often believe the standard is set by the existence of a rule. It is not. The standard is set by what you correct and what you let pass. If sloppy voice procedure goes uncorrected on a quiet day, you have just taught the section that sloppy voice procedure is acceptable, and they will give you exactly that when the day is loud. The standard lives in your reactions, not in the doctrine, and the section reads your reactions far more closely than they read any manual.

There are three faces to the standard, and the NCO owns all three. The first is voice procedure: clean prowords, call signs, RSVP speaking (rhythm, speed, volume, pitch), readback of critical detail, brevity, the discipline that lets a single shared channel carry meaning without collisions. You learned it as an operator; now you guard it for others. The second is security: assume someone is listening, keep traffic short and unrevealing, protect the Meshtastic channel keys and the TAK certificates, and never let a casual habit hand a listener the picture for free. The third is EMCON, emission control, the deliberate decision about what the section transmits and when. EMCON runs on a scale from free use of the net, through minimised traffic where you pass only what must be passed, down to listening silence where the section receives but does not transmit at all unless ordered. Choosing where on that scale the section sits, and changing it as the task changes, is the NCO's call and a real one: too much emission gives a listener your strength and position; too little leaves the commander blind.

Enforcing the standard fairly is a leadership skill as much as a technical one, and it is easy to get wrong in two opposite ways. The first wrong way is to let everything slide for the sake of being liked, which produces a popular NCO and a net that fails under pressure. The second is to correct everything harshly in front of everyone, which produces a frightened operator who keys up less and hides faults rather than reporting them. The standard is held by correcting consistently, correcting the fault and not the person, correcting small things early so they never grow into the habit that collapses a net, and saving the public correction for the rare fault that endangers the task. Fairness is not softness. The fairest thing you can do for a young operator is hold them to a standard that will keep them and their section safe, and to do it in a way that makes them better rather than quieter.

Training, assessing, and managing the detachment

A signals NCO is an instructor whether or not they ever asked to be, because the only way to make a section's communications reliable is to make its operators reliable, and operators are made by training, not by issue. You cannot draw trained operators from the stores. You teach voice procedure, you set drills, you correct faults, and you assess until you are honestly sure that the operator can do the thing under noise and stress and not only on a calm afternoon. This links directly to the Training and Instruction speciality and is treated in full in a later lesson; what matters here is that you accept the duty. The operators on your net are as good as you have trained them, and on the day it counts you will not be able to do their job for them.

Alongside training sits the plain administration of the detachment, which is unglamorous and decides whether anything works. You manage the kit, knowing what sets the section holds, what state they are in, and crucially what state their batteries are in, because a flat radio is no radio and the battery is the part most often neglected. You manage the frequencies and call signs, keeping a simple card that records who talks to whom, on what frequency or channel, with what call signs, on what schedule, and what the fallback is, deconflicted with any other detachment so two call signs do not collide. You manage the section's access to its own devices, the Meshtastic channel keys, and the TAK server certificates, controlling who holds them and withdrawing them when a member leaves the role, because access that is never withdrawn is a growing security hole. And you keep, or have kept, the signals log, the running record of the net that lets you prove and reconstruct what was passed.

All of this is the same discipline applied before every task as a communications check. Before the section moves, you confirm every link with a radio check, confirm that everyone understands the PACE plan, and confirm that the shared map is current. The rule is firm and worth memorising: communications that have not been checked before moving are assumed broken. It is the cheapest insurance the NCO buys, a few minutes that turn "I think the net works" into "I know the net works", and it is the difference between discovering a dead link standing safe at the start line and discovering it spread out across the ground with the task already running.

Advising the commander, and holding the net when it goes quiet

The commander is not a signaller and should not have to be. They will tell you what they want to achieve, and your job is to tell them, honestly, what radio can and cannot do to serve it. This is one of the most valuable things an NCO offers and one of the most tempting to get wrong, because the easy answer is always "yes, we can do that". A commander who is told communications are possible when they are not will build a plan on a link that does not exist, and the plan will fail at the worst moment with no fallback prepared. The NCO who says "not by voice from that valley, the hills block VHF, but I can keep you a position picture over the mesh and reach you by HF" has given the commander something they can actually plan around. Your honesty about the limits is worth more than your enthusiasm about the possibilities. Advise on what is real: this distance, this terrain, these antennas, these licences, this battery state, and therefore this is possible and this is not.

The last duty defines the role under pressure and is the hardest to teach: when the net goes quiet, you keep a cool head, and the section reads your face to decide whether to panic. A silent net is the loudest test a signals NCO faces. Something has failed, or nothing has, and the section is waiting to know which. The untrained reaction is to fill the silence with anxious calls, "hello, hello, do you read", which clutters the channel and broadcasts to any listener that the section is rattled. The NCO's reaction is a drill, calm and ordered: work the simple "no comms" troubleshooting, power and battery, volume and squelch, the right frequency or channel, the antenna and its connection, and your own position, before declaring the link dead; and if the link is genuinely gone, move to the next rung of the PACE plan without drama, because it was agreed before the task for exactly this moment. You are the net authority. The net is steady because you are steady, and the section is steady because the net is. A cool head is not a personality you are born with; it is the visible result of a system you prepared and drills you rehearsed, so that when the quiet comes you are executing a response, not inventing one.

In Practice: A Corporal Takes the Detachment

Corporal Idris has been a strong operator for two years, top of his SIG 201 net and quietly proud of it. He has just been made responsible for his section's communications, and on his first exercise he makes the new NCO's classic mistake: he runs the net beautifully himself and lets the rest of the section drift. His own voice procedure is flawless. Two positions away, Private Sanu keys up over another station, forgets to read back a grid, and fills a quiet moment with chatter, and Idris, busy being an excellent operator, lets it pass. By mid-morning the net is a mess of collisions and half-heard reports, and the commander cannot get a clear picture. Idris's radio is working perfectly. The section's communications are failing. The gap between those two sentences is the whole of his new job, and he feels it land.

He resets that evening, and the difference the next day is not that he operates better, because he already operated well, but that he stops carrying the net alone and starts running it as a system. He builds a frequency and call sign card so everyone knows who talks to whom on what, and writes a PACE plan on it, primary VHF voice via the repeater, alternate VHF simplex, contingency the Meshtastic mesh for position and short text, emergency a return to the rendezvous, and briefs it in one sentence each. Before the section moves he does a communications check, a radio check on every link, a confirm that everyone can recite the PACE plan, a glance that the TAK picture is current, and only then lets them step off. On the ground he corrects Sanu once, quietly, on the readback, fault not person, and Sanu gets it right after. When the commander asks whether he can keep voice into the wooded low ground ahead, Idris does not say yes to please him; he says voice will not hold in there, but the mesh will keep the section on the map and he can relay by simplex from the high point, and the commander plans around that. When the repeater drops an hour later and the net goes briefly silent, nobody panics, because Idris does not. He works the no-comms drill, finds the repeater genuinely gone, calls the move to simplex in a level voice, and the task carries on. The section's communications held that day not because Idris was the best operator present, though he was, but because he finally answered the only question that was now his: are the section's communications working? Yes, because he had built the system that made them so.

Check Your Understanding

Describe the change from operator to signals NCO and explain why it is a change in kind and not merely in rank. State the one-line shift in the question each role asks, and give two specific ways the NCO's job differs from the operator's beyond simply doing more.
Explain what it means to own the section's communications as a system rather than as a heap of equipment. Name at least four parts of the system beyond the radios themselves, and explain why the system fails at its weakest part rather than at its strongest set.
The standard, you are told, is whatever the NCO actually enforces. Explain what that means and name the three faces of the standard the NCO owns. Then describe the two opposite ways of enforcing the standard badly, and how the NCO corrects fairly instead.

Reflection (write a short paragraph): You spent the operator courses learning to ask "is my radio working?" and learning to answer it well. The signals NCO never gets to ask so small a question again; the question becomes "are the section's communications working?", and it has no off switch and no clean finish. Think honestly about which part of that change you would find hardest: the loss of a bounded, finishable job, the responsibility for operators you did not train, the duty to tell a commander an unwelcome truth, or the quiet net that the whole section is watching you handle. Write, in your own words, what kind of signals NCO you intend to be, and what system you would build so that the section's communications are good without you having to hold every part of them by hand.

Summary

The move from operator to signals NCO is a change in kind, not just in rank. The operator asks "is my radio working?"; the NCO asks "are the section's communications working?", a question with no off switch and no clean finish.
The operator is measured by their own performance and is responsible for one handset. The NCO is measured by the weakest operator on the net and is responsible for the whole system: people, standard, kit, plan, and net authority.
A section's communications are a system, not a heap of equipment. The radios are the least interesting part; the people, training, antennas, batteries, frequencies, call signs, PACE plan, and habits are what make the radios useful. The system fails at its weakest joint, not its strongest set.
The NCO sets and enforces the standard, which is whatever they actually correct, not whatever a manual says. The standard has three faces: voice procedure, security, and EMCON. Enforce it consistently and fairly, correcting the fault and not the person, neither letting all slide nor crushing operators into silence.
The NCO is an instructor, making operators reliable through training and honest assessment, and a manager of kit, batteries, frequencies, call signs, the Meshtastic channel keys, the TAK certificates, and the signals log. Before every task comes the communications check: comms not checked before moving are assumed broken.
The NCO advises the commander honestly on what radio can and cannot do, because a "yes" that is not true builds a plan on a link that does not exist. The NCO is the net authority who keeps a cool head when the net goes quiet, works the no-comms drill, and falls back through the PACE plan without drama.
This lesson frames the role the rest of the course serves. Lesson 02 teaches communications planning and the PACE plan, Lesson 03 antennas and propagation, Lesson 04 running the net and the detachment, Lesson 05 training and assessing operators, Lesson 06 frequency management and the signals instruction, Lesson 07 supervising communications security in the detachment, Lesson 08 integrating the digital systems the Army fields, Lesson 09 sustaining communications over time, and Lesson 10 communications in support of a task. SIG 310 builds on SIG 201 · Radio Communications and Message Handling and SIG 220 · Communications Security and Digital Discipline, and draws on PME 210 · Basic Staff Duties and Written Orders, the Training and Instruction speciality, LDR 301 · Junior Leadership, and FLD 230 · Patrolling and Tactical Movement. The role is mastered by rehearsal and certified in person, including on airsoft milsim exercises.

The Signals NCO's Role