The Specific Aims page is the single most consequential page in an NIH grant application. It is capped at one page, it is read before anything else in the application, and by the time a study section reviewer finishes it, many have already formed a working opinion of the whole proposal. Reviewers with a full pile of applications to score routinely read the Specific Aims page closely and skim the rest — which makes this page worth more editing time per word than any other section you will write.
This guide covers the NIH-wide format rules, the conventional structure experienced applicants and program officers describe, the reviewer pitfalls that sink otherwise strong proposals, and how the emphasis shifts for mechanisms other than the standard R01 — including F31 and other fellowship applications. It assumes you already know how to plan the underlying science; for the surrounding application — budget, biosketches, letters of support, and the rest of the package — see CASRAI’s How to Write a Grant Proposal guide.
NIH Specific Aims Page Format Requirements
The formatting rules come from the NIH SF424 (R&R) Application Guide and apply across essentially every NIH grant and fellowship mechanism that includes a Specific Aims page:
- Length: one page. This is a hard limit, not a suggestion — NIH’s eRA Commons submission system and the Center for Scientific Review’s referral and assignment process both treat a Specific Aims section that runs onto a second page as non-compliant, which can trigger a withdrawal-and-resubmit cycle before the application is even reviewed.
- Margins: at least one-half inch on all sides (top, bottom, left, right).
- Font size: 11 points or larger for the body text (figure legends and tables may use a smaller size, but NIH still expects them to be legible without magnification).
- Type density: no more than roughly 15 characters per linear inch, effectively ruling out condensed fonts used to cram in more text.
- Page size: standard 8.5″ x 11″ (US letter).
These specifics live in the NIH “How to Apply — Application Guide” page-limits table (grants.nih.gov) and are reissued periodically as NIH updates its SF424 forms package (most recently the Forms-I series) — the underlying one-page limit for Specific Aims has been stable across form revisions for years, but always check the current page-limits table for your specific funding opportunity announcement (FOA) before submitting, since some mechanisms and some FOAs layer additional instructions on top of the general rule.
The Standard Specific Aims Structure
NIH does not mandate a structure for the Specific Aims page the way it mandates the page limit — there is no required template. But across study sections and mechanisms, a de facto structure has become the convention because it reliably answers the questions a reviewer needs answered fast. It has three parts.
1. Opening: Hook and Problem Statement
The first paragraph (typically 3-6 sentences) establishes why the work matters before it explains what you will do. A strong opening usually does four things in quick succession: states the broader problem or unmet need, identifies the specific knowledge gap or critical barrier standing in the way, briefly establishes your preliminary evidence or rationale for believing the gap is addressable, and states your central hypothesis or long-term objective. Reviewers are triaging dozens of applications; an opening that buries the actual scientific problem under throat-clearing background loses attention it will not get back.
2. The Aims Themselves (Typically 2-4, Numbered)
Most Specific Aims pages present two to four numbered aims, each as a short paragraph (roughly 3-5 sentences) that states the aim as a clear, falsifiable objective, briefly describes the approach, and — where useful — states a working hypothesis specific to that aim. Three aims is the most common count; two aims can look thin for a full R01, and five or more often signals the project is trying to do too much for the funding period and starts raising feasibility concerns instead of addressing them. See “Common Reviewer Pitfalls” below for the specific ways aims structure most often goes wrong.
3. Closing: Impact Paragraph
A final short paragraph (2-4 sentences) states the expected outcome of the project as a whole and connects it back to the significance established in the opening — what will be different, known, or possible once all the aims are complete that isn’t now. This is also where applications sometimes gesture at the longer-term trajectory the proposed work sets up, without overpromising results the current budget period cannot actually deliver.
An Illustrative Specific Aims Skeleton
The example below is a generic, illustrative composite written to show structure only — it is not drawn from, or attributed to, any real funded application, applicant, or institution. Do not use its scientific content as a model; use only its shape.
[Opening — 1 paragraph]: States the disease burden or knowledge gap, cites the field’s current limitation, briefly summarizes the applicant’s preliminary data supporting feasibility, and states the central hypothesis.
Aim 1: Determine [a specific, measurable mechanistic or clinical question], using [approach], to test the hypothesis that [X]. Expected outcome: [what this aim establishes, independent of Aims 2-3].
Aim 2: Evaluate [a related but independently answerable question], using [approach]. Expected outcome: [what this aim establishes on its own].
Aim 3: Test [a third, independently answerable question], using [approach]. Expected outcome: [what this aim establishes on its own].
[Closing — 1 paragraph]: Restates the overall expected contribution and the field-level significance once all aims are complete.
Common Reviewer Pitfalls
Study section critiques of the Specific Aims page cluster around a small number of recurring problems. Each is fixable in editing, which is exactly why reviewers penalize them — they read as avoidable.
- Aims that aren’t independent. If Aim 2 can only be interpreted, or only makes sense, once Aim 1 succeeds, reviewers will describe the aims as “not independent” — a specific, commonly used critique. Each aim should be able to stand on its own and produce an interpretable, publishable result even if the other aims fail entirely.
- Aims contingent on each other’s success. A closely related problem: if Aim 3 requires a specific (and uncertain) outcome from Aim 1 to even be attempted — “if we find X in Aim 1, we will then test Y in Aim 3” — the whole project’s risk becomes correlated across aims instead of diversified. Reviewers read this as a single high-risk bet dressed up as three aims, which undermines exactly the feasibility argument the aims page exists to make.
- One aim split into two (or three). The inverse problem — presenting what is really a single line of investigation as multiple numbered aims to look more ambitious. Reviewers who work with this format daily recognize it quickly, and it reads as padding rather than scope.
- Vague or unfalsifiable aims. An aim phrased as “explore the role of X in Y” without a stated hypothesis, method, or measurable outcome gives a reviewer nothing concrete to evaluate feasibility against.
- Overpromising relative to the mechanism and budget period. Proposing what reads like a five-year research program’s worth of work inside a two-year R21, or a full R01-scale investigation inside a six-page F31 research strategy, signals a mismatch between ambition and the funding instrument that experienced reviewers flag immediately.
- No preliminary data or rationale for feasibility. Aims presented with no supporting rationale at all — not even in the opening paragraph — leave a reviewer with no basis to judge whether the approach is likely to work, which mechanisms like R01s in particular expect the aims page to at least gesture toward.
How Mechanism-Specific Aims Pages Differ
The one-page limit and the three-part opening/aims/closing shape are consistent across NIH mechanisms. What changes is emphasis — what the aims page needs to establish given what the rest of that mechanism’s application does and doesn’t ask for.
F31 and Other Fellowship (F-Series) Applications
An NRSA predoctoral fellowship (F31) Specific Aims page is still one page, but the surrounding Research Strategy is shorter than an R01’s — six pages rather than twelve — and the project it describes should read as a focused, completable dissertation project rather than an open-ended multi-year research program. F31 aims pages typically frame two to three aims scoped to what a graduate student can realistically complete within the fellowship period, and the broader F-series application evaluates training and mentorship (sponsor, co-sponsor, institutional environment) in dedicated sections outside the aims page itself — so the aims page can stay focused on the science without needing to argue the case for the training plan, which is made elsewhere in the application. The postdoctoral equivalent, F32, and institutional training grants like T32, follow a similar logic: scope the science to the career stage and the award period.
R21 Exploratory/Developmental Research Grants
An R21 funds early-stage, higher-risk exploratory work over a shorter period (typically up to two years) and explicitly does not require extensive preliminary data the way an R01 does. R21 aims pages tend to lean more heavily on the novelty and potential impact of the idea in the opening paragraph, since the feasibility argument an R01 makes through preliminary data is, by design, a lighter lift here. The R33 mechanism (often phased with an R21) and the R34 planning grant follow related but distinct logic for staged or preparatory work.
R03 Small Grants
The R03 mechanism funds small, limited-scope projects — typically pilot studies, secondary analysis of existing data, or small self-contained research projects — over a short period with a capped budget. R03 aims pages should reflect that scope directly: reviewers expect one or two tightly bounded aims rather than the three-to-four-aim structure common on a full R01, and an R03 aims page that reads like a scaled-down R01 program (rather than a genuinely small, self-contained project) invites a feasibility critique.
R01 Research Project Grants (the Baseline)
The R01 is the mechanism the conventional three-part structure described above is built around — a multi-year, hypothesis-driven research program expected to be supported by preliminary data and to plausibly sustain two to four independent aims across the full project period.
A Note on Other Mechanisms
Career development (K-series) and some special mechanisms — for example DP2 (NIH Director’s New Innovator Award), which funds unusually innovative early-stage-investigator programs rather than a single defined project — layer additional expectations onto the aims page (career development milestones for K awards; an explicit case for innovation and investigator vision for DP2). The one-page limit and general opening/aims/closing shape still apply; always confirm the exact instructions in the specific funding opportunity announcement, since NIH updates FOA-level instructions independently of the general SF424 page-limits table.
Frequently Asked Questions
What is the NIH Specific Aims page limit?
One page, with one-half-inch margins and 11-point or larger font, across essentially every NIH mechanism that includes a Specific Aims section — including R01, R21, R03, and F-series fellowship applications. Always confirm against the current NIH page-limits table and your specific FOA, since NIH periodically reissues its SF424 forms package.
What is the standard NIH Specific Aims format?
The conventional (not formally mandated) structure is a short opening paragraph establishing the problem and hypothesis, two to four numbered aims each stated as an independent, falsifiable objective with a brief approach, and a short closing paragraph on overall expected impact.
How do I write specific aims for an NIH grant?
Start from the gap in current knowledge your preliminary data supports addressing, state a central hypothesis, and build each aim so it can produce an interpretable, publishable result even if every other aim fails — that independence test catches most of the structural problems reviewers flag. Draft the page early and revise it more than any other section of the application; because it is typically the most-read page, the return on editing time is disproportionately high.
What does a strong Specific Aims example look like?
There is no single template NIH endorses, and CASRAI does not publish specific funded examples verbatim (they are copyrighted applicant work, and using one as a literal template risks reviewers recognizing recycled structure). The skeleton above shows the shape a strong aims page typically follows; many universities’ offices of research and grants-writing centers make redacted or de-identified funded examples available to their own affiliated researchers.
How does an F31 Specific Aims page differ from an R01’s?
The format (one page) and general shape are the same. The difference is scope and framing: an F31 aims page should describe a focused dissertation project scaled to what a graduate student can complete within the fellowship period, typically with two to three aims, while the fellowship’s training and mentorship case is made in separate sections of the application rather than on the aims page itself.
Related CASRAI Resources
For the full application package this page sits inside — budget, biosketch, letters of support, and submission logistics — see How to Write a Grant Proposal: A Research Administrator’s Guide. For related NIH mechanics referenced above, see NIH Study Section, NIH Standard Due Dates, eRA Commons ID, and Cooperative Agreement for how NIH’s grant mechanism compares to a cooperative agreement or contract.
