Royal Army College

Lesson Overview

The course has given the officer a way to think (the estimate), a way to direct (intent and main effort), and a philosophy to command by (mission command). This lesson brings them together in the act they all serve: planning. It is about how an officer turns a decision into a plan and a set of orders a command can act on, and how to do so in a way that survives contact with reality rather than shattering at the first surprise.

The title holds the lesson's hardest truth, drawn from the whole Commonwealth tradition: no plan survives contact unchanged. The purpose of planning is therefore not to script the operation but to prepare the command to act well when the script fails. An officer who plans to produce a precise scheme to be executed as written is planning for a world that does not exist; their plan will break and leave them nothing. An officer who understands that the plan will change, and that planning's real products are shared understanding, a sound framework, and a prepared command, builds something that bends and holds.

By the end you will be able to explain why no plan survives contact and what the true purpose of planning therefore is; build a plan that is simple and robust rather than complex and brittle, and say why simplicity is a military virtue; use time well through the warning order and parallel preparation; provide deliberately for friction through reserves, contingencies, and decision points; and issue orders that convey the intent and the essentials clearly, in the standard sequence, confirmed by back-brief.

Key Terms

Plan: the scheme of how a decision is to be carried out, who does what, where, and when; a framework for action built to be adapted, not a script to be followed to the letter.
No plan survives contact: the tradition's summary of the truth that friction and the enemy or the situation will force change on any plan the moment it meets reality; the foundation of how a wise officer plans.
Simplicity: the military virtue of a plan as plain as the task allows, so that it is understood, remembered, and robust under stress; complexity multiplies the ways a plan can fail.
Warning order: the early, preliminary notice of a coming task, issued before the plan is complete, that lets subordinates begin their own preparation in parallel rather than waiting idle.
Parallel preparation: the practice by which subordinate levels prepare at the same time as the commander, fed by warning orders, so the whole command's preparation overlaps instead of running in sequence.
Reserve: a force or means deliberately held uncommitted, so the commander has something in hand to meet the unexpected, exploit success, or restore a situation; the chief practical provision against uncertainty.
Decision point: a point in space, time, or events, identified in advance, at which the commander expects to have to make a particular decision, prepared for so it can be made fast when it arrives.
Orders: the means by which the plan and intent are communicated to those who must act, issued in a standard sequence so nothing essential is omitted and the hearer knows where to find each thing.

Why no plan survives contact, and what planning is really for

The starting truth is blunt: no plan survives contact with reality unchanged. Lesson 01 explained why. The plan is made on a picture that is incomplete and ageing, and it meets a reality full of small difficulties and chance events no foresight can fully anticipate. The route floods, the vehicle fails, the situation is not as assumed, the timing slips. Within the first hour, the careful scheme made on the map is no longer quite the operation actually happening. This is not bad planning. It happens to good plans and bad alike, because a plan is a forecast, and forecasts of a complex, changing situation are always wrong in their details.

The tempting wrong conclusion is that planning is therefore pointless. The opposite is true. Planning is essential, but its purpose is to prepare the command to act well when the plan changes, and it does this by producing three things that survive contact even when the detail does not.

The first is shared understanding: through planning, the whole command grasps the aim, the intent, the main effort, and the shape of the operation, and that understanding guides action when the details fail, as Lesson 04 taught. The second is a sound framework: a good plan gives a sensible starting structure, a sound first move, and a clear allocation of tasks and resources, from which the command adapts far better than it could improvise from nothing. The third is a prepared command: through planning and its warning orders, subordinates ready themselves, their people, and their kit in advance, so they are set to act and adapt when the moment comes.

These three endure; the detailed plan is, in a sense, the by-product. An officer who plans for them plans well; an officer who plans only to produce a precise scheme plans for a world that will not arrive.

Simplicity and robustness: the plan that bends and holds

The qualities to seek in a plan are not precision and cleverness but simplicity and robustness. The inexperienced officer often values the wrong ones, admiring an intricate, finely-timed, clever plan that is in fact brittle. Simplicity is a genuine military virtue, not a confession of limited imagination.

It matters for three reasons, all tracing to the climate of Lesson 01. A simple plan is understood by everyone who must carry it out. Under stress, in noise and fatigue and fear, people execute what they have grasped and remembered; a plan too complicated to hold in the head will be done wrong. A simple plan is robust, because complexity multiplies the points at which a plan can fail: every extra moving part, every fine dependency of one thing on another happening exactly on time, is another thing friction can break. A simple plan adapts, because there is less to unpick when the situation changes; an over-engineered, finely balanced plan is hard to alter without the whole thing collapsing.

So make the plan as simple as the task allows, and in particular avoid fragile dependencies: plans where success requires several things to happen precisely on time and in sequence. Friction will disrupt the timing and bring the sequence down. Robustness is built by simplicity, by slack (time and resources not committed to the last minute and the last soldier, so there is give when things run late), and by the reserves and contingencies of the next section. A plan that is simple, has slack, and keeps something in hand bends and holds. A plan that is intricate, tightly timed, and fully committed shatters at the first surprise. Build the former, and distrust your own attraction to the latter.

Using time: the warning order and parallel preparation

