ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...
ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...
ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 5<br />
addresses the factors of METT-TC. The order <strong>and</strong> detail in which leaders analyze the factors of METT-TC<br />
is flexible. It depends on the amount of information available <strong>and</strong> the relative importance of each factor.<br />
For example, leaders may concentrate on the mission, enemy, <strong>and</strong> terrain, leaving weather <strong>and</strong> civil<br />
considerations until they receive more detailed information.<br />
5-13. Often, leaders do not receive their final unit mission until the WARNO is disseminated after COA<br />
approval or after the OPORD. Effective leaders do not wait until their higher headquarters completes<br />
planning to begin their planning. Using all information available, leaders develop their unit mission as<br />
completely as they can. They focus on the mission, comm<strong>and</strong>er’s intent, <strong>and</strong> concept of operations of their<br />
higher <strong>and</strong> next higher headquarters. They pick major tasks their unit will probably be assigned <strong>and</strong><br />
develop a mission statement based on information they have received. At this stage, the mission may be<br />
incomplete. For example, an initial mission statement could be, “First platoon conducts an ambush in the<br />
next 24 hours.” While not complete, this information allows subordinates to start preparations. Leaders<br />
complete a formal mission statement during TLP step 3 (make a tentative plan) <strong>and</strong> step 6 (complete the<br />
plan).<br />
5-14. Based on what they know, leaders estimate the time available to plan <strong>and</strong> prepare for the mission.<br />
They begin by identifying the times they must complete major planning <strong>and</strong> preparation events, including<br />
rehearsals. Reverse planning helps them do this. Leaders identify critical times specified by higher<br />
headquarters <strong>and</strong> work back from them, estimating how much time each event will consume. Critical times<br />
might include times to load aircraft, the line of departure, or the start point for movement.<br />
5-15. Leaders ensure that all subordinate echelons have sufficient time for their own planning <strong>and</strong><br />
preparation needs. Generally, leaders at all levels use no more than one-third of the available time for<br />
planning <strong>and</strong> issuing the OPORD. Leaders allocate the remaining two-thirds of it to subordinates.<br />
Figure 5-3 illustrates a time schedule for an infantry company. The company adjusts the tentative schedule<br />
as necessary.<br />
0600 – Execute mission.<br />
0530 – Finalize or adjust the plan based on leader’s reconnaissance.<br />
0400 – Establish the objective rallying point; begin leader reconnaissance.<br />
0200 – Begin movement.<br />
2100 – Conduct platoon inspections.<br />
1900 – Conduct rehearsals.<br />
1800 – Eat meals.<br />
1745 – Hold backbriefs (squad leaders to platoon leaders).<br />
1630 – Issue platoon OPORDs.<br />
1500 – Hold backbriefs (platoon leaders to company comm<strong>and</strong>er).<br />
1330 – Issue company OPORD.<br />
1045 – Conduct reconnaissance.<br />
1030 – Update company WARNO.<br />
1000 – Receive battalion OPORD.<br />
0900 – Receive battalion WARNO; issue company WARNO.<br />
STEP 2 – ISSUE A WARNING ORDER<br />
Figure 5-3. Sample schedule<br />
5-16. As soon as leaders finish their initial assessment of the situation <strong>and</strong> available time, they issue a<br />
WARNO. Leaders do not wait for more information. They issue the best WARNO possible with the<br />
information at h<strong>and</strong> <strong>and</strong> update it as needed with additional WARNOs.<br />
5-4 <strong>ATTP</strong> 5-<strong>0.1</strong> 14 September 2011