A field debrief checklist should capture context, what was done, the results, the insights gained, and the follow-up actions needed. Starting with a situational summary sets the scene so others understand why certain actions were taken and what conditions influenced decisions. Recording the actions taken shows exactly what was done in response to the situation. Documenting the outcomes reveals the results and whether objectives were achieved, providing a basis for evaluating effectiveness. Capturing lessons learned pulls out useful insights and knowledge that can be applied in the future, helping teams avoid repeated mistakes and adopt better practices. Finally, outlining improvement actions translates those lessons into concrete steps, responsibilities, and timelines to close gaps and drive continuous improvement. When all five elements are included, the debrief becomes a complete learning and accountability tool, ensuring clear context, actionable results, and a path forward.

The idea being tested is that effective offensive action relies on proactive cooperation across multiple organizations and domains to synchronize what the force does. When different units and supporting elements—like infantry, armor, artillery, aviation, engineers, logistics, and even external partners—work together with a shared plan and timely information, the attack is coordinated in time and space. This unity of effort lets commanders align intent, timing, and resources, enabling rapid, synchronized actions that overwhelm an adversary and exploit combined-arms effects. This is why proactive cooperation across organizations is the best choice: it captures that coordination is not a single factor or a last-step check, but the enabler of coordinated action across the whole battlefield. Centralized decision making as the sole factor misses how speed and flexibility come from distributed, cross-organizational effort. Coordination isn’t overrated in fast operations; in fact, it’s more critical when tempo is high. Limiting coordination to unit level ignores the broader network of assets and partners that must move in concert to achieve a decisive strike.

Reconnaissance is about answering a specific question by gathering targeted information about enemy dispositions and terrain features to support a planned action. It has a clear purpose and endpoint, aiming to reduce uncertainty for a particular mission. Surveillance, in contrast, is ongoing observation of an area or activity over an extended period to maintain situational awareness and detect changes, patterns, or threats as they develop. In a patrol, you’d use reconnaissance to obtain the precise details you need before moving, while surveillance would keep a watch on a scene to notice anything that deviates from the norm. The other options mix up purpose or scope (weather data or medical evac, or speed), which aren’t the defining difference between these two tasks.

Initiative is the ability to set the terms of an operation by deciding when to strike, where to strike, and how to strike, forcing the enemy to react. When a commander can choose the time, place, and method of the attack, they dictate the conduct of the engagement and maintain the attacker’s tempo, seize opportunities, and surprise the opponent. This control over the flow of events is what distinguishes having initiative from simply maneuvering, pacing actions, or consolidating gains after the fact. Maneuver is about how forces move for advantage, tempo is the pace of operations, and consolidation is securing gains—none capture the total authority to decide the attack’s core elements as clearly as initiative.