Time is the scarcest resource in most operations, and how a commander uses it is one of the clearest marks of skill. The central technique is to make the command's preparation happen in parallel rather than in sequence, and the instrument is the warning order.

The wrong way is sequential: each level waits for complete orders before it begins anything, so preparation runs in a slow chain. The commander plans in full, then orders subordinates, who only then begin to plan, then order theirs, each level idle until the one above finishes. Against the clock this is ruinous: the lower levels, who need time to ready people and kit, get what little is left after everyone above has used theirs.

The right way is parallel preparation, made possible by the warning order. As soon as the commander knows a task is coming, even before they have a plan, they issue one: a preliminary notice that says, in essence, here is what is coming, here is what I know, begin now. Subordinates start at once on everything that does not depend on the final plan, readying people, checking kit, doing their own preliminary thinking, moving toward likely areas. When the full orders arrive, the command is already half prepared and acts fast.

Behind it lies a sound rule of thumb the tradition teaches: use no more than a third of the available time on your own planning and pass at least two-thirds down, because the lower levels have more to do to get ready. A commander who hogs the time may produce a better plan and lose the operation, because the soldiers who must execute it had no time to prepare. Issue warning orders as a reflex the moment a task appears, and update them as the picture firms.

   USING TIME: SEQUENTIAL vs PARALLEL PREPARATION

   SEQUENTIAL (wrong):
   Cdr plans fully ----> orders down ----> sub plans ----> orders down
   |--------- all the time ---------|  little left -> lower levels idle,
                                        then rushed, unready

   PARALLEL (right):
   Cdr: WARNING ORDER early --> subs prepare NOW, in parallel
        Cdr plans (<= 1/3 of time) ----> full orders
        subs already half-ready -------> act fast
   |-- at least 2/3 of the time passed DOWN for those who execute --|

Providing for friction: reserves, contingencies, and decision points

Since the plan will be disrupted, a wise plan provides for disruption in advance. Three provisions do most of the work: the reserve, contingency planning, and decision points.

The reserve is the chief practical provision against uncertainty, and keeping one is among the oldest disciplines in the profession. A reserve is a force or means deliberately held uncommitted, so the commander has something in hand to meet the unexpected, exploit a sudden opportunity, or restore a situation gone wrong. The temptation is always to commit everything, because every task seems to want more and holding force back feels like waste. Resist it. A commander who has committed every soldier and every vehicle cannot respond when something unforeseen occurs, and in an uncertain situation something always does. The reserve is the commander's freedom of action made physical: with it they can still influence events after the plan has been overtaken; without it they are a spectator to their own operation. Even a single section or a spare vehicle, held back, is worth far more than its size suggests, because it is the difference between being able to act and being able only to watch.

Contingency planning is the second provision. The officer cannot foresee everything and should not try, but the few most likely branches can be thought through in advance: the main route floods, the casualty is found early, the situation worsens on one flank. A little forethought turns a crisis into a prepared response, so the command does not meet it cold.

Decision points are the third. The commander identifies in advance the points, in space, time, or events, at which they expect to have to make a particular decision, so it is anticipated and made fast when its moment arrives. To have decided beforehand "if the water reaches this line by this time, I will shift the main effort east" is to have a decision ready to trigger the instant the moment comes, far better than recognising the need only once it has passed.

Together these do not predict the disruption. They prepare the command to absorb and answer it.

Issuing orders that carry the intent

The plan, once made, must reach those who will act, through orders. The earlier courses taught the orders format in detail, and the Signals and Field Communication course owns it. This lesson's concern is their command quality: that they carry the intent and the essentials clearly, not merely the detail. An order that transmits a mass of instruction but fails to convey what the operation is for has failed at the one thing that matters most, because, as Lesson 04 taught, it is the intent that guides the command when the instructions no longer fit.

Orders are issued in a standard sequence, the familiar five parts running from the situation, through the mission, to the execution, the administrative and logistic support, and command and signals. Its value is that it is standard: nothing essential is omitted, because each thing has its place, and the hearer knows where to find each thing, because it always comes in the same order.

Within that structure, the discipline is to put the intent at the head of the execution and state it plainly, so it is held above the detail, and to express tasks as the mission-command philosophy of Lesson 05 requires: tell subordinates what to achieve, why, and the few limits that bind them, and leave them the how. Orders must be clear, in plain words the youngest soldier will grasp, because an order misunderstood is worse than none. They must be complete in the essentials but not drowned in detail, because an order too long to remember will not be carried out as given. And they must be confirmed by back-brief, the subordinate restating the intent and their task in their own words, which is the only proof the order has landed as meant. The Officer Candidate Foundation Course and Lesson 04 both insisted on this: the intent must be stated, never assumed, and confirmed, because the commonest failure of orders is not that they are wrong but that the commander believed they were understood when they were not.

Good orders are the last step that turns a decision into action. They ensure that all the thinking of the estimate and all the clarity of the intent reach the soldiers who must carry them out.

In Practice: A Plan Built to Bend

