NIH Resubmission Introduction Page: The One-Page Letter That Changes Your Score

Why This One Page Gets More Reviewer Attention Than You Think

When a reviewer picks up an A1 application, they already have context: they read — or at least skimmed — your original submission. That history shapes everything. They come to the resubmission with specific questions in mind. Did you hear what I said? Did you address the feasibility concern I raised about Aim 2? Did you add the positive control I asked for? The Introduction is the first place they look for answers.

Many applicants assume their reviewers won't remember the first submission in detail. That assumption is sometimes correct when a reviewer wasn't assigned to the original. But your assigned reviewers often do remember. And even reviewers who are new to your application will read the summary statement you received before they open the Introduction — it's standard practice. So the Introduction is a public document in a subtle sense: it's being read by people who already know what the critiques were.

The NIH policy on this is clear: the Introduction must summarize substantial additions, deletions, and changes, and it must respond to issues and criticisms raised in the summary statement. What the policy does not specify is how to do that well. That's what this article covers.

Reading the Summary Statement Strategically Before You Write

Before you write one word of the Introduction, do something that many researchers skip: read your summary statement analytically, not emotionally. That takes about a week after you first get it. The first reading is almost always reactive. You're looking for what the reviewers got wrong, what they missed, what feels unfair. That reaction is natural, and you should let it happen — then set the document aside.

On the second reading, do a different exercise. For each critique, ask: even if this is stated unfairly, is there a legitimate underlying concern? A reviewer who says "the preliminary data are insufficient" may be poorly articulating a concern about whether your model actually recapitulates the disease. A reviewer who says "the timeline is unrealistic" may be worried about whether your postdoc has the bandwidth to run two assays simultaneously. The surface critique and the real concern are often different, and your Introduction needs to address the real concern — not just the surface statement.

Then categorize. Sort each critique into one of three buckets: critiques you can fully address with new data or clarified writing; critiques you can partially address and need to acknowledge; and critiques you genuinely disagree with and need to respectfully rebut. Your Introduction must touch all three categories. Skipping the third entirely — or pretending every critique is addressed — signals to reviewers that you're not being honest with them.

The Four Things a Strong Introduction Delivers

Not all one-page introductions do the same work. The strongest ones consistently deliver four things, and the weakest ones deliver one or two at most.

1. A Clear Signal That You Heard the Panel

The opening paragraph — even just the first two sentences — should demonstrate that you understood the overall tenor of the review, not just the individual criticisms. If three reviewers said your Approach was underpowered, say so explicitly: "Reviewers raised concerns about statistical power across multiple aims." Naming the pattern shows engagement. Applicants who immediately jump to item-by-item responses without acknowledging the gestalt often read as defensive.

2. Specific, Verifiable Responses to Major Weaknesses

For each substantial critique, the Introduction should name what you changed and where reviewers can find it: "We added a validation cohort addressing Reviewer 2's feasibility concern; see Aim 1b on page 18." This is not about padding with page references — it's about letting reviewers verify your claims without hunting. Reviewers who can quickly confirm you did what you said are more likely to advocate for you at the discussion meeting.

3. An Honest Account of What You Couldn't Fully Address

No resubmission resolves every critique. Some concerns require a different study design. Some need data that can't be generated in a single submission cycle. Acknowledging this honestly — "We could not fully address Reviewer 1's request for longitudinal outcome data within the scope of this proposal, but we have added a future-directions section on page 24 describing how this will be pursued in a subsequent application" — is substantially better than pretending the critique was resolved when it wasn't. Reviewers can tell the difference, and they respect candor.

4. A Brief, Evidence-Based Rebuttal Where You Disagree

Respectful disagreement is allowed and sometimes necessary. If a reviewer misread your preliminary data, or applied a criterion that doesn't fit your mechanism, you can say so — once, briefly, with a citation or data reference. The key word is brief. One sentence of rebuttal backed by evidence is credible. Three paragraphs of argument reads as defensiveness, even when you're right.

Structuring the One Page: A Practical Template

There's no NIH-mandated format for the Introduction, which is a blessing and a curse. Applicants who treat it as an unstructured letter often run long. Those who treat it as a checklist often read as perfunctory. The format below works well for most R01 resubmissions, and with minor adjustment for fellowship and career award resubmissions:

Opening paragraph (3–4 sentences): Acknowledge the review constructively. Name the primary concern the panel raised. State that your resubmission addresses it substantially and briefly name how (one clause, no detail yet).
Major concerns, numbered (3–5 items, 2–3 lines each): List each major critique, state your response in one sentence, and give the page reference for where reviewers can verify the change. If you couldn't address a critique fully, say so here with a brief explanation.
Minor concerns, briefly noted: A short paragraph or bulleted list acknowledging the minor issues and pointing to corrections. Don't skip minor concerns entirely — reviewers notice when they're omitted.
New data or scope change, if applicable: If you added substantial new preliminary data, restructured your aims, or narrowed your scope in response to review, name it explicitly so reviewers enter the application knowing to look for it.

