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

§2.4 Relationships, best practices and practice

The cycle doesn't stand alone: it feeds IPB, supports every MDMP step and demands discipline in execution.

Open §2.4 in the academy

Relationship with IPB. The Intelligence Cycle produces the information IPB analyzes: collection → processing → analysis → IPB → threat assessment → decision support. In turn, IPB continuously generates new requirements (gaps, NAIs) that steer collection again.

Relationship with MDMP. The cycle supports every step of the decision-making process: mission analysis gets the environmental picture, COA development the enemy evaluation, wargaming the enemy COAs, and execution is tracked with updated intelligence. See the process diagram.

Best practices and common mistakes

Best practices

✔ Continuously update assessments · ✔ fuse multiple disciplines · ✔ challenge assumptions · ✔ separate facts from judgments · ✔ state confidence explicitly · ✔ identify intelligence gaps · ✔ keep products concise and actionable.

Common mistakes

✘ Treating information as intelligence · ✘ relying on a single source · ✘ ignoring contradictory evidence · ✘ delaying dissemination while seeking "perfect certainty" · ✘ failing to update previous assessments · ✘ collecting without a defined requirement.

Practical example: Bridge Bravo

Case — one complete cycle

Mission: a mechanized battalion must seize Bridge Bravo.
PIR (Direction): is the bridge prepared for demolition?
Collection: UAV imagery detects engineering vehicles near the bridge.
Processing: images are georeferenced and interpreted.
Analysis: engineering assets and explosive signatures indicate a high probability the bridge is prepared for demolition.
Dissemination: threat assessment sent to the commander.
Decision: engineer company tasked to secure the bridge before the assault.
Feedback: PIR answered → new PIR: where is the enemy reserve?

AI support and key points

An AI assistant can support analysts by summarizing reports, correlating observations, identifying patterns, drafting concept assessments and INTSUMs, suggesting PIRs and highlighting gaps.

Boundary

AI supports the analytical judgment — it does not replace it. Responsibility for the judgment remains with the human analyst.

Key points of this chapter

» The Intelligence Cycle turns raw information into intelligence.
» Collection alone does not produce intelligence — analysis creates understanding.
» Feedback keeps the process relevant.
» The cycle is continuous and directly supports IPB, IPOE, MDMP and operational decision making.