An officer of the Royal Kaharagian Army is warned that a wildfire, driven by a rising wind, is threatening a scattered rural settlement. Their platoon must help evacuate residents and protect what can be saved before the fire arrives, in a window no one can predict precisely. The officer plans for a world in which the plan will not survive contact, and it shows in every choice.

Before they have a plan at all, they issue a warning order. The platoon does not wait idle while the officer thinks; the sections ready people and kit, top up water and fuel, and move toward the settlement, so preparation runs in parallel with the planning. The officer holds themselves to a fraction of the time and passes the rest down, knowing the sections need it more.

The plan is deliberately simple: a plain division of the settlement into areas, a clear order of priority (most vulnerable and most exposed first), and one obvious scheme of who goes where, with no fragile dependencies on fine timing, because the wind and the fire will wreck any. They keep slack and a reserve, one section held uncommitted, against the certainty that something will go wrong. They work the likely branches as contingencies: what to do if the wind shifts to threaten a different edge, what to do if a route out is cut. They fix decision points: if the fire crosses a named ridge by a certain time, the evacuation priority shifts and the reserve commits to the newly threatened side. Their orders put the intent first and plainly, get every resident out alive and protect what can be saved without risking a life for property, state tasks as results, and are confirmed by back-brief.

Then contact comes, and the plan does not survive it. The wind shifts earlier and harder than expected. A route out is cut by fire. One area holds more residents than reported. None of it breaks the platoon, because the plan was built to bend. The wind shift hits a prepared decision point, and the reserve commits to the newly threatened side at once, because the decision had been made in advance and only needed triggering. The cut route is met by a section that re-routes on its own initiative, steering by the intent and leaving the how to those who can see the fire in front of them. The under-reported area is covered because the officer had slack and a reserve in hand rather than every soldier committed.

The platoon acts coherently throughout, not because the plan was right, it was wrong in most of its details within the hour, but because the planning had produced what survives contact: a shared understanding of the aim, a simple robust framework, a command prepared by warning orders, and provisions ready for the friction. The residents are out and safe before the fire reaches the settlement. The officer planned not for the operation they hoped to run but for the one they would actually face. That is the difference this lesson teaches.

Check Your Understanding

Explain why no plan survives contact with reality unchanged, and why it does not follow that planning is pointless. What are the three real products of planning that survive contact even when the detailed plan does not, and why does it matter that an officer plans for these rather than to produce a precise script?
Explain why simplicity is a genuine military virtue, giving the three reasons a simple plan is superior under the climate of command. What is a fragile dependency, and why should a plan avoid one? Then explain how robustness is built, through simplicity, slack, and reserves, and contrast the plan that bends and holds with the one that shatters.
Explain the technique of parallel preparation and the role of the warning order, including the rule of thumb about how a commander should divide the available time and why the larger share goes down. Then explain the three provisions a wise plan makes against friction, the reserve, contingency planning, and decision points, and what each contributes. Finally, explain what makes orders carry the intent rather than merely the detail.

Reflection (write a short paragraph): This lesson asks you to distrust your own attraction to the clever, intricate, finely-timed plan and to prefer the simple, robust, slack one. Think about how you plan things in your own life: a project, a journey, an event. Are you drawn to detailed, tightly optimised plans where everything must go right, or to simple ones with room to absorb the unexpected? Be honest, because many capable people are seduced by the elegant plan that is in fact brittle. Then think about the discipline of keeping a reserve, something deliberately held back against the things you cannot foresee. Do you tend to commit everything, or do you keep something in hand? Name which of these two disciplines, preferring simplicity over cleverness, or keeping a reserve rather than committing everything, you would find harder as a commander, say why, and describe one way you could begin practising it now, so that the plans you make one day are built to bend and hold rather than to shatter at the first surprise.

Summary

No plan survives contact unchanged. Planning is not pointless; its purpose is to prepare the command to act well when the plan changes. Its three products survive even when the detail does not: shared understanding, a sound framework to adapt from, and a prepared command.
Seek simplicity and robustness, not precision and cleverness. A simple plan is understood and remembered under stress, is robust because complexity multiplies the points where friction can break it, and adapts easily. Avoid fragile dependencies. Robustness comes from simplicity, slack, and reserves: the plan that bends and holds is simple, slack, and keeps something in hand.
Time is usually the scarcest resource. Use the warning order to make preparation parallel, not sequential. Spend no more than a third of the time on your own planning and pass at least two-thirds down, because the lower levels have more to do. Issue warning orders as a reflex.
A wise plan provides for friction in advance. The reserve, deliberately held uncommitted, is the commander's freedom of action made physical; resist committing everything. Contingency planning outlines a response to the few most likely branches. Decision points are anticipated decisions, identified in advance, so they can be made fast when their trigger is met.
Orders carry the intent and essentials clearly, not merely the detail: intent at the head of the execution, tasks as mission-command tasking (what, why, the few limits, leaving the how), clear, complete in essentials, and confirmed by back-brief. This lesson synthesises the estimate (Lesson 03), the intent and main effort (Lesson 04), and mission command (Lesson 05) into the act of planning, draws the orders format from the Signals and Field Communication course, and leads into commanding the plan in execution (Lesson 07).

Planning Under Uncertainty: the Plan That Survives Contact