How to Write a Grant Budget That Survives Review

The Budget Is Where Applications Quietly Lose

Most people preparing a grant application pour their energy into the narrative. That is understandable, because the narrative is the story, and the story is what feels like it should win. But if you want to know how to write a grant budget that holds up, start with a hard truth I have watched play out many times: the narrative is rarely where strong applications fall apart. The budget is. A reviewer can love your program and still score you down, or pass you over, because the numbers do not add up, do not match what you described, or do not follow the funder's rules.

I manage more than $15 million in active federal and state grants at The Ohio State University's Government Resource Center, full lifecycle from proposal through closeout, and I am a Certified Research Administrator who works in 2 CFR 200 (Uniform Guidance) every day. From that seat I can tell you that experienced reviewers read budgets carefully and often skeptically, because the budget is where they see whether you actually understand the work or just wrote a nice essay about it. A budget that foots, ties to the narrative line for line, and respects the cost rules signals a competent organization. A sloppy one signals risk, and funders do not give money to risk.

This post walks through how to build a grant budget reviewers trust: the building blocks, the difference between direct and indirect costs, the budget justification that explains your math, the three tests every federal cost has to pass, and the mistakes I see most often. A quick note before we go: this is general educational information, not formal accounting, tax, or legal advice. Your specific funder's rules and your own CPA should govern the final call.

The Building Blocks of a Grant Budget

Almost every grant budget, whether it is a foundation's simple one-page form or a federal SF-424A, is built from the same cost categories. Learn these and you can read any budget template you are handed. Most funders provide a required format, so use theirs, but if you want a neutral starting point, a basic grant budget template organized around these categories will translate to almost any application.

Personnel. The salaries and wages of your own employees who will work on the grant. You list each position, the percentage of time (or level of effort) they will spend on the project, and the portion of their salary that represents. Do not charge a whole salary to a grant a person spends a quarter of their time on.
Fringe benefits. The employer cost of benefits tied to those salaries: payroll taxes, health insurance, retirement, workers' compensation. This is the line most often forgotten, and forgetting it means you have under-budgeted the true cost of your own staff. Fringe is usually expressed as a percentage of salary.
Contractual. Payments to outside vendors, consultants, or subrecipients who do part of the work. A consultant doing program evaluation lives here. So does a subaward to a partner organization, though subawards carry extra rules.
Travel. Mileage, airfare, lodging, and per diem for project-related travel. Tie it to specific trips and use defensible rates (the federal per diem and mileage rates are a common, safe basis to cite).
Supplies. Consumable, lower-cost items: office supplies, program materials, software under your capitalization threshold.
Equipment. Higher-cost, durable items, typically tangible property above a dollar threshold (federally, that threshold is defined in 2 CFR 200, and many organizations set their own at or below it). Equipment is treated differently from supplies and is often excluded from the indirect cost base, which matters later.
Other direct costs. The legitimate project costs that do not fit the boxes above: participant incentives, printing, postage, training registration, communications.
Indirect costs. The real cost of running your organization that you cannot trace to one specific grant: general management, accounting, rent for shared space, IT. These are recovered through a rate, not by sprinkling overhead onto direct lines. More on this in a moment, because it is where the most money gets left on the table.

Add the direct categories together, apply your indirect rate to the correct base, and you have a total. The arithmetic sounds trivial. The discipline is in making every number defensible.

Direct vs Indirect Costs, and the Indirect Rate You Are Allowed to Use

The line between direct and indirect costs trips up nearly every first-time applicant, so it is worth slowing down. A direct cost is one you can tie to a specific project: the salary of the person running the program, the materials they hand out, the consultant who evaluates it. An indirect cost benefits multiple programs and the organization as a whole, so you cannot honestly assign it to one grant: the executive director's general oversight, the bookkeeper, the office rent, the phone system.

Indirect costs are real, and on federal awards you are entitled to recover them, but only through an approved rate applied to a defined base. You generally have two options.

The first is a negotiated indirect cost rate, formalized in a Negotiated Indirect Cost Rate Agreement (a NICRA) with your cognizant federal agency. This is worth pursuing once your grant volume is large enough to justify the effort, because a negotiated rate often recovers more than the alternative.

The second is the de minimis rate, available to organizations that have never held a negotiated rate. Under the 2024 revisions to 2 CFR 200, the de minimis rate rose to 15 percent of modified total direct costs, up from the long-standing 10 percent. Modified total direct costs (MTDC) is a defined base: it generally includes salaries, fringe, supplies, and the first $50,000 of each subaward, and it excludes items like equipment and the portion of any subaward above $50,000. Because that revision is recent, confirm both the current percentage and the exact base against your specific award terms and with your CPA before you rely on it. Verify, do not assume.

Here is the practical mistake I see constantly: small organizations either bury overhead inside their direct lines (which fails review when a sharp reviewer catches it) or they skip indirect costs entirely and quietly subsidize the grant out of their own unrestricted funds. Neither is necessary. Learning how to write a grant budget that uses the indirect rate correctly is, in plain terms, learning how to stop leaving money on the table while staying compliant.

Make the Budget Match the Narrative, Line for Line

This is the step that separates budgets reviewers trust from budgets they flag, and it costs nothing but attention. Every activity you describe in the narrative needs a corresponding cost in the budget, and every cost in the budget needs a reason in the narrative. The two documents have to agree.

