Skip to main content

How to Write a Grant Narrative: Step-by-Step Process

Published: Last updated: Reviewed:

TLDR

A grant narrative that wins is one where the reviewer can check every box on their scoring rubric without hunting for the answer. Writing that narrative requires reading the RFP the way a reviewer reads it - as a checklist - not the way a program staff member reads it, which is as an invitation to explain your work.

What This Workflow Covers

A grant narrative is the written proposal document that describes your organization, the need you’re addressing, your proposed program, your evaluation plan, and your budget rationale. Most grant applications require some version of these components, whether for a private foundation letter of inquiry or a 100-page federal grant application.

This workflow applies to both types. The steps are the same; the depth of each step scales with the size and complexity of the grant.

Estimated time: 2-4 weeks for a mid-complexity foundation grant; 6-10 weeks for a major federal grant.

Who runs this workflow: Development Director or grant writer, with substantive input from program staff and executive leadership.


Step 1: Read the Full RFP Before Writing a Word

Time: 3-6 hours

This is the step most writers shorten and most rejections trace back to. The Request for Proposals (RFP), Funding Opportunity Announcement (FOA), or grant guidelines contains everything you need to know about what the funder is buying. Reading it closely before writing anything is not optional.

What to extract and document during your RFP read:

Eligibility. Confirm your organization is eligible. Check entity type requirements, geographic restrictions, budget size requirements, and prior funding history requirements. If you’re ineligible, nothing else in this workflow matters.

Required components. Make a list of every required section, document, and attachment. Some applications require sections that aren’t obvious from the narrative instructions alone - certifications, forms, organizational documents. Add all of them to your checklist.

Page limits. Note the page limit for the full narrative and for each section if specified. Build your outline with these limits in mind from the start, not as a compression exercise at the end.

Evaluation criteria. If the RFP includes a scoring rubric or list of evaluation criteria, this is the most important page in the document. Reviewers score applications against these criteria. Every section of your narrative should address the criteria explicitly, in the order they appear.

Funder priorities. What does the funder say they care about? Their priorities language often appears in the introduction, the eligibility section, and the evaluation criteria. Your narrative should use their language where it genuinely applies to your program - not as pandering, but because alignment with funder priorities is required for competitiveness.

Formatting requirements. Font size, margin requirements, single vs. double spacing, header requirements. Federal applications in particular have strict formatting rules, and violations can result in rejection or point deductions.

Build a one-page checklist from this reading: required sections, page limits, due dates, required attachments, formatting requirements. This checklist governs the rest of the process.


Step 2: Gather Your Organizational Capacity Documents

Time: 1 week (some documents may have longer lead times)

Before writing, assemble the documents you’ll need to describe your organization accurately and attach as required:

  • Most recent IRS Form 990
  • Most recent audited financial statements (within 2 years)
  • IRS 501(c)(3) determination letter
  • Current organizational budget
  • Board of directors list with names, affiliations, and terms
  • Organization chart
  • Bios for key project personnel (ED, program director, project lead)
  • Prior grants received and their outcomes (a simple table: funder, year, amount, program, results)
  • Relevant certifications, licenses, or accreditations for your organization or programs

If any of these documents are out of date, the grant narrative deadline creates a forcing function to update them. Don’t wait for the day before submission to discover your 990 is two years old.


Step 3: Gather Data About the Problem You’re Addressing

Time: 1 week

The Statement of Need section of a grant narrative is where many applications lose points they didn’t need to lose. Weak Statements of Need use national statistics to describe a local problem, repeat what the program staff already know, or describe the need for the organization rather than the need in the community.

Strong Statements of Need use data specific to your geographic service area to demonstrate that the problem you’re addressing exists here, is significant, and is not being adequately addressed.

Data sources to gather:

Census data. American Community Survey (ACS) data provides population, income, poverty rate, educational attainment, housing cost burden, and other indicators at the county, city, or tract level. The Census Bureau’s data.census.gov is the primary source.

