There is a moment in every grant you write where the document stops cooperating.
You have done the reading. You have the preliminary data. You know, from this series or from hard experience, what the Aims page needs to do, what the Significance section needs to carry, how the Approach section needs to read. You sit down with the framework clear in your mind. And the paragraph will not come together.
You rewrite the sentence. You restructure the paragraph. You step away, come back, read it fresh. The words are fine. The logic tracks. And something is still wrong — a resistance in the writing that you can feel before you can name.
I want to talk about that moment. Because it is the most important moment in your grant, and it is the one that every grantsmanship workshop skips.
What the resistance is telling you
A paragraph that will not come together is almost never a writing problem. It is a thinking problem wearing a writing costume.
When the sentence will not land, something underneath it has not been resolved. The conceptual model has a joint that does not connect. The mechanism you are proposing has a step you have not fully reasoned through. The link between your aim and your method has a gap that your mind has been stepping over but your writing cannot.
I have experienced this on every grant I have written. Every single one. There is always a paragraph — usually in the Significance section or the opening of the Approach — where the writing goes slow. Where I find myself reaching for "filler" language. Where the sentence I produce sounds right but feels hollow. And every time, when I stop trying to fix the writing and start asking what the writing is trying to tell me, I find the same thing: the science underneath that paragraph is unfinished.
The draft is not failing you. It is teaching you.
The filler language diagnostic
There is a specific kind of language that appears in a grant when the thinking underneath it has not been completed. I call it scaffolding language — words that hold the space where a precise claim should be but is not yet ready.
You know this language. You have written it. You may be writing it right now.
"This innovative approach will address a critical gap in our understanding of..."
"The proposed study has the potential to significantly impact..."
"These findings will provide important insights into..."
Each of these sentences sounds like a grant. Each of them says almost nothing. They are placeholders for specificity that has not yet arrived — and they appear in your draft at the exact locations where your scientific reasoning has not yet crystallized into a precise, defensible claim.
When I review grants — for study section, for colleagues, for LIT participants — I can find the unresolved science by finding the filler language. It is diagnostic. The sections where the writing is sharp, specific, and precise are the sections where the investigator knows exactly what they think. The sections where the writing turns vague, abstract, and full of words like "innovative" and "significant" and "critical" are the sections where they are still figuring it out.
Your reviewer reads the same pattern. They may not name it the way I am naming it here. But they feel the shift — the moment the writing goes from someone who knows to someone who is reaching. And that shift registers as a concern about scientific rigor, even when the methods are sound, because the language has communicated uncertainty the investigator did not intend to communicate.
Why this gets worse as you get better
Here is the part that nobody tells you, and it is the part that matters most for anyone reading this in the middle of a February deadline draft.
The better you get at grantsmanship, the harder the resistance hits. When you were writing your first grant, the whole document was difficult and the difficulty felt uniform. You did not notice the paragraphs that resisted because every paragraph resisted. The writing was hard everywhere, and you attributed that difficulty to inexperience.
As you develop craft — as you internalize position aims, dual-audience Significance, operational Approach sections — the easy parts of your grant start writing faster. The sections where your thinking is solid come together in an afternoon. The Aims page, if your conceptual model is clear, writes itself once you have given yourself permission to assert a position.
And then you hit the paragraph that will not come. And now the contrast is sharp. The rest of the document is moving. This section is stuck. And the stuckness feels worse than it did when everything was stuck, because now you know what flowing feels like, and this is not it.
That contrast is information. It is telling you exactly where your grant needs more thought — which is exactly where your reviewer would have found the weakness if you had papered over it with scaffolding language and moved on.
The resistance is a gift. Granted, it does not feel like a gift. It feels like failure at 11:59 PM with a deadline approaching. But it is your draft telling you where the science needs you to go deeper before the reviewer gets there first.
What to do when the paragraph will not come
Stop writing. I mean this literally. Close the document. Not because you need a break — although you might — but because the tool you need in that moment is not a keyboard. It is a whiteboard, a blank piece of paper, or a conversation with the smartest person on your team.
The paragraph will not come together because the idea underneath it is not yet a paragraph. It is still a question. And questions do not resolve through better sentence construction. They resolve through thinking — drawing the conceptual model, walking through the logic aloud, asking yourself the question your draft is asking you: What do I actually believe happens here, and why?
When I hit the resistant paragraph, I do three things in this order.
First, I name what the paragraph is supposed to accomplish. One sentence. "This paragraph needs to explain why stigma, and not health literacy, is the operative barrier to screening uptake in this population." If I cannot write that sentence — if I cannot articulate in plain language what the paragraph is doing in the grant — the paragraph is not stuck because of the writing. It is stuck because I have not decided what it needs to say.
Second, I answer the paragraph's question out loud. Not in writing. Aloud. To a colleague, to my dog, to the wall. Because spoken language is less precise than written language, and that imprecision is exactly what I need. When I am writing, I reach for the careful, hedged, grant-register sentence. When I am talking, I say what I actually think. And what I actually think is usually the paragraph.
Third, I write the paragraph ugly. No grant language. No scaffolding. Just the claim, stated plainly, with the reasoning underneath it. "I think stigma drives avoidance because people who smoke internalize a belief that they caused their own risk, and that belief makes the screening encounter feel like a site of judgment rather than a site of care. The intervention addresses this by restructuring the encounter around the person's agency rather than their risk behavior." That is not a polished paragraph. It is a clear one. And a clear paragraph can be polished. A vague one cannot.
The paragraph nobody wants to write
There is one more version of the resistant paragraph, and it is the one that keeps people stuck the longest. It is the paragraph where you know what you need to say but you do not want to say it — because saying it means acknowledging a limitation, a complexity, or an uncertainty that you have been hoping the reviewer would not notice.
The paragraph about why your comparison condition might show effects too. The paragraph about what happens to your study if attrition exceeds your projections. The paragraph about the alternative explanation for your preliminary findings that you have not yet ruled out.
These paragraphs resist because writing them feels like weakening your own application. It feels counterintuitive to name a vulnerability on a page that is supposed to persuade. And so investigators avoid them — leaving the space blank, or filling it with scaffolding language that gestures at the issue without addressing it.
The reviewer finds it anyway. They always find it. And when they find a limitation that you did not address, they read it as a limitation you did not see. When they find a limitation you addressed directly — with precision, with a contingency plan, with the intellectual honesty to say "this is a real consideration and here is how we account for it" — they read it as scientific maturity.
The paragraph you do not want to write is often the paragraph your grant needs most. And the resistance you feel when you approach it is the truest signal your draft will give you about where the reviewers' attention will land.
The February question
If you are writing right now — Aims page open, Significance section in progress, Approach taking shape — I want you to hold one question this week.
Where is your draft resisting you?
Find that paragraph. The one that will not come together. The one where you keep reaching for words like "innovative" and "significant" and "critical" instead of saying what you mean. The one you have been skipping and coming back to. The one you wrote at midnight and are hoping looks better in the morning.
That paragraph is where your grant lives. Everything else is execution. That paragraph is where the science is still becoming itself — where your understanding of the problem is deepening in real time, on the page, through the act of trying to articulate it.
Do not paper over it. Do not fill it with scaffolding. Sit with the resistance. Let the draft teach you what you have not yet figured out. And then write the paragraph that comes after the figuring out — the one that is specific, precise, and honest about what you believe and why.
That paragraph will be the strongest paragraph in your grant. Because it will be the one you earned.
What is one paragraph in a grant, a paper, or a proposal that resisted you — and what did the resistance eventually teach you about your own thinking?
~Lisa Carter-Bawa, PhD, MPH, APRN, ANP-C, FAAN, FSBM
More insights at lisacarterbawa.com/insights
Lost In Translation (LIT) grantsmanship curriculum is available as a self-paced online course and as an intensive institutional cohort for cancer centers, training programs, and research-intensive departments. Module 1 is free.
I also run small cohorts timed to the NIH grant submission cycle — five live Monday sessions, full access to the LIT course (14 modules + 13 workbooks), and 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.
If you are interested in an upcoming cohort, indicate interest here: https://forms.gle/Eysi8qEjBXNY1w388
