Week 11: The Summary Statement You Already Read — and What You Missed the First Time

Last week, I talked about how reviewers actually write — not in the order the template presents, not with perfect fidelity to what they read, but shaped by the availability heuristic, by the Factor 1 ceiling, and by the awareness that their critique is a script they will have to perform in front of a (virtual) room.

This week, I want to bring you back to a document you have already seen. Your summary statement.

If you have been following this series, you read your summary statement once before — back when it first arrived. You probably read it the way most applicants do: scanning for problems, cataloging concerns, looking for the reasons behind the score. And if you read Week 4 of this series, you may have read it more carefully than most — distinguishing observations from concerns from foundational issues, noting where reviewers disagreed, paying attention to the Resume and Summary of Discussion that appears at the very top.

But here is what I want you to understand now, ten weeks into this series: you are not the same reader you were then. You now know things about the other side of the table that change what your summary statement is telling you. And the resubmission you are building — or considering — depends on whether you go back and read it again with what you now know.

This is the most common misread that derails resubmissions. And it does not happen because people are careless. It happens because they read their summary statement exactly once, in the worst possible emotional state, and then build an entire revision strategy on that first reading.

Why the first reading is almost always incomplete

Think about when your summary statement arrived. You had already been sitting with your score — or your Not Discussed designation — for weeks. You had already constructed a story about what happened. If the score was close, you had probably convinced yourself of what went wrong. If the score was far from fundable, you had probably started grieving the idea or planning your next move. If you were not discussed, you had been living with a silence that felt like a verdict.

Into that saturated emotional space, the summary statement landed. And you read it through the narrative you had already built.

That is not a character flaw. That is how humans process evaluative information. We do not read feedback in a vacuum. We read it through the interpretation we have already committed to. And then we find confirmation of that interpretation on every page.

The problem is that a revision strategy built on a first reading is a strategy built on confirmation rather than comprehension. And confirmation is not the same as understanding what the room actually said.

The sentence most applicants read past

When I say the Resume and Summary of Discussion tells you more than the individual critiques, I do not mean it contains more information. I mean it contains different information — and it is the information that matters most for your resubmission.

Here is why. You now know from Week 10 that a reviewer's written critique is shaped by what was most cognitively available when they sat down to write. You know that concerns receive more detailed treatment than strengths — not because the reviewer weighted them more heavily, but because concerns require more careful articulation. You know that the length of a critique point is not a reliable proxy for its weight.

And critically, you know that the critique was written before the study section discussion. It represents one reviewer's pre-discussion position.

The Resume and Summary of Discussion represents what happened after that. It is the record of what the room converged on when multiple reviewers — each with their own pre-discussion positions, their own availability biases, their own interpretive frames — talked through your application together.

Sometimes the room confirmed what the individual reviewers wrote. Sometimes it did not.

There is usually a sentence in the Resume and Summary of Discussion — sometimes two — where the panel's actual concern crystallizes. Not a list of everything that was raised. The distillation. The thing the room agreed mattered most. Applicants scan past it because it is short, because it is surrounded by broader summary language, and because they are already looking for the detailed critique points that will tell them what to fix.

But that sentence is not a summary of the critiques. It is a summary of the discussion — the conversation that happened after the critiques were read aloud, after the assigned reviewers presented their scripts, after the room asked questions and pushed back and refined the assessment.

That sentence is the room's voice. And the room's voice is the one your resubmission needs to answer.

The misread that derails resubmissions

Here is where this goes wrong, and I have seen it happen to strong scientists with strong applications who should have been funded on the resubmission.

An applicant reads their summary statement and catalogs every concern raised by every reviewer. They build a response matrix. Reviewer 1 raised X, Y, and Z. Reviewer 2 raised A, B, and X. Reviewer 3 raised C and Y. They then systematically address every point — revising the design, adding sensitivity analyses, strengthening justifications, clarifying language — and write an Introduction page that walks through each concern and its corresponding revision.

