Here is the truth: The OPORD isn't for the Commander. It is for when the Commander gets hit.
Because the OPORD contains the ("Capture the HVT, don't level the village"), you, as a Team Leader, know what to do when the radio goes dead. Do you withdraw? No. You still know the "Why." You adapt.
"Iron Company seizes OBJ TIGER (Grid XY 1234 5678) NLT 020400Z JAN 2025 to capture HVT RED in order to disrupt enemy VBIED networks in the AO." Why it matters: If the Platoon Leader forgets everything else, they remember this sentence. The "Why" (disrupt VBIED networks) allows them to make smart decisions when the original plan falls apart. PARAGRAPH 3: EXECUTION (The "How") This is the longest section. It contains the Concept of Operations (CONOPS), the Commander’s Intent, and specific tasks for each subordinate unit. army company opord example
Friendly: B Co is blocking Phase Line DOG to the West. A Co is the QRF (Quick Reaction Force) 2 kms East." 1st Platoon now knows they need to avoid the PKM fields of fire. They will approach from the South, not the North. PARAGRAPH 2: MISSION (The "Who, What, When, Where, Why") This is the clearest sentence in the entire brief. It is the only thing the Commander can legally change his mind about.
What is the most confusing OPORD you have ever received? Drop your war stories in the comments below. Hooah. Here is the truth: The OPORD isn't for the Commander
"Enemy: A squad-sized element is defending OBJ TIGER. They have established two crew-served machine guns (PKM) covering the MSR (Main Supply Route) from the North. Expect 3x IEDs placed at chokepoints.
To the untrained eye, a Company OPORD looks like a bureaucratic nightmare—dense paragraphs, grid coordinates, and acronyms like PACE and METT-TC. But to a professional Soldier, it is a contract of intent. It is the指挥官’s (commander’s) will, translated into actionable tasks. Do you withdraw
The Blueprint for Battle: Breaking Down a Company OPORD (with Example)