(Copy No ….of ……) 
(Issuing HQ and Location) 
(Date) 
(File Ref) 
(See Distr)
OPLAN - (TITLE OF OPLAN)
References: List any maps, charts or other documents essential to an understanding of the basic plan.
TASK ORGANIZATION: AS SHOWN IN APPENDIX 1.
1.	SITUATION. 
a.	General. Describe the general politico-military environment that would establish the probable preconditions for implementation of the plan.
b.	Pre-Conflict Actions. Describe pre-conflict actions desired and prioritise specific units and resources in terms of latest-arrival-date (LAD) relative to G-Day.
c.	Enemy. Identify the opposing forces expected on implementation and evaluate their general capabilities. Details are given in Appendix 2. However, the subparagraph should provide the information essential to a clear understanding of the magnitude of the hostile threat.
d.	Friendly.
(1) Describe the operations of unassigned forces, other than those tasked to support this operation, which could have a direct significant influence on the operations envisaged in this plan.
(2) List the specific tasks of friendly forces, commands, or governmental agencies that would directly support plan execution (e.g. MAS, MISC and etc.).
e. Assumptions. List the necessary assumptions on which the plan is based, i.e. those contingent conditions, the absence of which will have a significant impact on this plan or supporting plans. Assumptions normally state expected conditions over which the commander has no control. Those included must be directly relevant to the development of this plan and supporting plans and should express the conditions that, should they not occur as expected, would invalidate the entire OPLAN or its CONOP. Additional assumptions relevant to specific aspects of the operation are included in the appropriate annexes.
f. Legal Considerations. List those significant legal considerations on which the plan is based. 
2.	MISSION. State concisely the task and purpose to be accomplished on implementation. The mission stated should be that of the appointed commander, it may be the task assigned by the JCC or it may be deduced from the ID based on a task assigned by the JCC.
3.	EXECUTION
a.	CONOP. It is preferable that the entire CONOP be included in the basic plan. However, some OPLAN necessarily encompass alternative COA for accomplishing the mission and others require considerable details to convey adequate guidance for the development of supporting plans. Accordingly, the entire concept may be placed in Appendix 3.
(1)	General. The CONOP is derived from the Step 4 JMAP (Decision) and it is endorsed by the JCC. The appreciation states how the commander intends to accomplish his mission, including the forces involve, the time phasing of operations, the general nature and purpose of operations to be conducted and the inter-related or cross-service support, coordination and execution of the operation. The concept should show how security against enemy actions will be maintained, and superiority and surprise achieved. The CONOP should be sufficiently developed to include an estimate of the level and duration of conflict to provide assigned and supporting commanders a basis for preparing adequate supporting plans. The requirements to maintain secrecy and to use tactical military deception initiatives during the planning and preparatory phases, during movement to objective areas and after operations are over, should be briefly outlined. Detail information is given in Appendix 1 for force requirements.
(2)	Employment. Without encroaching on the authority of assigned and supporting commanders, the concept describes how the forces are to be employed. Plans on conducting supporting operations (e.g. SAR, deception and etc.) is indicated by reference to appropriate appendices of Appendix 3.
(3)	Deployment. The requirements to deploy forces from their normal peacetime locations to the area of operations should also be summarised. Particular attention should be given to anticipatory deployments that may be required in order to implement and to support the plan when directed. Considerations should also be given to deception measures required to provide security, mislead the enemy and achieve surprise.
b.	Tasks. In separate numbered sub-subparagraphs, list the tasks assigned to each element of the assigned, subordinate forces and supporting forces. Each task should be a concise statement of a mission to be performed either in future planning for the operation or on plan implementation.
c.	Coordinating Instructions. List of instructions applicable to the entire forces that are necessary for proper coordination of the operation but are not appropriate, are to be included in a particular annex. Terms pertaining to the timing of execution and deployments should be explained; as should other operational terms that appear in the plan but are not defined in other MAF publications.
d.	Supporting Plans. List any requirements for supporting plans to be prepared by assigned, subordinate and supporting commands or agencies.
4.	SERVICE SUPPORT. 
a.	Concept of Support. The major portion of guidance on Service Support normally is contained in a series of detailed annexes. In order to provide a general understanding of the requirements for logistics support, personnel policies and administrative plans, this subparagraph outline broad guidance as to how such support is to be provided.
b.	Logistics. Appendix 4.
c.	Personnel. Appendix 5.
d.	Civil Affairs. Appendix 6.
5.	COMMAND AND SIGNAL.
a.	Command Relationships. Appendix 7.
b.	Headquarters. List the designations and locations of each major headquarters involved in execution. When headquarters are to be deployed or the OPLAN provides for relocation of headquarters to an alternate command post, indicate the location and time of opening and closing of each headquarters.
c.	Succession to Command. Designate in order of succession the commander responsible for assuming command of the operation in specific applicable circumstances.
d.	Command and Control Systems. Provide a general statement concerning the scope of C2 systems and procedures required to support the operation. Highlight any C2 systems or procedures requiring special emphasis. Refer to Appendix 8 for details.
e.	Execution Checklist. Appendix 9.

(Name) 
(Rank) 
(Joint Force Commander) 

Authentication:

(Name) 
(Rank) 
(Appt) 

Appendixes: (List only those actually used)
1. Task Organization.
2. Intelligence.
3. Operations.
4. Logistics.
5. Personnel.
6. Civil Affairs.
7. Command Relationships.
8. Command and Control Systems.
9. Public Affairs.