Intel Academy · Contents · Chapter 2 · §2.2 · Nederlandse versie

§2.2 The six phases

Each phase has its own purpose, questions and products — and each phase can be the weakest link.

Open §2.2 in the academy

The six phases are covered individually below. Keep in mind: the cycle is a mental model. In practice phases overlap, reports skip phases, and multiple cycles run simultaneously — one per intelligence question.

Phase 1 — Direction

Direction establishes what intelligence is needed to support the operation. The commander and intelligence staff identify: the PIR, FFIR and EEFI, collection priorities and intelligence gaps.

Typical direction questions

Where is the enemy reserve? · Has the enemy crossed the river? · Which air defense systems are operational? · Is the bridge prepared for demolition?

Products: PIR matrix, collection plan, intelligence requirements, collection synchronization matrix.

Pitfall

Without sharp direction, collection becomes a dragnet: lots of data, few answers. Every sensor tasking should trace back to a requirement.

Phase 2 — Collection

Collection gathers information from all available sources: the INT disciplines (HUMINT, SIGINT, GEOINT, IMINT, MASINT, OSINT), but also patrols, reconnaissance units, UAVs, radar, EW sensors and civil authorities.

Key point

Collection is not the same as producing intelligence. Collecting only yields raw information.

Example

A UAV detects ten armored vehicles moving east. That's information — not yet intelligence. What it means only becomes clear during analysis.

Phase 3 — Processing & Exploitation

Processing makes collected information usable for analysis: imagery interpretation, translation, signal decoding, geolocation, database entry and report formatting.

Processing is the invisible phase — and therefore often the underestimated bottleneck. A mountain of untranslated intercepts or unexploited imagery is operationally worthless.

Phase 4 — Analysis & Production

This is where information becomes intelligence. Analysts combine information from multiple sources and assess credibility, reliability, operational significance, enemy intentions and capabilities, and possible courses of action.

Key questions: what happened? — why? — what does it mean? — what happens next? — and how confident are we?

Example

Information: increased radio traffic · artillery movement · fuel convoys moving forward · UAV activity.
Assessment: "The enemy is preparing for an offensive operation within 24 hours." — that is an intelligence product.

This is where the IPB process runs: the structured framework that systematically works through environment, enemy and COAs.

Phase 5 — Dissemination

Dissemination delivers the product to whoever needs it. Intelligence that arrives too late has little value.

Common products: INTSUM, INTREP, SPOTREP, threat assessment, intelligence estimate, situation update, DST, maps and threat overlays.

Principles: timely · relevant · accurate · actionable · secure. The best product is the one the recipient can use immediately — not a reference work, but an answer.

Phase 6 — Feedback

Feedback determines whether the intelligence met the need: was the product useful? Were the PIRs answered? What's still missing? Do priorities need to change?

Feedback generates new requirements — and the cycle begins again. Without feedback the process produces products no one uses.

Air force example: a SEAD mission through the cycle

Case — Suppression of Enemy Air Defenses (SEAD)

Direction: PIR — "Is SAM site RODNIK still operational at the time of the strike wave?" Collection: ELINT sensors listen for RODNIK's search radar; an IMINT pass photographs the site. Processing: the radar emission is identified as a specific SAM type; the image is georeferenced. Analysis: radar active + vehicles in position → the site is operational and threatens the strike route. Dissemination: an updated threat overlay goes to mission planners and the Air Operations Center. Feedback: PIR answered → new PIR: "Does the site remain active after the first SEAD wave?"

Same six phases, but with a different sensor mix and a tighter timeline: air operations typically run on the cadence of the Air Tasking Order cycle (usually 24-72 hours from planning to execution), meaning collection and analysis must deliver within a strictly bounded window.