Grant Writing

A grant is a request to a specific funder, not a brochure with a new cover letter. The 80/20 of grant writing is the part a reviewer can score: what you will do, what it costs, and why this organization can do it.

Start from their question

Read the guidelines for the decision, not for the formatting. What change do they want, for whom, by when? Write that answer in one sentence before you open a narrative template. If your project does not answer it, another adjective will not help. A different funder might.

Fit with the funder's priorities is the first filter. Research the mission, recent awards, and the language they use for success. A polished proposal that aims at a different outcome still loses. Build a calendar around funders whose priorities already match your work instead of applying everywhere and swapping the name on the cover.

Experienced writers treat a small portion of each proposal as the decision weight: the fit story, the problem and solution, the outcomes, and the budget that proves the plan. Formatting matters because guidelines say it does. It does not replace those four. When time is short, protect them first.

The budget is the argument

A budget that matches the story is more persuasive than a story that waves at the budget. Name the few costs that make the work possible. Cut lines that exist so the total looks familiar. If you cannot explain a line in a sentence, it is not ready.

Alignment goes both ways. Questionable or orphaned line items make reviewers doubt delivery even when the narrative sings. Staff time, materials, access, and evaluation should appear because the plan needs them, not because the categories were available. Read each cost beside the sentence that depends on it.

Proof is past work, not adjectives

Reviewers look for a sign you have done something like this, or that a partner has. One concrete example beats a page of mission language. Stories from existing work, paired with clear metrics you already track, give the example weight. If the example is thin, say what you will learn in the first month instead of pretending the organization is older than it is.

Reusable core content - mission, track record, key facts - can save time. The problem statement, outcomes, and funder language still need to be written for this opportunity. Send fewer, better-matched proposals rather than the same text with the name swapped.

Turn the guidelines into a reading path

Before drafting, mark the funder's nouns and verbs: the population, the place, the outcome, and the work they will fund. Then mirror that order where it helps the reviewer find the answer. Matching the question is not parroting the guidelines. It is removing the cost of translating your project into their decision.

Make a small requirement list with the page, limit, attachment, and person responsible for each item. A beautiful narrative can still fail when a required budget note is missing. Compliance is not the most inspiring part of the proposal, but it protects the parts that deserve to be read.

Outcomes need a visible chain

Connect the work to a change the funder can recognize. If you will provide sessions, say what participants will be able to do afterward and how you will notice that change. Do not turn every hope into a guaranteed result. A modest measure that fits the work is more credible than a grand number with no way to observe it.

A vague or overly broad goal is a common reason for rejection. Defining a specific, well-supported problem and a focused, realistic solution builds credibility faster than passionate but unquantified promises. Give the budget the same logic as the outcomes: every major cost should make a scorable piece of the plan possible.

Edit as a reviewer with one tired hour

Read only the first sentence of every paragraph. Can the reviewer reconstruct the project? Then read the questions in the application and point to the answer in your draft. Replace mission language with the people, place, and action that the grant would support. Ask a colleague outside the project to underline the sentence they trust and circle the one they cannot score. If they cannot explain back what you do, reviewers may struggle as well.

Submit fewer proposals when the match is weak. A tailored request can reuse honest building blocks, but it cannot reuse the funder's reason for caring. That reason belongs to the particular opportunity.

Keep evidence proportional to the claim. A local record, partner letter, prior project, or clearly described need may be enough to establish context; it does not need to pretend to be a national study. Explain what is known, what the project will learn, and who is accountable. Reviewers can support a plan they can understand, even when the organization is still building its history.

After each round, keep a short note on feedback and outcomes. Which funders and messages returned attention for the effort? That record decides the next calendar more honestly than optimism alone. A team that used to spray generic proposals often improves by writing fewer applications and investing the saved hours in funder-specific problem statements, measurable outcomes, and budgets that match the narrative exactly.

Grant writing is both craft and triage. Clarity beats volume. The goal is not endless rewriting for every open call. It is a shorter list of requests where a tired reviewer can still find a fundable plan.

8020 move: Before drafting the next narrative, write the funder's desired change in one sentence, list the budget lines that make that change possible, and name one piece of past work that proves you can start. If any of the three is blank, do not open the template yet.

Keep returning to the answer a reviewer must be able to score. When a draft feels long but unclear, shrink the question: fit, problem, outcome, budget. Those few pieces carry most of the decision. Everything else is support, not a substitute.