The Military Decision-Making Process starts when a unit receives its mission from higher headquarters. That initial direction sets the planning work in motion: Mission Analysis follows, then Courses of Action are developed and evaluated before approved plans become orders. Knowing the sequence makes the process easier to follow.

Multiple Choice

Which statement correctly identifies the first step in the Military Decision-Making Process?

The important idea here is the sequence of starting information and then planning steps. MDMP begins when a unit actually receives a mission from higher headquarters. That moment provides the initial direction, constraints, and intent you’ll need to start making sense of what has to be done. Because you must have that mission input first, receiving the mission is the correct first step. Once the mission is received, you move into Mission Analysis to understand tasks, identify gaps, and determine what information you still need. After that analysis, you develop Courses of Action to propose feasible ways to accomplish the mission. Drafting and refining orders comes later, after a COA is evaluated and a plan is approved. So, receiving the mission is the starting point, with the subsequent steps following in the established order: Mission Analysis, COA Development, and finally Orders Production.

Why the Military Decision-Making Process Starts with a Mission

Military planning can look like a stack of maps, timelines, and staff estimates. But before a unit can compare plans or write orders, it needs something more basic: a mission. In the Military Decision-Making Process (MDMP), the first step is Receipt of Mission. That moment gives the commander and staff the initial direction they need to begin planning.

This may sound obvious, but the sequence matters. A unit can’t sensibly analyze a mission it hasn’t received, and it can’t develop a useful course of action without first understanding what higher headquarters expects. The mission is the starting point—not the finished plan.

Planning begins with a signal

A mission may arrive as a formal order, a warning order, a fragmentary order, or another message from higher headquarters. However it comes, receipt of the mission tells the unit that planning must begin. The information may be complete, or it may leave important details unclear. Either way, the staff now has a task: make sense of the direction provided and prepare for the work ahead.

The mission gives the unit its first look at the purpose, expected actions, and desired result. It may also include constraints, deadlines, and the higher commander’s intent. These details shape the planning effort. A deadline can affect how much time is available for analysis; a constraint can rule out an otherwise attractive approach. Even a small detail in the initial order can matter later.

Receipt of mission is therefore more than a handoff. It is the point at which a unit’s planning effort begins to take form.

What happens right after the mission arrives?

Once the mission is received, the unit starts organizing its response. The commander and staff review the information, alert key personnel, and identify immediate requirements. They may issue a warning order to help subordinate units begin their own planning while the staff continues its work.

The staff also builds a planning timeline. This is a practical step, not just calendar management. Every hour spent by the headquarters affects the time available to subordinate units. A workable timeline helps keep the planning process moving and gives everyone a shared sense of what needs to happen next.

At this early stage, the unit may not have all the answers. That’s normal. The staff identifies information gaps and considers what needs clarification from higher headquarters. Planning often begins with uncertainty; the goal is to manage it, not pretend it isn’t there.

Mission Analysis turns direction into understanding

After Receipt of Mission comes Mission Analysis. Here, the staff examines the mission in detail and works to understand what must be done, why it matters, and what conditions affect success.

The staff reviews the higher headquarters’ order and intent, considers the situation, and identifies specified and implied tasks. A specified task is directly stated. An implied task is not written out, but is still needed to accomplish the mission. The staff also identifies essential tasks—the actions that the unit must complete to achieve its purpose.

This is where the original direction becomes clearer. The staff considers available time, resources, risks, and information gaps. It may develop questions for higher headquarters or seek additional information. Mission Analysis does not produce a complete plan by itself; it gives the commander and staff a stronger understanding of the problem they need to solve.

That distinction is useful. Receiving a mission tells the unit to begin. Mission Analysis helps the unit understand what that mission requires.

From understanding to possible approaches

Once the staff has analyzed the mission, it moves to Course of Action (COA) Development. A COA is a proposed way to accomplish the mission. The staff develops possible approaches that meet the commander’s intent and account for known constraints, available resources, and the situation.

A COA is not just a list of actions. It needs enough detail for the commander and staff to assess whether it is workable. The staff considers how forces might be organized, what tasks they might perform, and how the approach supports the mission’s purpose. A strong COA offers a clear path forward while leaving room to respond to changing conditions.

Later MDMP steps examine and compare the proposed approaches. The commander selects or approves a way ahead, and the staff prepares the plan as an order. Orders Production comes much later than Receipt of Mission because an order needs a sound, approved plan behind it.

In short, the process moves from initial direction to understanding, then from understanding to possible approaches and a finalized plan.

Why the order matters

It can be tempting to think of MDMP as paperwork that follows a mission. That misses the point. The steps help a unit move from limited information toward a coordinated decision. Each stage builds on work done earlier.

If a staff jumps straight to COA Development, it risks proposing approaches before it fully understands the mission. If it starts writing orders before a COA has been assessed and approved, it may create a polished document that doesn’t reflect a sound decision. The sequence helps prevent that kind of mismatch.

The steps also create a common structure across the staff. People with different responsibilities can contribute to the same planning effort, using a shared process to organize information and decisions. That structure doesn’t remove judgment. It gives judgment a place to work.

A starting point, not a complete picture

Receipt of Mission is the first MDMP step because it provides the initial direction from which planning can begin. It establishes that a task has arrived and gives the unit information to review, questions to resolve, and a timeline to manage.

From there, the sequence proceeds through Mission Analysis, COA Development, and later planning steps, including evaluation, approval, and Orders Production. The process is orderly, but real planning can still involve updates and new information. A change from higher headquarters may require the staff to revisit its understanding or adjust its approach.

That doesn’t make the starting point less important. Quite the opposite: knowing where the planning process begins helps the unit respond with discipline when the situation becomes complicated. First, receive the mission. Then work out what it means—and how to accomplish it.