How Hill Staffers Use Budget Data to Prepare for Defense Authorization Hearings

A good oversight question isn't improvised — it's built from three years of budget comparisons, witness testimony cross-referenced to funding requests, and an understanding of what was promised versus what was delivered.

The National Defense Authorization Act is passed annually. It is the primary legislative mechanism through which Congress directs, constrains, modifies, and sometimes cancels specific defense programs. The hearing process that precedes the NDAA — testimony from the Secretary of Defense, the service secretaries, the chiefs, and dozens of program officials — is one of the most information-dense events in Washington's policy calendar.

The quality of that hearing process depends heavily on how well committee staff are prepared. A well-prepared staffer can ask questions that elicit genuine accountability from program officials and create a factual record for the markup process. A poorly prepared staffer asks questions that program officials can deflect with talking points.

The difference between the two, at the level of technical defense programs, often comes down to budget data.

The Staff Function

House and Senate Armed Services Committee staff are divided by portfolio — each professional staff member covers a specific set of programs across one or more military departments. A staffer covering Army aviation might be responsible for dozens of programs, from the Black Hawk replacement to specific Research, Development, Test and Evaluation (RDT&E) efforts in advanced rotorcraft technology. A staffer covering space might follow 30-plus PE numbers across Air Force, Space Force, and DARPA.

For each of those programs, the staffer's job is to understand what the program promised to deliver, what it actually delivered, and whether the current budget request is justified by the program's performance history. That understanding has to be deep enough to survive a hearing where the program manager or program executive officer — who has spent years on that single program — is on the other side of the table.

Building that understanding requires the same budget data analysis that BD teams and researchers use — but with a different goal. Instead of asking "where is the opportunity?", the staffer is asking "where is the gap between promise and delivery?"

Building the Hearing File

For a significant program, staff preparation typically begins with the multi-year budget history. The staffer will pull the R-2A exhibit for the current submission and compare the "prior year accomplishments" section with what the prior year's submission said would be accomplished. This comparison, done systematically, produces a performance audit.

The questions this audit generates are the foundation of effective hearing prep:

The program said in the FY2024 President's Budget (PB2024) that it would complete a critical design review by March 2024. The PB2025 submission's prior-year accomplishments section reports that CDR is now scheduled for Q4 FY2025. What changed, and what is the cost impact of the 18-month delay?
The program requested $145M in FY2024, received $145M, and reported obligating $112M. What happened to the $33M that wasn't obligated? Is the program execution-constrained in a way that makes the FY2025 request of $180M implausible?
The Future Years Defense Program (FYDP) in PB2022 projected $400M for this program in FY2025. The PB2025 request is $280M. That's a $120M reduction from what the program projected for itself three years ago. What capability was removed to accommodate the reduction?

Each of these questions has a factual foundation in the budget documents. A witness who has not anticipated the question — who doesn't realize the staffer has done this comparison — will often give an answer that creates further record. A witness who has anticipated it will have a prepared response, which is itself useful information: it tells the staffer the program office considers the question significant.

The NDAA Markup Process

Hearings are one part of the legislative process. The markup is where the legislative language is actually written, and budget data drives that process in a different but equally important way.

When committee staff propose to cut a program, add a reporting requirement, direct a study, or mandate a restructuring, those proposals are grounded in specific data. A $50M cut to a program's budget request is not an arbitrary number — it reflects a judgment that the program cannot execute at the requested level based on its prior-year obligation rate. A requirement to submit a report to Congress on schedule and cost variance is typically triggered by a pattern visible in the budget history.

This also means that programs with clean budget histories — where funding tracks projections, obligations match appropriations, and prior-year accomplishments match prior-year plans — are much less likely to attract adverse legislative action. The budget data serves, implicitly, as a report card.

Beyond the R-2

Effective staff preparation draws on sources beyond the budget justification books. Selected Acquisition Reports, published quarterly for major defense acquisition programs, provide independent cost and schedule assessments that often tell a different story than the program office's own narrative. Government Accountability Office reports on specific programs provide yet another analytical layer. Defense Contract Audit Agency findings, available through various oversight channels, add a financial management perspective.

But the budget justification is the primary source because it is the most comprehensive, the most current, and the most directly tied to the specific dollar requests being considered for authorization. It is also the document that witnesses will have in front of them during the hearing, which means questions grounded in it cannot be dismissed as based on incorrect information.

The Information Asymmetry Problem

The fundamental challenge for oversight staff is that they cover dozens of programs simultaneously while each program office has dedicated personnel for every aspect of the program. A three-person staff portfolio might include 40 active programs. The program office for a single large program might have 200 people.

Tools that make it possible to query across multiple programs simultaneously, to flag year-over-year anomalies automatically, and to surface patterns in execution data that would otherwise require manual comparison across multiple documents can substantially reduce the staff burden without reducing the analytical depth.

The oversight function works when staffers ask questions that witnesses can't deflect. Making those questions possible, at scale, across a complex portfolio — that's the analytical problem that budget data tools are designed to solve. When that problem is solved, the hearing record improves, the markup is better grounded in fact, and the NDAA that emerges more accurately reflects what the programs have actually demonstrated they can do.