FM/C111 - Deployment planning

---

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

UNITAF operations follow a strict framework which is outlined in this section. Ultimately the goal of standardisation in UNITAF is to ensure in our system of dynamic ORBATs that standardisation is maintained across all operations so players know what to expect when joining, preparing, planning, gearing out and executing UNITAF operations. This standardisation encompasses but is not limited to;

• What factions can be played
• Duration of missions
• SOP standardised ORBAT organisation
• ORBAT restrictions
• Equipment restrictions
• Database integration
• Limited arsenals

All UNITAF operations use a database framework which ultimately issues standard loadouts to players based on database driven loadouts directory. The framework can be obtained from Operations Command (OC) or Operations Staff (J3) a template is provided and can be copied to your desired maps.

For a mission to be approved, it must follow the framework, in order to follow the framework it must be in line with the following;

• Full arsenals are not to be used under any circumstances, this means;
  • Arsenal content is dictated by the Framework and restricted per the content provided to it by Loadouts Staff (J5) in accordance with FM/C110 - Loadouts and Factions
  • Arsenals with unrestricted content, or not utilising the Framework are not permitted.
• Loadouts should be attainable through the framework ORBAT injection system and must be approved by Loadouts Staff (J5)
• All mods must be on the UNITAF approved mods list
• The faction players are deploying as must be an approved faction
  • Approved factions have limited arsenals prepared already according to that factions equipment
  • Approved factions have default loadouts created for all combat positions that can be ORBAT deployed
  • If a faction is not on the approved factions list, then the faction must be created before the mission can be approved
• The mission file with integrated framework should be ready and tested, prior to the ORBAT being released.

• Theatre Operations must be named using the format:
  • Operation [Name] [Roman Numeral] (e.g. Operation Overlord I).
• The operation name must remain unchanged for all deployments within the same operation.
• If the mission is a one-off operation, there is no requirement to use a Roman numeral.
• The Roman numeral must increment sequentially for each deployment within the same operation.
• The maximum number of deployments within a Theatre Operation is 10, anything beyond this should be submitted to J3 as a campaign.
• The first deployment of an operation must use Roman numeral I.
• Each subsequent deployment must increase the numeral by one sequential value.
• Subtitles, additional descriptors, or secondary naming elements are not permitted.

The purpose of this content is to provide policy guidance on the construction of ORBAT and the rules by which ORBATs are approved. It's important to note that these policies may be an extension of other policies, or impacted by them.

These policies are designed to cover the majority of encountered questions in ORBAT construction, although for flexibility we acknowledge that not all circumstances will be covered. In this instance, as with other policies FM/BP-859 - Doctrine Authority applies and FM/BG-614 - Operations Command (OC) is the relevant Command Unit Authority.

See FM/C149 - The UNITAF Way for more information on doctrine and what happens if a specific instance is not covered by this section.

• Consists of 4-6 people
• Lead by a fireteam leader or the squad leader
• Must be part of a squad

• Consists of 8–15 people (excludes attached elements)
• Composed of 2–3 fireteams
  • Minimum of 2 fireteams
  • Maximum of 2 fireteams when multiple squads are present
  • Maximum of 3 fireteams if operating as a single squad
• Maximum of 4 elements
  • Fireteams and integrated vehicles combined
  • Attached elements are not counted
• Led by a Squad Leader
  • When a squad has 10 or more members (2 fireteams of 4–6 members), the Squad Leader must have at least 1 person under their direct command as a buddy
  • the Squad HQ element can include a maximum of 3 personnel
  • When a squad has 8–10 members, the Squad Leader does not require a buddy
• Permitted Squad HQ roles include*
  • Up to 1 Squad Leader or Squad Commander
  • Up to 2 Radio Operator
  • Up to 1 Squad Medic
  • Up to 1 Joint Fires Observer or Forward Observer
  • Up to 1 Forward Air Controller
  • Up to 1 Designated Marksman
  • Up to 2 Combat Engineer or EOD
  • Up to 2 UAS Operator roles or equivalent
  • Up to 1 Rifleman
  • Up to 2 Ammo Bearer
  • Up to 2 Interpreter
  • Up to 1 Driver or Crewman, if the Squad HQ operates within a vehicle
  • Any Leadership Observer where required by policy in line with that policy.
• Extra elements may be attached such as vehicles

*Should the deployment be Special Forces, any SF variant of the same role is permitted.

