How to Write Specific Aims: A Paragraph-by-Paragraph Method

To write Specific Aims, you compress the whole project onto one page in four moves: the problem and the gap in current knowledge, your objective and central hypothesis, two or three concrete aims, and the impact if you succeed. In NIH applications this page is limited to one page, it is the first thing every reviewer on the panel reads, and the rest of the application is judged against the promises it makes. This guide covers the method. To see complete pages built with it, go to our worked Specific Aims examples for R01, R21, K, and SBIR applications.

Format rules to set before you write

For NIH, the Specific Aims page is a single-page PDF attachment in the research plan, and exceeding one page is flagged as an error at submission. Standard NIH formatting applies: Arial, Georgia, Helvetica, or Palatino Linotype at 11 points or larger, and margins of at least half an inch on every side. Other funders that ask for aims (foundations, some NIH-style programs at other agencies) may set different limits, so check the instructions.

One page at those settings holds far less than most first drafts. Plan for that from the start: cut background, not specifics, and never push the font or margins below the minimums to make a long page fit.

Paragraph 1: the problem and the gap

The opening paragraph earns attention and sets up the need. It usually runs four to six sentences that move in a fixed direction:

1. The problem and why it matters, with one concrete number if you have it. "Roughly 30 percent of patients started on first-line therapy do not reach target within a year" lands harder than "this is an important clinical problem."
2. What is known, in one or two sentences, only as much as the reader needs.
3. The gap: the specific thing nobody knows or cannot yet do. This is the sentence the whole page depends on.
4. Why the gap matters: what stays stuck while it remains open.

Avoid opening with your lab's history or "has been studied extensively," which argues against novelty. Your qualifications belong in the biosketch; our NIH biosketch example shows where they go in the current format.

Paragraph 2: objective, hypothesis, and rationale

This paragraph turns the gap into your project. A widely used sequence is:

• Long-term goal: the larger program of work this project serves.
• Objective of this application: what this award specifically delivers.
• Central hypothesis: a statement that could be shown wrong. Many applicants bold it.
• Rationale: the preliminary data or prior work that makes the hypothesis credible, stated with a number where possible.
• Why you: one sentence on the team, data, or resource that makes you well placed to do it.

Sentence patterns that do this work:

"Our long-term goal is [larger aim]. The objective of this application is to [specific deliverable]. Our central hypothesis is that [testable statement], based on preliminary data showing [result, with number]."

If the project is not hypothesis-driven (technology development, method building, many SBIR projects), replace the hypothesis with the key innovation and the feasibility question the project will answer. Do not invent a hypothesis to fit the template; reviewers notice.

The aims

List two or three aims for most applications. Each aim gets:

• A one-line heading that states what the aim does, starting with a verb: determine, test, quantify, validate, establish.
• One to three sentences of approach: the system, sample, or design, at a level a reviewer can picture.
• An expected outcome, ideally with a threshold or criterion that would count as success.

Compare two versions of the same aim:

Weak: "Aim 1. Investigate the role of transporter expression in treatment response."

Strong: "Aim 1. Test whether baseline transporter expression predicts twelve-month treatment response. We will measure the signature in 600 treatment-naive patients and model response at twelve months. Expected outcome: a validated predictive model meeting a pre-specified accuracy threshold."

The weak version cannot fail and so cannot succeed. The strong one tells the reviewer what will be done, to whom, and how you will know it worked.

Check independence. Ask of each aim: if the previous aim returns a null result, is this one still worth funding? Strictly sequential aims (build it, then train it, then test it) mean a single setback ends the project, and reviewers will say so. Where the science is sequential, design each aim to produce a useful result on its own, or build in an alternative path.

Keep scope honest. Two aims usually suit a two-year R21 or an SBIR Phase I; three suit a five-year R01. Four or more rarely fit the time and budget and suggest scope that has not been disciplined.

The closing paragraph: impact

End with what success makes possible, not a restatement of the aims. State the expected outcome of the project as a whole, the effect on the field or on patients, and the next step it enables (a larger trial, a Phase II, an R01). One sentence on the broader payoff is enough. "This work will have a major impact" is where reviewers stop reading.

How the page shifts by mechanism

The four-part structure holds, but emphasis changes:

• R01: three aims, substantial preliminary data, a mechanistic or confirmatory hypothesis, and an impact paragraph that points toward clinical or scientific consequence.
• R21: exploratory, so preliminary data is optional. Emphasize why the idea is high-risk and high-reward and what result would justify a larger study. Two aims is normal.
• K awards and F fellowships: the aims describe the research project, but the page should make clear how that project builds the candidate's skills toward independence, often with a sentence linking the aims to the training plan.
• SBIR and STTR Phase I: one feasibility question, usually two aims, numeric success criteria, and a closing line on the commercial path. Our guide to writing an SBIR proposal covers how the aims fit the rest of a small-business application.
• Resubmissions: the aims can change, and often should, in response to the summary statement. Explain the changes in the one-page introduction rather than on the aims page itself.

A drafting process that works

1. Write the gap sentence and the hypothesis first. If you cannot write those two sentences, the page is not ready to draft.
2. Draft the aims next, then write paragraphs 1 and 2 to lead into them.
3. Cut to one page by removing background, not specifics. Numbers and criteria stay; adjectives go.
4. Test it on a colleague outside your subfield. Ask them to tell you the problem, the hypothesis, what you will do, and why it matters. Any stumble marks the paragraph to fix.
5. Let it drive the Research Strategy. Each aim becomes a section of the approach, the hypothesis becomes the thread of Significance and Innovation, and the preliminary data you cite becomes the feasibility subsection. If the aims change later, carry the change through every section.

For a fill-in scaffold, use our Specific Aims template. For the wider NIH process the page sits inside, from activity codes to review, see our overview of NIH grants. If you would rather have specialists draft or rebuild the page, our NIH grant writing service starts there.