R01 Budget Justification: The Line Items Reviewers Actually Question

The budget justification is the section of an R01 application that most investigators treat as paperwork. They pour months into the Specific Aims and Research Strategy, then allocate an afternoon to the budget narrative, filling in dollar amounts that seem reasonable and attaching a few sentences of explanation. Reviewers notice.

Study sections do not score the budget directly -- it falls outside the five scored review criteria -- but the NIH Grants Policy Statement explicitly instructs reviewers to evaluate whether the budget is reasonable and appropriate for the proposed work. A budget that looks inflated signals a PI who does not understand costs. A budget that looks thin signals one who does not understand the work. Either way, the result is the same: eroded confidence in the applicant's ability to manage a multi-year, federally funded research program.

The current NIH salary cap, effective January 11, 2026, sits at $228,000 -- the Executive Level II rate set by NOT-OD-26-034. The modular budget threshold remains $250,000 in direct costs per year. And a recent policy change eliminated the longstanding requirement to get prior IC approval before submitting applications requesting $500,000 or more in direct costs. Those are the numbers. What follows is how reviewers actually read the budget behind them.

Personnel: Where Most of the Money Goes and Most of the Questions Start

Personnel typically consumes 60 to 80 percent of an R01 budget, and it is the category where reviewers have the sharpest instincts. They have written their own budgets, staffed their own labs, and reviewed hundreds of applications. They know what three calendar months of PI effort looks like on a project, and they know when the number on the page does not match the scope of the aims.

For new and early-stage investigators, the conventional guidance is to commit at least 25 percent effort -- roughly three calendar months -- on each R01. Anything less, and reviewers question whether you have the bandwidth to lead the project. Anything substantially more on a single R01 can raise questions about whether you are overcommitting, particularly if you hold other funded awards. The effort figures listed in person-months must be internally consistent with the work described in the Research Strategy. If Aim 3 involves a two-year longitudinal study requiring weekly data collection, but the research coordinator is budgeted at 15 percent effort, reviewers will do that math.

The salary cap creates a specific budgeting problem for senior investigators. If a PI's institutional base salary is $310,000, the NIH will only reimburse up to $228,000. The institution must cover the difference or the PI absorbs it. What reviewers watch for is whether the effort percentage and the salary request are consistent. Requesting 30 percent effort on an R01 means the NIH contribution is capped at $68,400 (30 percent of $228,000), regardless of actual salary. Misaligning these numbers suggests the applicant either does not understand the cap or is padding the budget elsewhere to compensate.

Postdoctoral researchers are another area of scrutiny. The FY2025 NRSA stipend for a Year 0 postdoc is $62,652, rising to $75,564 for those with seven or more years of experience. Most institutions pay postdocs above the NRSA minimum, and NIH allows this on research grants, but a budget that lists a postdoc at $95,000 in a city with a moderate cost of living will draw questions. So will a budget that lists two postdocs doing essentially the same work described for one.

Graduate students bring a different wrinkle. NIH caps the allowable compensation for a graduate student research assistant at the zero-level postdoctoral stipend -- currently $62,652, including salary, fringe, and tuition remission. Going above this level on the initial budget requires justification. Going significantly above it virtually guarantees a reviewer comment.

The $5,000 Line That Separates Equipment from Supplies

Federal regulations define equipment as a single item with an acquisition cost of $5,000 or more and a useful life exceeding one year. Everything below that threshold is a supply, regardless of how sophisticated the item is. A $4,800 centrifuge is a supply. A $5,200 centrifuge is equipment. The distinction matters because equipment is excluded from the modified total direct cost base used to calculate facilities and administrative (F&A) costs, which means listing an item as equipment rather than supplies reduces the total award cost.

There is a further complication. NIH now recognizes an updated equipment threshold of $10,000, but only for institutions whose current negotiated indirect cost rate agreement explicitly cites the higher threshold. If your institution's rate agreement still uses $5,000, that is your threshold. Misclassifying items based on the wrong threshold is a compliance issue that can surface during post-award audit.

