A primary-source reading guide: how to tell GAO testimony from a full audit, why recommendation-tracking matters more than headlines, and how to avoid conflating requested and appropriated budget figures.
When media outlets report on major acquisition programs, the coverage typically focuses on simple headlines: a program is declared "late and over budget," or a fleet expansion effort is described as failing to meet its targets. For project managers, defense contractors, and acquisition professionals, these high-level summaries are insufficient. Skimming executive summaries or news digests strips away the precise risk indicators, baseline variances, and structural constraints necessary to evaluate a program's performance.
The Government Accountability Office (GAO) serves as a primary oversight body for federal defense expenditures. However, reading a GAO release effectively requires an understanding of how the agency structures its work, how its findings are bounded, and where to find actionable data. Extracting real intelligence from GAO material requires moving past headline metrics and evaluating document formats, scope boundaries, implementation metrics, and funding dynamics. Using real findings from GAO and Congressional Budget Office (CBO) reviews of Navy shipbuilding, project managers can learn how to read these primary sources as analytical tools rather than passive status reports.
Decoding GAO Formats: Testimony vs. Full Audit Reports
The first step in evaluating any GAO publication is identifying the document type and understanding its underlying methodology. GAO reports are assigned unique document numbers (such as GAO-25-108136 or GAO-26-109068) that signal their placement in the agency's publication history. Beyond the tracking number, project managers must distinguish between congressional testimony and full audit reports.
On March 11, 2025, GAO released GAO-25-108136, titled Navy Shipbuilding: A Generational Imperative for Systemic Change. This document was written testimony presented by Shelby S. Oakley, GAO's Director of Contracting and National Security Acquisitions, before the House Armed Services Committee's Subcommittee on Seapower and Projection Forces. Testimony documents serve a specific purpose: they synthesize and summarize a broad body of prior audit work to inform congressional hearings. They do not present new primary fieldwork. Instead, testimony pulls together established findings to provide lawmakers with a high-level operational picture. In GAO-25-108136, the core message synthesized years of prior findings: despite the Navy's shipbuilding budget nearly doubling over two decades, the fleet has not grown, and new ships have consistently been delivered late, cost more, and delivered less capability than promised.
In contrast, GAO-26-109068, published on April 22, 2026, under the title Navy and Coast Guard Shipbuilding: A Disciplined, Strategy-Driven Approach Is Needed to Achieve Ambitious Goals, is a full audit report. A full audit report presents primary fieldwork, detailed scope descriptions, and direct investigation. When a project manager reads a full audit report like GAO-26-109068, they are examining original evidentiary findings. For example, this report revealed that Navy officials could not quantify the full funding needed to expand the submarine industrial base to meet the Navy's submarine construction-rate goals. Furthermore, it demonstrated that the Navy's industrial-base investment strategy has generally focused on the Department of Defense's 5-year budget cycles rather than a genuine long-term approach.
Distinguishing between these two formats prevents misinterpreting the source of the data:
- Congressional Testimony: Synthesizes past audit reports for oversight hearings. Use testimony to identify high-level trends, cross-program systemic risks, and congressional areas of focus, but do not look to testimony for original methodological sampling.
- Full Audit Reports: Deliver primary research, direct interview results, quantitative gap analyses, and formal agency responses. Use audit reports to extract specific baseline assumptions, process failures, and root causes.
Distinguishing Program-Specific Audits from Fleet-Wide Syntheses
Acquisition management requires matching the level of analysis to the correct operational context. Conflating fleet-wide structural evaluations with single-program performance audits leads to inaccurate risk assessments. A systemic issue affecting an entire enterprise does not impact every contract baseline in the same way, nor can a single program's variance explain cross-fleet challenges.
Fleet-wide summaries, such as the testimony in GAO-25-108136, outline macroeconomic and institutional friction: such as broad industrial capacity constraints, enterprise-level governance failures, and fleet-wide procurement delays. These reviews are vital for understanding the operational environment, but they cannot replace single-program baseline tracking.
To analyze program-level performance, a project manager must look to program-specific audits. A clear example is GAO-24-107732, which focuses specifically on the Columbia-class ballistic missile submarine (SSBN-826). In this program-level report, GAO documents concrete variance metrics: the lead boat's construction cost has risen to roughly $8.6 billion, with delivery projected 12 to 16 months late against the original contract date. This specific baseline cost and schedule growth provides target metrics that a contract manager or risk analyst can track directly against earned value management (EVM) data and contract milestones.
When conducting primary-source analysis, project managers should observe key analytical boundaries between report types:
- Scope Boundaries: Enterprise reports address portfolio management, legislative authority issues, and fleet composition. Program reports evaluate specific contract execution, vendor performance, technical maturity, and baseline adherence.
- Variance Root Causes: Enterprise delays may stem from budget instability or industrial base capacity. Single-program delays, such as the 12-to-16-month delay on SSBN-826, highlight specific technical, component-supply, or execution challenges on a specific baseline.
- Actionable Remediation: Enterprise reports recommend policy shifts and structural realignments. Program reports recommend direct changes to acquisition strategies, testing schedules, and contract incentives.
Measuring Progress: Recommendations Made vs. Recommendations Closed
The narrative sections of a GAO report describe historical problems and current challenges. However, narrative descriptions reflect where a program has been, not necessarily where it is going. To assess an agency's trajectory and willingness to institutionalize change, project managers must look at the quantitative relationship between recommendations made and recommendations closed.
When GAO completes an audit, it issues formal recommendations designed to correct identified vulnerabilities. How an agency handles these recommendations serves as a leading indicator of project management maturity and governance effectiveness. A high volume of open, unaddressed recommendations indicates that known operational and administrative risks remain active across the program baseline.
The testimony in GAO-25-108136 provides a stark primary-source baseline for this metric:
- Total Recommendations Issued: GAO had made 90 total recommendations to the Navy regarding shipbuilding practices over the evaluated period.
- Fully Addressed Recommendations: As of that testimony, the Navy had fully addressed only 23 of those recommendations.
- Open/Unaddressed Recommendations: 52 recommendations remained open and unaddressed.
For a project manager, these numbers reveal far more than executive statements promising reform. When less than a third of official oversight recommendations have been implemented (23 closed out of 90 made, with 52 remaining open), it indicates that the structural conditions causing cost growth and schedule slipping remain unmitigated. When evaluating defense programs, risk managers should treat a high volume of open GAO recommendations as an active risk multiplier that directly affects contract delivery schedules and cost baselines.
Budgetary Literacy: Requested vs. Appropriated Funding Figures
Financial analysis in defense project management requires absolute clarity regarding budget terminology. Non-specialists and news summaries frequently conflate requested or planned funding figures with actually appropriated funds. In defense acquisition, a plan is an expression of intent; an appropriation is an authorization to spend cash. Treating planned budgets as confirmed operational funding creates flawed risk models.
This distinction is illustrated by comparing strategic budget requests against actual historical appropriations, as documented in CBO report 61155. In analyzing the Navy's FY2025 30-year shipbuilding plan, CBO noted the following budget figures:
- Requested/Planned Funding: The FY2025 30-year shipbuilding plan averages roughly $40.1 billion per year in requested funding.
- Actually Appropriated Funding: Over the preceding five years, actual appropriations for shipbuilding averaged roughly $27.5 billion per year.
The roughly $12.6 billion annual gap between requested plans ($40.1 billion/year) and historical actuals ($27.5 billion/year) demonstrates why project managers cannot build realistic programmatic assumptions on long-range plans. If an acquisition strategy or industrial expansion strategy assumes spending levels that exceed historical appropriation averages by more than 45 percent, the program's schedule and scope are exposed to significant fiscal risk.
Project managers evaluating defense programs must isolate these financial concepts:
- Requested/Planned Figures: Projected budget requests submitted in long-range strategy documents or Future Years Defense Programs (FYDP). These represent desired resource levels, subject to legislative alterative and fiscal constraints.
- Appropriated Figures: Enacted funding passed by Congress and signed into law. This represents the actual financial ceiling under which procurement, industrial base investments, and contract execution must operate.
When reviewing reports like GAO-26-109068, which highlighted that Navy officials could not quantify full funding needs for the submarine industrial base and relied on 5-year budget cycles, comparing these figures against actual appropriations trends provides a realistic measure of whether program goals are achievable under expected funding levels.
Establishing a Primary-Source Workflow via gao.gov
To avoid reliance on secondary media coverage, acquisition professionals and project managers should establish a direct primary-source monitoring workflow. GAO maintains a public repository of all published reports, testimony, and legal decisions on its website (gao.gov). Incorporating direct document review into standard risk management protocols ensures that program planning is informed by verified audit findings.
Step 1: Direct Document Retrieval
Project managers can locate specific audits directly using the GAO document tracking number. Entering a report number (such as GAO-24-107732 or GAO-26-109068) into the search portal on gao.gov brings up the official landing page for that specific publication. Users can also filter searches by agency (e.g., Department of the Navy) or subject topic (e.g., National Defense, Acquisition and Sourcing Management).
Step 2: Analyzing Document Landing Pages
Each landing page provides several key resources:
- Fast Facts / Summary: A concise, technical overview of the scope, methodology, and core findings.
- Highlights Page (PDF): A single-page summary designed for rapid extraction of primary metrics.
- Full Report (PDF): The complete primary text, including scope, methodology, detailed findings, agency comments, and full appendice analysis.
Step 3: Leveraging the "Recommendations" Tab
One of the most valuable tools for program tracking on gao.gov is the dedicated "Recommendations" tab on report landing pages. GAO maintains dynamic tracking of open versus closed recommendations across all active reports. By navigating to the Recommendations tab, a project manager can:
- Review the exact corrective actions requested by GAO.
- Check the current implementation status (Open, Closed - Implemented, or Closed - Unimplemented).
- Track agency progress over time as GAO updates the status of open items following periodic re-evaluations.
By regularly auditing the Recommendations tab for key acquisition programs, project managers can objectively measure whether an agency or service branch is addressing systemic issues or allowing known operational vulnerabilities to persist. Moving from secondary news reporting to direct, structured evaluation of primary documents ensures that risk registers, cost models, and schedule projections reflect audited operational realities.
