How to write NIH Specific Aims: what funded applications do

The Specific Aims page is one page, and for many reviewers it is the application. Study-section members read it first, often before anything else, and form an opinion they rarely change. This guide sets out what funded applications do on that page, based on our analysis of 200 funded NIH R01 abstracts, openly shared funded applications, and NIH's own review guidance.

How NIH scores applications now

Since January 2025, NIH reviews most research grants with its Simplified Review Framework:

• Importance of the research (significance and innovation), scored 1–9.
• Rigor and feasibility (the approach), scored 1–9.
• Expertise and resources, rated only as sufficient or not.

Because your reputation is no longer scored, feasibility has to come from the page itself: preliminary data, a sound design and a plan B. The Specific Aims page is where reviewers first decide whether the project is important and doable.

The structure funded aims pages follow

Funded aims pages are among the most consistent documents in research funding. Nearly all follow this order:

1. The problem and why it matters. Open with the burden, scale or stakes. 40% of the funded R01 abstracts we analyzed open with a burden or scale figure.
2. What is known, then the gap. State precisely what is missing and why it blocks progress. In funded abstracts the gap typically arrives about a quarter of the way in.
3. Your long-term goal, the objective of this application, and the central hypothesis. Ground the hypothesis in your own preliminary data.
4. The aims. Each is a bold one-line statement followed by two to four sentences on the approach and the expected result.
5. Expected outcomes and impact. Close with what will be true when the work is done, and why it matters.

How many aims, and how to phrase them

Three aims is the norm. Among funded R01 abstracts that number their aims, 77% have three, 17% have two and 6% have four.

Funded aims start with an action verb: determine, test, establish, define, evaluate, develop. Compare:

• Weak: "Aim 2: Studies of transporter function in drought."
• Strong: "Aim 2: Test whether root nitrate transporters limit recovery after drought."

Make the aims independent. A common reviewer criticism is that Aim 2 depends on Aim 1 succeeding. If it does, say what you will do if Aim 1 comes up empty.

Write like the plan is real

Across every funder we studied, funded abstracts use "will" about ten times as often as "may", "might" or "could". Reviewers fund plans, not possibilities. Save cautious language for interpreting results, not for describing what you will do.

Length

The page limit is one page. Funded aims pages in openly shared applications ran from about 480 to 950 words, with a median near 630. Most use the whole page, with short paragraphs and bold aim statements so a skimming reviewer can find each aim.

Common reasons aims pages fail

• The gap is vague ("little is known about X") rather than specific and consequential.
• No stated hypothesis. 44% of funded R01 abstracts state one outright, and most others imply one clearly.
• Aims that are descriptive ("characterize", "explore") without a testable question.
• Aims that depend on each other with no alternative.
• Generic claims of novelty. Most funded abstracts call their work novel, so the word carries no weight. Say concretely what is new compared with current practice.

A note on this evidence

These patterns come from funded applications, so they show what successful applications have in common, not what guarantees funding. Always follow the instructions in your specific funding announcement.

GrantMatch's NIH template follows this structure, and Pro and Lab users can ask Claude to review their aims the way a study section would.