Royal Army College

Lesson Overview

The earlier lessons in this course built communications inward: a force-level architecture, a spectrum and licensing plan, and resilience that keeps the force talking to itself when bearers fail. This lesson turns the planner outward. In the humanitarian and civil-support tasks the Royal Kaharagian Army actually performs, the hardest communications problem is rarely talking to your own sections. It is talking to the people who own the operation: the fire service, the police, the ambulance and medical services, the local council, the utility crews, and the volunteer agencies, none of whom share your radios, your call signs, or your procedures. A plan that connects the force to itself but not to its civil partners has solved the easy half of the problem.

This is the planning layer for that outward connection. It teaches you to agree a common channel or a liaison before the task, to strip your traffic of internal jargon and codes on any shared net, to exchange contact and frequency plans in advance so nothing has to be improvised under load, and to fall back on the International Code of Signals and standard voice procedure as the common ground that works across organisations and even across languages. Above all it teaches the principle that governs every part of it: in Aid to the Civil Power the Army supports and does not supplant the civil authorities, so the communications plan defers to theirs. Their net, their channels, their command. You fit in.

This is the knowledge layer. The planning method here is studied online and at your own pace, but actually liaising with civil agencies, agreeing channels, and operating on a shared net are practised and signed off in person and on airsoft milsim exercises that simulate a multi-agency task. Any live radio transmission in such an exercise is made only by licensed members on the proper bands, or by anyone on licence-free or low-power sets, never on a civil agency's operational frequencies, which you listen to and coordinate with but do not key up on without their leave. By the end you will be able to explain why interoperability with civil agencies is a planning problem and not an equipment problem, set up a common channel or a liaison arrangement, write and operate on a shared net in plain language, exchange a contact and frequency plan in advance, use the International Code of Signals and standard voice procedure as cross-organisation common ground, and design a communications plan that defers properly to the civil authority under HCR 210.

Key Terms

Interoperability: the ability of two or more organisations to communicate and work together effectively, despite using different equipment, procedures, and language. It is achieved mostly by agreement and planning, not by buying matching radios.
Civil integration: fitting the force's communications into a civil-led operation so that the force becomes a useful contributing element rather than a separate, disconnected one.
Aid to the Civil Power: the doctrine, taught in HCR 210, under which the Army assists the lawful civil authorities at their request and under their direction, supporting and never supplanting them.
Liaison officer (LO): a named person placed with another organisation, or hosting another organisation's person, whose job is to carry information accurately between the two and to translate procedures and intent across the boundary.
Common channel: a single agreed frequency or talk-group that two or more organisations monitor and use to coordinate, distinct from each organisation's own internal nets.
Shared net: any radio net on which more than one organisation operates, where the lowest common standard of plain language and discipline must govern, because not everyone shares your training.
Plain language: ordinary, unambiguous words in full, with no internal codes, abbreviations, or unit slang, used so that anyone listening from any organisation understands the message first time.
Frequency plan (comms card): a single written sheet listing the channels, call signs, contacts, and meeting points for a task, exchanged between organisations before the task begins.
International Code of Signals (ICS): the public-domain international system (NGA Pub 102) of single-letter and short-group signals, given by flag, light, or sound, carrying fixed safety and distress meanings that cross language barriers.
Incident command: the civil arrangement (often a single Incident Commander supported by agency leads) that runs a multi-agency response and to whose structure the force's communications plan must conform.

Why interoperability is a planning problem, not an equipment problem

It is tempting to think interoperability is solved by hardware: buy the radios the fire service uses, or a gateway box that bridges two systems, and the problem disappears. It does not. A small humanitarian force cannot afford, license, or justify the encrypted trunked networks the emergency services run, and it has no business on them uninvited. Even where a technical bridge exists, two organisations that have never agreed who calls whom, in what words, about what, will talk past each other on a perfectly clear channel. The failures that matter in a real multi-agency response are almost never "we could not make a radio link." They are "nobody knew which channel the others were on," "we used a code they did not understand," "we did not have their number," and "we cut across their command without meaning to." Every one of those is a planning failure, fixed before the task with a conversation and a sheet of paper, not with equipment on the day.

