Operations Order / OPORD
Task organization: This information may be provided in Paragraph 3 "EXECUTION" or in an Annex, which may be in text or graphical form. Under this heading, as appropriate, give the sub-division of the force, including attached units, command relationships, states of command, together with the names and ranks of the commanders when necessary.
1. Situation. Briefly give the general picture so that subordinate commanders will understand the current situation under the following headings:
a. Enemy Forces. Composition, estimated strengths, identification, disposition, current location, movement anticipated, capabilities, and assessment of intentions. References may be made to other record documents that amplify information included here;
b. Friendly Forces. Information concerning friendly forces other than those covered by the Op O, which should directly affect the action of subordinate commanders. These forces include those not attached or organic to the command of the contemplated operation, but whose presence on a flank or other adjacent area is of interest. Include information on such forces that subordinate commanders need to know in order to accomplish their tasks. This includes the mission of the higher unit, and should include the higher commander's intent and/or concept of the operation, one level up;
c. Attachments and Detachments. Units attached to or detached from the issuing formation/unit, together with the times they are effective may be listed here, in an annex, or both; and
d. Commander's Evaluation. This is an optional subparagraph to be used when directed. It gives briefly the commander's evaluation of the situation.
2. Mission. A clear, concise statement of the task(s) to be accomplished by the commander and its purpose. This paragraph must not be sub-paragraphed.
3. Execution. This paragraph will be laid out to suit the requirements of the particular operation. Summarize the overall course of action intended, or CONOPS. In subsequent paragraphs, assign specific tasks to each element of the task organization charged with the execution of operations required to accomplish the CONOPS or in support of those operations, and give details of coordination and task organization not already given in the task organization section. Instructions applicable to two or more elements of the task organization can be set forth in a final paragraph of this section headed "coordinating instructions.” Intent: Accurately convey to subordinates the commander's intent.
a. Concept of Operations. Describe, in brief, how the commander visualizes the execution of the operation from start to completion. The Commander's Intent is a concise expression of the purpose of the operation, which describes the desired end state. It should be understood two echelons down and helps his subordinates focus on what has to be accomplished in order to achieve success so that mission accomplishment is possible in the time available and in the absence of additional communications or further instructions. This paragraph should set forth the phases of the operation; schemes of manoeuvre for major subordinate task elements that describe precisely what the commander expects to be done; general plans for the employment of supporting fires and weapons, and the general plan for the landing force in amphibious operations;
b. Tasks/Missions to Sub Units. Subsequent subparagraphs assign specific tasks to each element of the command charged with the execution of tactical duties, and give details of coordination and the task organization/groupings if not included under "Task Organization" or in an annex; and
c. Coordinating Instructions. Instructions applicable to two or more elements of the task organization. Typically, such instructions might include boundaries, objectives, beaches, lines of departure, time and direction of attack, and other specifics needed to coordinate the activities of different task elements. Other information is also included, such as reporting instructions, anticipated time of execution and when the order becomes effective for planning and/or execution.
4. Service Support. State administrative and logistics arrangements applicable to the operation. Describe the manner of logistics support for the contemplated operation. At higher command levels this paragraph could state, "See Administrative/ Service Support Order. At lower command levels this paragraph, or the Service Support annex, may eliminate the need for an Administrative/Service Support Order.
a. Support Concept. Include enough information to make clear the basic concept for logistics support. Summarize the overall operation from the Combat Service and Combat Service Support perspectives;
b. Materiel and Services. List materiel and services for supply, maintenance, transportation, and construction, and allocation of labour for logistics purposes;
c. Medical Evacuation and Hospitalization. List plans and policies for hospitalization and evacuation of military and civilian personnel;
d. Personnel. List unit strengths, replacements and personnel policies and procedures, including those pertaining to civilians and enemy prisoners of war;
e. CIMIC. Describe control of civil population, refugees, and other relevant civil affairs matters; and
f. Miscellaneous. In many cases, reference to administrative and logistics policies and procedures in an existing plan as amended by the Op O will suffice.
5. Command and Signals. Include signal, recognition, and identification instructions; electronic policy; HQ locations and movements; code words; code names; and liaison.
a. Command and Control. Give information about pertinent command, control, and communications nets; operating procedures; recognition and identification procedures; electronic emission constraints; etc. A separate annex may be required, or reference to an existing plan may be made; and
b. Command. Op Os must be specific concerning these arrangements, including shifts that may take place as the operation progresses from one phase to the next. Clearly state all command relationships. Include command posts, and alternate command posts with their times of activation and deactivation.