The Rapid Decision-making and Synchronization Process (RDSP) follows five steps defined in U.S. Army doctrine: (1) determine that a decision is required, (2) compare the current situation to the order, (3) develop a course of action, (4) refine and validate the course of action, and (5) implement. The process is designed for speed during active operations, when the full Military Decision-Making Process (MDMP) would take too long.
Why RDSP Exists
RDSP fills a gap that MDMP cannot cover under time pressure. Where MDMP involves developing multiple courses of action, establishing decision criteria, and running detailed synchronization briefs, RDSP skips most of that. It prioritizes a timely solution over an optimal one. Much of the planning happens mentally rather than in writing, and the staff moves directly to a preferred or directed course of action instead of comparing several options side by side. Army strategist Steve Leonard has described the approach as “skipping straight to the solution and avoiding needless staff work.”
The process relies heavily on leader experience and intuition. It is typically triggered during execution, when something on the battlefield deviates from what the original plan anticipated.
Step 1: Determine That a Decision Is Required
The process begins when leaders or staff members identify what doctrine calls “exceptional information,” any variance from the conditions the original plan assumed. This could be an unexpected enemy action, a change in available resources, a new constraint from higher headquarters, or an emerging opportunity. ATP 5-0.2-1 provides a detailed checklist of variance indicators that help staffs recognize when the current plan may no longer be viable.
This step is largely verbal. The key question is simple: has something changed enough that we need to act? If the answer is no, the unit continues executing the existing order.
Step 2: Compare the Current Situation to the Order
Once the staff recognizes a potential variance, this step confirms how significant it actually is. Leaders compare what is happening on the ground to what the plan expected to happen at this point. The intelligence lead typically generates an updated picture of the enemy situation to support this comparison.
The goal is to determine whether the gap between reality and the plan is large enough to demand a new course of action, or whether minor adjustments to timing or sequencing can keep the original plan on track. In recent warfighter exercises, division staffs frequently encountered competing pressures at this stage: enemy actions pulling them one direction while higher headquarters imposed constraints (such as pausing to allow corps-level operations) that pulled them another.
Step 3: Develop a Course of Action
Unlike MDMP, which generates and compares multiple options, RDSP typically produces a single course of action. The commander or senior leader often directs this COA based on experience, battlefield awareness, and the comparison completed in step two. Staff members then flesh out the details enough to make it executable, focusing on the essential coordination needed to move units, fires, and logistics into alignment with the new plan.
Step 4: Refine and Validate the Course of Action
Before the new plan goes out, the staff pressure-tests it. Validation generally checks whether the course of action is feasible (can we actually do this with the time, troops, and supplies we have?), suitable (does it accomplish the mission or move us toward it?), and acceptable (are the risks and costs proportional to the expected gain?). This step catches mismatches between what the commander envisions and what the current force can realistically execute. Adjustments happen here, not after orders are issued.
Step 5: Implement
The validated course of action is translated into orders and pushed to subordinate units. Because RDSP favors speed, these orders are often fragmentary orders (FRAGOs) rather than full operations orders. The emphasis is on getting clear, concise direction to the units that need it as quickly as possible so execution can begin or resume with minimal delay.
Where RDSP Fits in Army Doctrine
RDSP is not one of the three formal planning methodologies listed in ADP 5-0, The Operations Process, which covers Army Design Methodology, MDMP, and Troop Leading Procedures. Instead, RDSP lives in supplemental publications like ATP 5-0.2-1 and is treated as an execution-focused tool rather than a standalone planning process. It bridges the gap between having a plan and needing to adjust that plan under pressure, which makes it especially relevant in large-scale combat operations where conditions shift faster than a full MDMP cycle can keep up with.
In practice, units that perform RDSP well tend to be those that invested heavily in thorough MDMP during the initial planning phase. A detailed base plan with clearly identified decision points gives the staff a strong reference point for step two, making it far easier to gauge how far reality has drifted and what kind of response is appropriate.