General guidance for the Operational Context includes:

- This section provides an operational context for the capability requirements identified later in the document and explains how the capability requirements contribute to the missions and activities of the joint force.

- This document that you are writing is generally intended to supplant the Initial Capabilities Document (ICD) from the JCIDS process and has many similar requirements.

- As an ICD did, this document should focus on identifying and defining the problem (capability gap) and NOT bias toward any solution (material or otherwise).

- In support of (and as a complement to) what the JFRP Manual states as requirements for this section, consider also addressing the following:

1. Joint and/or Service/Component Task identified as containing a capability gap

2. Concept of Operations (CONOPS) or Concept of Employment (CONEMP)

3. Exportability

4. Timeframe Under Consideration

5. Measurable Operational Outcomes

1. Joint and/or Service/Component Task

- Specify which task under consideration contains a capability gap. Is it a current task or a future (anticipated) task?

- Discuss how the absence of this capability could lead to critical mission failure.

- These elements should have been discussed in the capabilities-based assessment (CBA) or other preceding studies or reports. Summarize here and refer to the report for additional detail.

2. Concept of Operations (CONOPS) or Concept of Employment (CONEMP)

- Describe how a solution—identified later—would be employed within the execution of the above-described task.

- You can also begin to proscribe required attributes in general terms. For example, you might assert that the solution must provide desired effect “X” within proscribed time “Y” at range “Z” to close the identified gap.

3. Exportability:

- The general idea is to “bake in” exportability considerations for any potential material solution up front, using this document.

- Considerations:

- Each administration usually adjusts the conventional arms transfer policy; however, in representing the warfighter, you should consider which technologies should be shared with allied and partner nations and which should only be used by the US military. The general goals of the United States government are: 1. to support our allies and partners; 2. to prevent our enemies from getting US defense technology; and, 3. to support U.S. defense industry. These factors should form the basis of decisions upon which weapon system exportability is based.

- Did the CBA (or other study or report) consider allied/partner interoperability and coalition use of any current systems or of any of the identified capability requirements? If so, highlight in this section of your document.

- NOTE. As of January 2026 (subject to change), DoDI 5000.85 requires that PMs integrate international acquisition and exportability planning into the program’s acquisition strategy beginning at the entry milestone. PMs must design the system for exportability to foreign partners, except when the program has an MDA-approved waiver allowing for a U.S.-only design.

4. Timeframe (for Initial Operational Capability (IOC) & Full Operational Capability (FOC)):

- Provide estimates for IOC and FOC based on input from the warfighter (Combatant Commands) and the acquisition community. (Note: this information may not be available until you have socialized the document draft).

5. Measurable Operational Outcomes:

- What outcomes are required?

- What effects must be produced to achieve them?

- How do the outcomes complement the integrated joint/multinational force?

- What enabling capabilities are required?