Intel Academy · Contents · Chapter 6 · §6.3 · Nederlandse versie

§6.3 Fusion, assessment and the intelligence estimate

The purpose of threat evaluation is not to describe the enemy, but to enable the commander to anticipate enemy action.

Open §6.3 in the academy

The final phase of Step 3 integrates all analyses into a coherent threat assessment — the principal intelligence input for Step 4.

Intelligence fusion combines all disciplines into one picture: correlate reports, resolve contradictions, identify reporting gaps, confirm or reject assumptions, and record confidence.

The structured threat assessment

A good threat assessment answers six questions:

#ElementExample
1Enemy situationForward elements in positions along Phase Line RED; reserve battalion 15 km east; artillery dispersed in wooded terrain
2CapabilitiesDeliberate defense, local counterattacks, long-range fires, delaying friendly maneuver
3LimitationsLimited bridging assets, fuel shortages, reduced artillery ammunition, damaged command network
4Intent (assessment)Not directly observable — inferred from doctrine, indicators, activity, logistics and historical behavior
5Intelligence gapsReserve artillery location, engineer status, ammunition stocks, AD disposition
6ConfidencePer judgment: main defensive line high · reserve location medium · counterattack plan low

Unknown information is operational risk: every gap should yield a collection recommendation (reserve → UAV reconnaissance · artillery → counter-battery radar · CP → SIGINT · logistics routes → IMINT). Goal: answer outstanding PIRs before the operation begins.

The intelligence estimate

The threat assessment is summarized in the intelligence estimate, with a standard structure: situation → enemy forces (ORBAT summary) → operational environment (terrain & weather) → capabilities → limitations → MLCOA (preliminary) → MDCOA (alternative) → intelligence gaps → collection priorities.

Case — River Crossing BRAVO

Mission: a mechanized brigade must secure river crossing BRAVO.
Situation: enemy mechanized brigade in prepared positions west of the river; artillery ~8 km behind the forward line; reserve battalion observed moving south.
Capabilities: defense in depth, limited counterattacks, indirect fire, delaying the crossing.
Limitations: limited engineering, disrupted fuel distribution, no bridging assets observed.
Gaps: exact reserve location, artillery ammunition, minefield density, engineer reserve.
Collection: UAV reconnaissance, SIGINT against brigade HQ, engineer reconnaissance, counter-battery radar, HUMINT.
Assessment (confidence: medium): the enemy will probably defend the river line while preserving combat power for a counterattack against any successful bridgehead.

Checklist, best practices and AI

Checklist before Step 4

ORBAT: organization, strengths and command relationships known? Doctrine: offensive, defensive and logistics doctrine analyzed? Capabilities: maneuver, fire support, AD, engineers and sustainment assessed? Assessment: strengths, weaknesses, limitations and confidence recorded? Gaps: identified, translated into collection and reflected in the PIR list?

Best practices

✔ Base judgments on multiple independent sources · ✔ record confidence per judgment · ✔ separate facts from conclusions · ✔ revise continuously · ✔ let every gap generate a collection requirement · ✔ orient products to the commander's decision.

Common mistakes

✘ Assuming intent without indicators · ✘ treating doctrine as certainty · ✘ mistaking threat templates for actual dispositions · ✘ confusing HVT and HPT · ✘ overvaluing a single indicator · ✘ reporting descriptively instead of predictively.

AI applications: extracting unit information from reports, building draft ORBATs, comparing behavior with doctrine, flagging inconsistencies, suggesting candidate HVTs, drafting concept estimates, and ranking gaps. The final judgment remains human work.

Key points of this chapter

» Step 3 evaluates the enemy as a fighting system: ORBAT (structure), doctrine (expected behavior), capabilities (possibilities).
» Threat template = doctrine; SITEMP = doctrine × terrain × current intelligence.
» HVTs matter to the enemy; HPTs matter to friendly success.
» Gaps are not failures — they define the next collection priorities.
» The completed threat assessment is the bridge between understanding the enemy and predicting enemy action.