Middle Tier of Acquisition (MTA)

AAF  >  MTA Rapid Prototyping Path  >  Reporting & Governance

Reporting & Governance

How To Use This Site

Each page in this pathway presents a wealth of curated knowledge from acquisition policies, guides, templates, training, reports, websites, case studies, and other resources. It also provides a framework for functional experts and practitioners across DoD to contribute to the collective knowledge base. This site aggregates official DoD policies, guides, references, and more.

DoD and Service policy is indicated by a BLUE vertical line.

Directly quoted material is preceeded with a link to the Reference Source.

Check out the MTA FAQs and MTA Tips for potentially related questions from the field and helpful tips!


MTA program documentation will be updated continuously throughout program execution.

In addition, there are three main timelines when the MTA Program data and documentation must be submitted to OSD(A&S) for governance:

Twice a year

Reference Source: DODI 5000.80, Paragraph 4.1.e


CAEs will submit updated PID via DAVE interfaces [Note: CAC required for access] with the President’s Budget and Program Objective Memorandum submissions to OSD.


Reference Source: DODI 5000.80, Paragraph 4.1.b


For any MTA program expected to require an eventual total expenditure that exceeds the threshold defined pursuant to Section 2302d of Title 10, U.S.C., CAEs will ensure documentation in [the summary table on MTA Program Entrance & Initiation page] is available via DAVE at the time of the President’s budget submission. Full funding plans for the MTA program (to include year of execution), will be reflected in the documentation, consistent with the cost estimate.

Within 2 Years

Reference Source: DODI 5000.80, Paragraph 4.1.a


Rapid prototyping acquisition strategies will include security, schedule and technical risks; a test strategy or an assessment of test results; and a transition plan that includes a timeline for completion within 2 years of all necessary documentation required for transition, as determined by the DA, after MTA program start.

After Program Completion

Reference Source: DODI 5000.80, Paragraph 4.3


No later than 60 calendar days after the MTA program completion date, CAEs will submit the following documentation via DAVE interfaces [Note: CAC required for access]:

    1. Outcome determination ADM signed by the DA.
    2. An assessment of test results.
    3. Final PID capturing updated entries, to include the outcome, sustainment, and final budget of the MTA program.

MTA Test Reporting

Reference Source: DoDI 5000.89, Section 4.3.e


The OTA is responsible for producing an independent ops demo report that identifies the system’s operational capabilities and limitations.


The ops demo report will be delivered to the decision authority to support the initial production decision: before a rapid prototyping program transitions to a follow-on program.


The DOT&E will provide independent OT&E and LFT&E reports to the Office of the Secretary of Defense, Joint Staff, Military Services, and congressional defense committees as required.


Reference Source: DODI 5000.80, Paragraph 4.2


The USD(A&S) will chair an advisory board comprised of the CAEs, the VCJCS, the USD(R&E), the Director of Cost Assessment and Program Evaluation, the DOT&E, the USD(C)/CFO, and others as requested by the USD(A&S), to assess the use of the MTA authority when a request is made by a CAE for a program that exceeds the major defense acquisition program threshold to use the MTA pathway, as provided in Paragraph 4.1.c. In the event of a USD(A&S) decision that any program is not appropriate for the MTA pathway, the USD(A&S) will direct the program to use an alternate acquisition pathway.


See the MTA Responsibilities page for more information on governing responsibilities by role.

