NIH’s Project Narrative is a required attachment on most NIH grant applications, but it is not the long-form case for the research that the term “project narrative” means at almost every other funder. It is a short, plain-language statement — in practice usually two to three sentences — that says why the proposed research matters to public health. Because that is its entire purpose, NIH staff and applicants commonly call it the public health relevance statement instead, and that is the more accurate name for what this page describes.
This page covers NIH’s specific attachment only. For the general, cross-funder document that most people mean by “grant narrative” or “project narrative” — the one that argues significance, approach, and methods — see Grant Narrative / Project Narrative: What It Is and How to Write One, which also covers how NIH’s usage diverges from that general sense. At NIH, that longer argument is instead built from the Specific Aims page and the Research Strategy attachment — not from anything called “Project Narrative.”
Quick facts
| Question | Answer |
|---|---|
| What is it | A required attachment stating the proposed research’s relevance to public health, in plain, non-technical language |
| Length | No more than three sentences (some NIH institutes phrase this as a strict one-page/half-page attachment; three sentences is the consistently repeated guidance across NIH institute application-help pages) |
| Where it’s filed | Uploaded as a separate PDF attachment on the SF424 (R&R) Other Project Information form, alongside the Project Summary/Abstract |
| Audience | Written for a non-specialist reader — NIH guidance notes these statements can be seen by Congress and the public, not only scientific reviewers |
| Is it scored | Not itself a separate scored review criterion, but reviewers and NIH staff read it, and an unclear or jargon-heavy statement reflects on the rest of the application |
| Required on | Most NIH research grant and career-development mechanisms submitted via SF424 (R&R) — confirm the specific requirement against the funding opportunity’s instructions, since attachment requirements are set at the FOA level |
Last verified 2026-08-16. NIH updates its SF424 (R&R) Application Guide periodically; always confirm the current length/format instruction against the specific funding opportunity announcement (FOA) and the current-year NIH Application Guide before submitting, since exact wording and any page-limit specifics can shift between guide revisions.
What NIH’s Project Narrative is — and is not
NIH’s Project Narrative is not a summary of the science, not a restatement of the Specific Aims, and not a shortened Research Strategy. It answers exactly one question: why does this research matter to public health? A common, effective structure is: (1) the health problem or burden the research relates to, (2) what the project will do, and (3) how the result could ultimately benefit health or advance the field toward a health benefit — each in one plain sentence, with no jargon, abbreviations, or technical terminology a member of the public wouldn’t recognize.
This is a different artifact from the Project Summary/Abstract, which is also required and also public-facing, but is longer (typically capped around 30 lines / one page) and is meant to describe the project itself — aims, design, and methods — for a scientifically literate but non-specialist audience. The Project Narrative is shorter still, and narrower in purpose: it exists specifically to state relevance, not to describe the study.
Where it goes in the application
The Project Narrative is uploaded as its own PDF attachment on the SF424 (R&R) Other Project Information form — the same form that carries the Project Summary/Abstract and the Bibliography & References Cited attachment. It is a separate uploaded file, not a text box, so it must be prepared and saved as a standalone one-page (or shorter) PDF before submission through ASSIST, Grants.gov Workspace, or an institutional system-to-system tool.
How to write one
- State the health problem in one sentence. Name the disease, condition, population, or public-health issue the work relates to — in language a non-scientist would recognize.
- State what the project will do, in one sentence. A plain-language version of the research aim, not a methods summary.
- State the expected public-health payoff, in one sentence. What becomes possible, known, or treatable as a result — phrased as relevance, not as a results claim you can’t yet support.
- Cut every technical term you can. If a term needs a definition to be understood by a non-scientist, either drop it or replace it with the plain-language equivalent.
- Read it against the three-sentence/plain-language instruction in the current FOA and Application Guide before finalizing — requirements are set at the funding-opportunity level, and this is the single most common place applicants drift out of compliance without noticing.
- Save it as its own PDF and attach it in the correct field on the SF424 (R&R) Other Project Information form — not combined with the Project Summary/Abstract attachment.
Worked example
Illustrative composite — not drawn from or attributed to any real application, institution, or investigator. It exists to show structure and register, not to be copied.
Diabetic kidney disease affects millions of Americans with type 2 diabetes and is a leading cause of kidney failure, yet current treatments slow but do not stop its progression. This project will test whether a newly identified blood marker can predict, years in advance, which patients are most likely to progress rapidly. If successful, this marker could allow doctors to identify high-risk patients earlier and target existing treatments to the patients who need them most.
Notice the shape: problem (one sentence), what the project does (one sentence), payoff (one sentence). No abbreviations, no assay names, no statistical language — every clause would make sense read aloud to someone outside science.
Common mistakes
- Confusing it with the general “project narrative.” Applicants who have written proposals for other funders sometimes assume NIH’s Project Narrative is the long-form argument for the work — described on the general grant/project narrative guide — and either attach the wrong document or leave the real Project Narrative attachment blank.
- Restating the Specific Aims instead of stating relevance. The Specific Aims page already states what the project will test or accomplish scientifically; the Project Narrative’s job is to say why that matters to public health, not to repeat the aims in shorter form.
- Leaving in jargon. Disease abbreviations, gene/protein names, statistical terms, and methodology language all defeat the purpose of a statement meant to be readable by Congress and the public.
- Treating length as flexible. Three sentences is a real constraint, not a suggestion — a Project Narrative that runs to a paragraph or more is out of format and should be tightened before submission.
- Confusing it with the Project Summary/Abstract. Both are short, public-facing, and filed on the same SF424 (R&R) form, which is exactly why they get mixed up — but they are separate required attachments with separate purposes and separate length limits.
Frequently asked questions
Is the Project Narrative the same as a public health relevance statement?
Yes — “public health relevance statement” is the informal, more descriptive name NIH staff and applicants commonly use for the same attachment. The formal attachment name on the SF424 (R&R) form is “Project Narrative.”
Is the Project Narrative the same as the SF424 Project Narrative used by other agencies?
No. SF424 is a government-wide form family used by many federal agencies, but each agency’s instructions define what goes in a given attachment field differently. NIH’s instructions for its “Project Narrative” attachment specifically call for a plain-language, public-health-relevance statement of a few sentences; other agencies using SF424 forms may use a “Project Narrative” attachment for the general long-form narrative document instead — always follow the specific funding opportunity’s instructions rather than assuming NIH’s convention applies elsewhere.
Does the Project Narrative count toward the Research Strategy page limit?
No. It is a separate attachment on the Other Project Information form, uploaded independently of the Research Strategy and Specific Aims attachments, and is not counted against those page limits. See NIH Application Page Limits and Format Requirements for the full set of page limits across NIH attachments.
Who reads the Project Narrative?
Scientific reviewers see it as part of the application, but NIH guidance also notes it may be read by Congress and members of the public — for example, project narratives are the kind of plain-language description that can surface in publicly searchable databases of funded NIH research. That public-facing audience is the reason for the plain-language requirement.
Is the Project Narrative scored by reviewers?
It is not one of NIH’s five core scored review criteria (Significance, Investigators, Innovation, Approach, Environment). It is nonetheless a required part of a complete application, and an unclear or noncompliant Project Narrative can create a poor impression alongside the scored sections.
