What is the purpose of the Threat/Adversary, Situation, and Event templates?

• A. Threat/Adversary- composition, disposition and tactics; Situation- environment overlay; Event- confirms/denies a COA; used to develop IC overlay/DST
• B. Threat: reconnaissance only; Situation: support; Event: random; used for mapping
• C. Threat: adversary's past actions; Situation: enemy morale; Event: weather changes
• D. Threat: adversary's location; Situation: none; Event: none

Answer: (A)

Templates for Threat/Adversary, Situation, and Event provide a structured way to capture the essential inputs that drive how fires are planned, monitored, and adjusted. The Threat/Adversary portion records who the threat is, their composition, where they’re positioned, and how they’re likely to fight—their tactics and capabilities. The Situation portion lays out the environment—the terrain, weather, civilian considerations, legal or political constraints, and other factors that shape how fires can be employed. The Event portion identifies indicators or triggers—events that would confirm or deny a proposed COA or signal a change in the situation that requires adapting the plan.

Together, these templates feed an intelligence overlay and decision-support tools used during COA development and execution. They ensure planners have a clear, integrated picture of the adversary, the operating environment, and the indicators that will drive timely decisions. Other options don’t fit because they narrow the focus improperly or miss the coordinating role these templates play in informing decision support and overlay products.