Core Definition (BLUF)
Detachment mission planning is the Special Forces Operational Detachment-level process for turning a received mission into an executable plan, OPORD, and briefback. GTA 31-01-003 is the open planning engine for that echelon: mission receipt through mission analysis, COA development and war game, orders, and the briefback that proves the team can run the job.
Doctrinal Framework
- Pub: GTA 31-01-003 Special Forces Detachment Mission Planning Guide (January 2020)
- Echelon: SFODA (and analogous small teams)
- Coverage: full on process shape; partial on annex templates (use what fits; do not cargo-cult every appendix)
- Related: FM 6-0 (commander and staff process at higher echelons); Mission Command as philosophy substrate
The GTA walks a Military Decision-Making Process (MDMP) adapted to isolation planning, often on a compressed clock (classically on the order of days, not weeks).
Mechanics
MDMP steps (detachment flavor)
- Receipt of mission - WARNO mindset: alert the team, pull higher products, start the clock, protect OPSEC.
- Mission analysis - restated mission, intent two up, constraints, facts/assumptions, PIRs/IRs, initial risk, draft mission statement.
- COA development - multiple ways to achieve the mission; each COA has a clear scheme of maneuver / concept.
- COA analysis (war game) - action, reaction, counteraction; kill weak COAs early.
- COA comparison - criteria that match the mission (not aesthetics).
- COA approval - commander decides; dissent recorded if needed; commit.
- Orders production - OPORD and essential annexes; load plans, routes, abort, link-up, med, comms as required.
Briefback
The briefback is not theater. It is the test that every member can:
- state mission and intent
- describe their role under the approved COA
- run contingencies (abort, compromise, casualty, comms loss)
- prove timing, sustainment, and support requests are real
If the briefback fails, the plan is not ready. Fix it or re-COA.
Time-constrained planning
When the clock is short, compress deliberately: fewer COAs, heavier reliance on SOPs, earlier commander guidance, tighter war game. Do not “skip analysis” silently; state what you assumed.
Templates worth knowing (open GTA list)
OPORD and annexes; intelligence annex; infiltration/exfiltration; load plan; route overlay; abort; assembly; link-up; training plan; transition; MISO and CA annexes when relevant; logistics; medical; communications; planning matrices; CARVER; evasion plan of action; key leader engagement cycle.
Application
Map the SFODA cycle onto any small element that must plan in isolation from a large staff:
| Planning idea | Function |
|---|---|
| Isolation / focused planning block | Protected time and attention for analysis |
| NCO rhythm | Ops lead owns schedule, inspections, and time hacks |
| Intelligence running estimate | Living target/site/threat file owned by the intel billet |
| Briefback | Dry-run with roles; junior member can brief the plan |
| Abort plan | Written walk-away criteria before departure |
| CARVER / target matrices | Ranked priorities for sites, people, or systems to affect |
Minimum viable products: restated mission, analyzed METT-TC, at least two serious COAs, war-gamed selection, order, briefback, abort criteria.
Related Concepts
Philosophy: Mission Command.
Leader sequence under compression: Troop Leading Procedures.
Targeting tools: CARVER Matrix, Center of Gravity.
Activity selection: Special Forces Core Activities.
Failure Modes
- One COA only - then the first obstacle ends the operation.
- Beautiful OPORD, no briefback - the team cannot run it.
- Annex spam - templates filled to look complete while the scheme of maneuver is mush.
- No abort criteria - pride keeps people in a burned plan.
- Planning past the time available - perfect plan, late arrival.