So the planner treats interoperability as a set of agreements reached in advance. There are only a few of them, and they are simple. Agree how the force and the civil agencies will reach each other: a common channel, a liaison, or both. Agree to speak plainly on anything shared. Agree the channels, call signs, and contacts in writing and swap them ahead of time. Agree the common fallbacks, voice procedure and the International Code of Signals, for when the agreements themselves run short. And agree, first and last, that the civil authority is in charge and the force conforms to its plan. Get those agreements made and written down and the equipment, whatever each side happens to own, becomes a detail. Skip them and the best equipment in the country will not save the response.

The mindset shift the planner must make is from "how do I connect my force" to "how does my force plug into theirs." The civil response existed before the Army arrived and will continue after it leaves. The Army is a guest contributing a capability. The communications plan is the plan for being a good, legible, well-behaved guest who can be reached, understood, and tasked, and who never gets in the way.

Agreeing a common channel or a liaison

There are two basic ways to bridge two organisations, and a good plan usually uses both. The first is a common channel: a single frequency or talk-group that the force and the relevant civil agencies all monitor and use to coordinate. This does not mean the force joins the fire service's encrypted operational net. It means a plainly agreed shared channel, very often on a licence-free allocation that anyone may use, such as PMR446 or, in the US example, FRS or GMRS, set aside for cross-organisation coordination. Each organisation keeps its own internal nets private; the common channel is the doorway between them. The planner's job is to agree which channel that is, confirm every party can reach it with the sets they have, and publish it on the comms card so nobody is hunting for it on the day.

The second is a liaison, and it is often the more powerful of the two. A liaison is a person, not a frequency. The force places a named liaison officer, with a radio for the force's own net, physically alongside the civil incident command or the relevant agency lead; or it hosts a civil liaison who sits with the force. That person carries information across the boundary in both directions, translating not just words but procedures and intent. A liaison solves the problems a common channel cannot: they can clarify a confusing request face to face, they can represent the force's capabilities and limits honestly so the force is tasked sensibly, and they give the civil commander a single accountable point of contact for everything the Army is doing. Where a common channel connects the nets, a liaison connects the commands.

  MULTI-AGENCY COMMS LIAISON  (flood / disaster task)

                +-------------------------------+
                |   CIVIL INCIDENT COMMAND       |
                |   (Incident Commander +        |
                |    agency leads)               |
                +---------------+----------------+
                                |
            ......COMMON CHANNEL (plain language).......
            :              :              :            :
      +-----+----+   +-----+----+   +-----+----+   +---+--------+
      | Fire     |   | Police   |   | Ambulance|   |  RKA       |
      | service  |   |          |   | / medical|   |  LIAISON   |
      +----------+   +----------+   +----------+   +-----+------+
       (own net)      (own net)      (own net)          |
                                                        | RKA internal net
                                                        | (own call signs,
                                                        |  PACE, TAK)
                                              +---------+----------+
                                              |  RKA sections /    |
                                              |  detachment        |
                                              +--------------------+

  Two bridges:  COMMON CHANNEL joins the nets (coordination, plain language).
                LIAISON joins the commands (tasking, intent, accountability).
  The RKA keeps ONE internal net; only the liaison and the common
  channel cross the boundary. The force never keys the agencies' own nets.

Notice what the diagram protects. The force runs one tidy internal net, with its own call signs, its own PACE plan, and its TAK common operating picture, and that internal complexity stays on the force's side of the line. Only two things cross into the civil response: the liaison and the common channel. This keeps the force legible to its partners. A civil commander does not need to learn the Army's call signs or watch its map; they need one person they can task and one channel they can call. The planner's design should make the boundary that clean on purpose.

Plain language on shared nets

The single most common avoidable failure on a multi-agency net is language. Every organisation grows its own shorthand: codes, abbreviations, unit nicknames, numbered statuses, and procedures that mean something precise to insiders and nothing, or worse the wrong thing, to everyone else. On the force's own internal net, that shorthand is efficient and proper. On any shared net it is a hazard. A code that saves the force three seconds can cost a partner agency a wrong turn, a missed casualty, or a unit sent to the wrong place. The rule on shared nets is absolute: plain language only. Say what you mean in ordinary, full words that any listener from any organisation understands the first time.

