DarkDot (ops)

CONOP

Concept of Operations

A narrative or graphical description of how the commander intends to accomplish the mission, linking the commander's intent to the scheme of maneuver, tasks to subordinate units, and coordinating instructions — typically developed during the MDMP and presented before the OPORD.

The CONOP is the bridge between the commander's vision and executable orders. It answers how the force will move from its current state to mission accomplishment, providing enough detail for subordinates to understand intent and retain initiative if the situation changes.

CONOP vs. OPORD

AspectCONOPOPORD
PurposeDescribe the approach; get approvalDirect execution
AudienceHigher HQ (for approval), subordinate commanders (for parallel planning)All assigned elements
Level of detailConceptual — describes scheme of maneuver, not task-organized detailsFull — all five paragraphs, annexes, and coordinating instructions
TimingIssued early (during MDMP, COA development)Issued before execution
FormatBrief or summary documentFive-paragraph OPORD format

CONOP Components

A complete CONOP addresses:

1. Situation Summary

  • Abbreviated enemy and friendly analysis (condensed METT-TC)
  • Key assumptions that drive the design

2. Mission Statement

  • The restated, approved mission in the 5-W format: Who, What, When, Where, Why
  • Example: "1-6 IN conducts a deliberate attack on OBJ RAVEN NLT 041500L MAY to defeat the 2d BN 7th Guards Regiment and enable brigade exploitation."

3. Commander's Intent

  • Purpose — why the mission is being conducted in the larger context
  • Key tasks — what must be accomplished for the operation to succeed
  • End state — the desired conditions when the mission is complete

4. Concept of the Operation (Core)

  • Scheme of Maneuver — the movement and positioning of units to achieve objectives
  • Scheme of Fires — how fires support maneuver (shaping, suppression, isolation)
  • Decisive Point — where the commander will mass effects to achieve the end state

5. Task Organization

  • Forces assigned, attached, or OPCON for the operation
  • May be expressed as a matrix or narrative

6. Coordinating Instructions

  • Time-phased requirements (SP times, phase lines, PCI windows)
  • Risk mitigation measures, ROE summary

CONOP Briefing Format

CONOPs are briefed to higher HQ for approval before the full OPORD is issued. The brief typically follows:

  1. Situation — enemy COA most likely / most dangerous; friendly forces
  2. Mission — restated mission statement
  3. Commander's Intent — purpose, key tasks, end state
  4. COA Development — criteria applied, courses analyzed, selected COA
  5. Scheme of Maneuver — talk through the graphic overlay step by step
  6. Risk Assessment — probability/severity matrix, mitigation measures
  7. Timeline — backward planning from H-Hour

CONOP Approval Cycle

In time-constrained environments, CONOP approval is the checkpoint that triggers parallel planning by subordinate units. Once the CONOP is approved:

  1. Commander issues a planning guidance or WARNO #2
  2. Subordinate units begin their own MDMP
  3. Staff begins drafting the full OPORD
  4. Rehearsals and coordination begin

The one-third / two-thirds rule applies: the higher HQ consumes no more than one-third of available planning time, leaving two-thirds for subordinate units.

CONOP in Dark Dot

In Dark Dot, a CONOP is represented through the Terrain Plan overlay (scheme of maneuver graphic) combined with Objectives (the decisive tasks) and Teams (the task organization). The operation's name, terrain plan, and objective list collectively communicate the CONOP to any operator viewing the shared scenario.

Command & Controlplanningmdmpcommandmission-command
RELATED TERMS
OPORDFRAGOWARNOMETT-TC