Standing Operating Procedures

Standing (or Standard) Operating Procedures, otherwise called SOPs provide a unit with a set of regular, common
 functions and operations that are carried out in day-to-day activities. Below are a series of minimal standards, that
 when practiced or observed, can help enhance any given team or unit that requires insight into proper fielded SOP.

## Radio Communications

The purpose of this section is to introduce fundamental tactical radio communications at the Company and Platoon
level, including basic Voice Procedure on the Combat Net Radio (or CNR). Communicating effectively is a crucially
important aspect of warfare fieldcraft; especially in how it pertains for command and control, situational awareness,
and battlefield information across the battlespace. It is especially vital for Commanders, NCOs and Radio Operator
personnel who need to understand how to pass on critical information swiftly, accurately and with appropriate need.

Standard operating procedures vary between countries and even different units, although NATO countries follow a
common standard when necessary.  The scope of this guide covers US and UK/Commonwealth variations. Varied
relevant parts have been labelled to clearly indicate these differences. Proper net discipline and accurate, realistic
communications not only enhance unit effectiveness but also increase the capability and capacity for any said unit.

### 1. **Combat Net Radio & Radio Nets**

Unit level radio nets at Battalion and above are formal nets. They have watchkeepers maintaining their set 24 hours
listening watch, are fully logged and require scheduled reports, returns and requests (R3) as well as regular use of
command, control or admin traffic. As such, there is a prescribed amount of formal protocol that applies specifically
toward these nets. At a sub-unit level (Company and below), command nets are usually informal although standard
Voice Procedure (VP) still applies. At a Section or Squad level, short range nets used on Personal Role Radios are
considered ‘chat nets’, although it is good practice to follow standard VP regardless of what broadcast level is used.

A Light Infantry Company operates a single command net with occasional use of additional nets for busier operations
in order to declutter the command net, such as an Admin net or Offensive Support (Fires) net for Forward Observers,
Forward Air Controllers or Joint Terminal Attack Controllers attached to the subunit. Each Platoon has their separate
Platoon Command net, sometimes referred to in the US as an Assault net. Finally, each Section / Squad has a PRR
chat net. Fire Teams work on the Section/Squad net but Team Leaders will monitor (listen to) the Platoon Command
net on a separate radio. The Battalion Signals Officer distributes frequency allocations, call signs and passwords via
Communications Electronic Instruction (CEI) ahead of operations. As a rule it is better to use as few nets as possible.

### 2. **Call Signs**

Call signs provide a means of uniquely identifying each station on a net. Call signs will vary slightly depending on the
structure and type of unit and even unit SOP, but this guide focuses on a generic Light Infantry Company. While both
the US and UK follow a slightly different approach, there is logic to both system that require the Operator understand.

In the US Army, a Company is allocated a call sign identifier, often starting with the letter of the Company (e.g. Sabre,
Dagger or Raider, etc). Platoons are designated with a number (Sabre-1 for 1 Platoon). Additionally, a unit leadership
position each has a number affixed: 7 for NCOs, 6 for Commanders, 5 for Executive Officers. Hence Sabre-7 is a unit
Company First Sergeant. Sabre-1-6 is Sabre Company, 1 Platoon Leader. Support platoons are often given a unique,
separate callsign (e.g. Steel for mortar platoon). For brevity once comms have been established, the total identifier is
omitted and only numbers are used. New call signs joining the net must announce themselves with the full call sign/ID.

On the Platoon nets, Squads use the same call sign with their squad number affixed.  Hence Sabre-1-1 is 1 Platoon
1st Squad; Sabre-1-1-A is 1 Platoon, 1st Squad, Alpha Team. “Actual” is appended to any call sign to specify a team
commander, as opposed to the Radio Telephone Operator (RTO) who would otherwise routinely answer their radios.

In the UK, a call sign indicator (often a phonetic letter or unique word) is allocated to each sub unit. Platoons and the
Sections are designated by number, for example the “B10” (pronounced Bravo One Zero) is B Company, 1 Platoon,
where Bravo is the call sign indicator allocated to B Company in the CEI. “Alpha” specifies the Commander, so B10A
is 1 Platoon Commander. This can be further broken down to designate Sections and Fire Teams, hence B11 is their
1 Platoon, 1 Section; F11C is 1 Platoon, 1 Section, Charlie Fire Team. This system continues throughout platoon level.

Leadership positions have fixed call signs: 0A is the Company Commander, 0C is the 2IC, 33A is the given Company
Sergeant Major. 0 (Zero) is the Control Station and is typically manned by their Radio Operator. On the Platoon nets,
Sections use the same call signs though in this context 0A is the Platoon Commander, 0B the Platoon Sergeant, etc.

### 3. **Voice Procedure**

Voice Procedure is used in order to get the most amount of information across in the shortest possible time. Airtime is
precious and as much as possible needs to be reserved for command and control, so reducing the amount of relayed
unnecessary chatter is vital. To facilitate brevity and accuracy, VP employs a number of prowords with specific jargon
or meanings and rules associated to them, which are largely standardised throughout NATO. Good net discipline can
be maintained by following some basic rules, which are demonstrated via a table and guideline system shown below:

