Communications - Verbal Communications - UNITAF Force Manual (FM)




FM/C86 - Communications - Verbal Communications
The FM outlines our core skills, policies and guides to ensure every member stands ready for the mission ahead.



FM/G276 - Communication Basics

FM/BG-1276 - Brevity

Brevity is the art of saying a lot with few words. One must always strive to be frugal on the number of words needed to convey a message - there's a lot that needs to be said by many people in a fight, and it's all important. Utilizing brevity allows for all the important things to be communicated as rapidly as possible.

FM/BG-1277 - Clarity

One must strive to be very clear in their language. This requires the usage of defined tactical language terms, brevity words, a clear and loud voice, and so forth. Enunciation and repetition of critical statements is helpful as well.

FM/BG-1278 - Confirmation and read-back

It's important to confirm that you heard orders, so that leaders know that they are being understood. Additionally, it can be helpful to provide a 'read back' of an order to confirm that you fully understand what is being asked of you - this is done by restating what you were ordered to do, so that the person giving the orders can confirm that you heard them correctly.

FM/BG-1279 - Alerting and identifying

Alerting is the act of using key words to get the attention of people before you start saying something important. For example, a Squad Leader might say "Squad, listen up!". Identifying is the act of saying who you are and who you're trying to contact when speaking over a radio. This helps reduce confusion and alerts people that someone is attempting to tell them something.

FM/BG-1280 - Usage of standard operating procedures and tactical language

Being familiar with the standard formats of SITREPs, CASREPs, contact reports, etc, as well as being familiar with the wide range of brevity words and tactical terms, helps to ensure that communication is easy to understand by all involved participants.

FM/BG-1286 - Examples: Brevity, Clarity and Confirmation

Brevity by avoidance of doubling callsigns

This example shows how to improve Brevity by avoiding the callsigns on transmissions between two parties AFTER the identification has been completed.

Here we are having the callsigns Outlaw and Phoenix.

 

Bad Brevity:

Here, Outlaw and Phoenix will Warn the receiver and Identify themselves before each transmission even though it is clear that the conversation is only carried out between these two as no other callsigns are Warned. 

Outlaw: Phoenix, this is Outlaw.

Phoenix: Outlaw, this is Phoenix.

Outlaw: Phoenix, this is Outlaw, READ BACK, move South 300 m and establish a hasty defensive position.

Phoenix: Outlaw, this is Phoenix, I READ BACK, move South 300 m and establish a hasty defensive position.

Outlaw: Phoenix, this is Outlaw, CORRECT, OUT.

Phoenix: Outlaw, this is Phoenix, from what direction are we expecting contacts at that location?

Outlaw: Phoenix, this is Outlaw, contact is to be expected from the South-West.

Phoenix: Outlaw, this is Phoenix, ROGER, OUT.

 Better Brevity:

Here, Outlaw and Phoenix will Warn the receiver and Identify themselves only until the identifications have been completed. Afterwards they omit this to keep the messages significantly shorter. This is possible because as they are not establishing communications with another party, it is implied that all transmissions are between these two. 

Outlaw: Phoenix, this is Outlaw.

Phoenix: Outlaw, this is Phoenix.

Outlaw: READ BACK, move South 300 m and establish a hasty defensive position.

Phoenix: I READ BACK, move South 300 m and establish a hasty defensive position.

Outlaw: CORRECT, OUT.

Phoenix: From what direction are we expecting contacts at that location?

Outlaw: Contact is to be expected from the South-West.

Phoenix: ROGER, OUT.

 Clarity by avoidance of multiple Warning Orders

This example shows the importance of properly Alerting and Identifying and subsequently how to improve clarity by avoiding multiple warning orders when transmitting. This is crucial as oftentimes callsigns will ignore any incoming transmissions as soon as they don’t hear their call sign at the very beginning of the Warning Order. Further, it avoids confusion as to who is the calling station and who is the receiving station.

Here we are having the callsigns Alpha 1-0, 1-1 and 1-2 on a Squad net.They are using the shortened callsigns 1-0 or Actual, 1-1 or 1, and 1-2 or 2.

 

Bad Clarity:

Here, 1-0 wants to pass an order to both his fireteams, 1-1 and 1-2. However, 1-0 forgets to properly establish communications and identify himself, creating a widely ambiguous message.

 

1 transmits:

1, 2.

 

What 1 means is:

1, and 2, this is Actual.

 

However his transmission could be understood as:

1-1, this is 1-2.

 

Meaning 1 will assume that 2 wants to talk to him.

Furthermore, 2 might just ignore this transmission and not answer Actual, even if it was transmitted as intended, because he didn’t hear his own callsign at the beginning of the transmission.

 Better Clarity:

Here, 1 will properly identify himself to ensure everything is understood as intended. To ensure that 1-2 is listening as well he also avoids using multiple warning orders back to back through the clever use of ALL STATIONS as only 1-1 and 1-2 are on the net with him. 

1-0: ALL STATIONS, this is Actual.

1-1: Actual, this is 1.

1-2: Actual, this is 2.

Though keep in mind that if you want to be sure the call signs are listening to a long message, ask yourself, does the whole message concern all call signs? If not, break it up, address the call signs one by one with their relevant traffic.

And if there would be another callsign, 1-3, on his net, the best alternative would be to call 1-1 and 1-2 individually, in separate transactions.

 

The importance of confirmation

This example shows how to improve information flow with confirmations. Here we are having the callsigns Outlaw and Phoenix.

 

No Confirmation:

Here, Outlaw passes an attack order to Phoenix who starts his attack as intended but is not confirming that he has received the order. Because of this, Outlaw doesn’t start his part of the attack yet, leading to Phoenix receiving heavy losses due to being outnumbered as a result of the missing support.

 