State and county health data. Most state health departments publish county health profiles, vital statistics, and disease burden data. County Health Rankings (countyhealthrankings.org) provides standardized, comparable data across counties.

Local needs assessments. Community Health Needs Assessments (CHNAs) produced by hospitals, local health departments, or regional planning bodies often contain the most specific local data and are frequently cited approvingly by grant reviewers.

Your own program data. Your organization’s service data - waitlists, unmet need, outcomes from current programs, demographic information about clients served - is the most compelling evidence you have. Don’t omit it in favor of external statistics.

Local media and reports. Recent news coverage, policy reports, or advocacy documents about the need in your community can supplement quantitative data with qualitative context.

Cite your sources in the narrative. Reviewers who fact-check expect sources; reviewers who notice a lack of citations may discount the data.


Step 4: Draft the Statement of Need

Time: 2-3 days

The Statement of Need answers: why does this problem need to be addressed, why here, and why now?

Structure:

  1. The problem in your community. Lead with local data. The national opioid crisis, the national housing affordability problem, or the national education gap is context - not your statement of need. What does the problem look like in your county, city, or neighborhood?

  2. Who is affected and why they’re underserved. Describe the population experiencing the need. What barriers do they face accessing existing services? What gaps in the current service system are you addressing?

  3. The consequence of not acting. What happens to the people you’re describing if this program doesn’t exist or doesn’t expand? Concrete consequences are more compelling than abstract statements about social costs.

  4. Bridge to your program. End the section with a sentence or two connecting the described need to your proposed solution - but don’t describe the solution in detail yet. That’s the next section.

Common mistakes:

  • Using outdated data (check publication dates)
  • Describing the need for funding rather than the need in the community
  • Making claims without citation
  • Writing the Statement of Need after writing the Program Description, which leads to need statements that perfectly fit the proposed solution rather than the actual community

Step 5: Write the Program Description

Time: 3-5 days

The Program Description answers: what will you do, for whom, how, and why this approach works?

Align explicitly with funder priorities. The first paragraph of your Program Description should name the funder’s priorities and state directly how your program addresses them. Don’t make reviewers infer the connection.

Describe the program operationally. What does a client experience when they participate in your program? What services are delivered, in what sequence, by whom, and in what setting? Reviewers who read dozens of proposals appreciate specificity - “weekly group therapy sessions of 90 minutes with a licensed clinical social worker” is more compelling than “evidence-based therapeutic interventions.”

Name your evidence base. If your program model is based on an evidence-based approach (Motivational Interviewing, Cognitive Behavioral Therapy, an identified curriculum), name it and briefly describe why it’s appropriate for your population. If your model is adapted from evidence-based approaches or is promising but not yet established, explain the evidence for the components you’re using.

Describe organizational experience. Why is your organization equipped to deliver this program? What is your track record with this population, this service type, and this geography? Prior outcomes data from existing programs is the strongest evidence of organizational capacity.

Address sustainability. Many funders - especially foundations - want to know what happens when their grant ends. Address this directly: whether through other grant funding, earned revenue, government contracts, or a plan to build individual donor support. Vague gestures toward sustainability (“we will pursue diverse funding sources”) are less convincing than specific plans.


Step 6: Write the Goals, Objectives, and Evaluation Plan

Time: 2-3 days

This section trips up many grant writers because it requires specificity about outcomes that program staff are sometimes reluctant to commit to.

Goals are broad statements of intended impact: “Reduce substance use among program participants.”

Objectives are specific, measurable commitments: “70% of program participants will report reduced substance use at 6-month follow-up, as measured by the AUDIT-C tool.”

Strong objectives have: a specific indicator (what you’ll measure), a baseline (current rate or a stated starting point), a target (what improvement you’re committing to achieve), a timeline (by when), and a measurement methodology (how you’ll know).

Evaluation plan: Describe how you will measure progress toward each objective. Who is responsible for data collection? What instrument or data collection method will you use? How frequently will data be collected? Who will analyze the results?

