Skip to main content

3. MPC In-Brief / Kick-Off

Intent

The MPC In-Brief / Kickoff is led by the MPCC. It formally convenes the MPC, frames the tactical problem, establishes planning discipline, validates the Plan-to-Plan, and releases LOEs to execute assigned MPTs.

3.1. Pre-MPC Checks (MPCC Only)​

Purpose

Ensure the MPCC has completed mission framing, structured the planning approach, and imposed control mechanisms before convening the MPC.

The MPC does not gather to figure out what to do. It gathers to execute directed planning work.

The MPC will not convene unless the following are complete:

Mission Analysis

  • Mission documentation reviewed in full (Order + Annexes + SPINS)
  • Tasked Mission clearly restated (5 W’s)
  • Essential Tasks identified (Specified + Implied)
  • Limitations extracted (Constraints + Restraints)
  • Acceptable Level of Risk (ALR) reviewed and understood
  • Initial Facts / Assumptions identified
  • Initial FFIRs/RFIs generated and submitted (if required)

Plan-to-Plan Prepared

  • MPOs drafted (planning end states defined)
  • MPTs identified for each MPO
  • Planning LOEs defined
  • Initial MPT-to-LOE assignments completed
  • Initial MPC timeline drafted

Administrative Preparation

  • Mission documentation disseminated to MPC members as pre-read
  • MPC boards / digital collaboration spaces prepared
  • MPO–MPT tracker prepared
  • MPC Timeline visible in planning space
  • Required MPC members identified and confirmed
  • Tentative MPC role assignments identified
MPC Whiteboards

See APPENDIX - MPC Whiteboard Layouts for suggested whiteboard layouts.

3.2. Establish Control and Accountability​

Purpose

Formally assume control of the MPC, confirm required participants, establish the command structure, and ensure the planning environment is set before mission discussion begins.

This step mirrors the Timehack / Roll Call / Security discipline outlined in USCCI 3300-06 and sets the conditions for controlled planning execution.

Ensure Planning Environment Setup

  • Planning timeline displayed
  • MPO–MPT tracker displayed
  • Whiteboard / collaboration space visible
  • Assumptions / RFI tracker visible

Conduct Roll Call

  • Identify the MPCC
  • Identify the DMPCC
  • Identify the LOE leads
  • Identify the Intel support lead
  • Identify Timekeeper
  • Identify Scribe / Artifact manager
  • Identify Supporting SMEs / Mission Partners
  • Confirm required participants are present or delegated

Validate Security / Classification

  • State the facility / system / discussion classification levels
  • Confirm all participants are cleared
  • Confirm handling and storage procedures
MPC Whiteboards

See APPENDIX - MPC Organization for MPC role descriptions.

3.3. Frame the Tactical Problem​

Purpose

Force alignment on the exact tactical problem to be solved before planning begins.

All MPOs, MPTs, and LOEs must directly support solving this problem. If the problem is unclear, the plan will fragment.

Review Mission Analysis

  • Essential Tasks acknowledged and validated
  • Constraints acknowledged
  • Restraints acknowledged
  • High-impact Assumptions highlighted
  • Initial RFIs/FFIRs status reviewed
  • Known information gaps identified
  • Updates and corrections captured and adjudicated

Restate the Tasked Mission

  • Who is tasked
  • What must be accomplished
  • When execution occurs
  • Where (terrain / network / AO)
  • Why (operational objective(s) being enabled)

Review the Tactical Problem

  • Describe the tactical problem in plain language
  • Confirm required end-state condition(s)
  • Identify unacceptable outcomes

Bound the Tactical Problem

  • Restate mission constraints
  • Restate mission restraints
  • Confirm authorities (DIRLAUTH, ATC, risk acceptance, escalation)
  • Identify explicitly out-of-scope activities

Validate Shared Understanding

  • Each LOE lead can restate the tactical problem
  • Each LOE lead confirms how their functional area supports solving it
  • No conflicting interpretations exist
  • No planning effort extends beyond directed scope

3.4. Present the Plan-to-Plan​

Purpose

Communicate the structured planning approach, confirm ownership, and establish how planning progress will be measured.

The MPC executes a directed planning construct - not independent efforts.

Present the Planning Construct

  • MPOs reviewed as planning end states
  • MPTs reviewed by supported MPO
  • Planning LOEs confirmed
  • MPT-to-LOE assignments displayed
  • Integration responsibility identified
  • Primary integrator for cross-LOE efforts identified
  • Initial timeline and battle rhythm reviewed
  • HGI checkpoints and GICL confirmed
  • Updates and corrections captured and adjudicated

Confirm for each LOE

  • Assigned MPTs are understood
  • Expected tangible outputs are defined and understood
  • Completion criteria for supported MPO understood
  • Cross-LOEs dependencies acknowledged
  • Integration requirements and suspense alignment understood

3.5. Release to Execute​

Purpose

Formally declare the planning construct authoritative and transition from alignment to controlled execution.

At this point, structure is locked and planning work begins.

Before concluding the MPC In-Brief/Kick-Off:

  • MPOs/MPTs declared authoritative (changes require MPCC approval)
  • Next HGI time confirmed
  • GICL reaffirmed
  • Open issues assigned owners and suspenses
  • Decision authority and escalation path reaffirmed

The MPCC releases LOEs to execute assigned MPTs under the established planning construct. Deviations require MPCC approval.