Outlaw: Phoenix, this is Outlaw.

Phoenix: Outlaw, this is Phoenix.

Outlaw: Start your Attack onto Objective Bravo.

(Phoenix does not answer, even though Outlaw didn’t use OUT. Hence, Outlaw tries to establish communications again)

Outlaw: Phoenix, this is Outlaw, NOTHING HEARD.

Phoenix: Outlaw, this is Phoenix, we are on Objective Bravo, where is your support?!

Outlaw: ROGER, commencing attack now, OUT.

 Confirmation used:

Here, Outlaw passes an attack order to Phoenix who confirms that he has received the order, will carry it out and subsequently starts his attack as intended. Because of this Outlaw can start his part of the attack as well, leading to a swift victory due to the mutual support.

 

Outlaw: Phoenix, this is Outlaw.

Phoenix: Outlaw, this is Phoenix.

Outlaw: Start your Attack onto Objective Bravo.

Phoenix: WILCO, OUT.

FM/G69 - Direct Communication

FM/BG-325 - Common phraseology
CalloutMeaning
Go firmInstruction to stop in place for a long amount of time and therefore to  take long-term defenses, such as establishing proper cover, building trenches etc.
ARDAll round defense. Instruction to establish security in a full 360° arc. Usually elements/individuals will be assigned to a sector of this defense.
Set security ([arc in degrees]) [cardinal direction] Instruction to take security centered around particular direction for the specified width. e.g. “Set security 180 north”, means hold position and establish security covering West through North, through to East. The direction specified is often the most likely direction of enemy attack and therefore usually held by the individual with the most firepower (e.g. the Automatic Rifleman/Machine Gunner). If no arc is specified it is 90°.
  
FM/BG-686 - Voice volume usage

During operations, always be mindful of your voice volume, as the enemy can hear you, and your choice could impact the success or failure of the mission. 

Generally, use a normal voice when you have radios and the situation is calm. Switch to yelling when urgent communication is needed, like when throwing a grenade, overcoming loud external noise, or if radios aren't available. Use whispering to keep your position concealed when infiltrating behind enemy lines, setting up and coordinating ambushes or simply when you don't want the guy on the other side of the wall hear you approach him as you coordinate with your team.

FM/BS-331 - Alert others when throwing a grenade

When throwing a grenade, shout:

[type of grenade] out

TypeGrenade category
FRAGFragmentation grenade
SMOKESmoke grenade
FLASHBANGFlashbang
FM/BS-333 - Alert others to a threatening grenade

When you see a grenade landing or being thrown in your direction, shout: 

grenade

FM/BS-334 - Alert others to incoming indirect fire

When hearing or observing incoming indirect fire, shout: 

IDF incoming

FM/G202 - Communicating within an aircraft

FM/BG-969 - Maintaining shared situational awareness

All crew members must continuously share threat intelligence, friendly positions, and ammunition status. Critical threats such as missile launches or tracers must be reported immediately to prevent loss of aircraft or crew.

FM/BG-970 - Pilot responsibilities in coordination

Pilots must communicate planned or ongoing maneuvers, especially when turreted systems are in use, allowing gunners to compensate for movement. They must also monitor and share updates on fuel levels and the aircraft’s airworthiness following any damage to ensure coordinated decisions on engagement and return-to-base timing.

FM/BG-971 - Gunner responsibilities in coordination

Gunners must communicate weapon employment activities and targeting status so the pilot can adjust aircraft behaviour. If specific attack vectors or flight stability are required for effective weapon use, the gunner must clearly communicate these to the pilot.

FM/BG-972 - Brevity for weapon employment and manoeuvres

Brevity words are essential for clear, fast, and unambiguous communication between aircrew during dynamic combat situations.

  • Steady: Request to hold current heading to provide a stable firing platform.
  • Rotate (left/right): Instruction to turn aircraft for optimal weapon employment.
  • Popping up / Pop up: Aircraft is rising to clear an obstruction or take a shot.
  • Dropping down / Drop down: Aircraft is descending behind cover, typically after engagement.
  • Firing / Engaging: Gunner is actively firing weapons.
  • Launched / Missile away: Gunner has launched a missile; aircraft may manoeuvre freely.
  • Running in: Aircraft is beginning an attack run on a known target.
  • Breaking (left/right/etc.): Aircraft is making a sharp turn in the indicated direction.
FM/BG-973 - Brevity for threat warnings

Quick threat callouts enable timely countermeasures and coordinated evasive action. 

  • Missile, missile: Suspected or confirmed missile launch; triggers missile evasion protocol.
  • Taking SAF: Aircraft is under small arms fire; evasive manoeuvres may be needed. Often shortened to “SAF, SAF.”
  • Taking heavy: Aircraft is under heavy weapon fire such as vehicle-mounted guns. Often shortened to "Heavy, heavy."
FM/BG-974 - Brevity for contact identification

Effective target and friendly identification depends on consistent use of contact brevity terms.

  • Visual: Friendly forces have been sighted.
  • Blind: Friendly forces cannot be seen.
  • Tally: Hostile forces have been spotted.
  • No joy: Hostile forces not seen.
  • Tracers (direction): Enemy tracer fire seen, direction specified.
  • Flashes (direction): Muzzle flashes spotted, direction specified.
FM/BG-975 - Brevity for aircraft status

Status terms inform the crew and controllers of critical conditions requiring resupply or immediate action.

  • Winchester: Out of ammunition; unable to continue attack.
  • Bingo: Low fuel; must return to base to avoid forced landing.
This page generated 1.57MB in 0.0980 seconds.