• Consists of 2-8 people
• Lead by an infantry team leader
• No fireteams, everyone under the command of the infantry team lead

• Consists of 26–64 people (includes attached elements)
• Composed of 2-4 squads/infantry teams
• Lead by a platoon leader or commander
• Platoon HQ element may consist of a maximum of 4 extra people under direct command of the platoon leader or commander*
  • Up to 1 Platoon Commander or Platoon Leader
  • Up to 1 Platoon Sergeant
  • Up to 2 Radio Operator or Communications Specialist
  • Up to 1 Platoon Medic
  • Up to 2 Joint Fires Observer or Forward Observer
  • Up to 2 Forward Air Controller
  • Up to 2 UAS Operator roles or equivalent
  • Up to 2 Combat Engineer or Support Engineers 
  • Up to 1 EOD Specialist
  • Up to 2 Interpreter
  • Up to 1 Rifleman or Ammo Bearer for security purposes
  • Up to 1 Driver or Crewman, if the Platoon HQ operates within a vehicle
  • Any Leadership Observer where required by policy in line with that policy.
• Extra elements (like a vehicle section) may be attached

*should the deployment be special forces, any SF variant of the same role is permitted.

sUAS Attack Teams must be independent elements with the following composition:

• 1 sUAS Team Leader
• 1-4 sUAS (Attack) Operator
• 0-4 sUAS (Recon) Operators
• At most 6 members using the above restrictions

Teams MUST be led by the sUAS Team Leader and are directly subordinate to the FL element

• Composed of 2-4 platoons
• Lead by a company leader
• May have 4 extra people under direct command of the company leader
• Extra elements (like a vehicle section) may be attached

• A single light vehicle can be integrated into a fireteam
• A single AFV or light vehicle can be integrated into a squad as a separate element
• MBTs cannot be integrated

• Can be subordinate to a company, platoon or the highest ranked element on the ORBAT
• Consists of 1-4 vehicles
• Lead by a vehicle section commander

• Can be subordinate to a company, platoon or the highest ranked element on the ORBAT
• Lead by a logistics support chief
• Consists of 2-5 people

• Can be subordinate to a company, platoon or the highest ranked element on the ORBAT
• Lead by a MERT officer
• Consists of 2-5 people
• Must be airborne

• Lead by a pilot
• Contains only the crew of a single aircraft

• Can be subordinate to:
  • A mortar/artillery battery
  • A company, platoon or squad
• Lead by a mortar/artillery section leader
• Consists of 1-4 gun teams

• Composed of 2-4 mortar/artillery sections
• Can be subordinate to a company, platoon or the highest ranked element on the ORBAT
• Lead by a Fire Support Chief
• Does not control gun teams directly

• SF teams follows the same rules as FM/BP-1378 - Fireteam composition, except the roles are replaced with their SF equivalent
• SF squads follows the same rules as FM/BP-1379 - Squad composition, except the roles are replaced with their SF equivalent

• A sniper team can be subordinate to a company, platoon, squad, or the highest-ranked element on the ORBAT.
• A sniper team must operate as its own independent element, led by the spotter.
• The team consists of two personnel: a spotter and a sniper.

Organisation

• UAS Operators MUST be organised as a distinct and separate element from the Ground Combat Element (GCE).
• The UAS Operator element MUST consist exclusively of qualified UAS Operators. No non-UAS personnel are permitted within this element.
• The UAS Operator element MUST be directly subordinate to Force Leadership (FL).
• Tasking and coordination MAY be conducted through FAC/JTAC elements where operationally required.

Deployment Restrictions

• UAS Operators MUST NOT deploy into the field alongside the Ground Combat Element under any circumstances.
• UAS Operators MUST REMAIN at STARTEX for the duration of operations.

Operational Rationale

• This policy reflects the requirement to simulate the logistical and physical constraints of UAS control systems, including:
  • Fixed, seated control terminals
  • Increased equipment footprint
• UAS systems  ARE NOT to be treated as lightweight or handheld (e.g. sUAS-style) platforms.

UAS Definition

• A UAS (Unmanned Aircraft System) is defined as the complete system required to operate an unmanned aerial vehicle.
• A UAS MUST INCLUDE all of the following components:
  • The operator
  • The control terminal
  • The aircraft (UAV)
  • Any supporting logistical infrastructure

Classification

UAS are categorised into two distinct types:

