Operational Reports

Operational intelligence is the middle child of the intelligence family -- often overlooked but absolutely essential. It supports the planners and commanders who translate strategic objectives into executable campaigns. This lesson covers the operational environment assessment, the key elements of an operational report, how to sync with the planning cycle, and the unique challenge of serving an audience that needs more detail than strategic consumers but more context than tactical ones.

Operational intelligence occupies the space between "why are we doing this?" (strategic) and "how do we do this specific thing right now?" (tactical). It answers the question: **"How do we plan and execute this campaign to achieve the strategic objective?"**

Key Characteristics

• Timeframe: Weeks to months. Long enough to plan phased operations, short enough that the intelligence remains actionable.

• Scope: Theater, region, or campaign-level. A specific area of operations or a defined mission set.

• Focus: The operational environment -- adversary order of battle, terrain, infrastructure, key actors, logistics, population dynamics, and how these factors interact.

• Audience: Theater commanders, campaign planners, task force leaders, and their staffs. These people are making resource allocation and sequencing decisions.

The Audience's Mindset

Your operational consumer is asking questions like:

• "What does the adversary look like in my area of operations, and how are they likely to respond to my actions?"
• "Where should I concentrate my resources over the next four weeks?"
• "What are the second- and third-order effects of the operation we are planning?"
• "What indicators should I watch for that would tell me the campaign is succeeding or failing?"

The operational analyst is the person who tells the chef what ingredients are available and what the guests are allergic to. The strategic analyst picked the restaurant. The tactical analyst is plating the dish. Everyone thinks their job is the hardest.

The Operational Environment Assessment (OEA) is the foundational product of operational intelligence. It provides a comprehensive picture of the operating environment that enables planning and decision-making. In military doctrine, this process is formalized as Joint Intelligence Preparation of the Operational Environment (JIPOE), but the principles apply in any operational context.

Core Components of an OEA

• Physical environment: Terrain, weather, infrastructure, lines of communication, key terrain features. What does the battlespace look like?

• Adversary assessment: Order of battle, capabilities, tactics, leadership, logistics, morale, and most importantly -- _probable courses of action_. What will the adversary likely do?

• Civil considerations: Population demographics, governance structures, economic activity, cultural factors, humanitarian concerns. How will the local environment affect and be affected by operations?

• Information environment: Media landscape, narrative dynamics, social media influence, information operations by all parties.

• Threat integration: How adversary capabilities interact with the terrain and civil environment to create specific threats to friendly operations.

The best OEAs are living documents, not one-time products. Establish an update cycle that matches your operational tempo. A fast-moving campaign may need weekly updates; a stability operation might update monthly. The key is that the OEA always reflects current reality, not the reality that existed when you first wrote it.

Beyond the foundational OEA, operational analysts produce a range of products tied to the planning and execution cycle. While formats vary by organization, most operational reports share these essential elements.

Situation Overview

Open with a concise summary of the current operational situation. What has changed since the last report? What is the adversary doing? What are the key developments that affect the campaign? This should be readable in under two minutes.

Adversary Course of Action Analysis

This is often the most valuable section for campaign planners. Present the most likely and most dangerous adversary courses of action (COAs), with supporting evidence and indicators for each. Planners use this to war-game their own options and develop contingencies.

Most Likely COA: What does the evidence suggest the adversary will probably do? Base this on observed patterns, capabilities, and assessed intent.

Most Dangerous COA: What is the worst-case scenario that the adversary has the capability to execute, even if it is less likely? Planners need to account for this even if they optimize against the most likely scenario.

Campaign Impact Assessment

How are current operations affecting the adversary and the operational environment? Are the campaign objectives being met? This section connects intelligence to **measures of effectiveness (MOEs) and measures of performance (MOPs)** to help the commander assess progress.

Intelligence Gaps and Collection Priorities

Be honest about what you do not know. Identify the critical intelligence gaps that affect planning and recommend collection priorities to fill them. This section drives the collection cycle and demonstrates analytical integrity.

An operational report without an intelligence gaps section is like a weather forecast that never mentions clouds. Sure, the sunny parts sound great, but the commander really needs to know about the storms they cannot see yet.

The Intelligence-Operations Planning Cycle

Operational intelligence does not exist in a vacuum -- it is tightly coupled with the operations planning cycle. Intelligence inputs are needed at every stage:

• Mission analysis: Intelligence provides the environmental context and adversary assessment that shapes how the mission is understood.

• COA development: Intelligence informs which friendly COAs are feasible by assessing adversary reactions and environmental constraints.

• COA comparison: Intelligence helps war-game each option by projecting adversary responses and identifying risks.

• Execution: Intelligence provides the indicators and warnings that trigger branches and sequels during execution.

• Assessment: Intelligence helps evaluate whether the operation achieved its objectives and what adjustments are needed.

Know where your planning staff is in the cycle and tailor your products accordingly. During COA development, they need adversary COA analysis. During execution, they need indicators and warnings. Delivering the right product at the wrong time is almost as bad as delivering the wrong product.

