---
name: grant-proposal
description: Use when asked to write a grant proposal — a formal application requesting funding from a foundation, government body, or other grantmaker for a specific project or program, covering need, objectives, budget, and evaluation — as distinct from the ongoing relationship work of [[donor-management]] with individual donors.
---

# Grant Proposal

A grant proposal is a formal application requesting funding from a
foundation, government body, or other grantmaker for a specific
project or program. Unlike general fundraising outreach, it's written
for one funder at a time, against that funder's own stated priorities
and application requirements, and it has to make the case for both
the need and the organization's ability to deliver on it.

## Key components

- **Statement of need** — a clear description of the problem the
  project addresses, backed by evidence (data, prior findings, direct
  experience) rather than assertion alone.
- **Objectives** — specific, measurable goals the funded project will
  achieve, stated so they can later be reported against.
- **Budget** — a realistic, itemized cost breakdown that matches what
  the narrative actually describes doing — every activity described in
  the narrative should show up in the budget, and every line in the
  budget should trace back to something the narrative describes.
- **Evaluation plan** — how success will be measured during and after
  the project, and how that will be reported back to the funder.
- **Organizational capacity** — evidence the organization can actually
  deliver what it's proposing: relevant experience, staffing, and
  track record.
- **Timeline** — when major activities and milestones will happen
  across the funding period.

## Why matching the funder's priorities matters

Grantmakers publish what they fund and why, and reviewers score
proposals against those stated priorities specifically — a proposal
can be well written, well justified, and still get rejected if it
doesn't speak to what that particular funder has said it cares about.
Matching priorities isn't cosmetic language-matching; it means
choosing which aspects of the project to emphasize, which evidence to
lead with, and which objectives to foreground based on what this
funder has said matters to them, and following their specific
application format and requirements exactly.

## Common pitfalls

- **Generic proposal sent to many funders unchanged** — reusing the
  same narrative everywhere, without adapting it to each funder's
  stated priorities and required format, reads as generic to reviewers
  who compare it against proposals written specifically for them.
- **Ignoring stated priorities and requirements** — skipping a
  funder's specific application instructions (page limits, required
  sections, formatting) or failing to address what they've explicitly
  said they fund signals the proposal wasn't written with them in mind.
- **Budget that doesn't match the narrative** — a narrative describing
  activities the budget doesn't cost out (or a budget with costs the
  narrative never explains) undermines confidence that the plan is
  real and fully thought through.
- **Vague objectives** — goals stated too broadly to be reported
  against later leave the organization with nothing concrete to show
  the funder once the grant period ends.
- **Evaluation plan added as an afterthought** — bolting on a
  generic evaluation section rather than designing it around the
  actual stated objectives makes the eventual report to the funder
  weaker than it needs to be.

## Learn more

- [[donor-management]] for the ongoing relationship practice with
  individual donors, distinct from a one-time application to a
  specific funder.
- [[smart-criteria]] for writing objectives that are actually
  measurable and reportable.
- [[training-needs-analysis]] for the same evidence-first discipline —
  confirming a real, specific gap — applied before designing a training
  program instead of a funding request.