How to Write a Winning Grant Application

Understanding what funders want

Before you write a single word, invest serious time in understanding your funder's priorities. Most grant failures happen not because the applicant's work is weak, but because the application doesn't demonstrate alignment with what the funder is actually trying to accomplish.

Read the program announcement in full — not just the eligibility criteria and deadline. Look for the program's stated goals, its theory of change, its evaluation criteria, and any examples of previously funded work. If the funder has a website, study their funded projects. If they have an annual report, read it. The more clearly you can see the world through the funder's eyes, the more persuasive your application will be.

Pay attention to language. If the announcement repeatedly uses terms like "systems change," "equity-centered," or "evidence-based" — mirror that language in your proposal. Not as mimicry, but because it signals that you understand the funder's framework.

The anatomy of a grant application

Most grant applications share a common structure, though the specific sections and word limits vary. The core components are:

• Executive summary / abstract: A concise overview of your organization, the problem, your proposed approach, and what you're asking for. Write this last — it's easier once you've written everything else.
• Statement of need: Why does this problem exist, why does it matter, and why is your community or field in need of this intervention? Use data, but don't let data overwhelm narrative.
• Project description / narrative: What you'll do, how you'll do it, and why your approach is likely to work. Be specific. Vague goals produce vague results — and reviewers know it.
• Evaluation plan: How you'll know if the project succeeded. Most funders require measurable outcomes. Define them in advance and tie them to your activities.
• Organizational capacity: Why your organization is positioned to execute this project. Relevant experience, key staff, partnerships.
• Budget and budget narrative: A detailed line-item budget with a written justification for every cost.

Common mistakes that disqualify applicants

Many applications are eliminated before a reviewer even reads the narrative — because they failed to follow the instructions. The most common disqualifiers:

• Missing or incomplete required attachments (letters of support, audited financials, 501(c)(3) determination letter)
• Exceeding page or word limits
• Using the wrong font size, margin size, or file format
• Submitting past the deadline — many portals are hard-cutoff
• Proposing activities outside the stated scope of the program
• Failing to demonstrate eligibility (wrong organization type, geography, or budget size)

Build a compliance checklist from the application instructions before you start writing. Check it again before you submit.

How to address evaluation criteria

Most grant announcements include a scoring rubric — either explicit (e.g., "Section A is worth 30 points") or implicit (e.g., ordered list of review criteria). This rubric is the single most important document in your application strategy.

Allocate your effort proportionally. If innovation is worth 10 points and capacity is worth 30 points, spend three times as much effort demonstrating your organizational capacity. Reviewers score what the rubric asks them to score — make their job easy by making it obvious that you meet each criterion.

Where possible, use the same section headers as the evaluation criteria. Some reviewers are looking for specific sections to score — if they can't find yours, they may undercount you even if the content is there.

Budget narrative best practices

The budget narrative (sometimes called a budget justification) is your opportunity to explain every line in your budget. It's often underinvested in, but reviewers — especially program officers — read it carefully.

For each line item, explain: what it is, how it was calculated, and why it's necessary for the project. Avoid vague justifications like "supplies as needed." Instead: "Office supplies for project team of 4 staff, estimated at $50/person/month for 12 months ($2,400)."

Be realistic. Reviewers have seen enough budgets to spot padding and to spot underfunding. Both raise questions. If your project genuinely costs $250,000, don't ask for $150,000 hoping to seem conservative — reviewers will wonder how the other $100,000 gets covered, or whether the project is actually feasible.

If there's a cost-share or matching requirement, address it explicitly. Explain your matching sources, document that they're committed, and make clear they meet the funder's matching definition.