The Key Players in DoD Acquisition: Who Does What

One of the most disorienting things about entering the defense acquisition world, from either the government or contractor side, is the sheer number of organizations and acronyms with authority over your program. The Program Manager (PM) runs the program, but the Contracting Officer (CO) signs the contracts. The COR monitors performance, but only the CO can change the contract. DCMA is watching the contractor every day, but DCAA is doing the accounting audits. CAPE might decide your cost estimate is too low, and that alone can blow up your Milestone B.

This guide maps every major player in the defense acquisition system, explains what authority they hold, who they answer to, and what you need to know about each one as a contractor or government acquisition professional.

This article is part of our series on the DoD acquisition system. For the full overview, see The Complete Guide to DoD Defense Acquisition.

The Program Management Layer

Program Manager (PM)

The Program Manager is the single person accountable for a defense acquisition program's cost, schedule, and performance. The PM is responsible for everything: requirements translation, acquisition strategy, budget defense, contractor management, test planning, and sustainment, across the entire lifecycle from Milestone B to end of life.

For ACAT I programs (Major Defense Acquisition Programs), the PM is a senior military officer (typically colonel/O-6 or general/flag officer) or a Senior Executive Service (SES) civilian. The job is a critical acquisition position under the Defense Acquisition Workforce Improvement Act (DAWIA), with its own training, experience, and certification requirements.

The PM doesn't have unilateral authority to obligate funds or change contract terms. That's the CO's job. But the PM sets the strategic direction, makes trade decisions, and is ultimately accountable to the Milestone Decision Authority and to Congress (via program reviews and budget justifications).

What contractors need to know: Build a strong relationship with the PM's office. The PM and their technical staff define requirements, evaluate performance, and influence source selection criteria. A PM who understands and trusts your company is your most valuable advocate inside the government. Program Managers are generally accessible at industry days and technical exchanges. Take advantage of those touchpoints.

Program Executive Officer (PEO)

The Program Executive Officer (PEO) oversees a portfolio of related programs and is the PM's direct supervisor. PEOs are typically flag officers (general/admiral) or SES civilians at the Senior Executive level. They are often designated as the Milestone Decision Authority for ACAT III programs (and sometimes ACAT II, which the Component Acquisition Executive can delegate) and are themselves accountable to the Service Acquisition Executive.

PEOs exist because individual PMs can't be expected to coordinate across programs that share platforms, subsystems, contractors, or funding. The PEO provides strategic portfolio management: balancing priorities, managing shared resources, and ensuring programs within the portfolio are coherent with each other.

The big change: PEOs are becoming PAEs. Secretary Hegseth's 7 November 2025 memo on the Warfighting Acquisition System moves major programs under Portfolio Acquisition Executives (PAEs) within about two years, and section 1802 of the FY2026 NDAA created the PAE role in law. PAEs report straight to the Service Acquisition Executive and can shift funding and make trade-offs across a portfolio to deliver faster (Holland & Knight summary). PEOs still run programs that haven't transitioned yet.

Examples: the Army's PEO Missiles and Space merged into the new PAE Fires in late 2025, one of six Army PAEs; the Air Force redesignated PEO Fighters and Advanced Aircraft as a PAE in January 2026; and the Navy reached nine PAEs in May 2026.

What contractors need to know: The PEO is the decision authority your PM answers to for significant program decisions. If a contract issue escalates past the program office level, it may land at the PEO. Understanding the PEO's portfolio priorities can help you position your capabilities as solutions to broader needs, not just a single program requirement.

Service Acquisition Executive (SAE)

Each military department has a Service Acquisition Executive (SAE), the senior acquisition official responsible for all acquisition activity within that service:

• Army: Assistant Secretary of the Army for Acquisition, Logistics and Technology (ASA(ALT))
• Navy/Marine Corps: Assistant Secretary of the Navy for Research, Development and Acquisition (ASN(RDA))
• Air Force: Assistant Secretary of the Air Force for Acquisition, Technology and Logistics (SAF/AQ), for non-space programs
• Space Force: Assistant Secretary of the Air Force for Space Acquisition and Integration (SAF/SQ), for space programs (DAFFARS 5302.101)

