Research Grant Proposal and Report Template

Start with the funder's call, which may be titled a solicitation, a notice of funding opportunity or a request for proposals. Read it three times before you write a sentence, looking for something different each time.

Don't skip the third pass because reporting feels years away. The period of performance (the award's start and end dates) and the reporting schedule fix every date you will be held to. If your study involves people, plan the ethics application alongside the proposal, not after it.

Draft the one-page summary of your aims before the long narrative, because everything else expands on it. NIH limits its Specific Aims page to one page and encourages drafting it early¹. It adds that a typical applicant for an R01 research project grant proposes about three related aims that can be completed in four or five years.

Open with the problem, then the gap your work fills, then the aims, and close with what will exist when the award ends. Give every aim deliverables someone could check. "Characterize the variation" can't be reported as done. "The variation analysis, published as a dataset and a paper" can.

As NIH suggests, have mentors and colleagues read the aims before you build on them. For an NIH application, a mock study section review shows what reviewers are likely to question.

Reviewers score against published criteria, so make those criteria your outline, with the funder's headings in the funder's order. For applications due on or after January 25, 2025, NIH reviews most research project grants on three factors². The first two, Importance of the Research and Rigor and Feasibility, are each scored from 1 to 9. The third, Expertise and Resources, is judged sufficient or not.

NSF evaluates all proposals against two criteria, Intellectual Merit and Broader Impacts³. Its guide also expects principal investigators (PIs) to be accountable for carrying out the activities a funded project describes, with clear goals and a plan to document outputs. A workshop added to sound generous is a workshop you will have to run.

Promises collect fastest in four places:

• The approach, where every count, site, duration and frequency is a separate commitment
• Broader impacts or outreach, often written last and left unpriced
• Letters of support, where a partner's offer becomes your obligation
• The data sharing plan, where each repository, format and deadline is a promise

Build the budget while you write, not after. NIH advises noting the related expenses for your budget and budget justification¹ while you draft your experiments.

Then check your promises against the budget in both directions. Promise by promise, name the line that funds it, and write "none" where nothing does, so nobody mistakes an unfunded promise for an unchecked one. Line by line, list the promises each budget line carries. A line carrying work from every aim is either the most important line in the budget or a default nobody costed.

Decide before you submit, while you can still change the text. Then write the budget justification line by line, in the funder's categories.

The data management and sharing plan is short, but nearly every line commits you to something: a repository, a format, a license, a deadline. NIH now requires its 2026 plan format⁴, which asks whether the data behind each paper will be shared by the time it is published. NIH staff then check compliance with the plan at each annual progress report.

NIH also wants data management and sharing costs in the budget and its justification, so price that work like any other. Then look for promises that outlast the award, such as a retention period, or sharing the data behind a paper that appears after the award ends. Decide now who will handle them once the money stops. For a full plan, start from the research data management plan template.

In the US, the federal Uniform Guidance sets the outer limits. Under 2 CFR 200.329⁵, performance reports come no less often than annually and no more often than quarterly. Annual reports are due within 90 calendar days after the period they cover, and the final report within 120 calendar days after the period of performance ends.

Your award can set earlier dates. NSF wants annual project reports at least 90 days before the budget period ends⁶. Late final reports also delay NSF's processing of other pending proposals from the same PIs and co-PIs.

Don't save bad news for the next report. The federal rule also requires you to tell the agency between reports when problems or delays will affect your ability to meet a milestone. That notice must include your plan for corrective action. Each report should then compare your accomplishments with the award's objectives and explain any goal you didn't meet.

The template on this page keeps every promise in a register beside the proposal documents. Open it with Edit with AI to have River date each report from your award and flag the promises nothing pays for.