Table of



The primary purpose of collection management is to answer the commander's intelligence requirements while making the best use of scarce intelligence collection resources. The secondary purpose is to answer intelligence requirements of other intelligence users.

Intelligence requirements generally focus on intelligence required to prevent surprise, support planning, support decisions during execution of' a friendly course of action (COA), and engage high payoff targets (HPTs) in support of that COA. They are products of the decision making and targeting processes. Collection management satisfies these requirements by synchronizing the activities of intelligence collectors and processors with the command's operations.

Collection Management and the Decision Making Process

The decision making process leads to the selection of a friendly COA. The selected COA includes a list of' intelligence requirements, some of which the commander will designate as PIR. Each intelligence requirement supports a decision expected to occur during execution of the selected COA.

Mission Analysis

Develop Courses of Action

Analyze and Compare COAs



Collection Management and the Targeting Process

The targeting process results in targeting guidance that supports the command's COA. This guidance generates additional intelligence requirements in support of each potential friendly COA the targeting process supports.




Collection Management and Intelligence Synchronization

Intelligence synchronization is the process that ensures the intelligence system provides answers to intelligence requirements in time to influence the decisions they support.

Synchronization begins with the decision making and targeting processes. Taken together, these processes identify the decisions that must be made during execution of a COA and its branches and sequels. It is these decisions which drive the command's intelligence requirements. Every identified decision should be supported by an intelligence requirement.

Other commands (higher, subordinate, and adjacent) develop their intelligence requirements through the same processes. They communicate their requirements to the collection manager in the form of specific orders (from higher commands) or specific requests (from subordinate or adjacent commands). The collection manager integrates their requirements into his planning to satisfy his own command's requirements.

To facilitate coordination, the collection manager establishes intelligence handover lines between higher and subordinate units. Requirements for intelligence in a given area can then easily be directed to the unit with responsibility for that area of the battlefield. Intelligence handover lines are especially useful when tracking particular threat units or HPTs. "Handing over" responsibility for the target as it crosses the coordination line, accompanied by liaison, ensures that it is not lost in the transition.

Synchronization continues during the collection management process. The collection manager uses the products of IPB, the decision making process, and the targeting process to develop SOR sets that synchronize the activities of collectors with the command's DPs. He ensures--

During execution the collection manager follows up and monitors the collection effort reporting to ensure synchronization. As needed, he prompts asset managers to meet timelines, cross-cueing, and retasking as necessary to keep intelligence operations synchronized with the command's operations.

An Example

The Collection Manager's Role

Desired End Effect

So What?