Key Facts
- The project narrative is the scored section. Budget, organizational charts, and attachments support the narrative — reviewers score the narrative. Every point in your score comes from this document.
- Reviewers spend 45–90 minutes per proposal. At most federal review panels, reviewers handle 10–20 applications per cycle. Your narrative must be scannable — headers, numbered objectives, and a clear logical structure matter as much as content quality.
- The NOFO is the scoring rubric. Every section of the NOFO that says "describe" or "explain" corresponds to a scored element. If the NOFO asks applicants to describe sustainability plans and you don't, reviewers deduct points regardless of how strong the rest of the narrative is.
- Local data beats national data — always. A needs statement using county-level rates from the state health department outscores one citing CDC national averages in virtually every review panel.
- SMART objectives are mandatory, not optional. Specific, Measurable, Achievable, Relevant, Time-bound. Objectives that don't specify numbers ("we will improve health literacy") are a consistent source of low scores on goals/objectives criteria.
Summary
The project narrative — sometimes called the program narrative, technical approach, or scope of work depending on the federal agency — is the core document of any grant application. It is what reviewers score, what program officers read when making funding recommendations, and what gets entered into the grant agreement if you're funded. Federal grant narratives typically run 15–30 pages and cover: a needs or problem statement, program goals and measurable objectives, a methodology or project design, an evaluation plan, and a sustainability plan. This guide covers each section in detail, with specific guidance on the language, structure, and evidence that distinguishes competitive proposals from the applications reviewers score below the funding line.
Before You Write: The NOFO Is Your Scoring Rubric
The Notice of Funding Opportunity (NOFO) — also called a Notice of Funding Availability (NOFA), Funding Opportunity Announcement (FOA), or Program Announcement — tells you exactly what reviewers will score. Most federal NOFOs include an explicit review criteria section that lists each scored element with its point value or relative weight. This is not background reading. It is the outline of your narrative.
Read through the review criteria before you outline. If the NOFO allocates 30 points to Project Design and 20 points to Evaluation, your narrative should give Project Design proportionally more depth. If a criterion is worth 15 points, write enough content to earn all 15. Reviewers work from a scoring sheet that maps directly to the NOFO criteria — if your narrative doesn't address a criterion, reviewers cannot award points for it regardless of how impressive the rest of your proposal is.
There is a mechanical step that experienced grant writers do first: print the NOFO, highlight every phrase that begins with "applicants should describe," "the narrative must include," "reviewers will consider," or similar language. Each highlighted item is a required element of your narrative. Make a checklist. Check it when you're done writing.
Needs Statement: The Most Common Scoring Failure
The needs statement — sometimes called the statement of need, problem statement, or community needs assessment — establishes why the proposed project is necessary. It is the most frequently underdeveloped section of federal grant narratives and the source of more lost points than any other section except evaluation.
The two most common weaknesses: using national data when local data is available, and documenting the problem without connecting it to the proposed intervention.
On local data: if you are applying for a HRSA community health grant serving Cuyahoga County, Ohio, your needs statement should cite Cuyahoga County's specific rates for the relevant health conditions — from the Ohio Department of Health, the County Health Rankings, or local hospital community health needs assessments. Citing the U.S. national uninsured rate when Ohio and Cuyahoga County data exist tells reviewers that you didn't do the community needs assessment that the program is designed to support. Local data demonstrates community knowledge. National data signals that the applicant is describing a generic problem, not this community's specific problem.
On connecting need to solution: the needs statement should end with a logical bridge to your proposed program. "The data above demonstrates that [specific population] in [specific geography] experiences [specific problem] at [specific rate] — X% higher than the state average and Y% higher than the national benchmark. Current services address only Z% of estimated need, leaving a gap of [specific number] individuals underserved annually. [Organization name]'s proposed [program] is specifically designed to address this gap by..." This framing — document the problem, quantify the gap, name your solution — is what funded needs statements look like.
GrantMetric Analysis
- Objectives that can't be measured are objectives that can't be scored — or funded again. Federal reviewers are trained to identify SMART objectives, and program officers reviewing reports will hold you to whatever you wrote. "Increase community awareness of diabetes prevention" is not a measurable objective. "Increase the percentage of Riverside County adults who report receiving a diabetes screening in the past 12 months from 34% (2024 BRFSS data) to 45% by December 31, 2027" is. The difference isn't just about impressing reviewers; it's about creating an evaluation plan you can actually execute. Vague objectives lead to vague evaluation plans, which lead to program reports that can't demonstrate impact, which make renewal applications nearly impossible to fund.
- The methodology section needs to answer the reviewer's implicit skepticism. When a reviewer reads your project design, they're asking: "Will this actually work?" That skepticism is productive — address it directly. For each major activity, briefly acknowledge the conditions under which it might not achieve the intended outcome and describe your contingency approach. Organizations that have delivered similar programs before should reference that experience with specific outcome data from prior work: "In our 2023 pilot serving 45 participants, 78% completed the full 8-session curriculum and 61% showed clinically significant improvement in [measure]." This is evidence that your approach is grounded in practice, not theory — and it scores well on organizational capacity criteria even in NOFOs that don't explicitly list prior experience as a criterion.
- Sustainability plans that describe future grant applications score lower than plans that describe revenue diversification. Almost every federal program requires a sustainability plan describing how the project continues after the grant period. The most common (and weakest) response: "We will seek additional grant funding to continue these services." Reviewers hear this as "we have no sustainability plan." A credible sustainability narrative names specific revenue sources — government contracts, Medicaid reimbursement, earned income, fee-for-service agreements, endowment interest, foundation commitments already in place — and explains the organizational infrastructure being built during the grant period that will persist afterward. If you are genuinely grant-dependent, at least describe what community relationships, partnerships, or credentials the project will generate that will make future funding applications stronger.
Goals and Objectives: The Architecture of the Narrative
Goals are broad statements of intended change — "Improve access to mental health services for uninsured adults in Monroe County." Objectives are specific, measurable steps toward that goal — "Enroll 120 uninsured adults in the CCBHC sliding-scale program by Month 12 of the project period." Most federal narratives need 2–4 goals, each with 2–5 objectives. More than that and the proposal becomes unwieldy; fewer than that and it may look underplanned.
The relationship between objectives and evaluation is direct: every objective you write will need a corresponding data source, baseline, target, and measurement timeline in the evaluation section. This is why experienced grant writers outline the goals/objectives section and the evaluation section simultaneously — the two sections are architecturally linked and must be internally consistent. If you write 12 objectives in the goals section and your evaluation plan only describes measurement for 6 of them, reviewers will deduct points for the disconnect.
Process objectives versus outcome objectives: both are necessary. Process objectives track whether you implemented the program as planned ("Deliver 48 workshops to 600 participants across 4 community sites by project end"). Outcome objectives track whether the program caused change ("Increase the proportion of workshop participants who report using evidence-based stress management techniques from 22% at baseline to 55% at 6-month follow-up"). Federal programs want to see both — process objectives show the government that you delivered what you promised; outcome objectives show that what you delivered made a difference. Programs with only process objectives are described in after-action reports as "outputs" rather than "outcomes," which is a persistent criticism in performance reviews.
Evaluation Plan: The Section That Separates Competitive Proposals
The evaluation section is where many otherwise strong proposals fall apart. A common misconception: that evaluation means "we will count participants and measure satisfaction." Satisfaction surveys and participation counts are outputs — they tell you what you did, not what changed. Federal reviewers evaluating programs funded under evidence-based practice frameworks (SAMHSA, HRSA, HUD's evidence tiers) are specifically looking for outcome measurement that captures behavior change, skill acquisition, or condition improvement.
A complete evaluation plan addresses: what you will measure (the outcomes, connected to your objectives), how you will measure it (validated instruments, administrative data, surveys — and why this method is appropriate), when you will measure it (baseline, mid-point, post-program, and ideally 6-month or 12-month follow-up for behavioral outcomes), who is responsible for data collection and analysis, and how you will use the data to improve the program during the grant period (formative evaluation) rather than just document results at the end (summative evaluation).
The program theory underneath the evaluation plan is the logic model. Even when the NOFO doesn't require a formal logic model diagram, the evaluation section should reflect logic model thinking: your inputs enable your activities, your activities produce your outputs, your outputs lead to short-term outcomes (changes in knowledge or attitudes), which lead to intermediate outcomes (changes in behavior), which lead to long-term outcomes (changes in conditions). If your evaluation only measures outputs, reviewers know that you haven't thought through the causal chain between your activities and the impact you claimed in the needs statement.
Organizational Capacity: Proving You Can Do What You're Proposing
Almost every federal NOFO includes a criterion asking applicants to demonstrate organizational capacity — the ability to manage the proposed program, handle federal funds, and deliver the described services. This section is often underweighted by applicants who feel it's redundant with their attachments. It isn't. The narrative description of organizational capacity is where reviewers look for evidence of specific program management experience, not just organizational history.
What scores well: prior experience with similar programs, with specific outcomes cited. Existing infrastructure that will support the project — a data management system, trained staff already in place, community relationships with target populations. Demonstrated ability to manage federal awards, particularly if you have prior federal grant history without findings or audit exceptions. Letters of commitment from partners that describe specific, concrete contributions (not just expressions of support) can be referenced here and attached.
What scores poorly: extensive organizational history that isn't directly relevant to the proposed program; descriptions of capacity in terms of what the organization has done in different program areas; and letters of support that say "we endorse this proposal" rather than "we will provide X specific contribution to this project."
Narrative Writing Checklist
- Print the NOFO and highlight every "describe," "explain," and "demonstrate" requirement — each is a scored element your narrative must address
- Needs statement: use local/county-level data with source citations; quantify the service gap; connect the documented need directly to your proposed intervention
- Objectives: write every objective as SMART — include a baseline, a target, and a specific deadline. Pair each objective with a measurement method in the evaluation section
- Methodology: describe activities with enough specificity that a reviewer can visualize the program in operation; include roles, timelines, and participant flow
- Evaluation: go beyond output counts; name at least one validated measurement instrument; describe both formative and summative evaluation activities
- Sustainability: name specific non-grant revenue sources or credentialing/partnership outcomes that will persist after the grant period
- Final check: every scored criterion in the NOFO review section should be findable in your narrative — use headers that mirror the NOFO's language so reviewers can locate scored elements quickly