FM/C108 - Planning and Execution - 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, Support Engineer or 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.

• 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 platoon
  • A company, platoon or squad
• Lead by a mortar/artillery section leader or a mortar/artillery gunner
• Consists of 2-5 people

• 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
• Consists of 1-3 people

• 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.

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
• 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 combined size of all game master slots may 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,...), 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

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
• In the case of an empty role:
  • Commander empty -> gunner combines the gunner and commander roles
  • Gunner empty -> commander combines the gunner and commander roles
  • Driver empty -> the commander and gunner come to an agreement who will fill driver and gunner. If no agreement can be reached, the gunner becomes the driver and the commander combines the gunner and commander roles

• 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.