Week 8: The Architecture of a Resubmission That Reads as Stronger, Not Just Different

Last week, I talked about the team — how reviewers read your investigative team as an argument, not a staffing list, and why resubmissions sometimes require changing who is at the table.

This week, I want to talk about the resubmission itself. Not the response to reviewers — that is one component. I mean the architecture. How do you take an application that did not land, restructure it so it genuinely is stronger, and make sure a reviewer who reads both versions can see the difference without having to hunt for it? Because here is what most people do. They get their summary statement. They feel the sting. They wait a few weeks. Then they sit down, open the original application, and start editing. Line by line. Critique by critique. Fixing what the reviewers flagged.

That is the most common resubmission approach, and it is the weakest one. It produces an application that looks patched. And reviewers can tell the difference between a grant that was rebuilt and a grant that was repaired.

Why line-by-line revision fails

When you respond to a summary statement by editing the sentences reviewers criticized, you are making a structural assumption that the original architecture was sound and only the details needed work. Sometimes that is true. More often, the critiques in a summary statement are symptoms of a deeper problem that lives at the level of logic, not language.

A reviewer writes "the innovation is not clear." You revise the innovation paragraph. But the real issue may be that your entire Aims page builds toward your approach before it ever establishes why the current approach is insufficient. The innovation was not unclear — it was structurally buried.

A reviewer writes "the preliminary data do not support the proposed aims." You add two more figures. But the real issue may be that your preliminary data tell a different story than your aims — one that reviewers followed more easily than the story you intended.

A reviewer writes "the significance is overstated." You soften the language. But the real issue may be that your significance section argues for the importance of the problem rather than the importance of what your study would add to what is already known. The overstatement was not a tone problem. It was a gap problem — you were answering a question the reviewer was not asking.

In each case, the surface-level fix addresses the words while leaving the architecture intact. And the next set of reviewers — who may or may not overlap with the first — will encounter the same structural problem wearing new clothes.

Start with the logic, not the critiques

The first thing I tell scientists preparing a resubmission is to put the summary statement aside and re-read their original application as if they have never seen it before. I know that is hard. You have been living inside this document for months. But the exercise matters, because what you are looking for is not what reviewers criticized — it is where your own reading stumbles.

Where do you lose the thread? Where do you have to re-read a sentence to follow the logic? Where does your eye skip ahead because a paragraph feels like it is building to a point that never arrives? Where do you catch yourself filling in meaning that is not actually on the page?

Those are the structural weak points. They existed before the summary statement arrived. The reviewers simply encountered them from the outside.

Once you have identified those points — honestly, not defensively — then pick up the summary statement. You will find that most of the critiques land on or near the same places. The overlap is where the real revision lives. The critiques that do not overlap with your own reading? Those may be preference-based, idiosyncratic, or rooted in a misunderstanding that a clearer architecture would prevent.

This is the distinction that matters: responding to reviewers versus redesigning the argument. The first is necessary — you must demonstrate that you heard the feedback and took it seriously. But the second is what actually changes the score.

The one-page introduction: your resubmission's opening argument

NIH gives you one page to tell reviewers what changed. Most people use it as a list: "Reviewer 1 said X, we did Y. Reviewer 2 said A, we did B."

That is a compliance document. It demonstrates that you read your summary statement. It does not demonstrate that you rethought your science.

The strongest resubmission introductions I have seen — and the ones I have written that scored well — do something different. They open with one to two sentences that name the central revision. Not a list of changes. The one structural shift that reorganized the application.

Something like: "The primary revision to this application is a fundamental restructuring of Aim 2, which now proposes a sequential mixed-methods design rather than the parallel design in the original submission. This change was informed by Reviewer 2's concern about the interpretive framework and reflects a reconceptualization of how the qualitative and quantitative components inform each other."

That is not a response to a critique. That is a scientific decision that was catalyzed by a critique. The reviewer reads it and understands immediately that this is a different application, not a corrected one.

After the central revision, then address the specific critiques. Briefly, directly, with page references so the reviewer can verify. But by then, the reviewer already knows this is a serious resubmission — not a find-and-replace.

What to keep

One of the most common mistakes in resubmissions is changing too much. You receive a summary statement with multiple critiques, you panic, and you restructure everything. The result is an application that has lost its center. The reviewers who valued the original idea cannot find it anymore, and the new reviewers have no anchor.

The principle is this: identify what reviewers valued and protect it. Summary statements almost always contain positive language alongside the critiques. "The research question is important and timely." "The PI is well-positioned." "The community partnerships are a strength." These are not throwaway compliments. They are the foundation the reviewer built their evaluation on. Your resubmission should preserve and strengthen those elements while restructuring what did not work around them.

If your significance was praised but your approach was criticized, do not rewrite your significance. If your innovation was clear but your aims were not well integrated, keep the innovation language and restructure the aim architecture. If reviewers liked your team but questioned the scope, your revision is about feasibility, not personnel.

The resubmission should read as a more mature version of the same scientific idea — not a different application that happens to have the same title.

Scope and mechanism: the harder question

Sometimes a summary statement is telling you something larger than "revise and resubmit." Sometimes it is telling you that the scope of work does not fit the mechanism, or that the science is not yet ready for the level of investment you are requesting.

This is where the program officer conversation from Week 6 becomes essential. Before you invest months in a resubmission, confirm that the mechanism is still the right vehicle. An R01 that scored in the 40th percentile with feasibility concerns may be telling you that the science is an R21 first. An R21 that reviewers felt was too ambitious may be telling you that you have an R01-scale idea that needs a phased approach.

A resubmission to the wrong mechanism — no matter how carefully revised — will encounter the same structural mismatch. The architecture of the revision only matters if the foundation is right.

The February 5 deadline is six months away

If you submitted in October 2025 or June 2026, your summary statement is in hand or arriving soon. February 5 is the resubmission window. And if you are preparing a first submission, February 5 is close enough to plan for and far enough to build something strong.

The decisions you make in the next eight weeks determine whether February is a scramble or a submission you are genuinely proud of. Not the writing — the writing comes later. The decisions. Which mechanism. Which aims architecture. Which team. Whether to resubmit or pivot. Whether to hold your ground on a critique or genuinely restructure.

Those are translation decisions. They happen before a single sentence gets revised.

What is one thing your summary statement told you that you have been avoiding?

Next week: writing for the reviewer who reads your application at 11 PM — cognitive load, information hierarchy, and why the clearest grants are the ones that score well.

~Lisa Carter-Bawa, PhD, MPH, APRN, ANP-C, FAAN, FSBM

Lost In Translation (LIT) grantsmanship curriculum is available as an institutional cohort for cancer centers, training programs, and research-intensive departments.

The LIT Founders Cohort launches in August — the first cohort outside of an institutional partnership.

New: The LIT February 2027 Deadline Cohort begins October 19 and is taking applications here. Five live Monday sessions, noon–1:30 PM ET, built around the Five Translation Gaps and timed so your Specific Aims page is reviewed, revised, and ready for the February 5 NIH deadline. The cohort includes full access to the LIT course (14 modules + 13 workbooks) plus a post-cohort Translation Feedback Brief — a one-on-one review of your revised Aims page and/or full grant returned in time for your submission.

10 seats. $997 includes the full LIT course and cohort experience. Already own the course? The cohort experience is $500. Apply here: https://forms.gle/5AWXyPwufN7LKSxr6

Contact lisa@soultosoulleadership.com with any questions or visit https://www.lisacarterbawa.com/losttranslation to learn more.