Plain language does not mean undisciplined language. The voice procedure taught in this speciality, clear call signs, the prowords, readback of critical detail, the phonetic alphabet for spelling, and figures spoken digit by digit, all still apply and in fact help, because they are widely recognised and unambiguous. What you drop is the internal vocabulary, not the discipline. You still say THIS IS, OVER, ROGER, SAY AGAIN, and I SPELL. You stop saying internal status codes, unit slang, and any abbreviation a partner would not know. The aim is a transmission that is short, disciplined, and instantly understood by a firefighter, a paramedic, and a council officer who have never heard of the Army's internal procedures.

  SHARED-NET PLAIN LANGUAGE  ·  DO  /  DON'T

  SITUATION            DON'T (internal)              DO (plain language)
  ------------------   ---------------------------   ----------------------------
  Report a casualty    "One T1, send the bus"        "One person, serious leg
                                                      injury, needs an ambulance"
  Give a location      "We're at the usual RV"       "We are at the road bridge
                                                      on Mill Lane, north side"
  Status / numbers     "Call sign 21A, status 4"     "RKA section, two people,
                                                      task complete, standing by"
  Acknowledge          "Lima Charlie, wilco"         "Received, loud and clear,
                                                      we will do it" (WILCO is OK)
  Ask for repeat       (mumble / guess)              "Say again all after
                                                      'evacuate', over"
  Numbers / spelling   "twenty-two houses"           "FIGURES two two houses";
                                                      spell names: "I SPELL..."
  Hand over a job      internal code for the task     name the task in full words

  KEEP: call signs, prowords (OVER/OUT/ROGER/WILCO/SAY AGAIN/I SPELL),
        phonetic alphabet, digit-by-digit figures, readback of critical detail.
  DROP: status codes, unit slang, internal abbreviations, "over and out".
  TEST: would a paramedic who has never met us understand this, first time?

The test in the last line of the table is the one to teach operators. Before keying a shared net, ask: would someone from another service, who has never trained with us, understand this on the first hearing? If not, say it again in plainer words. It is slower by a second or two and it prevents the mistakes that cost hours. The planner enforces this not by hoping but by writing it into the communications SOP and rehearsing it on every multi-agency exercise, so that plain language on shared nets is a trained reflex and not a thing operators have to remember under stress.

Exchanging contact and frequency plans in advance

Almost everything that goes wrong on the day was knowable beforehand. The remedy is to exchange the plan in advance, on a single sheet, between the force and its likely civil partners, before any task and ideally as a standing arrangement renewed periodically. This sheet, the frequency plan or comms card, is the most valuable single artefact of civil integration, because it turns a frantic on-scene scramble into a quick confirmation of something already agreed. It should be short enough to fit on one side and clear enough to read in poor light.

A workable comms card for a multi-agency task carries: the common channel or channels and who monitors them; each organisation's coordination contact and a phone number for them; the force's liaison and how to reach them; the call signs the force will use, kept simple and pronounceable; the PACE order for force-to-civil contact, so everyone knows the fallback when the common channel fails; the agreed meeting point or rendezvous; and the date and a version number so an old card is never mistaken for the current one. The planner produces the force's half of this, shares it with civil partners through whatever standing relationship exists with the local authorities and services, and asks for theirs in return. Exchanged ahead of time and held by every party, the card means that when the task begins nobody is asking "what channel," "who do I call," or "where do we meet." They already know.

The planner should also build these relationships in peacetime, not on the night of the flood. The right time to swap comms cards and agree common channels with the local emergency services is during quiet liaison, joint exercises, and emergency-preparedness planning under HCR 220, when there is time to test that the channels actually work between the sets each side owns and to fix it calmly if they do not. A relationship and a current comms card already in the drawer is worth more than any amount of clever equipment improvised at the scene.

Common ground across organisations and languages

Even with channels agreed and plain language enforced, two organisations meeting for the first time, or organisations that do not share a language, need a fallback that is common to everyone and depends on no prior arrangement. There are two, and the planner relies on both.