The resulting application is responsive. It is thorough. And it often scores the same or worse.

The reason is that the applicant treated every individual critique point as if it carried equal weight. They responded to the individual reviewers' pre-discussion positions rather than to what the room actually landed on. They addressed twelve concerns when the room's real concern was one — the one captured in that sentence in the Resume and Summary of Discussion that they read past because they were building a spreadsheet of critique points.

A resubmission that addresses twelve concerns with equal weight tells the new review panel that you did not understand what the fundamental problem was. It reads as patching rather than rethinking. And the new reviewer — who was not in the original room but who has your summary statement in front of them — will read the Resume and Summary of Discussion first to understand what the prior panel thought. If your Introduction page does not directly and substantively address what the Resume and Summary of Discussion identified as the central issue, every other revision looks like rearranging furniture.

How to re-read your summary statement now

If you are considering a resubmission — or if you are in the middle of one — go back to your summary statement. Not to the individual critiques. To the Resume and Summary of Discussion.

Read it without the narrative you built during those weeks between the score and the summary statement arriving. Read it with everything you now know about how reviewers write — that their critiques are shaped by cognitive availability, that concerns get more words than strengths, that what they wrote was a script drafted for a performance.

Find the sentence where the room's concern crystallizes. It is usually the most specific statement in the Resume and Summary of Discussion — not a broad characterization ("the reviewers noted some concerns about the approach") but the distilled version of what actually drove the discussion ("the panel questioned whether the proposed recruitment strategy could achieve the projected sample size given the population's documented screening avoidance").

That sentence is your resubmission brief. Not the only thing you address — but the thing you address first, most substantively, and most visibly. Everything else in your revision should be in service of demonstrating that you heard that sentence and fundamentally responded to it.

The skill of reading evaluative feedback this way — separating the room's voice from the individual voices, identifying the structural concern underneath the surface-level critique points — is one of the hardest things I teach in the Lost In Translation curriculum, because it requires setting aside the instinct to be comprehensive in favor of the discipline to be strategic.

Beyond grants

This principle applies to any context where you receive structured feedback from multiple evaluators. A hiring committee's debrief memo tells you more than the individual interviewer scorecards. An editorial decision letter — especially the editor's own paragraph — tells you more than the individual peer reviews. A client's summary of a proposal review meeting tells you more than the written comments from individual stakeholders.

In every case, the collective voice represents a synthesis that the individual voices do not. And in every case, the most common mistake is responding to every individual point with equal weight rather than identifying what the group actually converged on and building your response around that.

The evaluators who individually wrote the most about a concern may not have been the ones who shaped the group's conclusion. The concern that received the most words in an individual critique may have been dismissed in ten seconds during the discussion. And the sentence that captures what the room actually decided may be the shortest one in the document.

Reading evaluation well is not about being thorough. It is about being accurate.

What to carry forward

Your summary statement is not a static document. It is a document whose meaning changes as your understanding of the process that produced it deepens. The version you read the day it arrived is not the version you can read now — not because the words changed, but because you did.

If you are building a resubmission, build it around the room's voice. Find the sentence. Answer it first. Let everything else follow from that.

What is one piece of evaluative feedback — a summary statement, a decision letter, a performance review — that you think might tell you something different if you went back and read it now?

Next week: the Introduction page — one page, one chance, and why most applicants waste it on a list when the reviewers are looking for a narrative.

~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 launched in August — the first cohort outside of an institutional partnership.

NEW: Three seats remain for the next cohort — LIT February 2027 Deadline Cohort — and 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

If October isn't the right time for you — or if you're exploring whether this course is the right fit — I've created a brief interest form where you can tell me a little about where you are in your grant journey and what you're looking for. There's no commitment involved; it simply helps me plan future cohorts and formats around what investigators actually need. I'll follow up personally as new opportunities come together.

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