Week 9: Writing for the Reviewer Who Reads Your Grant at 11 PM

Last week, I talked about the architecture of a resubmission — why line-by-line revision produces applications that look patched rather than rebuilt, and how to identify the structural problem underneath the surface-level critiques.

This week, I want to talk about something that shapes every score but almost never gets discussed in grantsmanship training: how reviewers actually read.

Not how they are supposed to read. How they read at 10:47 PM on a Tuesday night, three grants into a stack of eight, with study section two weeks away and a full clinical or teaching load that did not pause because they agreed to serve on a review panel.

This is not a writing craft conversation. This is a scoring strategy conversation. Because the grants that score well are not always the ones with the strongest science. They are the ones where the strongest science is easiest to find.

The reviewer's cognitive reality

Here is what most applicants do not account for. A typical study section reviewer is assigned 6 to 8 applications. Each application is 12 pages of Research Strategy, plus Specific Aims, plus budget justification, plus biosketches, plus facilities and resources, plus letters of support. Multiply that across every assigned application, and your reviewer is reading hundreds of pages in the weeks leading up to study section — while continuing to do their actual job.

They are not reading your application the way you wrote it. You wrote it sequentially, building an argument across paragraphs, layering evidence, constructing a narrative arc from Significance through Innovation through Approach. You spent months making sure the logic flows.

Your reviewer is not following that flow. They are scanning. They are reading your Specific Aims page carefully — that is the one document almost every reviewer reads in full. Then they are moving through your Research Strategy looking for answers to specific questions: Is the problem real? Is the approach feasible? Is the design rigorous? Will this study actually produce what the applicant claims it will produce?

When they find the answer quickly, they note it and move on. When they cannot find it, they do not re-read. They write a critique.

The cost of making a reviewer search

This is the part that is hard to hear. A reviewer who cannot locate your argument is not going to assume the argument exists somewhere in the document. They are going to write that the argument is missing. Or unclear. Or insufficiently developed.

I have sat on review panels and watched this happen in real time. A critique gets raised in discussion — "the justification for the sample size was not well supported" — and the applicant had, in fact, included a detailed power analysis. It was buried in the middle of a dense paragraph in Aim 3, separated from the sample size description by two pages of procedures.

The science was there. The reviewer did not find it. The score reflected what the reviewer experienced, not what the applicant intended.

This is not a failure of the reviewer. It is a failure of information architecture. And it is one of the most fixable problems in grantsmanship.

Information hierarchy: what goes where and why it matters

Information hierarchy is a concept borrowed from design. It means organizing content so that the most important information is the most visually and structurally prominent. In grant writing, it means three things.

First, the most critical claim in any section should appear in the first two sentences of that section. Not the third paragraph. Not after the background. Not after you have established the context a reviewer needs to appreciate the claim. The claim comes first. The context follows. This is the opposite of how most scientists are trained to write — in academic papers, you build to your point. In a grant application, you lead with it.

Second, every aim should be independently legible. A reviewer should be able to read Aim 2 without having read Aim 1 and still understand what you are proposing, why it matters, and how you will do it. Yes, your aims are integrated. Yes, they build on each other. But a reviewer who is checking your approach against their concerns is not reading linearly. They are jumping to the aim they have questions about. If that aim depends on context from a previous section to make sense, you have created a dependency that costs you clarity — and clarity is what drives scores.

Third, use structure to do the work that sentences cannot. Subheadings that name your argument — not generic labels like "Approach" but specific ones like "Sequential Mixed-Methods Design Linking Community Narratives to Screening Outcomes" — tell a reviewer what you are doing before they read a single sentence. They function as an outline of your logic that a scanning reader can follow in thirty seconds. A reviewer who can follow your logic from subheadings alone will read the details with confidence. A reviewer who cannot follow your logic from subheadings will read the details with suspicion.

The Specific Aims page is a cognitive contract

I have written about the Specific Aims page before, but it is worth returning to here because it is the single most important piece of information architecture in your application.

The Aims page is not a summary. It is a contract with the reviewer. It tells them: here is the problem, here is what we do not yet know, here is what I propose to do about it, and here is what the field gains if this works. Every word on that page sets a reviewer's expectations for what they will find in the Research Strategy.

When the Research Strategy delivers on those expectations — when the reviewer finds exactly the argument the Aims page promised, in approximately the order it was promised — the cognitive experience is one of coherence. The application feels organized. The science feels clear. The applicant feels competent. These impressions are not separate from the score. They are the score.

When the Research Strategy contradicts or rearranges what the Aims page promised — when Aim 2 in the strategy looks different from how it was described on the Aims page, or when the Innovation section argues for something the Aims page did not set up — the cognitive experience is one of confusion. And confusion, in peer review, reads as weakness.

This is where the LIT curriculum lives

The Five Translation Gaps that structure the Lost In Translation curriculum — the gaps between what a scientist knows about their own work and what a reviewer can see on the page — are fundamentally about cognitive load. Gap 1 is the assumption that your expertise is visible in your writing. Gap 2 is the belief that logical connection implies written connection. Each gap represents a place where the applicant's internal clarity does not survive the translation to the page.

The LIT February 2027 Deadline Cohort is built around closing those gaps in real time — five live sessions timed so your Specific Aims page is reviewed, revised, and pressure-tested before the February 5 deadline. The work is not about better sentences. It is about building an application that a reviewer can follow at 11 PM without losing the thread.

Write for the scan, not the read

Here is a practical framework. Before you submit — or before you finalize a resubmission — print your Research Strategy and read it the way a reviewer will. Not carefully. Quickly. Give yourself 10 minutes to get through 12 pages. Notice where your eyes land and where they skip. Notice where you have to slow down to understand a transition. Notice where a paragraph runs long enough that you lose track of its point before reaching the end.

Those are the places where a reviewer will write a critique. Not because the science is flawed. Because the writing made the science invisible.

Then apply three tests.

Can a reviewer identify your central argument from the first two sentences of each section? If they cannot, restructure so the lead sentence carries the claim.

Can a reviewer follow the logic of your application from subheadings alone? If the subheadings are generic or do not connect to each other, rewrite them as an argument outline.

Can a reviewer find the answer to any single question — sample size, timeline, analytic approach — within thirty seconds? If any answer requires reading across multiple sections to assemble, consolidate it.

These are not stylistic preferences. They are cognitive accommodations for a reader who is doing demanding intellectual work under time pressure. And the applicants who make those accommodations consistently are the ones who score well — not because their science is better, but because their science is findable.

The deeper truth

I have reviewed grants where the underlying science was exceptional and the writing made it almost impossible to see. And I have reviewed grants where the science was solid — not extraordinary, but well-conceived and feasible — and the writing made it land with clarity and force. The second category scores better. Not because peer review is superficial, but because peer review is human. Reviewers are doing their best with limited time and significant cognitive demands. An application that respects those constraints is an application that gets a fair read.

This is not about dumbing down your science. It is about translating it — making what you know visible to someone who does not yet know it, under conditions that are less than ideal. That is the core of grantsmanship. And honestly, it is the core of every kind of communication that matters.

What is one section of your current application where you know the science is strong but you suspect the writing is making it harder to find?

Next week: what actually happens in the room during study section — how discussion unfolds, how scores shift, and why the conversation your reviewers have about your grant matters as much as what they wrote before they walked in.

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

More insights at https://www.lisacarterbawa.com/insights

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: 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.