Writing a winning grant narrative: structure, tone, and the 3 things reviewers look for

Reviewers read 15–20 applications in a week. They're scoring against a rubric, on a deadline, probably at 9pm after their day job. Your narrative should be so easy to score that they can hand you points without re-reading.

The 3 things reviewers actually look for

1. Is this project likely to work? (Does the applicant know what they're doing?)
2. Is the budget realistic? (Not too high, not suspiciously low.)
3. Will this have lasting impact? (Or does everything stop when the grant ends?)

Structure that reads well

Mirror the NOFO's scoring headings exactly. If the rubric says "Project Design (40 points), Organizational Capacity (25), Budget (20), Evaluation (15)," your narrative's H2s should be exactly those. Don't invent new ones.

Under each H2, use short paragraphs (2–3 sentences) and bulleted lists. Reviewers skim.

Tone

• Specific beats vague. "We'll serve 200 families" beats "We'll serve many families."
• Past evidence beats future claims. "Last year we placed 87 people in jobs at an 81% retention rate" beats "We have a strong track record."
• Numbers with context. "A 15% reduction — down from the state average of 22%" beats "A 15% reduction."

Red flags reviewers hate

• Over-promising: "We will end homelessness in Anytown." No, you won't.
• Overlap: Repeating the same paragraph under 3 different sections.
• Budget mismatch: Narrative says 2 staff, budget shows 4 salaries.
• Weak evaluation: "We'll distribute a survey at the end." Specify WHICH survey, baseline, and statistical test.

The final check

Before submitting, run through this:

• [ ] Each H2 matches a scoring criterion
• [ ] Every claim has a number or a citation
• [ ] Budget justifies every line item tied to a narrative activity
• [ ] Evaluation plan includes baseline, method, timeline, and who analyzes the data
• [ ] Sustainability plan names specific sources of continuation funding