Writing the Proposal
Budgets and the Justification Nobody Reads Carefully Enough
Direct and indirect costs, why overhead is real work rather than waste, and how a budget quietly tells a reviewer whether you have done this before.
Experienced reviewers read the budget early, sometimes first. It is harder to write persuasively than prose and therefore harder to fake: a budget that does not match the narrative reveals a project nobody has actually planned, and a budget costed as though nothing will ever cost more than quoted reveals someone who has not run one.
Experienced reviewers often read the budget early, sometimes before anything else. It's much harder to fake than prose. A budget that doesn't match the narrative shows a project nobody has really planned, and one costed as though nothing will ever cost more than quoted shows someone who's never run a project.
People who read a lot of these often look at the numbers first.
Numbers are much harder to fake than words. If the numbers don't match the story, they can tell straight away that nobody really planned it.
Direct and indirect
Direct costs are attributable to the project: the staff time spent on it, the materials it consumes, the travel it requires, the space it uses.
Indirect costs keep the organization running so the project can happen at all — accounting, insurance, rent on the office nobody's timesheet is charged to, the person who processes payroll. Real costs, genuinely caused by doing the work, and impossible to assign line by line.
Funders often cap indirect costs at a percentage, and some refuse them entirely. Read that rule before budgeting, because a project fully funded on direct costs and unfunded on indirect ones can still lose your organization money.
Some costs belong to the project itself — the people doing it, the supplies it uses, getting there.
Other costs keep the whole organization alive so the project can happen at all: the lights, the insurance, the person who does the paperwork. Those are real too, but you can't point at one and say "that light bulb was for this project."
Some funders will only pay for the first kind, which is worth knowing before you plan.
Video coming soon
This lesson explains the idea in full without it.
The justification
The budget justification explains each line: what the number is, how you arrived at it, and why the project needs it. It is where a budget stops being a list and starts being an argument.
The pattern is the same for every line — quantity, rate, and purpose. Not "Staff: an amount," but a role, at a stated fraction of time, for a stated period, doing a stated thing named in the method section. A reviewer should be able to trace every number back to an activity, and every substantial activity forward to a number.
That traceability is the actual test. If the narrative promises evening sessions and the budget has no evening staffing, one of the two is fiction — and the reviewer does not know which, which is worse for you than either.
The budget justification explains each line: what the number is, how you got it, and why the project needs it. It's where a budget stops being a list and becomes an argument.
Every line follows the same pattern — how many, at what rate, for what. Not "Staff: an amount," but a role, for a stated share of their time, over a stated period, doing something named in the method section.
That's the real test. If the narrative promises evening sessions and the budget has nobody working evenings, one of them is made up — and the reviewer can't tell which, which is worse for you than either.
For every number, say three things: how many, how much each, and what it's for.
The important part is that the numbers and the story have to match. If you said you'd run something in the evenings, there has to be money in there for someone to be there in the evening.
If they don't match, the person reading knows one of them isn't true — they just don't know which one.
Match, and what it really costs
Some funders require cost share — a portion of the project you cover yourself. It can be cash, or it can be an in-kind contribution: donated space, volunteer hours, loaned equipment, given a documented dollar value.
Two things to know. In-kind contributions have to be substantiated, not estimated generously, and you will be reporting on them. And a match requirement is a real cost even when nothing leaves your bank account — volunteer hours you commit are hours somebody has to actually work.
Sometimes a funder says they'll pay for part of it if you cover the rest. Your part doesn't always have to be money — it can be a room somebody lends you, or people helping for free.
But it has to be real and you have to keep track of it. Promising twenty volunteer hours means twenty hours somebody actually has to show up for.
Key takeaways
- Reviewers read budgets early because a budget is much harder to fake than prose.
- Direct costs attach to the project; indirect costs keep the organization that delivers it running.
- Low overhead signals fragility, not efficiency — present indirect costs, do not apologize for them.
- Every line needs quantity, rate, and purpose, and must trace to an activity in the narrative.
- Underestimating does not improve your chances; a budget too thin to survive is a reason to decline.
- Budgets get read early because they're harder to fake than prose.
- Direct costs belong to the project; indirect costs keep the organization running.
- Low overhead means fragile, not efficient.
- Every line needs how many, at what rate, for what — and must match the narrative.
- Asking for too little doesn't help; it signals a project that won't survive.
- People often look at the numbers first, because numbers are hard to fake.
- Some costs belong to the project; some keep the whole organization alive.
- An organization that spends nothing on itself is fragile, not careful.
- The numbers and the story have to match each other exactly.
- Asking for too little doesn't help you win.
Check your understanding
Question 1 of 4