The first is standard voice procedure itself. The prowords, the phonetic alphabet, the digit-by-digit numbers, and the readback of critical detail taught in ACP 125 and its civil equivalents are not the Army's private property. They are an international common standard, recognised by aviation, maritime, emergency, and amateur radio communities the world over. Two parties who have never met but who both use OVER, SAY AGAIN, I SPELL, and the phonetic alphabet can pass an accurate message immediately, because the procedure removes the ambiguity that language and accent introduce. This is precisely why voice procedure is the bedrock that data tools never replace: it is the lowest common denominator that works between strangers. The planner should treat clean voice procedure not as drill for its own sake but as the force's passport onto any shared net.

The second is the International Code of Signals, the public-domain system in which single letters and short groups carry fixed safety and distress meanings, given by flag, by light, or by sound. Its value here is exactly that it crosses language: a single letter has the same urgent meaning to anyone who knows the code, regardless of what language they speak. In a flood or disaster task with international or non-English-speaking partners, or simply where voice has failed and only light or sound is left, a handful of these single-letter signals are common ground that needs no shared vocabulary at all.

  INTERNATIONAL CODE OF SIGNALS  ·  a few single-letter signals worth knowing
  (each is one fixed meaning; given by flag, light flash, or sound)

    LETTER   PHONETIC    MEANING (fixed, crosses language)
    ------   ---------   -----------------------------------------------
      A      Alfa        Diver down; keep clear, slow speed
      K      Kilo        "I wish to communicate with you"
      N      November    "No" (negative)
      C      Charlie     "Yes" (affirmative)
      O      Oscar       "Man overboard"
      V      Victor      "I require assistance"
      W      Whiskey     "I require medical assistance"
      U      Uniform     "You are running into danger"

  ALSO: SOS (3 short, 3 long, 3 short) is the universal distress call,
        in sound or light. PAN-PAN by voice = urgency, not yet distress.

  Use case: where language is shared and radio works, talk plainly.
  Where it is not, or where only light/sound is left, these fixed
  signals pass the essentials with no common vocabulary at all.

The planner need not turn operators into signalling experts. The aim is that a force member in a multi-agency setting knows that this common ground exists, recognises the most important distress and assistance signals, and reaches for voice procedure as the default tool for talking to anyone. These are the bridges that work when prior arrangements have run out: a shared procedure and a shared code, both belonging to no single organisation and understood across all of them.

The Army supports and does not supplant: deferring to the civil plan

Everything in this lesson rests on one principle from HCR 210 Aid to the Civil Power: the Army assists the lawful civil authorities at their request and under their direction. It does not take over. The fire and rescue service, the police, the ambulance service, and the local authority own the response; the Army is a capability they may call upon. This is not only a legal and constitutional point, though it is firmly that. It is the rule that decides every communications question in a civil task. Whose channels do we use? Theirs. Whose call sign discipline governs the shared net? Theirs. Whose incident command structure does our plan conform to? Theirs. Who decides what the force does and when? They do, through the liaison and the common channel. The force's communications plan is built to defer.

In practice this means the planner designs the force's comms to fit under the civil incident command, not alongside it as an equal and certainly not above it. The liaison reports to and takes tasking from the civil command. The force monitors the common channel the civil commander nominates and uses the channels they allocate. The force does not impose its own procedures on the shared net beyond the plain-language and voice-procedure discipline that helps everyone; it adopts the civil command's language and reporting where they differ. And critically, the force never keys up on the emergency services' own operational frequencies uninvited, both because it is unlawful to transmit where you are not authorised and because it is the precise opposite of supporting: cutting across the very command you came to help. The force listens, coordinates through the agreed bridges, and acts when tasked.

There is a freeing simplicity in this for the planner. You do not have to design a communications system that runs a flood response, because you are not running the flood response. You have to design one that lets a small force be reliably reached, clearly understood, and sensibly tasked by the people who are, and that gets out of their way otherwise. A plan that achieves that, modest, plain, well-rehearsed, and deferential, is exactly the plan a humanitarian home-defence force should bring to the civil power's aid.

In Practice: a section into a multi-agency flood response

