How to Write the NIH Project Narrative (Public Health Relevance) in 3 Sentences

What the Project Narrative Is (and Isn't)

The Project Narrative is a short attachment in the Other Project Information form. NIH's instructions ask for two or three sentences, in plain language, describing the relevance of the research to public health. Older applications called this the "public health relevance statement," and plenty of people still do. Same idea, different label.

It isn't the Project Summary/Abstract, which is a separate attachment with its own length limit and gets read as a miniature version of the whole application. It isn't a restatement of your Specific Aims either. The abstract says what you'll do. The narrative says why a person who will never run your assay should care. If you paste the abstract's first sentence into the narrative box, you've answered the wrong question. We cover the abstract separately in our project summary guide.

Who Actually Reads These Three Sentences

I can't tell you exactly how much weight any given reader puts on it, and I'd be skeptical of anyone who claims to know. Reviewers don't score the narrative as its own criterion. But the text travels. It shows up in the public-facing record of your award, and it's the sort of sentence a program officer pulls into a portfolio summary, a council briefing, or an answer to a legislative inquiry.

That's the practical argument. Years after your study section meets, someone who doesn't know your subfield will be skimming a list of funded projects, and your narrative may be the only line of yours they read. A sentence that says "this work will advance understanding of mechanisms" tells them nothing. A sentence that names a disease, a population, and a plausible downstream benefit gives them something to quote. It also helps your own case with program staff when you're discussing fit, which pairs well with the outreach advice in our program officer guide.

A Three-Sentence Formula That Holds Up

You don't need a clever structure, only a reliable one. This is the pattern I use when I edit narratives for colleagues, and it fits comfortably inside the two-to-three-sentence expectation.

Before and After: A Rewrite

Here's a composite of the kind of narrative I see most often. It's invented for illustration, not taken from a real application.

The "after" version is three sentences, uses no jargon, names a patient group, and makes a claim modest enough to be believed. It also happens to be accurate to the science. Nothing was dumbed down; the specifics just moved to the pages where specialists will read them.

Mistakes That Make the Narrative Useless

Basic Science and Tool-Building Projects

The hardest narratives to write belong to projects with no obvious patient in them: structural biology, method development, model-organism genetics. The temptation is to invent a disease link that the project doesn't really support. Resist it. A narrative that says "this work builds a tool that will let other labs measure X, which is currently a bottleneck for studying Y disease" is perfectly acceptable, and it's true.

Think of the chain as two links rather than one. Your work enables or explains something, and that something matters to a health problem. If you can state each link in plain words and neither one requires a leap of faith, you're done. If the second link needs three qualifiers, use the qualifiers; they're honest. Checking which institute's mission your project actually touches can help you phrase that second link, and the institute strategic plan guide walks through how to read those priorities.

Frequently Asked Questions