5 Structural Mistakes I See in Almost Every NSF GRFP Draft (and How to Fix Them)

By Ya'el Courtney, PhD | Stanford Postdoc, Harvard PhD in Neuroscience
Last updated: March 2026

When I review a first draft of an NSF GRFP personal statement or research plan, I can usually identify the biggest structural problems within the first two minutes. Not because the writing is bad — most of my clients are talented writers and strong scientists. The problems are almost always structural, not surface-level. They're about what's missing, what's in the wrong place, and what's taking up space without earning it.

After coaching more than 25 GRFP applicants and reviewing drafts across neuroscience, molecular biology, ecology, genetics, chemistry, and engineering, I see the same five mistakes come up again and again. Here they are — and here's how to fix them.

Mistake #1: Writing a CV in Essay Form

This is the most common problem and the hardest to see in your own work. It sounds like this:

"In the summer of 2022, I worked in Dr. X's lab. I learned techniques A, B, and C. Then I moved to Dr. Y's lab, where I conducted experiments using technique D. I also gained experience in techniques E and F."

That's not a personal statement. That's a chronological list of jobs reformatted into paragraphs. It tells the reviewer what you did but not why you did it, what you learned from it, or how it changed the direction of your thinking.

The fix: For every research experience you describe, ask yourself three questions: (1) What drew me to this specific project? (2) What did I actually discover or contribute? (3) How did this experience shape what I did next? If your paragraph doesn't answer at least two of these, it's still a CV entry, not a narrative.

The reader should be able to follow the logic of your decisions. "My experience with fMRI in the Braver lab showed me I wanted to get closer to the cellular level" is a transition that tells me something about you as a developing scientist. "I then moved to Dr. Casadesus-Smith's lab" without explanation is just the next line on your resume.

Mistake #2: Describing Your Research Without Stating Your Results

This one drives me slightly crazy, because it's so easy to fix and makes such a big difference. I see it in almost every first draft I review. The applicant describes their project setup in detail — the model system, the techniques, the experimental approach — and then wraps up with something like:

"This research revealed critical insights into conservation efforts."

Or: "These findings contributed meaningfully to the field."

Or: "This experience deepened my understanding of environmental challenges."

These sentences say absolutely nothing. The reviewer finishes your paragraph not knowing what you actually found. And here's the thing — what you found is the most important part. It's the evidence that you can do science, not just participate in it.

The fix: Replace every vague summary sentence with a concrete result. You don't need to include every detail, but you need the headline finding. "I found that MED12 deficiency reduces cell ciliation without affecting ciliary length" is one sentence, and it tells the reviewer infinitely more than "my findings contributed to the field."

If you're not sure what your headline finding is, ask your PI. If the project didn't produce clear results yet, that's okay — describe what you expect to find and why, or describe what your analysis showed so far. Even "preliminary data suggest that X correlates with Y" is more informative than vague impact language.

Mistake #3: Treating Broader Impacts as an Afterthought

I've read personal statements from genuinely impressive scientists whose Broader Impacts section is two paragraphs of boilerplate: "I am committed to diversity and inclusion in STEM. I plan to mentor underrepresented students and participate in outreach events."

Reviewers evaluate Intellectual Merit and Broader Impacts with equal weight. An application with outstanding research credentials but thin Broader Impacts will not score as well as one with strong performance in both areas. I've seen it happen, and it's heartbreaking.

The fix: Broader Impacts should be as specific and story-driven as the rest of your application. Don't tell the reviewer you value diversity — show them what you've done about it. Did you organize a science fair for local middle schoolers? Develop educational materials for patients? Serve as a mentor through a specific program? Lead a DEI initiative in your department? Translate research for a community audience?

Whatever it is, name it, date it, and describe what happened. "I served as an advisor for the BP-ENDURE Neuroscience Pipeline program, guiding undergraduates through first-time lab work and scientific writing" is specific and credible. "I plan to mentor students" is not.

And if your Broader Impacts are deeply personal — if your commitment to access comes from your own experience navigating the system as a first-gen student, a person with a disability, an immigrant, someone from the foster care system — don't be afraid to say so. The most powerful GRFP personal statements I've worked on are the ones where the applicant's personal story and scientific mission are inseparable.

Mistake #4: Making Your Research Plan Too Technical (or Too Vague)

The Graduate Research Plan Statement is only two pages, but it's where most applicants either overdo it or underdo it.

The "too technical" version reads like a dissertation proposal. It's packed with jargon, assumes deep familiarity with the subfield, includes extensive literature review, and buries the main question under layers of methodology. Remember: your reviewers are in your broad area (biology, engineering, geosciences) but probably not your specific niche. If a neuroscientist who studies motor systems can't follow your proposal about synaptic pruning in the prefrontal cortex, you've lost them.

The "too vague" version goes the other direction. It describes a general area of interest ("I want to study how the immune system affects brain development") without a concrete plan. No specific aims, no methods, no expected outcomes. This tells the reviewer you don't yet think like a scientist.

The fix: Aim for a clear structure: a brief introduction that states the gap in knowledge, a specific goal, two concrete aims with enough methodological detail to show you know what you're doing, and expected outcomes plus alternative approaches if things don't work. Include references.

Write it so that a scientist in an adjacent field can understand every sentence. If you find yourself needing to explain three layers of background before stating your question, you're going too deep. Lead with the question, then provide just enough context to make it clear why it matters.

A good rule of thumb: could a fellow graduate student in a different subfield of your department read this and explain your project to someone else? If yes, your level of specificity is right.

Mistake #5: Forgetting That This Application Is About Your Potential, Not Just Your Past

The GRFP funds people, not projects. Reviewers are asking: "Does this person have the potential to make significant contributions to STEM?" Your past experiences are evidence, but they're not the whole case.

The mistake I see is an application that's 90% backward-looking and 10% forward-looking — all about what you've done, with a brief paragraph at the end about wanting to do more of the same in grad school. This misses an opportunity.

The fix: Your future goals section should feel like the natural culmination of everything that came before. Connect your proposed research direction to specific skills and questions from your past work. Articulate not just what you want to study but why it matters — for the field, for society, for the communities you care about.

And don't be afraid to think big. "I plan to pursue a career as an independent neuroscientist whose lab combines basic research with a deep commitment to training the next generation of diverse scientists" is a vision. "I hope to do more research in this area" is a placeholder.

The Underlying Pattern

If you look at all five of these mistakes, they share a common root: they're all ways of playing it safe. Listing accomplishments instead of telling a story. Describing techniques instead of results. Keeping Broader Impacts generic instead of personal. Writing too technically to avoid being "wrong." Looking backward instead of articulating a vision.

The strongest GRFP applications I've worked on are the ones where the applicant was willing to be specific, personal, and clear about who they are and where they're going. Specificity is what makes you memorable. Vulnerability is what makes you human. Clarity is what makes you fundable.

If you're staring at a draft right now and recognizing some of these patterns, that's a good sign — it means you know what to fix. And if you want a second pair of eyes from someone who's seen hundreds of these, I offer everything from single strategy sessions to full-cycle GRFP coaching that covers both statements from first outline to final submission. You can find the details here.

Ya'el Courtney is a Stanford postdoc with a PhD in Neuroscience from Harvard. She has supported 25+ NSF GRFP applicants and 75+ graduate school applicants across STEM fields. Learn more about coaching →