The SAE is the Milestone Decision Authority for ACAT IB programs (MDAPs where the DAE has delegated MDA authority) and for many ACAT IC programs. SAEs answer to both their service Secretary and to the USD(A&S) for acquisition matters.

What contractors need to know: SAE-level decisions affect entire portfolios and budgets. If your company is seeking to establish a new program or expand your footprint with a service, executive engagement at the SAE level (via industry associations, legislative affairs, or direct engagement at major conferences) is how strategic direction gets set.

Defense Acquisition Executive (DAE)

The Defense Acquisition Executive (DAE) is the Under Secretary of Defense for Acquisition and Sustainment (USD(A&S)), the top acquisition official in the entire Department of Defense. The DAE is the Milestone Decision Authority for ACAT ID programs (the largest MDAPs) and sets enterprise-wide acquisition policy.

The Contracting Layer

Contracting Officer (CO)

The Contracting Officer (CO) is, legally speaking, the most powerful individual in any government contract relationship. The CO is the only government official authorized to:

• Award contracts on behalf of the United States government
• Obligate federal funds
• Make binding decisions regarding contract terms
• Authorize changes to the contract (via formal modifications)

COs hold a Warrant (a formal delegation of authority from their agency) specifying the dollar limits of their contracting authority. A CO without a warrant, or a CO acting outside their warrant limits, cannot legally bind the government. Contractors who receive direction from non-warranted government employees act at their own risk.

Within the CO role, there are functional specializations:

• Procuring Contracting Officer (PCO): Handles pre-award activities: planning, solicitation, negotiation, and award.
• Administrative Contracting Officer (ACO): Takes over post-award contract administration. For large defense contractors, ACOs from DCMA administer contracts at the contractor's facility.
• Terminating Contracting Officer (TCO): Handles contract terminations (for convenience or default).

What contractors need to know: Everything significant goes through the CO. Technical direction from the PM or COR that isn't backed by a contract modification isn't legally binding, and following it without a modification can create a constructive change situation that's expensive to unwind. Maintain a clear line between technical conversations (PM/COR) and contract actions (CO). Never accept direction to perform out-of-scope work without a written mod.

Contracting Officer's Representative (COR)

The COR is the CO's designated technical representative on a contract. The COR is appointed by the CO and has authority only within the limits specified in their designation letter. Typical COR authorities include:

• Reviewing and approving (or rejecting) contractor deliverables
• Monitoring contractor performance and reporting to the CO
• Authorizing contractor access to government facilities
• Providing technical direction within the scope of the contract

The COR cannot authorize additional work, change delivery schedules, waive contract requirements, or obligate funds. Only the CO can do those things.

CORs are certified under DoDI 5000.72 and must complete required training. The joint appointment system (PIEE/JAM) tracks COR designations across the department.

What contractors need to know: The COR is your day-to-day government point of contact on most contracts. This is the person reviewing your deliverables and often providing the input for your Contractor Performance Assessment Reporting System (CPARS) evaluations, which follow your company for years. COR relationships matter enormously. Document all COR technical direction in writing, even informal guidance, to protect yourself from scope disputes.

The Oversight and Independent Assessment Layer

Defense Contract Management Agency (DCMA)

DCMA is the DoD agency responsible for contract administration: the day-to-day oversight of contractor performance after contract award. DCMA reports overseeing more than 300,000 contracts worth more than $11 trillion at more than 18,000 contractor locations (DCMA), and it has personnel embedded at major defense contractor facilities.

DCMA's primary responsibilities include:

• Assuring that contractor supplies and services are delivered on time, at projected cost, and meeting performance requirements
• Reviewing and approving contractor business and management systems (Earned Value Management, property management, purchasing systems)
• Conducting surveillance of contractor facilities and processes
• Performing quality assurance inspections
• Supporting source selection by evaluating contractor past performance and systems

