Chapter 11: The Budget — The Numbers That Tell Your Story in Dollar Signs

Beginners think the budget is where the writing stops and the arithmetic begins — a spreadsheet to fill in after the "real" proposal is written. Experienced grant writers know better. The budget is part of the argument, told in numbers, and a reviewer reads it as closely as any prose section, because the budget reveals things the narrative can hide: whether you understand the true cost of your work, whether your plan is realistic, whether you have thought it through, and whether you can be trusted with the funder's money. A budget that is too low looks naive; too high looks wasteful; internally inconsistent looks careless. The numbers tell a story, and you must make sure they tell the right one.

This chapter teaches you to build that budget. We will treat budgeting as the strategy it is, work through personnel and effort (the largest and most misunderstood category), the other direct costs, the contentious world of indirect costs, cost-sharing, and multi-year escalation — with worked calculations throughout, because this is a chapter where you must be able to do the arithmetic, not just describe it. By the end you will build a complete, multi-year, line-item budget for your project. The math is genuinely simple — multiplication, percentages, addition — but the strategy behind the numbers is what separates a fundable budget from a flawed one.

If you are math-anxious, let this chapter reassure you: there is no algebra here, no statistics, nothing beyond what a calculator and a clear head can handle. Salary times effort. Salary times a fringe percentage. Direct costs times an indirect percentage. A 3% annual increase. That is the entire mathematical content of even a complex budget. The errors that sink budgets are almost never arithmetic mistakes; they are conceptual — forgetting fringe, applying the indirect rate to the wrong base, mismatching the budget to the narrative, missing a whole category, or using the wrong format. So if numbers intimidate you, take heart: the skill this chapter teaches is not computation but bookkeeping discipline and strategic thinking — remembering all the pieces, keeping them consistent, and making the numbers tell the same story as your prose. Anyone who can run a household budget can build a grant budget; what takes practice is the strategy, not the sums.

11.1 The Budget Is Strategy, Not Arithmetic

A budget makes a series of claims about your project: this is what it costs, this is how the money will be spent, these are the resources the work requires. Reviewers read those claims critically, asking: Is this realistic? Does it match the plan? Is every expense necessary? Is anything missing? Is the request reasonable for what's promised? The budget that answers all of these well builds credibility; the one that raises questions undermines the whole proposal.

This is why budgeting is strategy. Every choice — how much effort to put on the project, whether to include a piece of equipment, how to structure a subaward, whether to request the full indirect rate — is a strategic decision that shapes how the reviewer perceives your project and affects your odds. The applicant who treats the budget as an afterthought, thrown together the night before (the late-start failure of Chapter 4), produces a budget full of the errors and inconsistencies that reviewers pounce on. The applicant who builds the budget thoughtfully, in concert with the narrative, produces numbers that reinforce the case.

🚪 Threshold Concept: The budget is your narrative expressed in dollars, and the two must match exactly. Every activity in your plan needs a number in your budget, and every number in your budget needs an activity in your plan. A reviewer who finds a mismatch — a staff position in the budget that the narrative never mentions, an activity in the narrative that the budget doesn't fund, a total that differs between the budget table and the text — stops trusting both. The budget and the narrative are two views of one project; when they disagree, the reviewer cannot tell which to believe, and a project the reviewer cannot pin down is one they will not fund. Build the budget from the narrative, line by line, and check that every activity and every dollar appears in both.

🗣️ From the Review Panel: I read the budget alongside the narrative, going back and forth, and I can tell almost immediately whether they were written together or separately. When the budget funds exactly the activities the narrative describes — the staff doing the work, the supplies the methods require, the travel the plan implies, the evaluator the evaluation plan names — I trust the applicant, because the pieces fit. When I find a line the narrative never explains, or an activity with no money behind it, I start checking everything, and a budget that needs checking has already cost the applicant my confidence. The budget is where I catch the proposals that were assembled rather than designed.

