Every February, the Office of the Secretary of Defense publishes several thousand pages of budget justification documents to support the President's Budget submission to Congress. These documents cover everything from aircraft carriers to communications satellites to basic research grants. They are available on the DoD Comptroller's website, organized by appropriation account and military department. Almost no journalists read them.
This is an information asymmetry that is not explained by difficulty. The documents are publicly available, free to download, and written in a formulaic structure that, once understood, can be navigated quickly. What they contain — program descriptions, funding histories, performance narratives, out-year projections, and occasionally the names of contractors and their deliverables — is the factual foundation for defense journalism that currently gets written from press releases and briefings instead.
The Document Types
The defense budget justification library consists of several document series, each covering a different appropriation account. For research, development, test, and evaluation (RDT&E) funding, the key documents are:
The R-1 is the summary document. It lists every program element in every RDT&E account across all defense components, with the prior-year actuals, current-year estimate, and budget-year request for each. Think of it as the index. It tells you which programs exist and at what funding level, but not what they do.
The R-2 is the detailed justification. For each program element, the R-2 provides a description of the program, its mission, the current year's planned activities, the budget year request and what it will accomplish, and the out-year Future Years Defense Program (FYDP) projections. This is the document that actually tells you what the government is funding and why.
The R-2A is the sub-element exhibit. Many PE numbers contain multiple distinct projects or subprograms, and the R-2A breaks those out individually. In some cases, the R-2A level is where contractor names and specific deliverables first appear.
The R-3 is the contract history exhibit. It lists the contracts that have been awarded in prior years against a specific PE number, including contract type, amount, and in many cases the performing contractor. The R-3 is invaluable for connecting budget lines to actual industry activity.
For procurement accounts — ships, aircraft, vehicles, ammunition — the parallel documents are the P-5, P-40, and P-5A exhibits, which cover justification, procurement history, and unit cost data respectively.
What Stories Are in There
Defense journalists who develop fluency with these documents gain access to several types of stories that are difficult to source otherwise.
Program performance stories become accessible when you compare what a program said it would accomplish (the prior year's budget request narrative) with what it actually did (the current year's "prior year accomplishments" section). The government is required to report what happened, and those reports, when compared to what was promised, often tell a story of delay, scope reduction, or cost growth that was never announced as news.
Cost growth stories are visible in the unit cost data for procurement programs. The P-5A exhibit shows unit cost history — what the aircraft or vehicle was expected to cost in the original Selected Acquisition Report, what it costs now, and how the quantity has changed over time. These data points are the factual foundation for cost overrun reporting that rarely gets done because most reporters don't know where to find the numbers.
Industrial base stories emerge from the R-3 contract history. When a single contractor appears across many program elements in a given technology area, that concentration is a story about industrial base structure. When a previously consistent incumbent suddenly disappears from the contract history, that is often a story about a program restructure, a technical failure, or a recompete that didn't go as expected.
Budget priority stories — who's up, who's down, what got cut — are the most straightforward, but the depth of analysis possible goes well beyond the top-line numbers that typically get reported. The FYDP out-year projections are particularly valuable here: when a program's out-year funding is cut in a new submission, it reveals a change in institutional priorities that often happens months before any public announcement.
A Practical Example
Consider a reporter covering the Army's helicopter fleet. The relevant R-2 exhibits will describe each modernization program — what was funded, what was accomplished, and what is planned. Reading across three years of submissions for the same program will reveal whether the program is executing on schedule, whether the budget is tracking the FYDP projections made two years ago, and whether the unit cost data is consistent with the original contract. If the program said in FY2023 that it would complete a critical design review (CDR) by March 2024, and the FY2025 submission reports that CDR is now planned for Q4 FY2025, that 18-month delay is a documented fact — sourced directly from the government's own budget documents — not an allegation requiring unnamed sources.
This kind of accountability reporting is possible across hundreds of programs, in every military department, for anyone who knows where to look.
The Practical Problem
The challenge with these documents is not access — it is scale. A thorough review of a single service's RDT&E justification book can run to 600–800 pages. The full DoD submission across all components and appropriation accounts easily exceeds 5,000 pages. No reporter can read all of it on a February deadline.
The answer is to develop familiarity with the structure so that navigation becomes efficient, and to build a list of programs to monitor year-over-year rather than starting fresh each budget cycle. A reporter covering Navy shipbuilding doesn't need to read the Army's aviation PE justifications. A reporter covering AI and autonomy can focus on specific budget activities across components. The corpus is large but not unsearchable once you know what you're looking for.
Tools that index the budget justification data and allow keyword and program search can substantially reduce the time from "new budget published" to "story filed." When you can search across all 1,700-plus PE numbers for terms like "artificial intelligence," "directed energy," or "hypersonic" and see how the funding for matching programs has changed year over year, the analytical work that previously took days can be done in hours.
Getting Started
For reporters new to this source, the most useful starting exercise is to pick one program you've already written about — an aircraft, a ship, a weapons system — find its PE number, download the R-2 exhibit from the current and prior two years, and read the "prior year accomplishments" section for each. Compare what was promised to what was reported. That comparison, done across a program you already know, is usually enough to understand both how the documents work and why they're worth reading.
The stories are there. The documents are public. The barrier is learning to read them — and once you do, you will never rely on a program office press release as a primary source again.