Bridging Strategic and Tactical

The operational analyst serves as a translator between two very different worlds. Strategic guidance comes down in broad terms: "Degrade the adversary's capability to project force in the region." Tactical reports come up in granular detail: "Patrol observed three vehicles at grid reference XY1234 at 0600."

Your job is to **translate strategic objectives into operational intelligence requirements that drive tactical collection, and to aggregate tactical reporting into operational assessments** that inform strategic decision-making.

Top-down: "The strategic objective requires us to understand the adversary's logistics network. This means we need operational-level mapping of supply routes, which requires tactical-level surveillance of key nodes."

Bottom-up: "Tactical reporting over the past three weeks shows increased movement along Route Alpha. At the operational level, this suggests the adversary is repositioning forces for a spring offensive, which has strategic implications for regional stability."

The Role of Operational Reports

Operational reports are the primary vehicle for communicating intelligence that directly supports ongoing operations. Unlike strategic assessments, which inform long-term planning, operational reports are produced and consumed in the same timeframe as the operations they support - often hours or minutes before the operation commences:

• Time-Sensitive Production: Operational reports must be produced quickly enough to inform the operation they support. A tactical report that arrives after the operation has begun has lost most of its value. This time pressure shapes every aspect of operational reporting - format, length, source requirements, and dissemination channels.
• Action-Oriented Content: Operational reports focus on specific, actionable information - the location and activity of a target, the security situation along a planned route, the presence of civilians or friendly forces in an area of operations. Information that does not directly support operational decision-making is excluded, regardless of its analytical interest.
• Direct Consumer Relationship: Operational reports are typically consumed by the operators or tactical commanders who will act on the intelligence. This direct relationship - often face-to-face or through a dedicated communications channel - allows for immediate clarification, refinement, and follow-up that formal reporting channels cannot provide.

Structure of an Operational Report

Operational reports follow a standardised format that allows operators to extract critical information rapidly:

• The SALUTE Format: A widely used template for tactical intelligence reports: Size (how many), Activity (what are they doing), Location (where are they), Unit (who are they), Time (when was the information collected), Equipment (what are they carrying or using). SALUTE reports are concise, structured, and immediately usable.
• The SITREP (Situation Report): A broader format that covers the current situation, friendly force status, enemy activity, and significant events since the last report. SITREPs are the standard reporting format for ongoing operations and are produced at regular intervals or when significant changes occur.
• The SPOT Report: A short, urgent report of time-sensitive information that cannot wait for the next scheduled SITREP. SPOT reports are used for imminent threats, significant enemy movements, or unexpected developments that require immediate command attention.
• The ACE Report: Army, Casualties, Equipment - a format used to report battle damage, casualties, and equipment status. ACE reports are essential for maintaining situational awareness of friendly force readiness during prolonged operations.

Operational Report Writing Standards

Writing for operational consumers requires specific adaptations from standard intelligence writing:

• Bottom Line Up Front: The most critical information - the threat to the operation, the change in the situation, the time-sensitive development - must appear in the first sentence. Operational consumers do not have time to read background before reaching the essential information.
• Specificity Over Generality: "The target was observed at 0630 hours moving from Location A to Location B in a white Toyota HiLux, licence plate ABC-123, accompanied by two unidentified males" is an operational report. "The target was seen leaving his residence in the morning with associates" is not.
• Grid Coordinates: Location information in operational reports should include grid coordinates (MGRS or lat/long) in addition to place names. "Near the market in the northern district" is not sufficiently precise for an operation. "Grid: 38T 0546789 1234567" is precise.
• Confidence Indicators: Operational consumers need to know how reliable the intelligence is so they can factor uncertainty into their planning. A report that does not include a confidence assessment forces the operator to guess at the intelligence's reliability.
• Source Protection: Operational reports may need to protect sensitive sources while still providing enough information for the operator to assess reliability. Standard caveats like "Source: HUMINT-3" (a source of known reliability reporting through established channels) provide the operator with a reliability framework without revealing source identity.

The Intelligence-Operations Interface

The relationship between intelligence producers and operational consumers is critical to operational success:

• Embedded Analysts: Many military and law enforcement organisations embed intelligence analysts directly with operational units. Embedded analysts develop a deeper understanding of operational needs and can produce more relevant intelligence faster than analysts working from a remote headquarters.
• The Intelligence Push: In a well-functioning intelligence-operations relationship, intelligence is pushed to operators based on their anticipated needs, not pulled based on requests. The analyst anticipates what the operator will need next and produces it before being asked.
• After-Action Review: Following every operation, the intelligence that supported it should be reviewed. What was accurate? What was missed? What could have been better? The after-action review is the most effective mechanism for improving operational intelligence.
• Trust Development: Operators trust intelligence they have seen validated through operational outcomes. New intelligence units or analysts must build this trust over time through consistent, accurate reporting. Trust once broken - through an inaccurate report that leads to a failed operation - is difficult to rebuild.