Reviewers question equipment requests in three situations. First, when the application lists a piece of equipment that is already described in the Facilities and Other Resources section. If you told reviewers your institution has a state-of-the-art confocal microscope and then request $180,000 for a new one, you need to explain what the existing instrument cannot do. Second, when equipment appears only in the later years of the budget without a clear scientific rationale tied to the project timeline. Third, when the equipment is general-purpose -- a high-performance computing cluster, for instance -- and the justification does not explain why the proposed research specifically requires dedicated hardware rather than shared institutional resources.

For modular budgets under $250,000 in direct costs, you do not itemize equipment at all. But you still must justify any equipment in the budget narrative, and reviewers will still notice if the total modules seem inflated relative to the work proposed. A modular budget requesting $250,000 per year for a project that involves one PI, one postdoc, standard lab supplies, and no subcontracts will prompt questions about where the remaining dollars are going.

Travel: Small Dollar Amounts, Outsized Scrutiny

Travel budgets on R01 applications rarely exceed $5,000 to $10,000 per year, but they attract attention disproportionate to their size. Reviewers question travel when the justification is vague ("travel to scientific conferences"), when the number of trips or attendees seems excessive for the project scope, or when foreign travel is included without a compelling scientific rationale.

The budget justification should name specific conferences, estimate costs per trip (registration, airfare, lodging, per diem), and explain the scientific purpose. Presenting a poster at the Society for Neuroscience annual meeting to disseminate findings from Aim 2 is a justifiable expense. Attending three international conferences per year with two lab members each is harder to defend on a standard R01.

Domestic travel to collaborator sites is generally straightforward to justify, especially when the collaboration is described in the Research Strategy and the collaborator has a letter of support. Foreign travel faces a higher bar. NIH allows it, but the scientific necessity must be explicit -- traveling to a field site in sub-Saharan Africa for sample collection, for example, or visiting a laboratory in Germany that maintains the only transgenic mouse colony relevant to your work.

Per diem rates should align with federal guidelines or your institution's travel policy, whichever is lower. Requesting $400 per night for hotel stays when the federal per diem for that city is $180 will not go unnoticed.

Consultants and Subcontracts: The Budget Lines That Trigger Extra Review

Consultant costs and subcontracts (formally called consortium arrangements) are among the most heavily scrutinized budget categories. A consultant is an individual providing expert advice or services, typically billed at a daily or hourly rate. A subcontract is a formal arrangement with another institution that takes on a defined portion of the scientific work.

The distinction matters because consultant costs above roughly $10,000 may need to be reclassified as a subcontract, which triggers additional requirements: a separate budget and justification from the subaward institution, a letter of intent, and documentation of the subrecipient's F&A rate. For subawards, only the first $25,000 of each subcontract is included in your modified total direct cost base for calculating F&A costs. Everything above $25,000 is excluded. This creates a strong financial incentive to route work through subcontracts -- and reviewers know it.

What reviewers want to see in a consultant justification is specificity. The consultant's name, their qualifications, the specific service they will provide, the rate, and the number of days or hours. "Dr. Jane Smith, Professor of Biostatistics at University X, will provide statistical consultation on the adaptive trial design for Aim 2, including sample size calculations and interim analysis plans, at $500/day for 10 days per year" passes muster. "Statistical consultation, $5,000/year" does not.

For subcontracts, the scrutiny is more structural. Reviewers want to understand why the work cannot be done at the primary institution, what the subcontract PI's specific role and effort are, and whether the subcontract budget is proportionate to the scope of work described. A subcontract consuming 40 percent of total direct costs with a Sub-PI listed at 5 percent effort is a red flag. So is a subcontract that looks like it was added to justify the budget rather than to advance the science.

Foreign subcontracts face an additional constraint: NIH caps F&A costs for foreign and international organizations at 8 percent of modified total direct costs. This is substantially below the 50-plus percent F&A rates common at U.S. research institutions, and it means the total cost of a foreign subcontract may look artificially low to reviewers who are not aware of the policy.

