Never written a grant before? Start here.
A grant application looks intimidating from the outside, but it is really just a clear, structured argument: here is an important problem, here is what we don’t yet know, here is how I’ll find out, and here is why it matters. This guide walks you through that argument in plain English, then hands you off to the editor to draft it with live feedback.
What a grant application actually is
A full application has many parts (budget, biosketches, forms), but two documents do almost all the persuading, and they are the two this tool helps you write:
1 · Specific Aims
One page. The whole proposal in miniature: the problem and gap, your goal and central hypothesis, 2–4 aims, and the impact. If this page is clear, reviewers arrive at the rest already on your side.
2 · Research Strategy
The longer core, organized as Significance, Innovation, and Approach — where you show the work matters, is new, and is feasible.
Your first draft, step by step
- 1
Orient before you write
Find the funding opportunity (NOFO) you’ll apply to and read it once, end to end. It tells you the deadline, page limits, and exactly what the funder is looking for. Then pick the mechanism that fits your project’s size and your career stage — a small pilot is an R03; a full project is an R01; a PhD training project is an F31. In the editor you can switch mechanisms and see how expectations change.
- 2
Open on why it matters
Start your Specific Aims with the real problem — the disease burden, the scientific puzzle — and then name the specific gap in knowledge. Not “this area is understudied,” but the precise thing we don’t yet know that your project will resolve.
- 3
State one goal and one hypothesis
Give your long-term goal, then the objective of this application, then a single testable central hypothesis that every aim serves. Anchor it in the prior work and any preliminary data that make it credible.
- 4
Lay out 2–4 aims that stand on their own
Each aim tests part of the hypothesis and should not collapse if another aim fails — avoid “Aim 2 only works if Aim 1 succeeds.” For each, hint at the approach and the expected outcome. Aims are objectives to test, not a list of methods.
- 5
Close on the payoff
End with the impact: what changes for the field or for patients if this works. Keep the whole thing to about a page — tighten wording rather than cutting the logic.
- 6
Expand into the Research Strategy
Now write the longer document. Under Significance, establish importance and the gap. Under Innovation, say plainly what is new. Under Approach, go aim by aim — rationale, design, expected outcomes — and address rigor (controls, blinding, sample size), preliminary data, anticipated problems with alternatives, and sex as a biological variable.
- 7
Tighten with live feedback
Paste each draft into the editor. It reads the way a time-pressed reviewer skims — flagging a buried aim, a missing rigor cue, hedged wording, or an unclear impact statement — and lets you fix them before anyone else sees the draft. You can download the feedback to work from it offline or share it with a mentor.
First-timer mistakes to avoid
- Burying the gap. Reviewers should find the exact unknown within the first paragraph, not infer it.
- Interdependent aims. If one aim failing sinks the others, the whole project reads as risky.
- Hedged language. “May possibly help elucidate” reads as unsure. State what you will do and expect to find.
- No payoff. A proposal that never says what changes if it succeeds leaves reviewers cold.
- Ignoring the mechanism. An R21 padded with feasibility reads like a weak R01. Write to the award you chose.
- Skipping rigor. Missing controls, power, or SABV are among the most common — and avoidable — score-killers.
Plain-English glossary
- NOFO (or FOA)
- Notice of Funding Opportunity — the official call that tells you what the funder wants, who can apply, page limits, and deadlines. Its instructions always override any general advice, including ours.
- Mechanism / activity code
- The type of award (R01, R03, R21, F31, K08, and so on). Each has its own scope, budget, page limits, and what reviewers expect. Pick the one that fits your stage and project size.
- Specific Aims
- A single page that summarizes the whole proposal: the problem, the gap, your hypothesis, 2–4 aims, and the payoff. Reviewers read this first — and sometimes it is nearly all they read closely.
- Research Strategy
- The longer core of the proposal, organized (for NIH) as Significance, Innovation, and Approach. It is where you prove the work matters, is new, and is feasible.
- Study section
- The panel of expert reviewers who read and discuss your application. Writing so a smart non-specialist on the panel can follow you is a real advantage.
- Preliminary data
- Your own early results showing the approach can work. They build the reviewer’s confidence that you can actually do what you propose.
- Rigor & reproducibility
- Controls, blinding, adequate sample size/statistical power, and validated key resources — the safeguards that make results trustworthy. NIH weighs these explicitly.
- SABV
- Sex as a Biological Variable. NIH expects you to account for sex in the design and analysis of research with vertebrate animals or humans, or to justify studying one sex.
- PI
- Principal Investigator — the person (that’s you) responsible for the project. Some awards support a candidate’s training and career, not just the science.
Ready to draft your first page?
Load an example to see the shape, then replace it with your own. It clears when you switch grant types, so you always start clean.