Mission planning is the process that turns an assigned task into a coordinated execution. A poor plan is not rescued by heroism; a complete plan reduces the number of decisions that must be taken under fire. This chapter describes METT-TC analysis, course of action development, contingencies and back-brief.
METT-TC analysis
METT-TC is the NATO-standard framework for mission analysis. Six factors to consider before formulating any course of action. Skipping one of the six is the most frequent cause of fragile plans.
| Factor | Key question | Output |
|---|---|---|
| M — Mission | What must I achieve and why | Task + Purpose |
| E — Enemy | Who, where, with what, what they likely do | Most likely / Most dangerous COA |
| T — Terrain & Weather | OCOKA: observation, cover, obstacles, key terrain, avenues | Map with tactical annotations |
| T — Troops available | What I have: men, weapons, supports, EW, drones | Operational inventory |
| T — Time available | How much time to plan, prepare, execute | Timeline 1/3 — 2/3 |
| C — Civil considerations | Civilians present, infrastructure, political consequences | Constraint list |
Of total available time, the commander uses at most 1/3 for their own planning. The other 2/3 are reserved for subordinates for their planning, briefing, rehearsal. If you receive a mission at 1800 for 0600, you must issue it to subordinates by 2200. Skipping the one-third rule strangles the team.
Course of action (COA) development
A COA is a complete solution to the mission problem. At least two contrasting COAs are developed and chosen by comparing them on explicit criteria. A single COA is not planning — it is wishful thinking.
- Generate 2–3 COAs that satisfy the mission with different approaches
- Test each COA against feasibility criteria (suitable, feasible, acceptable, distinguishable, complete)
- Compare COAs on comparison criteria (risk, surprise, simplicity, flexibility, time)
- Select preferred COA and identify branches/sequels
- Develop selected COA into detailed plan
- Suitable: COA achieves the mission if executed
- Feasible: can be executed with available resources in available time
- Acceptable: cost (risk, losses) is justifiable
- Distinguishable: significantly distinct from other COAs
- Complete: covers the entire mission duration
Contingencies
A contingency is a subordinate plan for an unforeseen but plausible event. You do not plan everything: you plan high-probability high-impact events. Three types: branches (you must change path), sequels (what to do after completion), abort criteria (when to break off).
| Event | Contingency | Trigger |
|---|---|---|
| Critical casualty | Priority CASEVAC, rally Echo | MARCH red |
| FPV incoming | Hard cover, EW if available, freeze 60 s | Audible buzz or spotter call |
| Road blocked | Bypass on alternate route Bravo | Recon call or point vehicle |
| OPSEC compromise | Break contact, withdraw, reposition | Drone observed, unexpected contact |
| Comms lost | Rendezvous at check point Charlie at xx:30 | 30 min of radio silence |
Abort criteria are the conditions that cancel the mission. They must be set in advance, not improvised. Example: 'abort if we lose 2 men before reaching the objective' or 'abort if support drones are not on-station by H+15'.
Briefing and back-brief
The briefing transmits the plan to subordinates. The back-brief is the moment when subordinates repeat the plan in their own synthesis to the commander, demonstrating understanding. Skipping back-brief produces divergent executions. Standard briefing format is OPORD or, in compressed version, FRAGO.
- 1. Situation: enemy, friendlies, terrain, civilians
- 2. Mission: task + purpose in one sentence
- 3. Execution: intent, scheme of manoeuvre, tasks per element, coordination
- 4. Service & support: logistics, medical, CASEVAC, ammo
- 5. Command & signal: who commands, frequencies, brevity codes
Each subordinate team leader repeats: 'Our mission is X by Y, because Z. My task is A; I work with B in phase 1; in phase 2 I withdraw on C. Constraints: D, E. Comms on freq F. ROE: G.' If they cannot do it in 60 seconds, the plan is not yet understood.
Rehearsal
Rehearsal is the concrete test of the plan before execution. Three forms: rock drill (2D physical model with rocks and string), walk-through (slow execution in similar terrain), live rehearsal (full execution with weapons no live fire). Even a 20-minute rock drill greatly increases the probability of success.
- Identify critical synchronisation points (who moves when relative to whom)
- Surface plan errors before they cost lives
- Forces subordinates to verbalise their role
- Lets medic, comms specialist, drone team rehearse their sequences
- Final rehearsal: full kit, light conditions similar to execution
Common mistakes
- Skipping terrain analysis because 'I know it by heart'
- Developing only one COA and calling it 'the plan' without comparison
- Transmitting the plan by chat without back-brief — fragmented interpretations
- Not defining abort criteria — mission self-perpetuates beyond the sensible point
- Ignoring civilians in analysis — political and propaganda surprises
- Skipping rehearsal for haste — expensive afterwards, free beforehand
Lessons learned Ukraine
Ukrainian units that win LOC assaults document a pattern: 4–8 hours of formal METT-TC planning per assault hour, two COAs compared on drone risk vs artillery risk, at least a 20–40 minute rock drill, individual back-brief per squad leader. Units that lose skip formal planning ('no time'), then spend the saved time improvising under fire. Planning is not wasted time — it is time invested in reducing the decisions taken under stress.