MavenlyMavenly
    Field Notes

    Practice · 11 min read

    How to write a budget narrative that actually justifies the budget.

    Most budget narratives describe what the money is for. The good ones explain why each line item is the right shape — why this many staff, this much overhead.

    The Mavenly Team·Mavenly Practice Team·February 20, 2026

    A weak budget narrative restates the spreadsheet in sentences. Personnel: two program coordinators at $58,000 each, plus benefits at 22%. Supplies: curriculum materials for 70 students. The reviewer already has the spreadsheet. You have spent a page telling them what they can read in a table.

    A strong budget narrative answers a different question, and it is the question the reviewer is actually holding: why is this the right shape for the money?

    Every line should carry a justification of form, not just of purpose. Not 'two program coordinators at $58,000' but 'two coordinators because the caseload ratio that produced our 84% retention outcome was 1:35, and this cohort is 70 students.' The second version turns a cost into evidence of operational thinking, and it makes the number difficult to trim without an argument.

    That is the underlying mechanic worth understanding. Budgets get cut in review, often arbitrarily, by people looking for a defensible way to fund more applicants with a fixed pool. A line with no stated logic is the easiest thing in the world to reduce by fifteen percent. A line tied to a ratio that produced a documented outcome forces the reviewer to argue with the outcome instead.

    Salaries deserve particular care because reviewers scrutinize them hardest and applicants explain them least. Name the role's function in the theory of change, not just its title. If the position is partially allocated, say what the other portion does and who pays for it. Unexplained partial FTEs read as budget-filling even when they are entirely legitimate.

    Overhead deserves the same treatment and almost never gets it. Reviewers discount indirect rates they do not understand, and many funders have internalized a norm that low overhead signals efficiency — a norm that is analytically wrong and operationally destructive, but real. A single sentence tying overhead to specific shared functions usually settles the question: finance, evaluation capacity, and the compliance reporting the funder itself requires are all paid for from indirect, and pointing that out is fair.

    If your negotiated federal rate exceeds what the funder allows, say so explicitly and state what the organization is absorbing. Absorbing cost silently teaches funders that the cost does not exist.

    Match and leverage should be described in a way that shows durability. In-kind contributions that will disappear the moment the grant ends are worth less than a smaller committed cash match, and a reviewer who has been burned before will read an inflated in-kind figure as inexperience.

    Then there is the paragraph that most narratives omit and that we think does the most work: name the number's sensitivity. What gets cut first if the award comes in at 70% of the request? What breaks entirely below 50%? Which line is genuinely fixed?

    Two things happen when you include it. Funders read it as operational maturity — you have thought about the failure mode, which suggests you will manage the money carefully. And it frequently prevents an arbitrary trim, because the reviewer now knows that cutting the evaluation line does not save 8% of the budget, it invalidates the outcome data the funder wants in the final report.

    A few mechanics that consistently help. Order the narrative to match the budget table exactly, so the reviewer can read them side by side. Use the same labels in both, without exception. Round in the narrative and be exact in the table. Keep unit-cost math visible: 70 students × $310 in materials is more persuasive than $21,700, because it shows the number was derived rather than chosen.

    And check the arithmetic independently, by someone who did not build it. Nineteen of the twenty-seven organizations we interviewed had no second reviewer on budget math. Arithmetic errors are the most preventable and most credibility-damaging mistake in the entire application.

    The test for a finished budget narrative: hand it to someone who has never seen your programs and ask them to explain, in their own words, why you need this much money. If they can do it, the reviewer can defend it internally. That is the whole job.