• UAS
  • Systems that REQUIRE dedicated infrastructure to operate.
  • Systems that are NOT man-portable.
•  sUAS (small UAS)
  • Systems that are fully man-portable.
  • Systems that DO NOT REQUIRE additional infrastructure beyond what can be carried by an operator.

The purpose of this content is to provide policy guidance on the construction of ORBAT and the rules by which ORBATs are approved. It's important to note that these policies may be an extension of other policies, or impacted by them.

These policies are designed to cover the majority of encountered questions in ORBAT construction, although for flexibility we acknowledge that not all circumstances will be covered. In this instance, as with other policies FM/BP-859 - Doctrine Authority applies and FM/BG-614 - Operations Command (OC) is the relevant Command Unit Authority.

See FM/C149 - The UNITAF Way for more information on doctrine and what happens if a specific instance is not covered by this section.

• A slot must have the most appropriate role assigned
• Roles that normally wouldn't make sense in a given element may still be put in for roleplaying aspects
• No slot may be the sole slot in a group, except for:
  • mission support slots
  • pilot slots

• The field leader may slot in:
  • The highest leadership role
  • The lead game master role
  • Another role that acts as the highest leadership position (vehicle section commander, flight leader,…)
• Leadership roles must not have more slots under them than their maximum count

    Every ORBAT must have exactly one lead game master, with size equal or exceeding the entire ground combat element- An exception can be made for special deployments or missions that are prebuilt/scripted in the 3den Editor. Which have been built and then ran by the FL. The FL must make provisions to ensure there are plans in place to manage Arma incidents.

• Game master slots may be added if they will operate in a semi-autonomous fashion.
  • The size of the game master slot must be similar to the size of the ground combat element they will oversee semi-autonomously
  • The size of the game master slots must not exceed the size of the lead game master
• Assistant game masters may be added as needed, within reason
• Civilian Roleplayers should be used if the primary role is player interaction through non-adversarial means
• OPFOR Roleplayers should be used if the primary role is combat against players
• Roleplayers should not be relied upon as extra game masters
• The Intelligence Officer must either occupy:
  • The lead game master slot
  • The next most senior game master slot, if the Field Leader is the Lead Game Master
• Mission support roles may only be used in the MST element
• If there is a need for specialist roles for the mission (ATC, doctor at a hospital, etc), the role that best matches the need from the role directory (like FAC or CMT tech) may be added to the MST. These roles do not report to the field leader, and may not participate in combat

• The squad medic may only be in the direct element of the squad leader.
• The platoon medic may only be in the direct element of the platoon leader or company leader.
• Squad sized operations must have at least two medic capable of giving blood (unless there will be no combat).
• Platoon sized operations must have at least two medics capable of giving blood.
• Company sized operations must have at least four medics capable of giving blood.
• Elements supported by CMT or MERT should have no roles capable of giving blood, with only CLS allowed as integrated medical personnel.

Medical capability beyond baseline policy is scaled to operational size, expected casualties, and available support.

At platoon and company level, distributing blood-capable medics across squads reduces time to advanced care and prevents over-reliance on a single medic if elements become separated or sustain multiple casualties.

Combat Life Savers (CLS) and Combat Medics provide depth by sustaining casualties until advanced treatment is available, increasing resilience within each squad.

When a CMT/MERT element is present on the ORBAT, ground medical posture shifts to stabilisation and handover. Limiting blood-capable medics on the ground reduces exposure while CLS personnel maintain immediate care capability until transfer.

• A vehicle crew can either consist of:
  • Driver
  • Driver + Gunner (light vehicle only)
  • Driver + Commander (AFV/MBT only)
  • Driver + Gunner + Commander
• Additional gunners may be added if the vehicle has multiple gunner slots

• Pilot (general) may only fly transportation
• Pilot (multi) must be used for helicopters used for both transportation and CAS
• Pilot (attack) must be used for helicopters only used for CAS
• WSO (attack) must be used for all non-pilot seats with weapons, except for doorguns

• Pilot (general) may only fly transportation, and AC-130 like platforms
• Pilot (CAP) may only be used for air-to-air engagements
• Pilot (CAS) may only be used for air-to-ground engagements
• Pilot (multi) must be used for aircraft used for both CAP and CAS
• Fixed-wing Weapons Systems Operator may control weapons, but not handle CAS procedures
• Fixed-wing Weapons Systems Officer may control weapons and handle CAS procedures

