Lesson Overview
The earlier lessons of this course built the parts: the signals NCO's role, the communications plan and the PACE plan, the physics of getting a signal through, the running of a net and a detachment, the training of operators, the frequency management and signals instruction that allocate the net, the supervision of communications security, the integration of the Army's digital systems, and the sustainment of communications over time. This lesson puts them together on an actual task. A task is the test of everything that came before, because a plan that looks complete on paper is worth nothing if the commander loses their voice at the moment they need it. The whole point of the signals NCO is this: from the moment the section steps off to the moment it returns, the commander is never without a way to talk to those above, beside, and below.
So we follow communications through the life of a task. We cover the part communications play in preparing for the task, confirming the PACE plan, issuing the frequency and call sign card, and briefing the reports the task will require; the pre-move communications check, a radio check on every link and a confirmation of the TAK picture, and the iron rule that comms not checked before moving are assumed broken; the flow of reports during the task that keeps the commander informed; the rehearsal of actions-on for a comms failure, falling back through PACE, sending a runner, and the lost-comms drill; and finally the after-action review that turns the day's signals into a better plan next time.
This is the knowledge layer. It teaches you how to think about communications across a task and what each step is for. The hands-on operating, the actual radio checks, the report drills, the runner and lost-comms rehearsals, is practised and signed off in person and on airsoft milsim exercises, where the net is run for real. Real transmitting is done only by licensed members on the amateur bands, or by anyone on licence-free or low-power sets; listening needs no licence, but transmitting does, and the signals NCO is the person who makes sure the section stays within the law.
By the end you will be able to prepare a section's communications for a task by confirming the PACE plan, issuing the frequency and call sign card, and briefing the required reports; run a pre-move communications check on every link and confirm the TAK picture; manage the flow of standard reports during a task and keep the commander informed; rehearse and lead the actions-on for a comms failure, including falling back through PACE, sending a runner, and the lost-comms drill; and run an after-action review of communications that improves the next plan.
Key Terms
- Communications in support: the discipline of weaving communications into a task from preparation to debrief, so the commander always has a working means to talk to higher, flanking, and subordinate stations.
- PACE plan: Primary, Alternate, Contingency, Emergency. For each link, the means listed in the order the section will fall back through when one fails (for example P = TAK over mobile data, A = VHF voice via repeater, C = VHF simplex, E = Meshtastic text or a runner).
- Frequency and call sign card: a small card or sheet held by every station that lists the call signs, frequencies and channels, the PACE means, the schedule, and the lost-comms drill, so no one is working from memory.
- Pre-move communications check: the radio check on every link, and confirmation of the TAK picture, carried out before the section moves; comms not checked before moving are assumed broken.
- Radio check: the proword exchange that confirms a link works and how well, answered with a readability and strength report (for example "Loud and clear").
- TAK picture: the shared common operating picture in Team Awareness Kit, showing team positions, markers, routes, and chat, exchanged as Cursor-on-Target messages.
- SITREP: a situation report, the routine update from a station to its commander on where it is, what it is doing, and what it needs.
- CONTACT report: the immediate report sent when a section makes contact with a person, vehicle, or incident of significance, sent first and detailed later.
- 9-line casualty report: a numbered casualty and evacuation report sent in a fixed order so nothing is forgotten and the receiving station can act on each line.
- SALUTE report: a sighting report, Size, Activity, Location, Unit or Uniform, Time, Equipment, used to report what is observed in a fixed order.
- Actions-on: the rehearsed drills for foreseeable events, including the action on a communications failure, agreed and practised before the task so no one improvises under pressure.
- Lost-comms drill: the pre-agreed plan for what each station does if it cannot raise the net, including timings, a rendezvous, and how contact is re-established.
- After-action review (AAR): the structured look back at how communications performed on the task, feeding lessons into the next plan and the next card.
Communications in mission preparation
A task's communications are won or lost in preparation, not on the move. By the time the section steps off, the signals NCO should have done three things, and a task that skips them is a task that will go quiet at the worst moment. The first is to confirm the PACE plan. The communications plan from Lesson 02 gives the section a PACE order for each link, who talks to whom, by what means, in what order of fallback. Preparation is where that plan stops being a document and becomes something every operator knows: the NCO confirms the means are actually available and serviceable for this task, this distance, and this terrain, and confirms that every station understands which means is Primary and what it falls back to. A PACE plan that lives only in the NCO's head is no plan at all.
The second is to issue the frequency and call sign card. Every station carries a small card or sheet that holds the working detail so that nobody operates from memory under stress. The card lists the call signs in use, the frequencies and channels for each link, the PACE means for each link, the radio schedule (when routine reports are due and when the net opens and closes), the Net Control Station, and the lost-comms drill in brief. On exercise this is a paper card; the discipline is that the same information sits in every station's hand, identical, so a station that loses the net knows exactly what to try next without asking. The card is short on purpose. It is a memory aid for trained operators, not a manual.
The third is to brief the reports the task will require. A task is a flow of information, and the section should know before it moves what it will be asked to send and in what form. The NCO names the reports the task will use, the routine SITREP and its schedule, the immediate CONTACT report, the casualty 9-line, the SALUTE sighting report, and reminds operators to compose before they key: think the message through, then send it cleanly. In a humanitarian or civil-response task the same applies to the reports the task is actually built around, a report that a route is blocked, that a shelter is full, that a vulnerable person has been found. If operators know the shape of the reports beforehand, they send them calmly and completely on the day instead of groping for words on a hot net.
FREQUENCY AND CALL SIGN CARD (example, exercise / low-power sets)
TASK: Civil response, river district DTG: 120600Z JUN 26
---------------------------------------------------------------
STATIONS CALL SIGN
Section comd SUNRAY
Det 1 ONE
Det 2 TWO
NCS / base ZERO (Net Control Station)
---------------------------------------------------------------
LINK: section internal LINK: section to base
P TAK / mobile data P TAK / mobile data
A VHF repeater (Ch 1) A VHF repeater (Ch 1)
C VHF simplex (Ch 2) C HF / NVIS (sked)
E Meshtastic text / runner E Meshtastic text / runner
---------------------------------------------------------------
SCHEDULE: routine SITREP every 30 min on the hour and half hour.
Net opens 0600Z, closes on ZERO's word.
REPORTS: SITREP / CONTACT / 9-LINE casualty / SALUTE.
LOST COMMS: see drill on reverse. RV at the start point.
---------------------------------------------------------------
The pre-move communications check
Nothing the section carries is assumed to work until it has been proven to work, and the proof is the pre-move communications check. This is the signals NCO's last act before the section moves, and it has two parts. The first is a radio check on every link. Not the Primary alone, and not a token check on one set, but a deliberate check across each link the PACE plan names, so that if the Primary fails on the day the section already knows the Alternate is alive. The NCS calls each station, each station answers with a readability and strength report, and the NCO notes any link that is weak or dead and acts on it before the section steps off rather than discovering it a mile out.
The second part is to confirm the TAK picture. Because the RKA fields a real TAK capability, a task that uses it must confirm the shared picture before moving: every station's marker is present on the common operating picture, positions are correct, the routes and markers for the task are loaded and visible to all, and chat passes both ways. A TAK client that shows itself but is not seen by the others, or shows a stale position, is a quiet failure that looks like success, and it is exactly the kind of thing the pre-move check exists to catch. Where a Meshtastic mesh carries position reports and chat off-grid, the NCO confirms the gateway is forwarding and that the light traffic, position and short text, is actually crossing between the mesh and TAK.
Running under all of this is one rule, and it is the rule of this whole lesson: comms that are not checked before moving are assumed broken. A link not checked is not a link the commander has; it is a hope. The discipline is to treat every unchecked means as already failed and to act accordingly, which in practice means the section does not move until the check is done, the failures are fixed or the PACE plan is adjusted to route around them, and the commander knows exactly which means are confirmed good. A clean radio check costs two minutes. A dead link found a mile from the start point can cost the task.
PRE-MOVE COMMS CHECK (run before the section steps off)
FOR EACH LINK IN THE PACE PLAN:
---------------------------------------------------------------
ZERO: "All stations, this is ZERO. Radio check, over."
ONE: "ZERO, this is ONE. Loud and clear, over."
TWO: "ZERO, this is TWO. Readability three, strength two,
over." <-- weak: NCO acts NOW, not on the move
ZERO: "ONE loud and clear, TWO weak. TWO, raise antenna /
get height / move to relay. Try again, over."
---------------------------------------------------------------
THEN CONFIRM THE TAK PICTURE:
[ ] every station's marker present on the shared map
[ ] positions correct (no stale / frozen markers)
[ ] task routes + markers loaded and visible to ALL
[ ] chat passes both ways
[ ] (off-grid) Meshtastic gateway forwarding PLI + chat
---------------------------------------------------------------
RULE: unchecked comms are assumed BROKEN.
Do not move until checked, fixed, or routed around.
Supporting the flow of reports during a task
Once the section is moving, the signals NCO's job is to keep information flowing so the commander is informed and those above and beside the section are informed in turn. Communications in support means the net carries the right reports at the right time, sent cleanly, without flooding it with chatter or starving the commander of the picture they need. The backbone is the routine SITREP on the schedule from the card: each detachment tells its commander where it is, what it is doing, and what it needs, on time, so that even when nothing is happening the picture stays current. A net that reports faithfully when quiet is a net the commander can trust when it is loud.
Against the routine sit the immediate reports, sent the moment the event happens and not held for the next schedule. The CONTACT report is sent first and detailed later: the fact of contact reaches the commander at once, with the detail following as it is known, because a commander who learns of a contact thirty minutes late has been failed by the net. The casualty 9-line is sent in its fixed numbered order so that nothing is forgotten under stress and the receiving station can act line by line. The SALUTE report passes a sighting in its fixed order, Size, Activity, Location, Unit or Uniform, Time, Equipment, so the observer reports what matters in a shape the commander can use. In a humanitarian or civil-response task the immediate reports are just as likely to be a person trapped, a route impassable, a hazard found, and they are sent with the same discipline.
The NCO's contribution to all of this is order on the net. Reports are composed before they are sent (think before you key), passed in clean voice procedure with the prowords that keep them short, and logged so there is a record of what was said and when. The NCO enforces the schedule, keeps the net clear for the immediate report when it comes, and above all keeps the commander informed, surfacing what the commander needs to know and not burying it under traffic that does not matter. Keeping the commander informed is not passing every word up; it is making sure the picture in the commander's head matches the picture on the ground.
THE FLOW OF REPORTS DURING A TASK
ROUTINE (on the schedule) IMMEDIATE (the moment it happens)
-------------------------- --------------------------------
SITREP where am I, CONTACT sent FIRST, detail later
what am I doing, 9-LINE casualty, fixed order,
what do I need nothing forgotten
(every 30 min) SALUTE Size Activity Location
Unit Time Equipment
+ civil-response reports:
route blocked, person found,
hazard, shelter full
-------------------------- --------------------------------
\ /
\ Think before you key. /
\ Clean voice procedure. /
\ Log every message. /
v v
+--------------------------------+
| COMMANDER KEPT INFORMED |
| picture in the head matches |
| the picture on the ground |
+--------------------------------+
Rehearsals and actions-on for comms failure
A plan survives contact only if it was rehearsed, and communications are no different. The signals NCO rehearses the actions-on for a comms failure before the task, so that when a link goes dead nobody improvises and nobody panics. The first action-on is to fall back through PACE. A station that cannot raise the net on the Primary does not declare failure; it works down the PACE plan in order, Primary to Alternate to Contingency to Emergency, trying the next means before deciding the link is gone. The simple troubleshooting drill runs alongside the fallback: check power and battery, volume and squelch, the right frequency or channel, the antenna and its connection, and your position (move, get height, try a relay) before declaring a link dead. Most "dead" links are a flat battery, a wrong channel, a loose antenna, or a body of ground in the way, and the trained operator runs the drill before they reach for the next PACE means.
When the means run out, the section falls back on the oldest bearer there is: a runner. A runner is part of the plan, not a sign it has failed. The Emergency line of many a PACE plan is a person carrying a message by hand to a known location, and on a task where the means are stretched the runner may be the thing that keeps the commander's voice alive. The NCO plans for it: a written message so nothing is lost in the carrying, a known route and a known destination, and a runner who knows where to go. A runner is slow, but a slow message that arrives beats a fast one that was never sent.
Holding all of this together is the lost-comms drill. This is the pre-agreed plan for what every station does when it cannot raise the net at all, and its whole value is that it needs no communication to work, because by definition there is none. The drill is on the card: it gives the time after which a station out of contact acts on the drill, what it then does (continue the task, hold, or return), an agreed rendezvous or lost-comms rendezvous where stations will go to re-establish contact, and how and when the net will try to call the missing station back. Because every station carries the same drill, a section can lose the net entirely and still come back together, each part doing the agreed thing at the agreed time and meeting at the agreed place. A lost-comms drill that is rehearsed turns a frightening silence into a known procedure, and that is the difference the signals NCO makes.
LOST-COMMS DRILL (every station carries the same plan)
CANNOT RAISE THE NET ON THE PRIMARY?
|
v
1. TROUBLESHOOT: power/battery -> volume/squelch ->
right freq/channel -> antenna + connection -> position
(move, get height, try a relay)
| still nothing
v
2. FALL BACK THROUGH PACE:
P -> A -> C -> E (try each in order before declaring dead)
| every means tried, still no contact
v
3. SEND A RUNNER (Emergency line):
written message, known route, known destination
| still no contact after the drill time
v
4. LOST-COMMS DRILL (no comms needed to work):
- after AGREED TIME, act on the drill
- do the AGREED ACTION (continue / hold / return)
- move to the AGREED RENDEZVOUS to re-establish contact
- NCS calls the missing station back on the schedule
|
v
SECTION REUNITES BY DRILL, NOT BY LUCK.
The after-action review of communications
A task is not finished for the signals NCO when the section returns; it is finished when its communications have been reviewed and the lessons captured. The after-action review of communications is short and honest, and it asks plain questions. Did the PACE plan hold, and at any point did the section fall back, and why? Did every link work as expected on the pre-move check and on the move, or did one fail in a way the check should have caught? Were the reports sent cleanly, on time, and in the right form, and did the commander always have the picture they needed? Did any station go to the lost-comms drill, and did it work? The signals log, kept through the task, is the raw material: with the times and the gist of each message in front of you, the review is grounded in what actually happened, not in what people half-remember.
The point of the review is not blame but improvement, and it feeds three things. It feeds the next plan: a link that failed for terrain becomes a changed PACE order or a planned relay next time; a repeater that did not reach becomes a note to get height or to go to HF and NVIS for that ground. It feeds the next card: a call sign that confused people, a schedule that was too tight or too loose, a lost-comms rendezvous that was poorly chosen, all get fixed on the card before the next task. And it feeds the training of operators: a fault corrected fairly in the review, a SITREP that rambled, a 9-line sent out of order, a key pressed before the message was composed, becomes a teaching point for the next exercise. The signals NCO who reviews every task honestly builds a section whose communications get quietly better with each one, and that is the whole craft: the commander is never without a voice, and the reason they are never without one is that the NCO learned from every time the voice nearly failed.
In Practice: A Civil-Response Task in the River District
After heavy rain a low-lying river district is flooding, and the section is tasked, in support of the civil authorities, to help check on isolated households and report blocked routes and hazards. The signals NCO prepares the communications the day before. She confirms the PACE plan for the ground: Primary is TAK over mobile data, but she knows the district has patchy coverage, so the Alternate is VHF voice through a repeater on high ground, the Contingency is VHF simplex between detachments, and the Emergency is Meshtastic text or a runner. She issues an identical frequency and call sign card to every station, base is ZERO and the Net Control Station, the section commander is SUNRAY, the two detachments are ONE and TWO, with the schedule, the PACE means per link, and the lost-comms drill on the reverse. She briefs the reports the task will use: a routine SITREP every thirty minutes, an immediate report of any route blocked, any household found in difficulty, and the casualty 9-line and SALUTE in case they are needed.
Before the section moves she runs the pre-move check. ZERO calls each station for a radio check: ONE answers loud and clear, but TWO comes back readability three, strength two, weak. Rather than move on it, she has TWO raise its antenna and step onto higher ground, and the second check is loud and clear, the antenna height doing what more power would not. She confirms the TAK picture: both detachment markers are present and correctly placed, the route and the marked households are loaded and visible to all, chat passes both ways, and because mobile coverage is thin she confirms the Meshtastic gateway is forwarding positions and short text off-grid. Comms checked, fixed, and confirmed, the section steps off.
On the task the net does its work quietly. SITREPs come in on the schedule and the commander's picture stays current. Then ONE finds a road washed out and sends an immediate report, composed before keying and passed in clean voice procedure, and ZERO logs it and pushes it to the civil authorities. Deep in the district TWO loses mobile data and TAK drops; the operator does not panic but runs the drill, checks battery, channel, antenna, and position, then falls back through PACE to VHF voice on the repeater and is back on the net within a minute, exactly as rehearsed. Later TWO drops out entirely behind a ridge that blocks the repeater; under the lost-comms drill on the card it does the agreed thing, completes its leg, and moves to the agreed rendezvous, where ZERO re-establishes contact on the schedule. No message was lost, because every station carried the same plan. That evening the signals NCO runs the after-action review from the log: the PACE plan held, the pre-move check earned its keep on TWO's weak link, the ridge that blocked the repeater becomes a planned relay for next time, and a rambling early SITREP becomes a teaching point for the next exercise. Through all of it the commander was never without a voice.
Check Your Understanding
- Describe the three things the signals NCO does to prepare a section's communications for a task, and explain why each one matters. Why does the lesson say a PACE plan that lives only in the NCO's head is no plan at all?
- What are the two parts of the pre-move communications check, and what is the rule about comms that are not checked before moving? Give an example of a "quiet failure" the TAK part of the check is meant to catch.
- A detachment cannot raise the net on its Primary means. Walk through what it does, in order, from troubleshooting through the PACE fallback and the runner to the lost-comms drill. Why does the lost-comms drill have value precisely because it needs no communication to work?
Reflection (write a short paragraph): This lesson says a task is the test of everything that came before, and that the signals NCO's whole job is to make sure the commander is never without a voice. Think about a task, real or on exercise, where a link might fail at the worst moment. What preparation, settled and rehearsed beforehand, the PACE plan, the card, the pre-move check, the actions-on, would keep the commander talking through that failure? Which of these is easiest to skip when time is short, and why is skipping it the false economy the lesson warns against?
Summary
- A task's communications are won in preparation. The signals NCO confirms the PACE plan so every station knows its means and its fallbacks, issues an identical frequency and call sign card so no one works from memory, and briefs the reports the task will require so operators send them cleanly on the day.
- Nothing is assumed to work until proven. The pre-move communications check is a radio check on every link in the PACE plan and a confirmation of the TAK picture (markers present and correct, routes loaded, chat both ways, the off-grid gateway forwarding). The governing rule: comms not checked before moving are assumed broken.
- During the task the net carries routine SITREPs on the schedule and immediate reports (CONTACT first and detail later, the casualty 9-line in fixed order, the SALUTE sighting, and the civil-response reports a humanitarian task is built around), all composed before keying and logged. The NCO keeps the net ordered and the commander informed, matching the picture in the commander's head to the ground.
- Comms failure is rehearsed, not improvised. The actions-on run the simple troubleshooting drill, fall back through PACE in order, send a runner with a written message by a known route when the means run out, and rest on a lost-comms drill carried identically by every station, with an agreed time, action, and rendezvous, so the section reunites by drill and not by luck.
- The task ends with an after-action review of communications, run honestly from the signals log, which feeds the next plan, the next card, and the training of operators, so the section's communications get quietly better with every task.
- Cross-references: this lesson rests on SIG 310 Lesson 02 (Communications Planning and the PACE Plan), Lesson 03 (Antennas, Propagation, and Getting Through), and Lesson 04 (Running the Net and the Detachment); it draws the report and voice-procedure discipline from SIG 201, the written signals paragraph from PME 210 Basic Staff Duties and Written Orders, the operational setting from FLD 230 Patrolling and Tactical Movement, and the civil-response framing from HCR 220 Emergency Preparedness.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia