What Is DOTMLPF-P?

Last updated: October 20, 2026

Why it matters to your mission. When a force cannot do something it needs to do, the reflex is to field a new system, which is the slowest and most expensive way to close a gap. DOTMLPF-P is the discipline that tests the shortfall against all eight categories first, so a change in doctrine, training, or policy can close it when no new materiel is required. The outcome is faster, defensible requirements decisions grounded in evidence instead of a default to procurement.

Definition

DOTMLPF-P is a U.S. Department of Defense analytical framework of eight categories, Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy, used in the U.S. Department of Defense requirements process (the Joint Capabilities Integration and Development System, JCIDS, which the Department directed be replaced by the Joint Force Requirements Process, JFRP, in 2026) to analyze a capability gap and determine whether it is best closed by a materiel solution or by non-materiel changes. It is pronounced by its letters and was formerly written DOTMLPF before Policy was added.

The framework exists to prevent a predictable failure: treating every capability gap as a reason to acquire new equipment. By checking a gap against all eight categories, analysts surface the non-materiel options, a change to doctrine, a training adjustment, a policy fix, that often resolve the shortfall without a new program of record, or that must accompany a materiel solution for it to work in the field.

Key takeaways

• What it is: an eight-part DoD framework for diagnosing a capability gap and choosing between materiel and non-materiel solutions.
• What the letters mean: Doctrine, Organization, Training, Materiel, Leadership and education, Personnel, Facilities, and Policy.
• Why the "-P": Policy was added to the original DOTMLPF to capture legal, regulatory, and policy barriers that no amount of equipment can fix.
• Where it is used: inside JCIDS, as part of a Capabilities-Based Assessment, to justify why a proposed solution is the right one.
• The point: it disciplines requirements so the Department does not default to buying materiel when a cheaper, faster non-materiel change would close the gap.

What Do the Letters in DOTMLPF-P Stand For?

Each category is a lens on the same gap. A rigorous assessment walks all eight before recommending a solution.

Only one of the eight, Materiel, implies buying something. The other seven are where cheaper, faster solutions usually live, which is the whole reason the framework is structured this way.

Why Does DOTMLPF-P Matter for Capability Development?

A capability gap is the difference between what a force is required to do and what it can actually do today. Left undisciplined, gap analysis tends to jump straight to a materiel answer, because new equipment is tangible and fundable. DOTMLPF-P interrupts that reflex and makes the analysis defensible.

In the requirements process, a Capabilities-Based Assessment identifies gaps and then uses DOTMLPF-P to reason about solutions. The output has to show that the recommended approach was chosen against all eight categories, not assumed. That is what lets the oversight body trust that a materiel recommendation is genuinely necessary rather than a default. For the broader analytic process this sits inside, see AI for capability gap and requirements analysis.

The process itself is changing, but the framework is not. In August 2025 the Department directed that JCIDS be disestablished and replaced by the Joint Force Requirements Process (JFRP); its procedures are documented in the Manual for the Joint Requirements Oversight Council and the Joint Force Requirements Process, CJCSM 5123.01, reissued 15 January 2026. DOTMLPF-P and the capabilities-based assessment carry forward under the new name, and the requirement to address all eight DOTMLPF-P elements together remains a standing principle. DOTMLPF-P is the structured step where a materiel-versus-non-materiel recommendation is built and justified.

What Is the Difference Between DOTMLPF and DOTMLPF-P?

They are the same framework at two points in time. The original construct was DOTMLPF, seven categories without Policy. Policy was added, giving DOTMLPF-P, once it became clear that many capability shortfalls are not equipment, training, or doctrine problems at all but legal, regulatory, or policy barriers that block a force from using a capability it already has. You will still see the older DOTMLPF spelling in legacy documents; current JCIDS practice uses DOTMLPF-P.

DOTMLPF-P vs. Related Terms

The framework is often named alongside the processes it lives inside. Separating them clarifies what DOTMLPF-P actually is.

What Makes a DOTMLPF-P Analysis Rigorous?

A DOTMLPF-P analysis is only as defensible as the discipline behind it. A rigorous one should:

1. Assess all eight categories, not a convenient subset. Walk Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy before recommending anything.
2. Test non-materiel options first. Seven of the eight categories are non-materiel; a materiel recommendation has to earn its place against them, not default to the front.
3. Tie each category to evidence. Every judgment should point to the doctrine, directive, training record, or policy it rests on, so the finding can be inspected.
4. Justify the materiel-versus-non-materiel call explicitly. Show why the chosen lane closes the gap and why the alternatives do not.
5. Check policy and authority barriers directly. Many shortfalls are a Policy problem, a legal or regulatory block on a capability the force already has, that no equipment can fix.
6. Preserve human judgment and traceability. An analyst owns the recommendation, and every element traces back to its source so it can be challenged and defended.

How Does AI Support DOTMLPF-P Analysis?

DOTMLPF-P is a reasoning framework, and the hard part is evidence: assembling, across fragmented data, the picture of what the force can do today, where the shortfall is, and which of the eight levers could close it. That assembly is where AI and data integration help, not by making the judgment, but by giving the analysts a faster, better-sourced basis for it.

Torch.AI's approach keeps the analyst in command and the evidence traceable:

• ORCUS ingests and normalizes the fragmented source data, readiness reporting, force structure, doctrine and policy documents, so the assessment is built on connected rather than siloed inputs.
• NEXUS extracts the entities and relationships from that material, including unstructured policy and doctrine text, so a gap can be tied to the specific authorities, units, and systems involved.
• Torch.AI's reasoning layer maps an identified capability gap against the DOTMLPF-P categories and surfaces candidate non-materiel and materiel options, each traceable back to its source. The analyst owns the finding and the materiel-versus-non-materiel call; the software assembles and cites the evidence, it does not decide.

Consider a unit that cannot share targeting data with a coalition partner. The reflex is to field a new system. With the evidence assembled across categories, a different picture emerges: the capability already exists, but a releasability authority blocks its use (Policy) and operators were never trained on the approved procedure (Training). The gap closes with a policy change and a training task, with no new program of record. Reaching that conclusion meant reading across policy directives, training records, and doctrine that no analyst had time to assemble by hand, which is exactly the assembly the software accelerates while the analyst keeps the call.

The result is a capability-gap analysis that reaches a DOTMLPF-P recommendation faster and shows its work. For the end-to-end analytic process, see AI for capability gap and requirements analysis; related reasoning is covered in AI for course of action (COA) generation and AI for military readiness assessment. To see how this is deployed, explore the Torch.AI software, or contact our team.

What does DOTMLPF-P stand for?

Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy. The final P, Policy, was added to the original DOTMLPF.

Is DOTMLPF-P only about buying equipment?

No. Only one of the eight categories, Materiel, involves acquisition. The framework exists specifically to surface the seven non-materiel ways a capability gap can be closed.

Where is DOTMLPF-P used?

In the DoD requirements process (JCIDS, now transitioning to the Joint Force Requirements Process), primarily during a Capabilities-Based Assessment, to justify why a proposed solution to a capability gap is the right one.

What is the difference between DOTMLPF and DOTMLPF-P?

Same framework; DOTMLPF-P adds Policy to the original seven categories to capture legal and regulatory barriers.