DCMA houses the ACOs (Administrative Contracting Officers) who administer large defense contracts on behalf of the procuring agency.

What contractors need to know: DCMA is a permanent presence in your business if you're a significant DoD contractor. Get your business systems, especially EVMS (Earned Value Management System) and purchasing systems, DCMA-approved before you need them, not after you've won a contract that requires them. A failed DCMA system review can trigger contract payment withholds.

Defense Contract Audit Agency (DCAA)

DCAA is DoD's contract auditor. Unlike DCMA, DCAA doesn't direct contract actions. It conducts audits and provides advisory services to help contracting officers make informed pricing and cost decisions.

DCAA audits include:

• Pre-award surveys: Evaluating whether a contractor's accounting system can accumulate costs in a way that supports a cost-reimbursement contract
• Incurred cost audits: Annual audits of a contractor's claimed costs on cost-reimbursement contracts
• Forward pricing rate reviews: Evaluating the contractor's proposed overhead and G&A rates for use in future proposals
• Defective pricing audits: Investigating whether a contractor's certified cost or pricing data was accurate, current, and complete at the time of contract award

DCAA does not have authority to direct contractors or make contract decisions. Its recommendations go to the CO, who makes the final determination.

What contractors need to know: If you're pursuing any cost-reimbursement contract, the contracting officer must find your accounting system adequate before award (FAR 16.301-3), usually with help from a DCAA pre-award survey. There's no dollar floor. Getting ready can take months, so start early, ideally before you win your first cost-type contract. Small businesses are frequently blindsided by DCAA accounting system requirements after contract award.

Cost Assessment and Program Evaluation (CAPE)

CAPE is the OSD office that provides independent cost estimates and program assessments to DoD leadership. For major defense acquisition programs, CAPE conducts or approves an Independent Cost Estimate (ICE) before each milestone decision (10 U.S.C. 3221), which is provided to the MDA as a check on the program office's cost estimate.

CAPE is famous (or infamous, depending on perspective) for producing cost estimates that are typically higher than program office estimates. That's the point. CAPE is an independent voice designed to counter optimism bias in program office estimates.

CAPE also conducts program assessments that evaluate cost, schedule, and performance, and its findings can lead the MDA to restructure or delay a program that is off track.

What contractors need to know: CAPE's independent cost estimate directly affects whether your program gets Milestone B approval and at what funding level. If CAPE's estimate is significantly higher than the program office estimate, the program may be restructured or delayed. Understanding CAPE's cost estimating methodology, and ensuring your cost proposals are defensible against independent scrutiny, is critical on major programs.

The Requirements Community

Joint Requirements Oversight Council (JROC)

The JROC, chaired by the Vice Chairman of the Joint Chiefs of Staff, used to be the body that validated joint military requirements. Under the Joint Capabilities Integration and Development System (JCIDS), it reviewed and approved Capability Development Documents (CDDs) and Capability Production Documents (CPDs) for the biggest programs, and an unapproved CDD meant no Milestone B.

That changed on 20 August 2025, when Secretary Hegseth and Deputy Secretary Feinberg disestablished JCIDS. Here's who does what now:

• The military services validate their own requirements.
• The JROC identifies and ranks a short list of joint Key Operational Problems instead of validating service documents.
• The Requirements and Resourcing Alignment Board (RRAB), co-chaired by the Vice Chairman and the Deputy Secretary of Defense, lines those problems up with money and recommends how to spend a new Joint Acceleration Reserve.
• The Mission Engineering and Integration Activity (MEIA) runs mission engineering and experiments against the top problems.

What contractors need to know: On newer programs, the requirements you're designing to were validated by the sponsoring service, not the JROC. Older programs still carry JROC-validated ICDs and CDDs, and changing a requirement mid-development still means going back to whoever validates it, which takes time and can disrupt your development program. Knowing who owns your requirement, and how stable it is, helps you manage scope risk. For more, see what replaced JCIDS.

