Intel Academy · Contents · Chapter 3 · §3.3 · Nederlandse versie

§3.3 Workflow, products and relationships

From mission to collection plan: the analytical workflow, the product set and IPB's place among the Intelligence Cycle, MDMP and IPOE.

Open §3.3 in the academy

The complete analytical workflow runs as follows: mission → mission analysis → AO/AI → terrain analysis → weather analysis → infrastructure analysis → threat analysis → capability analysis → threat template → enemy COAs → indicators → decision support → collection plan → continuous update.

ProductPurpose
AO / AI overlayOperational and intelligence boundaries
COO / MCOOObstacles and mobility
Terrain / Weather Effects MatrixWhat terrain and weather mean
ORBAT / capability matrixEnemy organization and capabilities
Threat template / SITEMPDoctrinal and expected enemy picture
Event template / event matrixExpected events and indicators
NAI / TAI overlayObserving / achieving effect
DST / DSMDecision support for the commander

All products are covered in the reference library.

Relationship with the Intelligence Cycle and MDMP

Intelligence Cycle. The cycle generates the information IPB analyzes: collection → processing → analysis → IPB → threat assessment → decision support. Every IPB product generates new requirements and thereby drives the next collection round.

MDMP. IPB is the primary intelligence input for the decision-making process: mission analysis draws on steps 1–2, COA development on step 3, wargaming on step 4. Without a completed IPB, planners cannot develop or compare friendly COAs.

Remember

IPB does not run after but alongside the MDMP: every MDMP step consumes IPB products that must be current at that moment.

IPB versus IPOE

IPB (classic/tactical)IPOE (current/joint)
Tactical focusOperational and strategic focus
BattlefieldFull operational environment
Terrain and enemyPMESII-PT, ASCOPE, information environment
Supports tactical planningSupports joint and multi-domain planning

The methodology is the same; the difference lies in scale and scope. Whoever masters IPB can make the step to IPOE by broadening the analytical frame.

Current terminology

IPOE is now also the official replacement for IPB, not merely its larger sibling. In January 2024 the US Army renamed Intelligence Preparation of the Battlefield to Intelligence Preparation of the Operational Environment (ATP 2-01.3, Change 2), aligning with FM 2-0 (2023) and JP 2-0. NATO likewise uses IPOE (AJP-2.1 / APP-28). This course keeps "IPB" as the widely recognised legacy term, but be aware that current doctrine says IPOE.

Best practices, pitfalls and AI

Best practices

✔ Update continuously · ✔ fuse disciplines · ✔ separate facts from assumptions · ✔ state confidence · ✔ test judgments against new information · ✔ orient everything toward the commander's decision · ✔ always work out both the MLCOA and the MDCOA.

Common mistakes

✘ Treating IPB as a one-time planning task · ✘ ignoring terrain effects · ✘ overestimating enemy capabilities · ✘ failing to challenge assumptions · ✘ collecting without PIRs · ✘ producing descriptive rather than predictive products.

AI can accelerate IPB: summarizing reports, generating OAKOC/RABVI analyses and ORBATs, drafting concept SITEMPs and COA suggestions, flagging gaps and recommending collection. Professional military judgment remains with the analyst.

Air force example: IPB in three dimensions

The IPB model is domain-independent, but its content shifts substantially for air operations:

Chapters 4 through 7 include an air force example alongside the ground-based example at each step.

Key points of this chapter

» IPB is a continuous analytical process that turns intelligence into operational understanding.
» Four mutually reinforcing steps, each with its own products for decision making.
» IPB drives collection, planning and targeting.
» The ultimate goal is predictive intelligence — for both ground and air operations.