Fitting this into one page requires discipline. The major-concerns section will be the most contested for space. Keep each response to two or three lines. You are not rewriting your Approach in the Introduction — you are signposting it. If you find yourself writing five lines per concern, you are writing defense, not navigation.

What Belongs in the Application Attachments, Not the Introduction

One of the most consistent errors in A1 introductions is trying to resolve critique inside the Introduction itself — writing the actual scientific argument, the new data summary, the statistical justification. That content belongs in the Research Strategy. The Introduction is a roadmap, not a destination.

Equally important: NIH policy explicitly prohibits marking changes within application attachments. You cannot bold, highlight, or use a different color to show revised text in your Research Strategy or Approach section. Everything that changed is supposed to be declared in the Introduction, and reviewers are expected to read the application fresh. Some applicants try to add margin notations or use a footnote system. Don't. Reviewers have seen this tactic and it reads as an attempt to work around the policy, not a clever workaround.

What does belong in the Introduction: the signposting, the acknowledgment, the brief rebuttals, and a note on any structural changes (new aim, removed aim, changed mechanism, added consultant). Anything that requires more than three lines to explain belongs in the body of the application where you have room to explain it properly.

Common Mistakes That Signal You Didn't Engage

Repeating the original argument without new evidence

"We respectfully disagree with Reviewer 3's concern about feasibility. Our preliminary data clearly demonstrates..." followed by the same data you already submitted is not a response. If the reviewer wasn't convinced by your data the first time, restating it without new evidence won't change that. Add something new or acknowledge the limitation.

Addressing minor critiques at length while glossing over major ones

Reviewers notice when the easiest critiques get the most attention. If your scored weaknesses were in Significance and Approach but your Introduction spends three-quarters of its space on a formatting comment and a missing reference, you signal that you either couldn't address the substantive issues or chose not to. Weight your responses to match the weight of the critiques.

Writing in a tone that reads as aggrieved

Reviewers are volunteers. Even when they misread your application, they gave time to your science. An introduction that opens with "In our previous submission, reviewers unfortunately misinterpreted our central hypothesis..." sets a tone that puts your advocate on the defensive before the discussion begins. You can disagree respectfully. Maintain that register throughout.

Omitting the page references

"We have substantially revised the Approach section in response to reviewer concerns" tells a reviewer nothing actionable. "We restructured Aim 2 to address Reviewer 1's concern about interdependence; see pages 16–18" lets them go verify. The difference in reviewer confidence between these two versions is real.

The Program Officer Conversation Before You Start Writing

Before you begin revising, call your program officer. This is especially important if your application was not discussed — triaged — at the meeting. Triage means the panel didn't spend time deliberating your score, which usually means either the application had a straightforward fundability problem or reviewer interest was low. A brief call with your program officer can help you understand which of those applies, and whether the institute sees a path to funding for a revised version.

Program officers can't tell you your likely score if you resubmit, and they won't predict funding decisions. But they can often tell you whether the reviewers' concerns were technical (solvable with data) or conceptual (harder to address without rethinking the project). That distinction should shape how you spend the months between submissions. An Introduction that responds to technical concerns with new data is a strong resubmission. One that responds to conceptual concerns with more text is usually not.

If the program officer suggests rethinking your approach significantly — not just revising the writing — take that seriously. A resubmission that makes cosmetic changes to a fundamentally unchanged application rarely fares much better than the original. Reviewers remember what they read. They will notice if you didn't substantively engage with their concerns.

Frequently Asked Questions

Do I need to respond to every single reviewer comment, including minor typos and formatting notes?

Not in exhaustive detail. Minor issues — typographical errors, a missing figure label, a citation formatting inconsistency — can be grouped and acknowledged in a single sentence: "Minor formatting and typographical errors noted by all reviewers have been corrected throughout." What you can't do is ignore substantive concerns, even partial ones. If a reviewer raised a scientific question, you need to address it.

My resubmission is going to completely different reviewers. Does the Introduction still matter?

Yes. New reviewers receive the prior summary statement as part of the review package. They read what the original panel said, and then they read your Introduction to see how you responded. In some ways, new reviewers read the Introduction more carefully because they're using it to calibrate how the prior panel scored you and whether those concerns were legitimate.

Fellowship and K award resubmissions have a three-page introduction limit. Should I use all three pages?

Only if you need them. A tight, focused two-page introduction for a fellowship resubmission is better than a three-page introduction padded to fill space. Use the extra room to describe new preliminary work, expanded training plan, or a substantially revised career development section — not to restate the argument in more detail than the original submission allowed.

What if I fundamentally disagree with the panel's premise and need to argue against the framing of the critique?

You can, but keep the disagreement contained and evidence-backed. Cite a paper. Reference a dataset. Show that there's genuine scientific uncertainty about the point the reviewer raised. What you can't do effectively is win a conceptual argument on one page against a panel who already voted. If the disagreement is deep enough that the resubmission can't resolve it, that's a signal to talk with your program officer about whether this is the right mechanism for the science you're proposing.