All close air support must be coordinated by either a forward air controller or joint fires observer. This includes rotary, fixed-wing and UAV.

All indirect fire support must be coordinated by either a forward observer or a joint fires observer. This includes mortar and artillery.

• Mortar gunners may be integrated into squads
• Only the mortar/artillery gunner may operate the weapon
• Mortar slots should be used if the weapon system is man-portable (or if a normally man-portable system is used on a vehicle), artillery slots should be used otherwise

Offensive objectives describe actions intended to defeat enemy forces or seize control of terrain or assets. These terms help clearly communicate the intended result of an attack.

Common offensive objective terms include:

• Clear
  Remove all enemy forces from an area or structure.
• Destroy
  Render an enemy force or asset permanently combat ineffective.
• Seize
  Take control of terrain or an objective by force.
• Capture
  Take possession of enemy personnel, equipment, or positions intact.
• Neutralise
  Render an enemy force or asset temporarily unable to interfere with operations.
• Suppress
  Reduce the effectiveness of enemy fire or observation.
• Raid
  Conduct a short duration attack to destroy, capture, or gather information before withdrawing.

Defensive objectives focus on protecting terrain, forces, or key assets while preventing enemy success.

Common defensive objective terms include: 

• Defend
  Prevent the enemy from seizing terrain or achieving their objective.
• Hold
  Maintain control of a position against enemy attack.
• Secure
  Ensure an area is safe from enemy interference after it has been cleared or before the enemy takes it.
• Protect
  Safeguard a specific force, asset, or location from enemy threats.
• Delay
  Slow enemy movement while trading space for time.
• Deny
  Prevent the enemy from using terrain, routes, or resources.
• Screen
  Provide early warning of enemy activity while avoiding decisive engagement.
• Guard
  Protect the main force by observing and reporting enemy activity while maintaining readiness to engage if necessary.

Patrol objectives focus on gathering information, maintaining presence, or assessing terrain and enemy activity without committing to major combat.

Common patrol objective terms include:

• Reconnoitre
  Gather detailed information about terrain, routes, or enemy activity.
• Observe
  Monitor an area or target and report activity over time.
• Investigate
  Approach and assess a specific point or report.
• Confirm
  Verify previously reported information or sightings.
• Locate
  Find and report the position of enemy forces or assets.
• Identify
  Determine the type, composition, or activity of a force or object.
• Track
  Follow signs of enemy movement to determine direction and intent.
• Assess
  Evaluate terrain, routes, or locations for suitability.
• Survey
  Conduct a detailed inspection of terrain, structures, or infrastructure.
• Mark
  Designate a location for navigation, targeting, or follow on forces.

Infantry mounted in IFVs with heavy weapon systems (e.g. autocannons, ATGMs). Smaller squad sizes offset by vehicle firepower.

Advantages:

• Highest protection among infantry carriers
• Significant firepower multiplier
• Effective in offensive manoeuvre

Disadvantages:

• High logistical demand (ammo, maintenance)
• Reduced infantry numbers increase casualty impact
• Vulnerable to heavy threats (MBTs, air, artillery)

Best Employment:

• Assaulting across open terrain
• Exploiting breakthroughs
• Urban operations (vehicle overwatch; avoid overextension beyond cleared areas)

Infantry mounted in APCs, integrated with vehicle crews. Vehicles support and operate alongside dismounted troops.

Advantages:

• Increased survivability for infantry
• Organic heavy weapons (HMGs, GMGs)
• Good mobility across varied terrain
• Organic resupply capability

Disadvantages:

• Vulnerable to AT weapons
• Risk of mass casualties if vehicle destroyed
• Detectable and targetable by heavy assets

Best Employment:

• Combined arms operations with MBT support
• Crossing open terrain under protection
• COIN or conventional environments with moderate AT threat

Infantry mounted in MRAP-class vehicles, offering increased protection over motorised forces but less than mechanised.

Advantages:

• Improved survivability vs small arms and IEDs
• Maintains speed and logistical capacity
• Supports crew-served weapons

Disadvantages:

• Vulnerable to anti-vehicle weapons
• Large vehicle profile increases detectability

Best Employment:

• COIN environments with limited AT threat
• Long-distance movement in contested areas

Infantry transported in soft-skinned vehicles (e.g. trucks, light utility vehicles).

Advantages:

• High mobility over long distances
• Strong logistical carrying capacity
• Ability to transport crew-served weapons

