Milestone Decision Authority (MDA)
The MDA is the single named official who can move an acquisition program from one phase to the next. AR_70-1 defines it as the “designated individual with overall responsibility for a program,” who “will have the authority to approve entry of an acquisition program into the next phase of the acquisition process and shall be accountable for cost, schedule, and performance reporting to higher authority, including Congressional reporting.”
Who holds it
MDA is delegable downward, and where it sits tells you how much the department cares about the program.
| Level | Official |
|---|---|
| Defense | Defense Acquisition Executive (USD(A&S)) |
| Component | Army Acquisition Executive — the ASAALT principal |
| Portfolio | Program Acquisition Executive or Program Executive Officer |
| Program | A PM of an ACAT IV program with delegated MDA |
In the Army the practical default is that the AAE is MDA and delegates. Per AR 70-1 the AAE is the sole authority for program initiation unless delegated, approves the acquisition pathway for every Army program, and is the authority that must approve any change of pathway.
What the MDA actually signs
The instrument is the Acquisition Decision Memorandum (ADM) — the written record of a milestone or decision review, the conditions attached, and the authority granted. The ADM is what a Type_Classification package attaches to and what a program office cites when it says it has approval to proceed.
Under the Adaptive Acquisition Framework the MDA’s decision points vary by pathway: traditional major capability acquisition still runs Milestones A/B/C and a full-rate production decision, while middle-tier, software, and urgent pathways compress or replace those gates. The pathway choice is itself an AAE decision.
Why it matters
The MDA is the answer to “who can actually say yes.” Requirements sponsors, testers, and users can all block; only the MDA can advance. Two practical rules follow. First, find the MDA before building a capture plan, because an ACAT IV program delegated to a product manager and an ACAT I program held by the AAE are entirely different sales. Second, a milestone approval is not a fielding approval — Materiel_Release is a separate AMC-side authority, and programs clear one and stall on the other routinely.
See Also
US_Army · ASAALT · Defense_Acquisition_System · Program_Manager_vs_Product_Manager_vs_Project_Manager · Type_Classification · Materiel_Release · JCIDS · PPBE_Process