The final phase of Step 4 converts predictive intelligence into decision support: linking enemy actions, friendly actions, collection, fires, maneuver and time — so the commander prepares decisions in advance rather than reacting. The chain: ECOAs → event template → indicators → NAIs → decision points → DST → DSM → decision.
Decision points and triggers
A decision point is a location, event or time at which the commander must decide based on intelligence — linked to time, terrain, enemy and friendly actions and information requirements. Every DP should have a corresponding intelligence trigger: a predefined observable condition that activates the DP (enemy reserve departs assembly area, bridging equipment detected, artillery displaces, AD radar activated).
A good DP is clearly identifiable, supported by intelligence, time-sensitive, actionable, and linked to one or more branches or sequels. See the card Decision points & triggers.
DP-3 — enemy reserve commitment. Decisions at stake: commit friendly reserve? Execute obstacle breach? Request CAS? Required intelligence: enemy reserve movement confirmed, artillery repositioning observed, engineer bridge assets identified.
DST and DSM
The Decision Support Template graphically integrates: friendly axes of advance, enemy avenues of approach, decision points, NAIs, TAIs, HPTs, engagement areas, fire support coordination measures, mobility corridors and key terrain. The commander sees in one picture where and when critical decisions are expected.
The Decision Support Matrix presents the same content procedurally:
| DP | Trigger | Intelligence required | Commander action |
|---|---|---|---|
| DP-1 | Recon detected | UAV confirmation | Increase ISR |
| DP-2 | Reserve movement | SIGINT + IMINT | Commit reserve |
| DP-3 | Bridge preparation | Engineer activity | Execute fires |
| DP-4 | Artillery displacement | Counter-battery radar | Conduct suppression |
Collection itself also gets triggers (reserve → UAV, immediate · artillery fire → CB radar, immediate · engineer activity → HUMINT, high priority · increased comms → SIGINT, continuous). Decision support requires close cooperation between S2/G2, S3/G3, fires, engineers, aviation, EW and logistics; every DP is reviewed during planning and rehearsal.
Branches, sequels and the transition to operations
Decision support anticipates plan changes. A branch is an alternative action executed when conditions change (enemy launches unexpected counterattack → delay the river crossing and reinforce the flank); a sequel is the subsequent operation after mission completion (bridgehead secured → expand the lodgement, continue the advance, or transition to defense). Decision points often determine when a branch or sequel is executed.
Mission: a mechanized brigade must seize Bridge BRAVO before enemy reinforcements arrive. MLCOA: enemy delays while preserving the reserve. MDCOA: immediate counterattack with reserve armor. DP-2: enemy reserve crosses Checkpoint CHARLIE. Trigger: two mechanized companies observed moving south; SIGINT confirms brigade command net activation. Decision: commit brigade reserve, request CAS, initiate artillery interdiction. Expected outcome: friendly forces disrupt the counterattack before it reaches the bridge.
Final products, best practices and key points
At the end of Step 4, the intelligence staff delivers: MLCOA and MDCOA with assumptions, event template and event matrix, NAIs and TAIs, DST and DSM, collection recommendations, and a confidence assessment. The completed IPB supports mission analysis, COA development, wargaming, targeting, ISR planning, risk assessment and execution — and does not stop when the operation begins: products are continuously updated during execution.
✔ Keep the DST focused on decisions · ✔ link every DP to observable indicators · ✔ validate triggers with multiple sources · ✔ synchronize with the operational timeline · ✔ update decision support throughout execution · ✔ ensure intelligence, operations and fires share one picture.
✘ DPs without an actionable decision · ✘ failing to update the DST after changed enemy behavior · ✘ overloading the DSM with detail · ✘ confusing triggers with operational tasks · ✘ treating IPB as a planning-only activity instead of a continuous process.
AI applications: generating draft event templates and DSMs, identifying candidate DPs, correlating indicators, recommending ISR allocation, detecting deviations from predicted COAs and updating assessments in near-real-time — always under human validation.
» Step 4 completes the transition from analysis to prediction.
» ECOAs are evidence-based, feasible and doctrinally consistent; the MLCOA drives the plan, the MDCOA drives the contingency.
» The event template and event matrix translate COAs into observable events; NAIs serve collection, TAIs serve targeting.
» DPs, triggers, DST and DSM let the commander anticipate rather than react.
» This closes the IPB loop: execution → assessment → updated intelligence → renewed IPB.
Air force example: SEAD/DEAD targeting and the ATO cycle
For air operations, ECOA development and decision support run in sync with the Air Tasking Order (ATO) cycle: a fixed rhythm of target selection, planning, execution and assessment, usually planned 24 to 72 hours ahead. Targeting gets its own product here: the Joint Integrated Prioritized Target List (JIPTL), where HVTs from the IADS (SAM sites, GCI radars, airfields) are prioritized into HPTs for SEAD/DEAD (Suppression/Destruction of Enemy Air Defenses).
MLCOA: the enemy IADS stays passively alert (radars briefly on/off) to avoid detection by SEAD missions. MDCOA: the enemy activates the full SAM network the moment the strike package nears the MEZ. Decision point: DP-Air-1 — is radar activity detected within the first 10 minutes of the mission? Trigger: ELINT reports search-radar emission from an SA-10 site. Decision: the SEAD package switches from "monitor" to "engage"; the strike package is rerouted to a lower ingress path. Time window: the decision must fall within the current ATO time slot — a missed trigger pushes the mission to the next cycle.
No-fly zones and airspace restrictions serve as the battlespace geometry for the COAs here: an MLCOA/MDCOA comparison for air weighs not just likelihood and risk, but also whether a route passes through defended airspace.
Deep dive: third-party targeting & engage-on-remote
A classic assumption in WEZ/MEZ analysis is that a weapon system can only engage what its own radar sees. Third-party targeting breaks that assumption: the sensor that finds the target and the shooter that fires need no longer be the same platform. They are linked by a datalink network.
| Term | Meaning |
|---|---|
| Launch-on-remote | The shooter launches on an external sensor cue; its own radar takes over guidance later |
| Engage-on-remote | The entire engagement — including guidance — runs on external sensor data; the shooter never sees the target itself |
The showcase example is the US NIFC-CA (Naval Integrated Fire Control – Counter Air) with the Cooperative Engagement Capability (CEC): an E-2D Advanced Hawkeye detects a target beyond the ship's horizon, shares the fire-control-quality track over CEC, and a ship launches an SM-6 at a target it cannot see itself. In demonstrations, even an F-35 cued an SM-6 launch from a ship, with intercepts beyond 100 nautical miles.
The reach of the threat is no longer the reach of the individual weapon system, but of the network. A SAM with its radar switched off can still be lethal if an AWACS or another platform cues it (see also kill web). Two consequences: (1) the engagement zone on your overlay must be stretched to the network boundary, not the system boundary; (2) sensor nodes — AWACS, elevated sensors, reconnaissance drones — become HVTs themselves, because taking them out shortens the whole network.
This topic bears directly on air defense. The defensive side — how an IADS uses third-party targeting with "silent SAM" tactics and network C2 — is worked out on the sister site airdefense-academy.