2. Avoid offering messages.
3. Be brief.
4. Be succinct.
5. Use Out instead of Over whenever possible.
“Roger SABRE, this is SABRE-1-6, send traffic over”
“SABRE-1-6, initiate movement at this time to checkpoint Three Two Tango, Break, how copy over?”
“SABRE this is SABRE-1-6, Roger Wilco, moving to checkpoint Three Two Tango, I am Oscar Mike over”
“SABRE-1-6 this is SABRE Roger Out”
“SABRE-1-6, Roger Out”

#### 3a. **Prowords**

Prowords are standardised calls used to ensure understanding of common terms and tasks and help keep the coms clear and succinct. Every proword has a specific and unique meaning and some of them will, by implication, trigger a certain set of activities. For example “CONTACT” explicitly means the call sign is engaged with the enemy and that a chain of command will react accordingly. Care should therefore be take to use the correct proword to avoid mistakes.

#### 3b. **Incorrect Prowords**

A number of words have entered into popular use which do not officially exist in military VP. Their provenance has
been incorrectly attributed to the military by the entertainment industry or habits picked up from CB radio and Civil
Aviation. This happens in the real military and not just in some MilSim groups but just because you heard a soldier
speak it once does not make it correct! They should be avoided as they add little value and merely clutter the net.

### 4. **Reports**

Reports are VP drills designed to communicate the most critical information in a simple, unambiguous format quickly
and easily. The most common tactical reports are Sighting, Contact, Spot and Situation Reports. SALUTE or SALTA
are acronyms used to describe the enemy in detail and are aids to completeness. SALUTE is used for detailed recce
reports whereas the slightly abbreviated SALTA is more commonly used for quick tactical reporting. All are in usage.

* Size of enemy
* Activity
* Location
* Time observed
* Actions taken
* Size
* Activity
* Location
* Actions
LINE 3 - Size \_\_\_ (number of enemy)
LINE 4 - Activity \_\_\_ (what they are doing)
LINE 5 - Location \_\_\_ (Grid of enemy)
LINE 6 - Unit \_\_\_ (or uniform worn)
LINE 7 - Time \_\_\_ (observed)
LINE 8 - Equipment \_\_\_ (carried)
LINE 9 - Assessment \_\_\_

#### **SITUATION REPORT (SITREP)**

Sitreps are the primary means of updating the chain of command on your current location and tactical situation. As a
rule of thumb, each sub unit should send their Sitrep every 5 mins in contact and every 15 mins out of contact. They
should also be sent after completing any significant task, such as an assault, upon reaching a checkpoint or RV, or if
and when requested by the commander. Remember, keeping their battlespace net up-to-date is every soldier's duty.

As a minimum, Sitreps must include the location of known Enemy and Friendly Forces. Admin or Logistics Requests
may be added if the situation dictates. HQ will send a consolidate downward Sitrep from time to time in order to make
sure everyone is fully aware of the situation and the commander’s intent. This is especially important due to changes.

* **Time of report**
* **Enemy locations, casualties inflicted, PWs taken**
* **Friendly locations and state**
* **Commander’s Intent**
* **Additional Info - Combat Service Support or other pertinent info**
* EXAMPLE SHOWN BELOW:

"0A this is 31, SitRep as at 0930 hrs, Grid 12345678, have engaged and destroyed 10 infantry at Objective Whiskey, further 8 enemy infantry sighted 1000m on Axis, withdrawing North. Am re-orging and awaiting further orders, Over."

#### **AMMUNITION AND CASUALTY STATE (AMCAS)**

AMCAS is an abbreviation of Ammunition and Casualty state. It can be used in a SITREP to indicate the overall
combat effectiveness (CE) of subunits. A unit at less than 40% CE is considered to be destroyed or fully disabled.

* **Green - Over 90% CE**
* **Amber - Over 60% CE**
* **Red - Less than 60% CE**
* EXAMPLE: "0B this is 31, AMCAS Green, Out.”

### 5. **Support Requests**

Some request formats vary between national militaries and different units, especially in the case of MilSim where numerous teams are often tailored to their game and capabilities of specific units. Refer to your unit SOPs for info.

#### 5a. **Fire Missions**

Target Grid is the method used by an untrained observer to request Offensive Support (such as an 81mm mortar and
105mm Light Gun) from a Forward Observer attached to the unit. The FO then handles the details and execution for
the fire mission with the artillery battery. Note that when requesting OS, every line is repeated in full by the answering
call sign to confirm it is correct. The VP used between FO and battery has additional detail but is not included below:

**Fire Mission "Target Grid" Template**

#### 5b. **Close Air Support**

CAS from fast air or attack helicopters is normally requested via a 9-line CAS request (“nine liner”). An abbreviated
7-line format can be used in emergencies. For most MilSim purposes, this ECAS request is sufficient. All the critical
information is between lines 1 to 3 and line 7. It is performed as a request for calling air support or CAS in missions.

**Emergency Close Air Support, ECAS TEMPLATE**

#### 5c. **Casualty Evacuation**