Indirect Costs and the Modular Math

Indirect costs -- officially F&A costs -- do not appear as a line item in modular budgets, but they shape every budget decision. Your institution's negotiated F&A rate determines how much of each dollar actually reaches the lab bench. At a research university with a 55 percent F&A rate, requesting $250,000 in direct costs means the total cost to NIH is approximately $387,500. At a university with a 45 percent rate, the same direct cost request costs NIH about $362,500.

Reviewers at study section do not typically see the F&A rate, and they do not score the budget. But program staff at the IC do see it, and when awards are made, the total cost -- directs plus indirects -- comes out of the IC's appropriation. This is why some ICs fund modular R01s at reduced levels, applying across-the-board cuts of 6.5 to 8.5 percent to the direct costs. The National Cancer Institute, for instance, currently applies a 6.5 percent reduction to new modular R01s requesting $175,000 or less in directs and an 8.5 percent reduction above that threshold.

For investigators operating near the $250,000 modular ceiling, the math gets tactical. A project that genuinely needs $260,000 in direct costs per year must use the detailed budget format, which requires itemizing every expense across more than a dozen categories. Some investigators deliberately trim their budgets below $250,000 to stay in modular territory and avoid the administrative burden. Others choose the detailed format strategically, knowing that a well-justified $270,000 budget looks more credible than a vaguely explained $250,000 one.

The recent elimination of the $500,000 prior-approval requirement, announced in NOT-OD-26-019, removes one barrier for large-budget applications. Investigators no longer need to contact their target IC and secure agreement before submitting an application exceeding $500,000 in direct costs in any single year. This change reduces administrative friction but does not reduce scientific scrutiny. A $600,000-per-year R01 will still need to justify every dollar to the study section and the program officer.

The Year-to-Year Problem

One of the most common reviewer comments on R01 budgets targets unexplained variation across the project period. If Year 1 requests $200,000 and Year 3 jumps to $250,000, the justification must explain why. Equipment purchases in a specific year, a postdoc starting in Year 2, or increased participant recruitment costs in the middle years of a clinical study are all defensible reasons. What is not defensible is a flat budget across five years when the research plan clearly describes front-loaded data collection and back-loaded analysis, or vice versa.

The budget should mirror the timeline of the science. If your project involves a six-month startup period to hire staff and establish protocols, your Year 1 budget should reflect lower personnel costs and higher equipment or supply costs. If the final year is primarily data analysis and manuscript preparation, the budget should step down accordingly. A perfectly flat budget across all years, with the same dollar amount in every category, suggests the investigator built the budget from a template rather than from the research plan.

Reviewers also watch for budget padding in the terminal year. An R01 that maintains full staffing and supply budgets through Year 5 when the research plan describes wrapping up in Year 4 raises questions about whether the applicant is requesting funds beyond what the science requires.

What Reviewers Are Really Evaluating

The budget justification is not a financial document. It is an extension of the scientific narrative. Reviewers use it to answer a single question: does this applicant understand what it takes to execute this research? An investigator who has thought carefully about personnel effort, equipment needs, travel requirements, and subcontract structures is demonstrating the same kind of planning and feasibility analysis that makes for a strong Research Strategy.

The most effective budget justifications share a common trait: every dollar connects to a specific aim or activity in the Research Strategy. The postdoc is not just "a postdoc" -- they are the person running the single-cell RNA-seq experiments described in Aim 1. The travel is not to "a conference" -- it is to the annual meeting where preliminary findings from Year 2 will be presented to the field. The consultant is not providing "statistical support" -- they are designing the adaptive randomization scheme that makes the Phase II trial in Aim 3 feasible.

That level of specificity does not require more pages. It requires more thought. And it is the difference between a budget that reviewers skim and one that reinforces their confidence in the entire application.

Granted helps research teams build budgets that align with their science -- connecting personnel, equipment, and costs to the aims that justify them.