There's a deeper way the budget tells a story: its proportions reveal your priorities and your understanding of the work. A youth-mentoring program whose budget is 70% administrative overhead and 10% direct mentoring tells a reviewer the priorities are backwards. A research project that budgets generously for equipment but almost nothing for the personnel time to use it reveals a misunderstanding of where the real cost lies. A budget where the evaluation — which the funder cares about (Chapter 10) — gets a token \$500 signals that the applicant doesn't take measurement seriously. Reviewers read these proportions, often unconsciously, and form judgments about whether you understand your own project. So as you build the budget, step back and look at the shares: does the money flow primarily to the activities that produce your outcomes? Are the proportions defensible? A budget whose shape matches a sensible understanding of the work reinforces the narrative; one whose shape is lopsided in puzzling ways undermines it, even if every individual line is correct.

11.2 Personnel: Salary, Effort, and Fringe

🧩 Productive Struggle: Before reading, estimate: if a staff member earns \$48,000 a year, works 60% time on your project, and the fringe rate is 30%, what does the project pay for them? Work it out. (The answer is below the next paragraph, but try first — the calculation is the whole skill, and it's just two multiplications and an addition.) If you got it, you've grasped the core of personnel budgeting; if not, the worked box will show you. Either way, notice that the "math" here is genuinely simple — the difficulty in budgeting is never the arithmetic, it's remembering all the pieces (effort and fringe and the right rate) and keeping them consistent with the narrative.

For most projects, personnel — the people doing the work — is the largest budget category, and it is where beginners make the most errors. Three concepts govern it: salary, effort, and fringe benefits.

Salary is a person's annual pay. Effort is the fraction of their time devoted to the project, often expressed as a percentage or, in federal research, as person-months (the number of months of full-time-equivalent work). The cost charged to the grant is salary × effort. If a staff member earning \$60,000 a year spends 25% of their time on the project, the project pays 25% of \$60,000 = \$15,000 of their salary. Fringe benefits — the employer's cost of health insurance, retirement, payroll taxes, and so on — are then added, usually as a percentage of salary (the fringe rate, which varies by institution and is often 25–35%).

💰 Budget Box — Personnel cost: A program coordinator earns \$50,000/year and will spend 50% effort on the project. The institution's fringe rate is 30%. - Salary charged: \$50,000 × 0.50 = **\$25,000 - Fringe: \$25,000 × 0.30 = **\$7,500 - Total personnel cost for this person: \$32,500 Repeat for each person on the project (PI, staff, students), and the personnel total is the sum. Note that effort and salary are both needed — a reviewer reads effort as a signal of commitment and feasibility: too little effort for a demanding role ("the PI is 2% effort on a project they're supposed to lead?") raises a red flag.

Effort is itself strategic. It must be realistic — enough to do the work credibly — and it must be consistent with the narrative and with the person's other commitments (a PI cannot be 80% effort on five different grants totaling 400%). Reviewers scrutinize effort because it reveals whether the team can actually deliver: a complex project staffed at implausibly low effort signals either a misunderstanding of the work or an attempt to hide its true cost. The PI's own effort is read especially closely — a principal investigator listed at minimal effort on a project they are supposed to lead raises an immediate question about whether the leadership is real, so commit credible effort to the roles you claim to fill.

⚠️ Common Pitfall: Forgetting fringe benefits, or applying the wrong rate. Salary without fringe undercounts personnel cost substantially (by 25–35%), producing a budget that is too low and a grants office that has to fix it at routing (Chapter 4) — or worse, an award that can't actually cover the staff. Always add fringe at your institution's actual rate, and get the rate from your grants/finance office rather than guessing. For nonprofits without a formal fringe rate, build benefits into the personnel calculation explicitly.

A fuller worked example shows how personnel adds up across a team. RYCC's project (composite) staffs two instructors and a coordinator, fringe at 25%:

Notice two things a reviewer reads here. First, the effort levels are plausible for an after-school program — half-time coordination, part-time instruction — and consistent with RYCC's narrative; nobody is implausibly stretched. Second, fringe adds over \$14,000 that a beginner who forgot it would have omitted, producing a budget that couldn't actually pay its staff. Personnel is usually the bulk of a budget, so getting it right — real salaries, credible effort, fringe included — is most of the battle, and errors here ripple through the indirect calculation too (since indirect often applies to salary and fringe).

11.3 The Other Direct-Cost Categories

Beyond personnel, direct costs — expenses directly attributable to the project — fall into standard categories. Not every project uses every category; include the ones your narrative requires.

• Equipment: durable items above a threshold (often \$5,000 for federal grants; below it, items are "supplies"). Equipment often has special budget treatment (it's frequently excluded from the indirect-cost base, Section 11.4).
• Supplies and materials: consumables the work requires — lab reagents, program materials, software, office supplies for the project.
• Travel: project-related travel — to field sites, to conferences to present results, for data collection. Itemize realistically (airfare, lodging, per diem) rather than guessing a round number.
• Participant support costs: payments, incentives, or support for the people your project serves or studies (stipends, transportation, childcare to enable participation). These often have special treatment (also frequently excluded from the indirect base).
• Consultants: experts paid for specific, limited contributions (e.g., an external evaluator, Chapter 10; a statistician). Distinct from personnel (consultants aren't your employees) and from subawards.
• Subawards / subcontracts: when part of the work is done by another organization (a partner university, a collaborating nonprofit). The subaward includes that organization's own direct and indirect costs. Subawards have important budget and compliance implications (Chapter 23).
• Other direct costs: anything else the project genuinely requires — publication fees, participant recruitment, equipment maintenance, communications.

📋 Template — Line-item direct-cost budget: | Category | Detail | Cost | |---|---|---| | Personnel | [each person: salary × effort + fringe] | | | Equipment | [items > threshold] | | | Supplies | [consumables] | | | Travel | [itemized] | | | Participant support | [stipends, incentives, support] | | | Consultants | [evaluator, statistician, etc.] | | | Subawards | [partner orgs' costs] | | | Other | [publication, recruitment, etc.] | | | Total direct costs | | | Build each line from a specific activity in your narrative. If a line has no narrative activity behind it, cut it; if an activity has no budget line, add it.

A few category subtleties save you from common errors. The equipment threshold matters because it changes both the category and the indirect treatment — a \$4,500 laptop is a "supply" (in the indirect base) while a \$6,000 instrument is "equipment" (often excluded from the base), so misclassifying changes your indirect calculation. Participant support costs are distinct from personnel and from incentives to your own staff; they're support for the people the project serves or studies, and federal rules often treat them specially (excluded from the indirect base, and sometimes restricted in how they can be rebudgeted). Consultants vs. subawards vs. personnel trips people up: a consultant provides a defined service for a fee and isn't your employee; a subaward sends part of the scope of work to another organization that runs it with its own budget; personnel are your own employees. The distinction matters for both budgeting and compliance (Chapter 23). When unsure which category a cost belongs in, ask your grants office — miscategorization is a frequent, avoidable error that the grants office or the funder will catch.

🔄 Check Your Understanding: Classify each into the right budget category: (a) a \$3,000 laptop; (b) a \$45/hour statistician hired for 40 hours of analysis; (c) \$50 gift cards for research participants; (d) a \$30,000 portion of the work performed by a partner university; (e) a \$12,000 specialized instrument.

Answer

(a) Supplies (below the typical \$5,000 equipment threshold, so it's in the indirect base); (b) **Consultant** (a defined service for a fee, not your employee — \$1,800 total); (c) Participant support costs (incentives for the people studied, often excluded from the indirect base); (d) Subaward (scope of work performed by another organization with its own budget); (e) Equipment (above threshold, often excluded from the indirect base). Misclassifying (a) or (e) would change your indirect calculation.

11.4 Direct vs. Indirect (F&A) Costs

Here is the most contentious and most misunderstood part of any budget: indirect costs, also called facilities and administrative (F&A) costs or overhead. Direct costs are tied to the project (the staff, the supplies, the travel). Indirect costs are the real but diffuse costs of running the organization that the project uses but that can't be assigned to it line by line: the building, utilities, the accounting and HR departments, the IT systems, administrative leadership. These are genuine costs of doing the work — your project really does use the building and the accounting department — but they can't be itemized per project, so they're recovered as a percentage.

Institutions negotiate an indirect cost rate (for universities and many nonprofits, a federally negotiated rate) that is applied to a base — usually the direct costs, sometimes with certain categories (equipment, participant support, the portion of subawards above a threshold) excluded. Total cost = direct costs + (indirect rate × the indirect base).

💰 Budget Box — Indirect costs: A project has \$100,000 in direct costs, of which \$10,000 is equipment (excluded from the indirect base). The institution's negotiated indirect rate is 40% of modified total direct costs. - Indirect base: \$100,000 − \$10,000 = \$90,000 - Indirect costs: \$90,000 × 0.40 = **\$36,000 - Total project cost: \$100,000 + \$36,000 = \$136,000 Note that the indirect rate applies to the base, not the headline direct total, and that excluded categories (here, equipment) reduce the base. Getting the base right is where budget errors hide.

Indirect costs are contentious because they are invisible — a funder can see the staff and supplies their money buys, but "overhead" feels like money not going to the mission, and some funders (especially foundations) cap indirect rates low (10%, or sometimes zero) or dislike them outright. This creates real tension: indirect costs are genuine costs of doing the work, but funders resist paying them. We'll address how to justify indirect costs to skeptical funders in Chapter 12; here, the budgeting point is to know your institution's rate, apply it correctly to the correct base, and understand each funder's indirect policy (in the announcement) before you build the budget — because a funder that caps indirect at 10% changes your budget math substantially.

🔍 Why Does This Work? (or not): Why do funders resist indirect costs even though they're real? Because of a perception problem: a donor or a member of Congress wants their money "to go to the cause," not to a university's electric bill, even though the cause genuinely can't be pursued without the building. This is partly irrational (the work truly requires the overhead) and partly a legitimate guard against organizations padding overhead. The practical consequence for you: indirect costs are where funder politics meets budget arithmetic. Know the rules, request what you're entitled to where the funder allows it, and be prepared to justify it (Chapter 12) — but never pretend indirect costs don't exist, because then your organization absorbs them, which is unsustainable.

🔄 Check Your Understanding: A project has \$120,000 in direct costs, including \$20,000 of equipment and a \$30,000 subaward (assume only the first \$25,000 of a subaward is in the indirect base). The negotiated indirect rate is 50% of modified total direct costs. What are the indirect costs and the total?

Answer

Modified total direct costs (the base) excludes equipment entirely and the subaward portion above \$25,000: base = \$120,000 − \$20,000 (equipment) − \$5,000 (subaward over \$25K) = \$95,000. Indirect = \$95,000 × 0.50 = **\$47,500. Total = \$120,000 + \$47,500 = \$167,500**. The lesson: indirect applies to the *base*, and getting the exclusions right (equipment, the subaward portion over \$25K) is exactly where budget errors hide — confirm your institution's specific base definition with your grants office.

📜 How We Got Here: The federally negotiated indirect-cost rate exists because, after WWII, the government recognized that funding university research required paying for the infrastructure that made research possible — labs, libraries, administration — not just the direct project costs. Rather than itemize overhead for every grant (impossible), institutions negotiate a single rate with the government, audited periodically. The system is imperfect and perpetually debated (rates vary widely; foundations often refuse to pay full rates), but it reflects a real truth: the work cannot happen without the infrastructure, and someone must pay for it. When a funder caps indirect at 10%, the institution typically absorbs the difference — which is why institutions track which funders pay full rates and why some limit how many low-indirect grants they'll accept.

11.5 Cost-Sharing and Matching Funds

Some funders require cost-sharing (or matching): a commitment that you (or other sources) will contribute some portion of the project's cost, not just the funder. A 1:1 match means you provide a dollar for every dollar the funder provides. Cost-sharing can be cash (other funds you commit) or in-kind (the value of donated goods, services, space, or volunteer time).

Cost-sharing is strategically significant in two ways. First, when required, you must document it credibly, or the proposal is non-compliant — a promised match you can't actually provide is a serious problem. Second, when not required, voluntary cost-sharing can signal commitment ("we believe in this enough to put our own resources in"), but it can also set a precedent and strain your finances, and some funders explicitly discourage it. Read the announcement: know whether cost-sharing is required, allowed, or discouraged, and never promise a match you cannot deliver.

📊 From the Field: In-kind cost-sharing is how many small organizations meet a match requirement without cash they don't have. The value of donated space, volunteer time (at a reasonable rate), donated equipment or services, and partner contributions can often count toward a match — but it must be documented and justified (what's donated, its fair value, how you calculated it). A nonprofit meeting a 25% match largely through documented in-kind contributions is common and legitimate; an undocumented "we'll match it somehow" is not. If you face a match requirement, inventory your in-kind resources early — they're often more substantial than you realize.

A caution on voluntary cost-sharing, because well-meaning applicants overdo it. When a funder does not require a match, the instinct to offer one — "to show our commitment" — can backfire. It sets a precedent (the funder may expect it next time), it strains your finances, and at some funders it actually counts against you, because they want to fund the full cost and a volunteered match suggests you don't need their full support or can't budget honestly. Some federal programs explicitly state that voluntary cost-sharing will not be considered in review, precisely to stop applicants from trying to buy advantage with matches. So unless the funder requires or clearly values a match, budget the full, honest cost and let it stand. Commitment is better shown through a strong, well-justified budget and a credible plan than through a voluntary match that weakens your finances and may not even help.

🪞 Learning Check-In: Cost-sharing surfaces a tension many applicants feel: the urge to appear self-sacrificing and not "greedy" by asking for less or offering to chip in. Notice that urge, because it usually leads to under-budgeting (Section 11.9) or unwise voluntary matches. Reframe it: asking for the full, honest cost of doing good work well is not greed — it's professionalism, and it's what lets you actually deliver. An organization that chronically under-asks to seem modest burns out its staff and fails its mission. The funder wants the work done well, which costs what it costs; your job is to ask for that honestly, not to perform humility by asking for less than the work needs.

11.6 Multi-Year Budgets and Escalation

Most substantial grants span multiple years, and a multi-year budget is not just year one repeated. Costs rise over time — salaries get raises, prices inflate — so multi-year budgets typically apply escalation: a modest annual increase (often 2–4%) to salaries and some other costs. The budget shows each year separately, with escalation applied, plus a total.

💰 Budget Box — Multi-year escalation: A \$25,000 (salary-charged) position in year 1, with 3% annual escalation over three years: - Year 1: \$25,000 - Year 2: \$25,000 × 1.03 = **\$25,750 - Year 3: \$25,750 × 1.03 ≈ **\$26,523 - 3-year personnel subtotal (this position): ≈ \$77,273 Apply escalation to salaries (and fringe, which is a percentage of salary) and to cost categories that genuinely inflate; some categories (a one-time equipment purchase) appear in only one year. Each year's total is its own direct + indirect calculation.

🔄 Check Your Understanding: Why would a one-time \$8,000 equipment purchase appear in only one year of a multi-year budget, while a staff salary appears in every year with escalation — and what does this do to the indirect calculation across years?

Answer

Equipment is a one-time cost (you buy it once), so it appears only in the year you purchase it (often year 1), with no escalation; salary recurs every year and rises with escalation (3% raises, etc.). For indirect: the equipment is typically excluded from the indirect base, so the year it appears it doesn't increase indirect costs, while salary and fringe (usually in the base) drive indirect up each year as they escalate. Each year is its own direct + indirect calculation, so the years won't be identical — which is exactly why a multi-year budget isn't just year one repeated.

Multi-year budgets also reflect the shape of the project: a project might front-load equipment in year 1, ramp up personnel as the work scales, and concentrate evaluation costs in the final year. The budget's year-by-year shape should match the narrative's timeline (Chapter 9) — another instance of the budget-narrative match. A reviewer comparing your timeline to your year-by-year budget should see the same story: if the narrative says recruitment happens in year 1 but the participant-support costs are all in year 3, something is inconsistent.

For a single-year project like RYCC's, the full budget pulls the categories together (composite, illustrative):

(RYCC scales effort or trims to bring the request near its \$50,000 target — a real budgeting decision.) Notice the budget tells the same story as the narrative: instructors and a coordinator deliver classes at three sites (personnel), materials and laptops equip them (supplies), family events and incentives drive engagement and retention (participant support, the attrition contingency from Chapter 9), and a modest indirect reflects the foundation's cap. A reviewer reading this budget alongside RYCC's narrative sees one coherent project — every line explained by an activity, every activity funded by a line.

11.7 The Budget Must Match the Narrative

We have stated the threshold concept; now make it a practice. Before any budget is final, check it against the narrative in both directions:

• Narrative → budget: for every activity, person, piece of equipment, and resource the narrative mentions, is there a corresponding budget line? (An activity with no money behind it is a hole.)
• Budget → narrative: for every budget line, is there an activity in the narrative that requires it? (A line with no narrative behind it is an orphan the reviewer will question.)
• Internal consistency: does the budget total in the table match the total stated in the text? Do the year-by-year totals sum correctly? Does the budget shape match the timeline?

⚠️ Common Pitfall: The mismatched total — a budget table that sums to \$148,000 while the text says "we request \$150,000," or a budget justification (Chapter 12) that describes costs adding to a different number than the budget table. These arithmetic inconsistencies are catnip for reviewers: they're easy to spot, they signal carelessness, and one of them makes a reviewer distrust every other number. Before submission, verify that every total matches everywhere it appears — table, text, justification, and any system-entered fields. This is the version-control discipline from Chapter 4 applied to numbers.

🔄 Check Your Understanding: A reviewer reads in the narrative that the project will hire a full-time evaluator and conduct a 200-participant survey, but the budget has no evaluator line and only \$300 for "data collection." Name the two budget-narrative problems and what each signals.

Answer

Two budget holes: the evaluator the narrative promises has no personnel/consultant line (the activity isn't funded), and a 200-participant survey cannot be done for \$300 (the cost is implausibly low for the described activity). Each signals that the budget and narrative were built separately — the reviewer now doubts whether the evaluation will really happen as described, and starts checking the rest of the budget for similar gaps. The fix: fund every promised activity at a realistic level, and reconcile the narrative and budget line by line.

🪞 Learning Check-In: Notice whether you're tempted to build the budget separately from the narrative — to write the prose, then "do the budget" as a distinct task. That separation is exactly what produces mismatches. The better practice is to build them together, or to build the budget directly from the narrative, line by line, treating each as a check on the other. If building the budget reveals an activity you can't afford, that's valuable information about your narrative (you may be over-promising); if it reveals a cost with no purpose, that's information too. The budget and narrative should be developed as one act, because they are two views of one project.

11.8 Budget Formats

Funders use different budget formats, and using the right one is part of compliance (Chapter 15). The major types:

• NIH modular budget: for smaller NIH grants (direct costs at or below a threshold, historically \$250,000/year), the budget is requested in \$25,000 "modules" rather than itemized in detail — a simplified format. You still build a real budget internally; you just present it in modules.
• NIH detailed (R&R) budget: for larger grants, a fully itemized budget by category and year, entered in the federal forms.
• Foundation budgets: usually simpler — often a one-page table of categories with a brief narrative — but foundations vary widely; follow each funder's template, and watch their indirect-cost cap.
• Government (non-NIH) budgets: typically detailed, on agency-specific forms (e.g., the SF-424 family for federal grants), with categories matching the federal standard and often a required budget narrative.

📊 From the Field: The NIH modular budget confuses newcomers, so it's worth clarifying: "modular" does not mean "you don't need a real budget." You still build a detailed, accurate budget internally — you must know your actual personnel, supplies, and other costs — but you present the request in round \$25,000 modules rather than itemizing every line on the form. So a project that really costs \$237,000 in direct costs is requested as 10 modules (\$250,000) or 9 (\$225,000), rounded sensibly, with the budget justification (Chapter 12) explaining the personnel and any unusual costs. The modular format simplifies presentation, not planning: a reviewer and a grants office still expect the underlying numbers to be real and defensible, and you'll need them to manage the award if funded. Never treat "modular" as license to guess at a round number — build the real budget, then express it in modules.

✅ Best Practice: Use the funder's exact required format and forms, and follow their categories and caps. Building a beautiful budget in the wrong format wastes effort and risks non-compliance. Get the template early (it's in the announcement or the forms package), build into it, and confirm with your grants office that you're using the current version. The strategic budgeting in this chapter is what numbers to put where; the format is how to present them — and both matter.

Reading the budget instructions carefully is as important as reading the rest of the announcement (Chapter 3), because budgets carry hidden rules that catch the unwary. Funders specify what costs are allowable (some prohibit certain expenses — equipment, food, certain travel, fundraising costs); they set caps (on indirect rates, on total request, sometimes on salary — federal grants have a salary cap above which the funder won't pay); they prescribe categories and forms (use theirs, not yours); and they may restrict rebudgeting (moving money between categories after award). A cost that's perfectly reasonable but unallowable under this funder's rules is a compliance problem, and a budget that exceeds a cap can trigger rejection or forced reduction. The grants office is your ally here (Chapter 4) — they know your institution's rates and many funders' rules — but you must read the specific announcement's budget instructions yourself, because the rules vary by program and change over time. The budget is where compliance (Chapter 15) and arithmetic meet, and both must be right.

11.9 Common Budget Mistakes

Budgets fail in recognizable ways:

• Underbudgeting: requesting too little to actually do the work, which looks naive and sets you up to fail if funded. Reviewers know what things cost; a budget that's implausibly lean reads as inexperience.
• Overbudgeting: padding, round numbers that look made-up, or costs out of proportion to the work — which looks wasteful and invites cuts.
• Missing categories: forgetting fringe, leaving out the evaluation costs your evaluation plan requires, omitting the indirect costs your organization will actually incur.
• Budget-narrative mismatch: the orphans and holes and total mismatches of Section 11.7.
• Wrong format or wrong indirect treatment: using the wrong forms, applying the indirect rate to the wrong base, or ignoring a funder's indirect cap.
• Implausible effort: personnel effort too low (or too high, exceeding 100% across commitments) to be credible.

The under- versus over-budgeting tension deserves a closer look, because applicants feel pulled toward both errors at once. The fear of looking expensive pushes toward under-budgeting — shaving effort, omitting costs, requesting less than the work needs — which feels strategically safe but isn't: a reviewer who knows what the work costs reads an implausibly lean budget as naivety ("they don't understand what this takes") or as a setup for failure ("they can't actually do this for that"). The opposite fear, of leaving money on the table, pushes toward over-budgeting — padding, round numbers, generous estimates — which reads as wasteful and invites cuts that may leave you underfunded anyway. The resolution is neither high nor low but accurate and justified: budget what the work genuinely costs, build each number from a real basis (a real salary, a real quote, a real rate), and let the budget justification (Chapter 12) explain why each is necessary. A reviewer trusts an accurate, well-justified budget far more than a suspiciously cheap or a comfortably padded one — the same honesty principle that governed the needs section (Chapter 8) applied to dollars. Reviewers have seen thousands of budgets; they know what things cost, and the budget that matches their sense of real costs, neither shaving nor padding, is the one they trust. The deepest budgeting skill, in the end, is honesty applied to numbers: ask for what the work genuinely costs, justify it clearly, and let the reviewer see a true accounting rather than a strategic guess. A budget built that way needs no defending beyond its own evident reasonableness — which is exactly the foundation on which the next chapter's justification builds.

📐 Project Checkpoint — Build your line-item, multi-year budget: For your project and funder, (1) build a line-item direct-cost budget by category, each line traced to a narrative activity. (2) Calculate personnel properly (salary × effort + fringe) for each person. (3) Apply your institution's indirect rate to the correct base (respecting the funder's cap). (4) If multi-year, build each year with escalation. (5) Apply cost-sharing if required (documented, including in-kind). (6) Use the funder's required format. (7) Run the budget-narrative match in both directions and verify every total agrees everywhere. Save it in your "My Proposal" document; Chapter 12 turns this budget into a justification that defends every line.

Spaced Review

Retrieve these from earlier chapters without looking back.

1. (From Chapter 9) Your approach described activities. What must the budget do with respect to them, and what's a "budget hole"?
2. (From Chapter 10) Your evaluation plan may require an external evaluator and data collection. Where do these appear, and why must they?
3. (From Chapter 5) How is the budget-narrative match an instance of the coherence principle, and why is one mismatch so costly?

Answers

1. Every activity in the approach must have a corresponding budget line that funds it; an activity with no money behind it is a "budget hole" — the reviewer asks how you'll do work you haven't funded. 2. As budget lines (the external evaluator as a consultant/subaward cost; data collection as supplies, staff time, incentives). They must appear because an evaluation plan the budget doesn't fund isn't a real plan — and the mismatch breaks coherence. 3. The budget and narrative are two views of one project (Chapter 5's "one argument"); a mismatch means they disagree, and the reviewer can't tell which to believe. One visible inconsistency makes the reviewer distrust every number — coherence is a single credibility asset.

Chapter Summary

Key Takeaways

• The budget is strategy, not arithmetic — a story in numbers that reviewers read critically. Too low looks naive; too high, wasteful; inconsistent, careless.
• The budget must match the narrative exactly (threshold concept): every activity has a number, every number has an activity, and every total agrees everywhere. Build them together.
• Personnel (the largest category) = salary × effort + fringe. Effort must be realistic and consistent with the narrative and the person's other commitments. Never forget fringe (25–35%).
• Build direct costs by category (equipment, supplies, travel, participant support, consultants, subawards, other), each traced to a narrative activity.
• Indirect (F&A) costs are real but diffuse overhead, recovered as a rate × a base (with exclusions). Funders resist them; know your rate, apply it correctly, and respect each funder's cap.
• Apply cost-sharing/matching where required (documented, including in-kind), and escalation (2–4%/year) in multi-year budgets, with the budget's year-by-year shape matching the timeline.
• Use the funder's required format (NIH modular/detailed, foundation, government forms). Avoid the recognizable mistakes: under/over-budgeting, missing categories, mismatches, wrong format/indirect treatment, implausible effort.

Action Items

• Build the line-item, multi-year budget, each line traced to an activity.
• Calculate personnel (salary × effort + fringe) and indirect (rate × base) correctly.
• Run the budget-narrative match in both directions; verify all totals agree.

Common Mistakes to Avoid

• Building the budget separately from the narrative (→ mismatches).
• Forgetting fringe; applying indirect to the wrong base; ignoring the funder's cap.
• Under- or over-budgeting; implausible effort; wrong format.

Decision Framework: Is your budget ready?

Ask: (1) Does every activity have a line and every line an activity? (2) Is personnel computed with effort and fringe, at credible effort levels? (3) Is indirect applied to the right base, within the funder's cap? (4) Is it built in the funder's format, with escalation and any required match? (5) Do all totals agree everywhere? Any "no" is your next revision.

Looking Ahead

Your budget is a table of numbers. By itself, a number is just a claim; it becomes persuasive when you explain why it's necessary. Chapter 12: The Budget Justification teaches you to write the narrative companion to the budget table — justifying each line as "necessary and reasonable," explaining personnel effort and major purchases, defending indirect costs to skeptical funders, and turning the budget from a list of costs into a persuasion document where every dollar is visibly essential. The budget says what; the justification says why.

Before moving on, notice that the budget completes a pattern running through all of Part II: each component is bound to the others by coherence, and the budget binds to all of them at once. It funds the personnel who carry out the approach's activities (Chapter 9), the data collection and evaluator the evaluation plan requires (Chapter 10), and the resources the capacity section will claim (Chapter 13), and it must total the amount your aims or executive summary requested (Chapters 6–7). This is exactly why the budget is so revealing to a reviewer: because it touches every other section, an inconsistency anywhere surfaces here. A budget that fits the whole proposal is the clearest signal that the proposal was designed as one coherent thing; a budget at odds with any section is the clearest signal that it was assembled from parts. Build it from everything that came before, and let it serve as the final check that the whole proposal holds together — then write the justification that defends it.

Continue to the Exercises, the Quiz, and the two Case Studies (1, 2). The Key Takeaways card is your quick-review anchor.

Next: Chapter 12 — The Budget Justification: Why Every Dollar Matters and How to Explain It.