Casualty Evacuation or CASEVAC via helicopter is normally conducted via a 9-line CASEVAC request (see above)
and can be used to recover injured personnel during emergencies. Commonly used in MilSim, a CASEVAC 9-Line
provides successful extraction of wounded casualties. All parts of the 9-line are critical for calling successful rescue.

**CASEVAC 9-LINER TEMPLATE**

**CREDITS: Based upon Friznit's VP Guide at VOLCBAT**

## Rules of Engagement

As warfare increases in complexity, so too does its proximity to civilian and non-combatant personnel closen. Several
methods of regulating unnecessary conflict are observed in military practice. The most common encountered is called
'Rules of Engagement' or ROE for short. The ROE for a given unit or military organisation may alter depending on the
political or military strategic decision implemented by said unit or organisation's national policy, or by a given situation.

**STRATEGIC RULES OF ENGAGEMENT (POLICY)**

EXAMPLE: U.S. Central Command (CENTCOM) CFLCC ROE CARD

* 01. On order, enemy military and paramilitary forces are declared hostile and may be attacked subject to the following instructions:
	+ A) Positive Identification (PID) is required prior to engagement. PID is a reasonable certainty that the proposed target is a legitimate military target. If no PID, contact your next higher commander for decision
	+ B) Do not engage anyone who has surrended or is out of battle due to sickness or wounds
	+ C) Do not target or strike any of the following except in self-defense to protect yourself, your unit, friendly forces, and designated persons or property under your control:
		- Civilians
		- Hospitals, Mosques, National Monuments, and any other Historical and Cultural Sites
	+ D) Do not fire into civilian populated areas or buildings unless the enemy is using them for military purposes or if necessary for your self-defense. Minimize collateral damage
	+ E) Do not target enemy infrastructure (public works, commercial communication facilities, dams), Lines of Communication (roads, highways, tunnels, bridges, railways) and Economic Objects (commercial storage facilities, pipelines) unless necessary for self-defense or if ordered to by your commander. If you must fire on these objects to engage a hostile force, disable and disrupt but avoid destruction of these objects, if possible.
* 02. The use of force, including deadly force, is authorised to protect the following:
	+ Yourself, your unit, and friendly forces
	+ Enemy Prisoners of War (EPW)
	+ Civilians from crimes that are likely to cause death or serious bodily harm, such as warcrimes
	+ Designated civilians and/or property, such as personnel of the Red Cross/Cresent, UN, and US/UN supported organisations
	+ Treat all civilians and their property with respect and dignity. Do not seize civilian property, including vehicles, unless you have the permission of a company level commander and you give receipt to the property's owner.
* 4. Detain civilians if they interfere with mission accomplishment or if required for self-defense.
* 5. CENTCOM General Order No. 1A remains in effect. Looting and the taking of war trophies are prohibited

**TACTICAL RULES OF ENGAGEMENT (SITUATIONAL)**

EXAMPLE: Unit-level Tactical Rules of Engagement

* Operational ROE
	+ **No Force**: Verbal Commands, Observed Presence Only (*for Obediant, and Compliant Offender*)
	+ **Moderate/Limited Force**: Physical Control, Self-Defense (*for Resisting, Non-Compliant Threat*)
	+ **Less-Than-Lethal Force**: Non-Lethal Munitions, etc (*for Low-Level Aggressive, Hostile Threat*)
	+ **Deadly or Lethal Force**: Firearms, Lethal Munitions (*Hostile Threat of Death or Serious Injury*)
		- **Weapons Free**: is Permitted to Engage any known **HOSTILE THREAT**
		- **Weapons Hold**: is Not-Permitted to Engage any known **HOSTILE THREAT** unless fired upon

## Operations Order (OPORD)

An Operations Order or OPORD is a document providing a clear sense of requirements, preparations and expected resistence prior to an Operation. While extremely detailed (only brief summary below), it provides an outline for unit activities or strategic objectives prior to Operational assessment, before any Tactical deployment is actually realised.

* I. **SITUATION:** Provides information essential to subordinate leader's understanding of situation
	+ A) Enemy Forces Intelligence
	+ B) Friendly Forces Data
	+ C) Squad Attachments and Detachments
* II. **MISSION:** The unit's mission statement incl. Who, What (Objective), Where, When and Why (Intent)
* III. **EXECUTION:** The mission breakdown, including Concept of Operation, Maneuvers and Fire Support
	+ A) Concept of Operation
	+ B) Maneuver
	+ C) Fires (Indirect and Direct Fires)
* IV. **SERVICE SUPPORT :** Logistical, Medical and Miscellaneous Requirements, including Transports
* V. **COMMAND & SIGNAL:** Designation of Command Posts/Leadership, Signals incl. Communications
	+ A) Command
	+ B) Signals

## Order of Battle (ORBAT)

The Order of Battle or ORBAT is a top-level structural or hierarchical view of all a unit's elements and components. It
can serve as a Strategic overview and help in planning Operational or Tactical level objectives. Furthermore, it is not
strictly limited to singular units, and can apply to entire divisions, provided the diagramming is conducted accordingly.

**EXAMPLE ORBAT**