MTA Reporting Process to OUSD(A&S). MDAPs must submit documentation at President's Budget submission (Feb); submit PID 2x/year (at President's Budget and POM submissions to OSD); Yes, required for OSD Staff role; Yes, required for Advisory board; and Yes, requires written decision by DAE. Major systems must submit documentation at President's Budget submission (Feb); submit PID 2x/year (at President's Budget and POM submissions to OSD); Not required for OSD Staff role; No, not required for Advisory board; and No, does not require written decision by DAE. Non-major systems must submit documentation 10 workdays before desired obligation of funds to performing activity (ADM only); submit PID 2x/year (at President's Budget and POM submissions to OSD); Not required for OSD Staff role; No, not required for Advisory board; and No, does not require written decision by DAE.

DoD Component Guidance

Note that DoD Component MTA Implementation policies and guidance are currently being updated to be consistent with the newly published DODI 5000.80 (effective 30 Dec 2019). 

Air Force


Reference Source: Air Force Guidance Memorandum for Rapid Acquisition Activities, 27 June 2019


8. Reporting. The PM should provide adequate information to support Air Force evaluation of cost, schedule, and performance and to support MDA, Office of the Secretary of Defense, and Congressional reporting where required.


8.1. All rapid acquisition activities using investment funding shall be included on the Investment Master List (IML) unless waived by the SAE.

8.1.1. ACAT II and III-level rapid acquisition activities will be exempt from the Acquisition Master List (AML) and are required to complete quarterly, vice monthly, Monthly Acquisition Reports (MARs) unless waived by the SAE.

8.1.2. ACAT I-level rapid acquisition activities will be included on the AML and must complete monthly MARs that may be tailored to the reporting needs of the program unless waived by the SAE.


8.2. For rapid acquisition activities, the PM will ensure the following data is collected in Comprehensive Cost and Requirement System/Program Management Resource Tools (T-0):

8.2.1. Name of effort,

8.2.2. Capability gap or problem being addressed,

8.2.3. Qualifications as a rapid acquisition activity,

8.2.4. Schedule acceleration over a traditional acquisition approach,

8.2.5. Budget, funding source, and date funds were approved,

8.2.6. Completion data and criteria,

8.2.7. Current status,

8.2.8. Contracting approach and time to award.


8.3. The PM shall provide a brief (e.g., 1- to 2- page) tri-yearly report summarizing status of progress towards cost, schedule, and performance objectives; progress toward design goals; and likelihood of crossing guardrail thresholds in future.

8.3.1. The summary will be reviewed by the next highest MDA in the reporting chain (i.e., the PEO or SAE) for accountability as well as evaluation and application of best rapid acquisition practices across the Air Force. The SAE will provide his/her updates to Congress.

8.3.2. To ensure consistent and transparent reporting, summaries for rapid acquisition activities meeting the criteria of a MDAP will contain information similar to a Selected Acquisition Report (SAR) and will be submitted to Congress. Submittal of the summary report does not indicate the program is an MDAP, nor require entry or tracking in the SAR database.


8.4. Capabilities and Limitations Reports may be appropriate for prototypes provided to units for training or deployed directly to operational units. These reports have no prescribed format. Reference AFI 99-103, Capabilities-Based Test and Evaluation, for more information.


Prototyping Analysis Report

Reference Source: A5R Requirements Guidebook Vol 5: MTA Requirements Validation Process, 4 Dec 2019

For Rapid Prototyping MTA efforts, once the prototyping effort is complete, the sponsor in coordination with the program office, submits a summary report of the prototyping findings to AF/A5R, AF/A5A and SAF/AQX and attaches it to the original document record in IRSS. The report should contain the following information:

  • Summary of original prototyping phase goals/objectives.
  • Summary of prototyping findings, including assessment of the ability to address the validated gaps and any findings not directly related to original gap(s).
  • Schedule summary (did the original schedule hold true?).
  • Prototyping funding summary.
  • Earned Value Management analysis.

CDWG and/or CDC review the report and, in coordination with AF/A5R and SAF/AQX, make an assessment for continuation of capability development efforts consistent with the Capability Development Strategy.


Reference Source: ASA(ALT) Middle Tier of Acquisition Policy, 20 March 2020, Enclosure 2
[Note: CAC required for access]


In addition to any other Decision Authority (DA)-directed status reports, the PM will provide the Army Acquisition Executive with an executive-level assessment of the program’s status with respect to cost, schedule, and performance objectives annually and submit updated Program Identification Data twice annually with the President’s Budget and Program Objective Memorandum submissions to the Office of the Secretary of Defense.




Reference Source: USSOCOM Middle Tier Acquisition Authorities and Guidance, 1 Aug 2018

Reporting Requirements: All MTA’ s must provide the following as defined by USD(A&S)’s guidance for MTA implementation:

    1. Name of the Program
    2. Capability Gap or Problem
    3. Definitive Source for the Capability Gap or Problem
    4. Capability Characteristic or Solution
    5. Date Funds Approved for Initiation
    6. Funding Source
    7. Program Result (Transition or Termination)
    8. Date of Transition or Termination
    9. Reason for Transition or Termination
    10. Program Budget
    11. Vendor Name

Items 1-6 should form the basis for requirements validation. Items 7-11 follow program initiation. This data will be shared across the Department via an open and collaborative Department-managed tool and internally via the SOF AT&L Acquisition Management System.