For major federal grants, the evaluation plan may need to include an independent evaluator. For foundation grants, your organization’s own staff data collection is typically sufficient.

The credibility test: Read your objectives back against your program description. Are the targets achievable given the program’s scale and timeline? Overpromising in objectives creates compliance problems and donor relationship strain when reports show you missed targets.


Step 7: Write the Budget Narrative

Time: 1-2 days

The budget narrative justifies every line item in your proposed budget. Its purpose is to show that each expense is necessary, reasonable, and tied to the funded program.

Personnel: For each position charged to the grant, include: position title, annual salary, percentage of time charged to this grant, and total grant cost. If positions are not yet filled, include the salary range and qualifications. Benefits should be presented as a percentage of salaries, with the rate justified.

Fringe benefits: Use your organization’s actual fringe benefit rate (or an explanation of how it’s calculated).

Travel: If travel is budgeted, specify where, why, how often, and how costs were estimated. Federal grants typically require using federal per diem rates for meals and lodging.

Supplies: List major supply categories and estimate costs based on vendor quotes or prior actual costs.

Other direct costs: Explain each item. “Other” without justification raises reviewer flags.

Indirect costs: If you’re charging indirect costs (overhead), use an approved indirect cost rate or explain your cost allocation methodology.

What not to include: Don’t include costs that are clearly not related to the funded program. Reviewers notice budget items that seem disconnected from the proposed activities, and they raise questions that can stall or sink an application.


Step 8: Revise for Page Limits

Time: 1 day

Once your first complete draft exists, compare every section’s length against the page limits. Cutting content is harder than writing, but it’s part of the process.

Cutting strategies:

  • Remove background information that the funder likely already knows
  • Eliminate repetition across sections
  • Cut organizational history that doesn’t directly support this application
  • Convert narrative explanations of data into tables where space allows
  • Shorten methodology descriptions to their essential elements

Do not cut content that directly addresses evaluation criteria. If you must choose between a well-developed answer to a high-point criterion and background organizational narrative, cut the background.


Step 9: Get an Outside Reader

Time: 3-5 days (allow for turnaround)

Before final submission, have someone with no connection to your programs read the narrative. Their job is not to evaluate your program’s quality - it’s to find passages that are confusing to someone without your internal knowledge.

Common issues outside readers identify:

  • Undefined acronyms
  • Assumed knowledge about your community or population
  • Program descriptions that make sense to insiders but are unclear to outsiders
  • Gaps between the described need and the proposed solution
  • Missing answers to evaluation criteria that staff assumed were obvious

Address every confusion an outside reader identifies. If it was confusing to one reader, it will likely be confusing to a reviewer.


Step 10: Final Check Against Evaluation Criteria

Time: 2-3 hours

Before submitting, go through the evaluation criteria in the RFP one final time with your completed narrative. For each criterion:

  • Can a reviewer find a clear, specific answer to this criterion without searching through multiple sections?
  • Does your answer use the language from the criterion?
  • If the criterion is worth 20 points and your answer is three sentences, is that proportional?

Fix any gaps. Submit with your checklist complete.


How GrantPipe Supports the Grant Writing Process

Tracking multiple active grant applications - their deadlines, required components, submission status, and follow-up dates - is where organizations lose opportunities through missed deadlines and incomplete applications. GrantPipe’s grant pipeline management keeps each application’s status visible, and grant calendar deadline alerts surface submission dates before they become emergencies.

After award, funder reporting templates support the progress reports that every funded grant requires. See the grant reporting guide for the reporting workflow.

Download the Grant Reporting Calendar Template to manage all your grant deadlines in one view.

Start a free trial to see how GrantPipe tracks your full grant portfolio from application through closeout.

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.

Looking for something else?

We'll email the resource and a short follow-up sequence. Unsubscribe any time.

Email is required because the download link is delivered by email, not on-page.

Next step

Check the workflow against GrantPipe.

Start a 1-month free trial and test donor, grant, restricted-fund, and compliance work in one place.