The Congressional Layer

Congress is, ultimately, the most powerful player in defense acquisition. They control the money and write the laws that govern the system. Congress exercises acquisition oversight through multiple mechanisms:

• Authorization: The National Defense Authorization Act (NDAA) is passed annually and authorizes defense programs and spending levels. Congress can add programs, cut programs, add conditions, or restructure acquisition authorities in the NDAA.
• Appropriations: The actual money flows through annual defense appropriations bills. Authorization without appropriation doesn't fund anything.
• Selected Acquisition Reports (SARs): The statutory SAR ended after the FY2023 submission (10 U.S.C. 4351(j)), so ACAT I programs no longer file it. Cost growth triggers mandatory notification (Nunn-McCurdy).
• Hearings: Congressional armed services committees hold regular hearings on acquisition programs; PMs and PEOs regularly testify on program status.
• Government Accountability Office (GAO): Congress's watchdog. GAO reports on acquisition program performance, and its findings carry significant weight.

What contractors need to know: Programs with strong congressional supporters tend to be more stable. Programs without congressional champions are more vulnerable to cuts. Major defense companies invest significantly in government relations, not to corrupt the process, but because congressional awareness and support is a real program stability factor. For smaller companies, working through industry associations that have congressional engagement programs is a viable path.

All Roles at a Glance

Frequently Asked Questions

What is the difference between a PM and a CO in defense acquisition?

The Program Manager (PM) is responsible for the overall success of an acquisition program: cost, schedule, performance, requirements management, and strategic direction. The Contracting Officer (CO) holds the legal authority to bind the U.S. government in contracts. The PM cannot sign contracts or obligate funds; the CO cannot direct the technical work or change requirements. They work together closely, but with distinct and complementary authorities. Every significant program action requires coordination between the two.

What does DCMA actually do on a day-to-day basis?

DCMA's day-to-day work depends on contract type and contractor size, but typically includes reviewing contract deliverables, monitoring contractor cost and schedule performance against Integrated Program Management Data and Analysis Reports (IPMDARs, which replaced the older IPMR) or other Earned Value reports, conducting quality assurance inspections, reviewing and approving contractor business systems (purchasing, property management, EVMS), and preparing Contract Performance Assessment Reports. At large defense contractors, DCMA has dedicated on-site teams that are essentially embedded in the contractor's facility year-round.

Can a COR tell a contractor to do something not in the contract?

No, and contractors should never comply with out-of-scope direction from a COR without getting a contract modification from the CO first. The COR's authority is limited to what's specified in their designation letter from the CO, and they cannot change contract scope, authorize additional work, or waive contractual requirements. Acting on unauthorized COR direction can result in the government refusing to pay for the work (it was out of scope), or creating an unresolved constructive change dispute. Always get it in writing and in the contract.

What is CAPE and why does its cost estimate matter?

CAPE (Cost Assessment and Program Evaluation) is the OSD office that conducts or approves independent cost estimates (ICEs) for major programs before each milestone. CAPE's ICE is provided to the Milestone Decision Authority and frequently differs from the program office's estimate, often coming in higher. If CAPE's estimate reveals a significant affordability problem, it can trigger a program restructure or milestone delay. Congress uses CAPE estimates to evaluate whether the program office is being realistic about costs.

How does Congress affect a specific acquisition program?

Congress affects programs in several ways. Authorization bills (the NDAA) can specifically authorize or restrict programs. Appropriations bills fund them and can add conditions ("fences") requiring specific reports or milestones before funds can be obligated. Congressional language can mandate competition, require OTA use, or impose reporting requirements. For ACAT I programs, cost growth above Nunn-McCurdy thresholds requires formal notification to and certification by the Secretary of Defense. Informally, congressional interest in a program (through member offices or staff conversations) can accelerate or complicate milestone decisions.