If your narrative promises a part-time outreach coordinator, the personnel line had better show one, at a percentage of time that matches the workload you described. If you write about traveling to four rural counties for site visits, the travel line needs to reflect four trips, not a round number pulled from the air. If the narrative mentions a program evaluation, the contractual line should fund the evaluator. When a reviewer can move from a sentence in your narrative to a number in your budget and back again without friction, you read as an organization that knows what its own plan costs.

The failure mode is just as visible. A narrative that describes an ambitious five-county program attached to a budget with no travel, no mileage, and a single underfunded staff line tells the reviewer the applicant has not thought it through. Mismatches are read as either carelessness or wishful thinking, and both lower your score. Before you submit, do a literal cross-check: read the narrative with the budget open beside it and confirm that each promised activity has a funded line, and each funded line has a stated purpose.

The Budget Justification: Where Reviewers Actually Look

The budget is the numbers. The budget justification (sometimes called the budget narrative) is the explanation of those numbers, and on competitive and federal applications it gets read closely. The justification answers the question behind every line: why is this cost necessary for the project, and how did you arrive at this amount?

A weak justification restates the budget in words: "Salaries: $48,000." A strong one shows the math and the reasoning. For a personnel line, that means naming the position, the base salary, the percentage of effort, and the resulting charge: a coordinator at a $60,000 annual salary working 50 percent on the project, charged at $30,000, plus fringe at your organization's documented rate. For travel, it means stating the number of trips, the destinations, the mileage rate, and the per diem basis. For supplies, it means describing what the supplies are and how the estimate was built, not just a lump sum. The justification is your chance to prove every number rests on a calculation rather than a guess.

I read budget justifications the way an auditor would, because that is the muscle the work has built. When a justification shows its math, ties cleanly to the activities, and uses defensible rates, I trust the rest of the application more. When it is vague, round, and unexplained, I start checking everything else twice. Reviewers do the same, and you want to be on the right side of that instinct.

Allowable, Allocable, Reasonable: The Test Every Line Must Pass

For any award with federal dollars in it, directly or passed through your state or a larger nonprofit, every cost in your budget has to satisfy three standards from 2 CFR 200. These are not abstractions. They are the exact tests an auditor or program officer applies, and budgeting with them in mind from the start prevents disallowed costs later.

Allowable. The cost is permitted by the cost principles in 2 CFR 200 and by your specific award. Some costs are flatly unallowable no matter what (alcohol and most lobbying, for example). Others are allowable only with prior written approval. If a cost is not allowable, it does not belong in the budget, full stop.
Allocable. The cost actually benefits the grant you are charging it to, in proportion to that benefit. A laptop used equally by two programs gets split between them, not loaded entirely onto whichever grant has room.
Reasonable. A prudent person would have paid that amount for that item under the circumstances. Paying well above market rate, especially to anyone connected to the organization, is the classic reasonableness failure.

If you cannot say yes to all three for a line, fix it before you submit. Building the budget to pass these tests up front is far cheaper than defending a questioned cost during a review or, worse, paying it back at closeout.

Common Grant Budget Mistakes

After years of building, reviewing, and managing budgets, I see the same errors over and over. They are all preventable.

Round numbers with no basis. A budget full of figures ending in three zeros tells a reviewer you estimated rather than calculated. Real costs are rarely round. Show how you got the number.
Math that does not foot. Lines that do not sum to the subtotals, subtotals that do not match the total, an indirect calculation applied to the wrong base. If your own arithmetic does not hold, why would a funder trust you with theirs? Check it, then have someone else check it.
Costs not tied to activities. A line item that does not connect to anything in the narrative reads as padding. Cut it or justify it.
Forgetting fringe. Budgeting salaries without the benefits that ride on them understates your true personnel cost and leaves you short once the award lands.
Forgetting indirect, or doing it wrong. Skipping indirect costs entirely subsidizes the funder out of your own pocket. Applying the rate to the wrong base (charging it on equipment or the full value of a large subaward) gets flagged.
Ignoring the funder's format. If they give you a template or a required form, use it exactly. A budget submitted in the wrong format can be rejected before the numbers are even read.

A Note on How Grant Budgets Get Priced

One thing I will say plainly, because it bears on budgets specifically. If you hire help with a grant, including the budget, pay a flat fee, never a percentage of the award. Contingency pricing (taking a cut of the grant) is prohibited by many funders, including on federal awards, and it puts the helper's incentives in the wrong place. At Up & Adam I price full application packages at a flat $1,500-$4,000 each and post-award management at $750-$2,000 per month. You are paying for the work and the compliance, not for someone talking you into chasing money you should not chase.

Where to Start

A grant budget that survives review is built, not guessed: every line calculated, tied to the narrative, justified in plain math, and tested against allowability, allocability, and reasonableness. Get those habits right and the budget stops being the place applications quietly lose and becomes the place yours stands out.

If you want help making sure your numbers and your books can actually carry the grants you are chasing, my Financial Operations Assessment is a flat $750-$1,500, takes about two weeks, and ends in a written roadmap you keep. If you are earlier in the process and weighing whether to bring in help on the application itself, the post on how to find a Columbus grant writer for nonprofits walks through what to look for, and you can always reach out through contact.

This article is general information and not a substitute for advice from your own CPA or attorney on your specific situation. Build the budget with the same care a reviewer will read it, and you give your application its best chance.