Disadvantages:

• Extremely vulnerable to ambush and direct fire
• Minimal protection against any threat

Best Employment:

• Rear-area movement
• Rapid deployment to defensive positions
• Logistical transport of personnel and equipment
• Low-threat environments or when no alternatives exist

Light Infantry operate primarily on foot without organic vehicle transport. Despite the name, they typically carry the heaviest individual loads.

Advantages:

• High self-sustainment (with resupply)
• Low visual and thermal signature
• Strong stealth and reconnaissance capability
• Reduced vulnerability to heavy weapons and artillery

Disadvantages:

• Slow operational movement
• Limited organic heavy firepower
• Can fall behind mounted elements

Best Employment:

• Dense terrain (woodland, jungle, mountainous)
• Urban environments with ambush risk
• Short-range operations
• Operations supported by external fire support (e.g. mortars, MBTs)

Line Infantry force types represent the default ground combat elements available to a Field Leader when specialist insertion methods (e.g. airborne or amphibious) are not required. These force types differ primarily in mobility, protection, and organic firepower.

Selection should be based on:

• Terrain and environment (urban, woodland, open ground)
• Threat level (presence of AT, armour, artillery)
• Operational tempo (speed vs stealth)
• Available support (MBTs, artillery, logistics)

River Patrol Infantry are closely related to Littoral Assault Infantry and make use of armed small craft to engage targets at or close to river banks.

Key Considerations

• Operates from armed small craft
• Focuses on riverbank and river-based engagements
• Similar in role and structure to Littoral Assault Infantry
• Requires coordination between watercraft and infantry elements

Best Employment

• Riverine operations
• Securing riverbanks
• Engaging targets along rivers and waterways

Littoral Assault Infantry are infantry that make use of armed small craft to engage beach or close-to-beach targets. They may be supported by missiles and guns from a littoral assault ship.

Key Considerations

• Operates from armed small craft
• Focuses on engaging targets near beaches or coastal areas
• May receive fire support from littoral assault ships
• Requires coordination between small craft and supporting naval assets

Best Employment

• Coastal engagement operations
• Supporting beach assaults with firepower
• Engaging targets near shorelines or coastal objectives

Amphibious Assault Infantry are infantry that land by landing craft to secure a beachhead before transitioning to another force type depending on what (if any) vehicles are available to them.

Key Considerations

• Primary role is securing a beachhead
• Operates from landing craft during initial insertion
• Will transition to another force type after landing depending on available vehicles
• Requires coordination between landing craft and ground forces

Best Employment

• Establishing a beachhead for follow-on forces
• Initial coastal landings
• Operations where infantry must transition from sea insertion to ground operations

Infantry deployed via armed utility helicopters (e.g. Wildcat, Blackhawk, etc).

Advantages:

• Extremely rapid assault capability
• Organic aerial fire support

Limitations:

• High coordination requirement (FAC control)
• Vulnerable to air defence

Best Employment:

• Shock assaults
• Rapid objective seizure
• Low-AAA environments

Infantry transported by heavy-lift helicopters (e.g. Chinook, Super Stallion, etc).

Advantages:

• Rapid repositioning
• Ability to remount and redeploy

Limitations:

• Limited lift availability
• Vulnerable to AAA

Best Employment:

• Widely dispersed objectives
• Difficult terrain
• Flexible, mobile operations

Infantry inserted via static line parachute. Operates as dismounted infantry post-landing.

Advantages:

• Strategic surprise
• Access to otherwise unreachable areas

Limitations:

• Dependent on air resupply
• Vulnerable to enemy air defence (AAA)

Best Employment:

• Behind enemy lines
• Shock operations
• Mountainous or inaccessible terrain

Infantry mounted externally on MBTs during assault.

Key Considerations:

• Provides no protection to infantry
• High vulnerability during movement

Best Employment:

• Emergency or historically constrained scenarios (e.g. WW2 Soviet doctrine)
• When no alternative transport exists

Specialist Infantry force types are defined by unique insertion methods (air, sea, or unconventional platforms). These forces often transition into standard infantry roles after insertion.

They are typically:

• Higher risk, higher reward
• Dependent on coordination (airspace, naval, or armour integration)
• Sensitive to enemy air defence or anti-vehicle capability

Force type distinctions may sometimes overlap or combine depending on operational context.

Example: US Marines going ashore in LAVs would be classed as Amphibious Mechanised Infantry