NIH RPPR Instructions: Annual, Interim, and Final Progress Reports
The RPPR is the report NIH uses to decide whether to release your next budget period's funds. An accepted RPPR keeps the money flowing; a late or incomplete one holds it up.
These instructions cover the three types of RPPR, who does what in eRA Commons, and a section-by-section checklist so you can gather everything before you open the report.
Annual, interim, and final RPPR
| Type | When it is used | Due | Key differences |
|---|---|---|---|
| Annual RPPR | Each year of a multi-year award | 45 days before the next budget period (SNAP) or 60 days before (non-SNAP) | Full report; non-SNAP awards include a detailed budget |
| Interim RPPR | The project period is ending and a competing renewal application has been submitted | Within 120 days of the project period end date | Becomes the annual RPPR if the renewal is funded, or the Final RPPR if it is not |
| Final RPPR | The project period has ended and will not continue | Within 120 days of the project period end date | Only participants section D.1 is required; Changes (F) and Budget (H) are omitted; Project Outcomes (I) is required |
Multi-year funded awards report annually on the anniversary schedule shown in eRA Commons. Always confirm the exact due date for your award there.
Who does what
- The PI initiates the RPPR in eRA Commons and prepares the content, or delegates preparation to someone with the right Commons role.
- Only the signing official (SO) can submit the report to NIH, so build your institution's internal review time into the schedule.
- Department administrators usually gather effort, publications, and budget details, and check them against payroll and the award.
Before you begin
- Confirm the due date and report type in eRA Commons.
- Verify your eRA Commons role and access.
- Pull current payroll and effort data for everyone on the award.
- Gather the year's publications and confirm Public Access (PMCID) compliance.
A. Accomplishments
- Restate the specific aims and major goals.
- Summarize what was accomplished under each goal.
- Note training and professional development.
- Describe how results were disseminated, and outline next-period plans.
B. Products
- List publications; confirm each is PMCID-compliant for Public Access.
- Report other products: datasets, software, protocols, patents, resources.
C and D. Participants and the All Personnel Report
- List everyone who worked at least one person-month on the project during the reporting period, with their role and effort in person-months.
- Effort is reported in whole person-months, so make sure it matches payroll and the commitments on the award.
- Flag new senior or key personnel, and update Other Support if anyone's support has changed.
- Include eRA Commons IDs for those who need them, such as students and postdocs supported on the award.
D. Impact and E. Changes
- Impact is usually 'Nothing to report' unless there's a notable effect on your field or beyond.
- Report changes in approach or scope, and any problems or delays.
- Flag significant changes to human-subjects, vertebrate-animal, biohazard, or select-agent use.
- Note any anticipated unobligated balance (carryforward) greater than 25%.
F to H. Budget, special reporting, and human subjects
- Non-SNAP awards: include the detailed budget and justification (SNAP awards don't).
- Update human-subjects and clinical-trial information and inclusion enrollment, if applicable.
- Complete any award-specific special reporting.
I. Project Outcomes (interim and final RPPR)
Interim and Final RPPRs require a Project Outcomes section: a short, plain-language summary of what the project found and why it matters. NIH makes it public, so write it for a general audience rather than reviewers, and avoid jargon and unpublished data you are not ready to share.
Before you submit
- Confirm reported effort matches payroll and your commitments.
- Resolve any Public Access non-compliance: it can hold up the award.
- Route for institutional sign-off, then have the signing official submit before the deadline.
Common pitfalls
- Letting Public Access slip. A single publication without a PMCID can hold the entire award, so reconcile PMCIDs before you open the report.
- Reporting effort that does not match payroll. The person-months in the participants section have to reconcile to what was actually charged and certified.
- Treating the deadline as soft. SNAP reports are generally due 45 days before the budget period start and non-SNAP 60 days, and a late report delays the money.
An accepted RPPR releases your next year of funding, and a Final or Interim RPPR closes the project out. Calendar the due date, reconcile effort and publications first, and leave time for the signing official.
Frequently asked questions
When is the RPPR due?
For SNAP awards it is generally due 45 days before the next budget period start date, and 60 days for non-SNAP awards. Confirm the exact date in eRA Commons for your award.
What is the difference between a SNAP and non-SNAP RPPR?
SNAP (Streamlined Non-competing Award Process) awards skip the detailed annual budget and some reporting, so their RPPR is shorter. Non-SNAP awards require the detailed budget and justification.
Can funding be delayed if the RPPR is late?
Yes. An accepted RPPR is a condition of releasing the next budget period, so a late or incomplete report is the most common reason continuation funding stalls.
When is the Final RPPR due?
Within 120 days of the project period end date. It replaces the old final progress report and is submitted in eRA Commons by the signing official.
What is an Interim RPPR?
The report you submit instead of a Final RPPR when a competing renewal application is pending. It is due within the same 120-day window and becomes the annual RPPR if the renewal is funded, or the Final RPPR if it is not.
Who submits the RPPR?
The PI initiates and prepares it in eRA Commons, and only the signing official can submit it to NIH.
Track this in GrantsManager
GrantsManager surfaces every deadline, reconciles spend, and keeps effort and reporting in one place, so checklists like this stay out of your inbox.