Skip to main content

APPENDIX - MPC Organization

Intent

This appendix defines the organization, roles, and relationships of the Mission Planning Cell (MPC).

The MPC is organized to support disciplined, parallel planning while preserving clear authority, ownership, and convergence toward an executable Tactical Mission Plan (TMP).

1 - Organizational Purpose​

The MPC is organized to:

  • Translate mission tasking into executable planning outputs
  • Manage complexity through deliberate role assignment
  • Enable parallel planning across functional areas
  • Ensure planning effort converges on decisions and products

The MPC is not organized to:

  • Mirror execution force structure
  • Provide equal representation to all disciplines
  • Serve as a forum for unfocused analysis
note

MPC organization exists to serve planning effectiveness, not inclusivity.

2 - MPC Roles​

The MPC is composed of personnel selected to enable disciplined, parallel planning while maintaining clear ownership and integration.

MPC composition is mission-driven, not fixed. Roles are assigned based on planning requirements, not organizational charts.

2.1 - MPC Chief (MPCC)​

The MPCC:

  • Exercises authority over all MPC planning activity
  • Establishes planning intent and priorities
  • Organizes MPC Lines of Efforts (LOEs)
  • Assigns Mission Planning Objectives (MPOs) and Tasks (MPTs)
  • Adjudicates conflicts and makes planning decisions
  • Represents the MPC to the Mission Commander (MC)

2.2 - Deputy MPC Chief (DMPCC)​

The DMPCC:

  • Has delegated MPCC authority in their absence
  • Executes MPCC intent day-to-day
  • Enforces the MPC battle rhythm
  • Tracks MPO/MPT progress
  • Manages integration and version control
  • Prepares decision inputs for MPCC and MC

2.3 - MPC Line of Effort (LOE) Leads​

MPC LOE Leads are responsible for executing assigned Mission Planning Tasks (MPTs) and producing defined planning outputs within their LOE.

MPC LOE Leads:

  • Execute MPTs assigned by the MPCC
  • Organize and direct LOE working sessions
  • Coordinate laterally with other MPC LOEs on shared MPTs
  • Ensure LOE outputs meet quality and timeline requirements
  • Identify dependencies, constraints, and risks early
  • Elevate blockers and conflicts to the DMPCC or MPCC
  • Support integration by delivering coherent, review-ready outputs

2.4 - Scribes​

Scribes are responsible for maintaining the accuracy, consistency, and traceability of MPC planning artifacts.

Scribes:

  • Maintain authoritative planning artifacts (e.g., TMP, workbooks, trackers)
  • Update MPO/MPT trackers and status boards
  • Capture decisions, taskings, and suspenses during MPC events
  • Maintain decision, assumption, and risk logs
  • Enforce version control and change tracking
  • Ensure planning products reflect current MPCC direction

2.5 - Intel Support​

Intel Support provides threat, adversary, and contextual inputs that directly inform mission planning and execution focus.

Intel Support:

  • Provide mission-relevant threat reporting and assessments
  • Apply adversary objectives and behaviors to mission-relevant terrain
  • Support development of hunt drivers and prioritization
  • Validate and update threat assumptions as planning progresses
  • Coordinate with external intelligence entities as required
  • Ensure intelligence inputs are actionable and decision-relevant

2.6 - Subject Matter Experts (SMEs)​

Subject Matter Experts (SMEs) provide focused technical or operational expertise in support of specific planning requirements or MPTs.

SMEs:

  • Provide domain-specific expertise to support assigned planning tasks
  • Advise LOE Leads and the MPCC on feasibility, risk, and constraints
  • Validate assumptions within their area of expertise
  • Identify technical limitations or dependencies impacting execution
  • Support integration by identifying inconsistencies or blind spots

SMEs support planning but do not own MPOs, MPTs, or planning decisions.

3 - MPC LOEs​

3.1 - Purpose of Planning LOEs​

Planning Lines of Effort (LOEs):

  • Structure MPC work
  • Organize planning focus areas
  • Generate planning outputs (TOs, TTs, assessments (MOPs), Contingencies)

Planning LOEs are:

  • Directed through MPOs and MPTs
  • Scoped by MPCC intent
  • Accountable for defined outputs

3.2 - Execution LOEs vs Planning LOEs​

Planning LOEs:

  • Exist only within the MPC
  • Structure planning effort
  • produce inputs to the TMP

Execution LOEs:

  • Organize TTs for execution
  • Are defined later during execution integration
  • May cut across multiple planning LOEs
note

Planning LOEs organize thinking.
Execution LOEs organize action.

3.3 - Typical Planning LOEs​

Depending on mission scope, planning LOEs may include:

  • Functional Mission Analysis (FMA-C)
  • CVA/H Deployment Planning
  • Data Collection Planning
  • Threat Intelligence
  • Hunt Planning & Maneuver
note

LOE titles and count are mission-dependent. Scope control is enforced through MPOs/MPTs, not LOE naming.

4 - "Right" Looks Like​

A well-organized MPC:

  • Has clear authority and ownership
  • Enables parallel planning without duplication
  • Integrates outputs continuously
  • Converges on decisions and products

A poorly organized MPC:

  • Blurs authority
  • Allows LOEs to self-direct
  • Duplicates effort
  • Defers decisions until execution
warning

Organizational ambiguity becomes execution risk.