HomeGlossaryKey Decision Point (KDP)
Systems EngineeringKDP

Key Decision Point (KDP)

A Key Decision Point (KDP) is a DoD acquisition milestone at which the Milestone Decision Authority makes a formal go/no-go decision on whether a program should proceed to the next phase of development.

Quick answer

A Key Decision Point (KDP) is a DoD acquisition milestone at which the Milestone Decision Authority makes a formal go/no-go decision on whether a program should proceed to the next phase of development.


A Key Decision Point (KDP) is a formal decision milestone in the DoD acquisition process at which the Milestone Decision Authority (MDA) reviews a program's status and readiness to determine whether it should proceed, be restructured, or be terminated, analogous to the Milestone A, B, and C reviews in the traditional defense acquisition system.

What is a Key Decision Point?

KDPs are used primarily within the Space Acquisition policy framework (DoDI 5000.02T and DODI 5000.87) and certain rapid acquisition pathways where the traditional Milestone terminology is replaced with KDP terminology. KDP A corresponds to a decision to enter technology development (similar to Milestone A). KDP B authorizes entry into the system development phase (similar to Milestone B). KDP C authorizes production and deployment (similar to Milestone C).

The KDP concept also appears in commercial technology transition pathways and Middle Tier Acquisition (MTA) programs under Section 804 authority, where programs can move faster than the traditional acquisition process. In MTA programs, KDPs serve as the decision gates that ensure leadership has visibility and decision authority even as the program moves on an accelerated timeline.

For contractors working on space systems or MTA programs, understanding KDP criteria and entry requirements is as important as understanding traditional milestone requirements on conventional MDAP programs. The technical and programmatic evidence required at each KDP mirrors what is required at traditional milestones, though the accelerated timeline may compress preparation time significantly.

Why KDPs matter for government contractors

Contract awards, option exercises, and significant funding releases are typically tied to successful KDP completion. A KDP delay means a delay in the associated contract action or funding release. Contractors on space programs and rapid acquisition pathways must plan for KDP preparation as carefully as for traditional milestone reviews.

Example

A commercial satellite imagery company competes for and wins a National Reconnaissance Office contract using a Middle Tier Acquisition pathway. KDP B is required before the development phase begins. The company prepares and presents a Technology Readiness Assessment showing all critical technologies at TRL 7, a program schedule demonstrating delivery within the two-year MTA statutory period, and a cost estimate supporting the negotiated price. The NRO MDA approves KDP B and the development phase begins.

Frequently Asked Questions

How does a KDP differ from a Milestone in the traditional defense acquisition system?


KDPs and Milestones serve the same decision function, authorizing phase transitions, but are used in different acquisition frameworks. Milestones (A, B, C) are the traditional DoD acquisition nomenclature under DoDI 5000.02. KDPs are used in space acquisition (under DODI 5000.87) and some rapid acquisition frameworks. The substance of the review and the decision authority are similar regardless of terminology.

What is Middle Tier Acquisition (MTA) and how does it use KDPs?


MTA (Section 804 of the FY2016 NDAA) authorizes DoD programs to pursue rapid prototyping or rapid fielding on two-year timelines without following the traditional milestone acquisition process. MTA programs use KDPs to maintain MDA oversight while avoiding the documentation and timeline requirements of traditional acquisition. KDPs in MTA programs are typically less formal and more streamlined than traditional milestone reviews.

Who is the MDA for a KDP decision?


The KDP decision authority depends on the program's acquisition category and the specific acquisition framework. For space ACAT I programs under DODI 5000.87, the USD(R&E) or the appropriate service acquisition executive may serve as MDA. For MTA programs, the MDA is typically at the service acquisition executive or program executive officer level.

Are there KDPs on civilian agency programs?


The KDP terminology is primarily DoD/space-specific. Civilian agencies use equivalent decision gates with different names, OMB's Stage Gate reviews for IT investments, Agency Investment Review Boards, and milestone approvals for major systems. The concept of formal leadership go/no-go decisions at phase transitions is universal even if the terminology differs.

How Bidovate helps

Bidovate puts Key Decision Point (KDP) to work inside your capture and proposal workflow.

Federal contracting

See Bidovate in action

Book a demo and we will show you the platform using your actual contract data.