menu

How to Write a Grant Proposal That Gets Funded


How to Write a Grant Proposal That Gets Funded

Most grant proposals fail for boring reasons: the budget doesn't match the narrative, the outcomes are vague, or the reviewer can't find the ask. None of that requires genius. It requires knowing what reviewers actually check and in what order.


Start With the Funder, Not the Idea


Before you type a single sentence, spend an hour reading the funder's guidelines like a checklist. What problem do they say they want solved? What size grants do they usually make? Look at their past awards page if they have one. A proposal that answers their stated priorities beats a more elegant proposal that doesn't. If you can't describe the funder's mission in one sentence without looking, you're not ready to write.


Write the Problem Statement With Numbers


Reviewers skim. The problem statement has to make them stop. Use one concrete figure, one human detail, and one sentence about who is affected. For example: "Last year, 42 percent of students in our district missed more than ten days of school, and the district has one counselor for every 600 kids." That's a problem statement. "Youth face many challenges today" is not. Pull your numbers from public data, your own records, or a survey you can describe in a footnote. Cite the source in one line so it's checkable.


Make the Budget Match the Narrative


This is where more proposals die than anywhere else. If your narrative says you'll hire a part-time coordinator, the budget line for that coordinator has to show up with the same title and roughly the same cost. Reviewers read the budget against the program description line by line. Round numbers look invented; use real quotes where you can. Include a short note for anything that looks odd, like a high travel line or a large equipment purchase.


Say What Success Looks Like in Measurable Terms


"Improved outcomes" is not an outcome. "80 percent of participants will complete the 12-week program, and 60 percent will report a wage increase within six months" is. Pick two or three measures you can actually track without hiring a consultant. Explain how you'll collect the data, who enters it, and how often you'll review it. Funders care less about ambitious targets than about whether you have a real plan to know if you hit them.


Show You've Done This Before (or Explain Why You Haven't)


If you have a track record, give one specific example: a prior program, what it achieved, and what you learned from it. If you're new, don't pad the section. Say plainly what your team has run before, what support you've lined up, and what you'll do in the first 90 days. Reviewers can tell when an organization is inventing capacity. Honest small is better than inflated.


Practical checklist before you submit


  • Read the guidelines once for requirements and once for priorities.
  • Confirm every narrative activity has a matching budget line.
  • Check that each outcome has a number and a data source.
  • Have someone outside your team read the first page and tell you what you're asking for.
  • Submit a day early; portals crash on deadlines.

Frequently Asked Questions


Q1: How long should a grant proposal be?

Follow the funder's page limit exactly; going over is a common reason proposals get rejected unread. If there's no limit, aim for the shortest version that covers the problem, the plan, the budget, and the outcomes. Reviewers read dozens of these, so clarity wins over length.


Q2: What's the most common mistake in a grant budget?

Mismatched numbers between the narrative and the budget spreadsheet. If your program description mentions three staff and the budget funds two, a reviewer will notice. Build the budget from the same activity list you wrote in the narrative, not separately.


Q3: Do I need a logic model?

Only if the funder asks for one. Many small grants don't require it, and a forced logic model can make a simple program look confused. If they do ask, keep it to one page: inputs, activities, outputs, outcomes. Don't bolt one on to look professional.


If you want a plain-language walkthrough of the application steps before you start drafting, try the free tool — it takes seconds.




Comments