“The commander must decide how he will fight the battle before it begins; then he must trust his subordinates to carry it out.” — Gen. George C. Marshall

I wish I had a copy of the Operations Order (OPORD) my cavalry unit wrote for our convoy security mission during Operation Iraqi Freedom (OIF) in 2008. It did not change much in the nine months we were there. We protected supply convoys leaving Kuwait for Iraq. Usually we handed the convoys over to other units in southern Iraq, turned around the next day, and did it all over again. It was not unusual to have over six convoy security patrols on the road on any given night. When missions went farther into Iraq, they could be gone for a week or more. Those were long days for everyone—from the troopers on the road to the ones ensuring vehicles were safe, maintained, and ready to roll again.
While the Mission section of an OPORD emphasizes what and why an organization is doing something, Execution is where you get into the weeds on how it will happen. In my unit’s case, it is where the rubber literally met the road. This section identifies the main effort, assigns responsibilities to subordinate units, and explains how their actions combine to achieve success. Most importantly, it establishes what success must look like so that when carefully built plans fail to account for something unforeseen—as they inevitably do—the team can continue to operate and accomplish the mission.
That shared understanding of success is where the Execution portion begins. Its first subsection is the Commander’s Intent. Commander’s intent describes the broad conditions that define success at the end of the mission through three elements: expanded purpose, key tasks, and desired end state. By clearly articulating how the friendly force, enemy, terrain, and civil environment should look when the mission is complete, it gives subordinate leaders the understanding they need to act decisively when plans inevitably change. Done well, commander’s intent aligns initiative across the force by clarifying acceptable risk, empowering disciplined flexibility, and keeping everyone oriented on the same operational vision. The commander is essentially saying: This is how you will know we have succeeded. When in doubt, keep this vision in mind and help us get there. The details that follow matter—a lot—but this section is foundational. In a community college, it is just as critical.

Other elements in the Execution section include the Concept of Operations, a high-level description of how the mission will unfold; the specific Tasks to Subordinate Units; and Coordinating Instructions that apply across the force. In combat, these might include rules of engagement and phase timelines. The level of detail grows with the number of units involved and the complexity of the mission.
How might an Execution section apply to a community college? The president might provide a narrative for the institution as a whole. In most cases, the main effort is instructional faculty teaching classes. Many other offices support this effort and must understand their roles clearly—Student Financial Services, Student Success Services, Information Technology, Admissions and Registration, cafeteria services, libraries, and others. An overarching order that explains how each office contributes to the main effort would be extremely valuable, and it would not need frequent revision. Like our cavalry squadron’s order in OIF, it becomes a standing reference and a tool for assessing institutional effectiveness. Strategic plans already exist and remain essential, but what I am describing is complementary: a mission-focused framework informed by the strategic plan and the college mission that clarifies roles and supports meaningful assessment across departments.
Subordinate areas can—and should—build their own OPORDs and nested Execution paragraphs. I work in Student Development Services (SDS). At our college, this division is overseen by a cabinet-level vice president and includes Advising and Counseling, Event Services, Wellbeing and Thriving, Recruitment and Outreach, Workforce Readiness, and others. While nested under the college-level order, the SDS OPORD, and Execution paragraph, would specify how our area supports the president’s mission. SDS would identify its own main effort (likely advising), articulate the vice president’s intent, and publish coordinating instructions and shared SOPs. Capturing this in a deliberate format, following deliberate decision-making (see my posts on MDMP), would provide a powerful tool for executing Student Development Services role in the college mission.
There is one more section of the OPORD that is especially important in higher education: Command and Signal. I will discuss that in my next post.



















