TLDR
A grant narrative is the argument for why your organization should receive this grant, written for a reviewer who doesn't know your organization or your community. Strong narratives start with the RFP, build from a specific needs statement, and treat the evaluation plan as a strength rather than a formality.
Grant narrative writing is not a writing problem. It’s a thinking problem. Organizations that struggle with grant narratives usually have one of three issues: they don’t fully understand what the funder is looking for, they know their work so well they can’t explain it to an outsider, or they write the narrative before they’ve thought through the evaluation plan.
This guide addresses all three. It assumes you already know the basics of grant proposals and focuses on the craft decisions that separate competitive narratives from generic ones.
Start with the RFP—Really Read It
Before you write a single sentence of narrative, read the RFP—request for proposals, funding guidelines, or letter of inquiry instructions—closely enough to find the evaluation criteria.
Every funder has evaluation criteria, whether they’re explicit (a scoring rubric attached to the application) or implicit (embedded in the priorities and language of the guidelines document). The evaluation criteria tell you exactly what the reviewer is being asked to assess when they read your narrative.
If the RFP has an explicit scoring rubric, that rubric is your outline. If a section is worth 25 points and another is worth 10, weight your narrative accordingly.
If the RFP does not have an explicit rubric, read the guidelines language carefully for what the funder emphasizes. Funders who use phrases like “evidence-based approaches” and “documented outcomes” are telling you that rigor and evaluation matter. Funders who emphasize “community voice” and “resident leadership” are telling you that participation and bottom-up design matter. Write to what they value, using their language.
Read the RFP twice: once to understand the full picture, once to annotate every requirement, criterion, and priority you identify. Requirements that you miss in your narrative will cost you in scoring; priorities you ignore will signal that you didn’t read carefully.
The Needs Statement: Foundation of the Whole Narrative
The needs statement is the most important section of the grant narrative, and the one most commonly written poorly. Every other section of the narrative depends on having a strong needs statement, because the rest of the narrative is your response to the need you’ve established.
A strong needs statement does four things:
Establishes the scope of the problem with specific, local data. National statistics are weak evidence for a local problem. If you serve a specific county, city, or neighborhood, the data should reflect that geography. A food insecurity statistic for your county is more compelling for a county community foundation than a national hunger statistic.
Sources every factual claim. State agency reports, census data, local needs assessments, peer-reviewed research—every claim of fact should have a citation. Unsourced claims make reviewers uncertain about whether they’re accurate.
Shows the specific gap your program addresses. The needs statement should create a direct line between the problem and your intervention. If you’re describing food insecurity broadly and your program is specifically about SNAP enrollment assistance, the needs statement should establish that a significant portion of food-insecure residents in your area are eligible for SNAP but not enrolled.
Is written for an informed outsider. Assume the reviewer is a professional in the foundation world who may or may not know your community. They should be able to read your needs statement and understand both the problem and why it matters without any prior knowledge of your organization or your geography.
A common mistake: the needs statement is written from the organization’s perspective (“we see many clients struggling with X”) rather than from a documented community perspective (“the county health assessment found that 34% of residents in zip codes 44444 and 44445 have not seen a primary care provider in the past two years”). The second version is evidence. The first version is an assertion.
Making the Funder Connection Explicit
One of the most effective techniques in grant narrative writing is making the connection between the funder’s stated priorities and your program explicit rather than leaving the reviewer to draw the connection themselves.
If the funder’s guidelines say they prioritize programs that “build long-term community resilience through economic empowerment,” your narrative should use those words—not because you’re parroting the funder, but because you’re making clear that you understand what they’re trying to accomplish and that your program contributes to that goal.
Reviewers often read many applications in a short time. Making the connection explicit reduces the work they have to do and reduces the risk that they miss the relevance.
Writing Measurable Objectives (SMART)
Objectives are specific, measurable statements of what your program will accomplish. They are not activities. “We will provide financial literacy workshops” is an activity. “80% of participants will demonstrate knowledge gain on a pre/post financial literacy assessment” is an objective.
SMART objectives are:
- Specific: precisely defined, not vague
- Measurable: can be expressed as a number
- Achievable: realistic for your capacity and timeline
- Relevant: connected to the need you established
- Time-bound: with a defined timeframe
Each objective should connect to:
- The need it addresses (from your needs statement)
- The activity that will achieve it (from your program description)
- The measurement method that will verify it (from your evaluation plan)
When an objective doesn’t connect to all three, something in your narrative is misaligned—fix the gap in the narrative, not just the objective.
A practical note: be careful about setting objectives you can’t actually measure. An objective that requires data you don’t currently collect is either (a) an opportunity to build your data collection capacity, in which case the evaluation plan should describe how you’ll do that, or (b) an objective that will be impossible to report on at year-end. The latter is a compliance problem waiting to happen.
The Program Description
The program description is the section where organizations usually spend the most time and write the most words. It’s often not the section where they should concentrate effort—that’s the needs statement and evaluation plan.
A strong program description answers:
- What does the program do?
- Who does it serve?
- How does the intervention work? (The theory of change: if we do X, then Y will happen because Z)
- What is the timeline?
- What are the evidence-based components? (If applicable—not all programs are evidence-based, and claiming EBP status for a program that isn’t is a credibility problem)
Write the program description for someone who doesn’t work in your sector. Avoid jargon. Explain why your approach works, not just what it does.
A common mistake: spending three paragraphs on the history of the program and the organization’s passion for the work, and one paragraph on how the program actually operates. Funders care about the theory of change and the operational details; they care less about organizational backstory in this section.
The Evaluation Plan as a Strength
Many grant writers treat the evaluation plan as a section to fill—a bureaucratic requirement. Strong organizations treat it as evidence of program quality.
An evaluation plan answers:
- What outcomes are you measuring?
- How are you measuring them?
- Who is responsible for data collection?
- When will data be collected?
- How will results be reported?
The section that most organizations rush through is the measurement methodology. “We will survey participants” is not a methodology. “We will administer a validated pre/post assessment tool (the [specific instrument]) to all participants at program entry and program exit. The assessment measures three outcomes: [list outcomes]. A trained staff member will administer the assessment, and results will be entered into our program database within one week of collection” is a methodology.
Reviewers who read grants from many organizations can usually tell the difference between organizations that actually evaluate their programs and organizations that describe evaluation for grant-writing purposes only. The difference shows in the specificity of the methodology description. Vague methodology descriptions suggest that the organization doesn’t actually collect this data and isn’t sure how it would.
Writing for the Reviewer, Not for Program Staff
This is the most common craft failure in grant narratives. Program staff write about their work in the language of their field, for people who already understand it. Grant narratives must be written for the foundation program officer who may work across many sectors and doesn’t know your terminology.
Test this by giving a draft to someone outside your organization—ideally someone with no sector-specific knowledge—and asking them to tell you: what problem does this organization solve? How does their program work? What will they measure? If the reader can answer all three clearly, the narrative is working. If they’re confused, you need to clarify.
Passive voice is a common problem in grant narratives. “Participants will be served” and “outcomes will be measured” are weaker than “we will serve participants” and “our evaluation team will measure outcomes.” Active constructions make your organization sound more confident and accountable.
Common Narrative Mistakes
Too much organizational history. The organizational background section often consumes space that should go to program description and evaluation. Keep it to one to two focused paragraphs.
Vague evaluation language. “We will track outcomes” is not an evaluation plan. See above.
Outcomes that can’t be measured. If your objective says “participants will have improved mental health,” you need to specify the instrument you’re using to measure it. Otherwise you have an unmeasurable objective.
Not answering the question asked. Reviewers will sometimes ask specific questions in the application. Answer them directly, in the order asked. Don’t reframe the question with your preferred framing and then answer that instead.
Overstating evidence base. “Research shows that our approach works” without a citation is unsupported. Either cite the research or don’t claim it.
Ignoring word or page limits. Going over the limit signals that you don’t follow instructions. Many electronic systems enforce hard character limits—test your draft in the actual application portal before you think you’re done.
The Revision Process
A grant narrative that hasn’t been reviewed by someone other than the writer is not ready to submit.
A minimum revision process:
- Write the complete draft
- Leave it for at least 24 hours
- Reread the RFP and your narrative side by side—did you address every requirement?
- Have at least one colleague review for clarity (do they understand what you’re proposing?) and one review for accuracy (are the program descriptions, outcomes, and data correct?)
- Check every fact and citation
- Verify that the budget and narrative are aligned (budget line items should match activities described in the narrative)
For major funders, a longer review process with program staff, finance staff, and senior leadership review is appropriate. Set your submission schedule with enough buffer to accommodate a real revision cycle.
Grant narratives improve with practice. Keep every narrative you write—both funded and declined—as a reference. When you receive feedback on a declined proposal, document it in your grant management system. The organizations with the strongest narratives got there by refining their approach over many submission cycles.
For managing your grant submission calendar and tracking revision deadlines, grant calendar deadline alerts help ensure narrative drafts and review cycles have enough lead time before submission deadlines.
Related resources:
- Grant Proposal Writing Guide
- Grant Lifecycle Guide
- Grant Budget Justification Guide
- Free Grant Compliance Checklist
Free resource
Get the Nonprofit Grant Compliance Checklist
A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.