Heavy rain has overwhelmed a low-lying district and the civil authorities, with the emergency services stretched, request RKA assistance under Aid to the Civil Power. A planning officer holding the rank of Major designs the communications for the contribution: one section, led by a Corporal, tasked with sandbagging and assisting evacuation of residents from flooded streets.

The planner does not invent anything on the night, because the work was done in peacetime. A current comms card, exchanged with the district's emergency planning team during a joint exercise three months earlier, already names a PMR446 coordination channel that every party can reach with handheld sets, lists the incident command's contact number, and records the force's standing call signs. The planner confirms the card is current, briefs the section, and deploys a Second Lieutenant as liaison officer to sit physically with the Incident Commander at the forward control point, carrying a force-net radio.

On the ground the arrangement does exactly what it was designed to do. The section runs its own quiet internal net with its own call signs, its PACE plan, and TAK positions feeding back over Meshtastic where mobile data has failed, all of which stays on the force's side of the boundary. The Incident Commander never has to learn any of it. When the command wants the section moved to a collapsing wall two streets over, the order goes to the Second Lieutenant liaison face to face, who passes it cleanly onto the force net. When the section finds an elderly resident who cannot walk, the Corporal reports on the common channel in plain language: "RKA section to control, we have one person, unable to walk, needs an ambulance, at the corner of the chemist and the bank, over." No status codes, no internal slang, full words, readback confirmed. A paramedic who has never trained with the Army understands it instantly and is routed there. At no point does the section transmit on the fire or ambulance services' own frequencies; it coordinates only through the common channel and the liaison, and takes its tasks from the civil command. The Army supported. It did not supplant.

Check Your Understanding

A colleague proposes solving interoperability with the local fire service by buying radios compatible with the fire service's network. Explain why this misunderstands the problem, and list the agreements that actually deliver interoperability.
On a shared multi-agency net, distinguish what an operator must DROP from their normal radio habits and what they must KEEP. Give two concrete examples of each, and state the one-line test for whether a transmission is fit for a shared net.
Under Aid to the Civil Power, the principle is that the Army supports and does not supplant the civil authorities. Give three specific communications consequences of that principle, and explain why the force must never key up on the emergency services' own operational frequencies uninvited.

Reflection (write a short paragraph):

Think about the comms card and the liaison as the only two things that cross the boundary between the force and the civil response. Why is it valuable to keep the boundary that clean, and what would go wrong for a civil commander if the force instead expected them to learn its internal call signs, codes, and common operating picture in order to work with it?

Summary

Interoperability with civil agencies is a planning problem, not an equipment problem. The failures that matter (wrong channel, codes nobody understands, no contact details, cutting across command) are fixed in advance with agreements and a sheet of paper, not with hardware on the day.
Bridge the force to its civil partners two ways: a common channel (often licence-free, joining the nets for coordination) and a liaison officer (a person joining the commands for tasking, intent, and accountability). Keep the force's internal net on the force's side of the boundary.
On any shared net, use plain language only: drop internal codes, status numbers, and slang, but keep call-sign and voice-procedure discipline (prowords, phonetic alphabet, digit-by-digit figures, readback). Test every transmission: would a partner who has never trained with us understand it first time?
Exchange a frequency plan / comms card in advance, built in peacetime through HCR 220 emergency-preparedness liaison, so that channels, contacts, call signs, PACE, and rendezvous are confirmed rather than improvised.
Rely on standard voice procedure and the International Code of Signals as common ground that crosses organisations and languages and needs no prior arrangement.
Defer to the civil plan. Under HCR 210 Aid to the Civil Power the Army supports and does not supplant: it uses the channels the civil command allocates, conforms to their incident command, takes tasking through the liaison and common channel, and never transmits on the emergency services' own frequencies uninvited.
Builds on Lesson 02 (architecture) and Lesson 04 (resilience) of this course; draws on FLD 220 Signals and Field Communication and SIG 310 for voice procedure, PME 210 Basic Staff Duties for the signals annex, HCR 220 Emergency Preparedness for peacetime liaison, and HCR 210 Aid to the Civil Power for the governing doctrine. Carries forward into Lesson 10 (Planning, Orders, and Governance).

Interoperability and Civil Integration