Skip to content

Federal Grant Progress Report Guide (2026)

Updated 11 official sources

Quick Answer: The award determines your progress-report format, frequency, due date, and submission system.

Full answer and how we checked it

NIH RPPR timing differs by award type: current NIH guidance generally uses about 45 days before the next budget period for SNAP awards, about 60 days for non-SNAP awards, and the anniversary date for multi-year-funded awards. Confirm the exact date in eRA Commons.

Data note: Checked October 9, 2026 against current 2 CFR 200.329 (opens in a new tab) (performance reporting), NIH RPPR guidance (opens in a new tab), and NSF reporting guidance. Use the Notice of Award and agency system for the actual report date and required content.

In this guide

If you're a program director or grants manager responsible for keeping your federal funder informed, this guide covers what to include, what to flag, and how to stay in good standing.

Knowing how to write a grant progress report well is a skill that matters every year of your award, not just at application time. At NIH, your Research Performance Progress Report (RPPR) determines whether your non-competing continuation funding gets released for the next year. At community-based agencies like SAMHSA, DOL, and ED, your progress report feeds into aggregate program performance data reviewed by Congress.

The writing isn't complicated, but most grantees make predictable errors. This guide covers what a progress report is actually for, what your program officer is looking for, and how to write each section well.

What a Progress Report Is For

Progress reports serve 2 audiences simultaneously, and you'll write a better report if you keep both in mind.

Your federal program officer is evaluating whether you're making satisfactory progress. At NIH, "satisfactory progress" is the standard for releasing non-competing continuation funding. At community-based agencies, it's the basis for continued funding through multi-year cooperative agreements.

The agency's administrative systems collect your data for Congressional and OMB reporting under GPRA Modernization Act (GPRAMA) requirements. Agencies are required to demonstrate to Congress that federal programs produce results. Your progress data gets aggregated into those reports.

The implicit question behind every progress report: "Is this grantee making enough progress to justify continuing this award?"

How Progress Reports Differ from Board Reports

This distinction matters because many program staff who write board reports also write progress reports, and the formats are very different.

Board reports are written for organizational leadership who have governance responsibilities and want high-level narrative about mission and organizational impact. They're typically narrative-heavy, relationship-oriented, and emphasize story.

Federal progress reports are written for program officers who want specific data, an honest assessment of where you stand against your targets, and evidence that you're managing public funds responsibly. Program officers aren't interested in your organizational story. They want to know whether you hit your numbers.

Common mistake: submitting a board report-style narrative as a federal progress report. Don't frame your work in terms of organizational purpose. Frame it in terms of measurable results.


Looking for your next grant?

About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.

No spam. Unsubscribe anytime.

NIH RPPR: Section-by-Section Guide

The NIH Research Performance Progress Report (RPPR) is submitted through eRA Commons (opens in a new tab). Annual RPPRs are required for non-competing continuation awards. At the end of a competitive segment, NIH (opens in a new tab) requires a Final RPPR as part of closeout, or an Interim RPPR if you've submitted a renewal (Type 2) application. Both are due 120 days after the period of performance ends, add Project Outcomes, and drop the budget and next-period plans.

Section A: Cover Page

The cover page is auto-populated from your eRA Commons profile and the award record. Before submitting, verify that the following are accurate:

  • Principal Investigator name and credentials
  • Institution name and address
  • Award number and grant mechanism
  • Project title
  • Budget period start and end dates
  • Reporting period

Errors on the cover page can delay RPPR acceptance and, by extension, delay release of your next year's funding.

Section B: Accomplishments

This is the core of the RPPR. It's where program officers spend the most time, and it's where most investigators either succeed or fail at demonstrating progress. According to NIH's RPPR page (opens in a new tab), Accomplishments asks five questions: the major goals, what was accomplished under those goals, what training and professional development opportunities the project provided, how results were disseminated, and what you plan to do in the next reporting period.

B1: Major Goals Restate your original specific aims exactly as they appear in your funded application. Don't update the language to reflect where the project is now - B1 is a record of what you proposed. The comparison between B1 and B2 is what tells the story of your progress.

B2: What was accomplished under these goals? This is the most important section of the RPPR. Write it in terms of each aim, not as a general narrative. Use the aim headings as subheadings.

Use numbers. Percentages. Specific findings.

Weak: "We made good progress on Aim 1 during the reporting period." Strong: "Aim 1: We enrolled 47 of the planned 60 participants (78% of the Year 2 target) across 3 recruitment sites. The enrollment delay at Site 2 (11 participants enrolled vs. a target of 20) reflects a 6-week IRB amendment process that was resolved in March. We expect to reach full enrollment by Month 14. Preliminary analysis of completed cases shows [specific finding]."

If you have preliminary data, describe it specifically and note where it's being written up or has been submitted. Significant results, including unexpected findings and null results with implications for the field, belong here too. Don't pad this section with routine activity; lead with results that would be worth describing in an abstract.

B3: Training and professional development Describe the training and mentoring the project provided to students, postdocs, and staff. If the project isn't intended to provide training, say so.

B4: Dissemination Describe how results were shared with communities of interest beyond journal articles, such as community presentations or reports to partners.

B5: Plans for the next reporting period State what you'll do next under each goal, and be specific about timing.

Where the honest assessment goes The Accomplishments section shows progress against your goals, and delays or problems are reported in Section F (Changes/Problems). Write both honestly. This is where many investigators get defensive when they shouldn't be.

If you're on track: say so clearly. "Enrollment, data collection, and preliminary analysis are all on schedule. We do not anticipate any changes to the project timeline."

If you're behind: disclose the shortfall, explain the cause, and describe your corrective action. "Aim 2 data collection is running approximately 6 weeks behind schedule due to [specific cause]. We have implemented [specific change] and expect to return to the original timeline by [date]."

Program officers know that research doesn't always go according to plan. What they're evaluating is whether you're managing the project responsibly. Transparent disclosure of delays with a concrete corrective plan is handled very differently from unexplained shortfalls discovered during monitoring.

Section C: Products

List every product generated by the grant during the reporting period:

  • Published journal articles (include PubMed IDs)
  • Manuscripts submitted or in press
  • Book chapters
  • Conference presentations and posters
  • Software, code repositories, or databases
  • Technologies, patents, or patent applications
  • Datasets made publicly available

Include publications that are only tangentially related to the grant if the work was funded by the award. Incomplete product reporting makes your progress look thinner than it is.

Use standard citation format consistently.

Section D: Participants

Report individuals who worked at least one person-month per year on the project during the reporting period, per the NIH RPPR Instruction Guide, regardless of how they were paid. For each person:

  • Name and role
  • Person-months devoted to the project
  • Contribution to the project

Include counts of:

  • Graduate students trained or supported
  • Postdoctoral researchers trained or supported
  • Undergraduate students involved (if applicable)
  • Individuals from underrepresented groups (where applicable)

Personnel changes - people who left the project, new hires, changes in effort - are disclosed here and in Section F.

Section E: Impact

Describe the influence of your work on the field, on training, and on broader society. Be honest about what's achievable in a single grant year.

A year-1 basic science R01 can't claim public health impact yet. But it might report: "The methodological approach developed in Year 1 has been requested by 2 collaborating laboratories at other institutions, who are applying it to [different scientific question]." That's a real, documentable impact.

Don't write aspirational statements about what the project might eventually accomplish. Write about what it has actually contributed.

Section F: Changes

This section covers any departures from the approved plan during the reporting period. Don't minimize this section - proactive disclosure of changes is a sign of good grants management.

Types of changes to report:

  • Personnel changes (key personnel departing or joining, changes in effort)
  • Budget changes (significant deviation from the approved budget by category)
  • Changes in the research approach or methodology
  • Changes in the human subjects protocol (if applicable)
  • Delays and their causes

Critical rule: Some changes require prior approval before they happen and cannot wait for the RPPR. Scope changes, extensions, key-personnel changes, and other actions are governed by the award terms and NIH procedure. The RPPR documents reportable changes; it is not a substitute for a required prior-approval request.

A format that works well for Section F: "Change: [Describe what changed]. Reason: [Why it happened]. Impact on project: [How it affects progress]. Resolution: [What you're doing about it]." This structure gives your program officer everything they need to evaluate the change quickly.

Section G: Special Reporting Requirements

Section G varies by grant mechanism and institute. Common items include:

  • Human subjects enrollment: Reporting actual enrollment against your IRB-approved enrollment targets by demographic category
  • Vertebrate animals: Reporting on animal usage relative to approved numbers
  • Select agent reporting: If your work involves select agents or toxins
  • Foreign component changes: Any changes to collaborations with international institutions
  • Special award conditions: Any conditions specified in your NOA that require additional reporting

Read your NOA before completing Section G. Special conditions from your NOA appear here, and missing them is a compliance issue.

Section H: Budget

For non-competing continuation awards, Section H includes the budget request for the next budget period. It should align with your originally approved budget unless you have a specific reason for changes.

Before submitting, reconcile the budget request in Section H with your financial records. Discrepancies between what you report spending in your SF-425 financial report and what you request in Section H will raise flags.

Section I: Project Outcomes (Final and Interim RPPRs)

Required on the Final RPPR and the Interim RPPR, not the annual report. Project Outcomes is a short, plain-language public summary of what the project found and why it matters, and NIH posts it to RePORTER. Write it for a general reader, not for reviewers.


Report ComponentAgency ExpectationRed Flag for Program Officers
Participant numbersActual vs. targetWell below the annual target with no explanation
Expenditure rateOn track with timelineFar behind or far ahead of the project timeline
Milestone completionDocumented with evidenceMilestones "in progress" for 2+ quarters
Carryforward amountUnder 25% of annual budgetAbove 25% without explanation
Staff turnoverReported with replacement planKey position vacant 3+ months
Subrecipient monitoringDocumented site visits or reviewsNo monitoring documentation

For Community-Based Grants: SAMHSA, DOJ, and ED

Progress report formats at community-based agencies vary significantly from NIH. They're typically structured around service delivery data and outcomes rather than scientific findings.

Match your evaluation plan. When you wrote your grant proposal, you included an evaluation plan describing what you'd measure and how. Your progress report should report on exactly those measures. If you told the agency you'd track [X] at intake, [Y] at 6 months, and [Z] at program exit, your progress report needs to include data on [X], [Y], and [Z].

Include your data tables. Most community-based agencies want to see a table showing actual vs. target performance on each outcome measure. Don't bury discrepancies in narrative. Put the numbers in a table where the program officer can see them at a glance, and then use the narrative to explain what's driving any gaps.

Structure by objective. If your grant has 3 program objectives, organize the report by objective, not by program activity. Program officers evaluate whether you're meeting your stated objectives - they don't need a detailed account of everything your staff did.


How to Handle Being Behind on Targets

Don't minimize delays or bury them in narrative. Program officers have read thousands of progress reports. They can see a minimized disclosure from a distance.

The effective formula has 4 parts:

  1. Acknowledge the shortfall specifically. "As of the reporting period end date, we have enrolled 47 of the planned 72 participants (65% of the annual target)."
  2. Explain the specific cause. Not "recruitment challenges" - what specific challenge? "Extended IRB review of the amended consent form (submitted Month 8, approved Month 11) delayed recruitment at our primary site for 3 months."
  3. Describe your corrective action. "We have added a second recruitment site and increased our community outreach budget by $8,000 from within the approved budget. We expect to reach our cumulative enrollment target by Month 18."
  4. State your revised expectation. "We do not anticipate this delay will affect our ability to complete data collection within the project period."

Being behind doesn't automatically threaten your next year of funding. How you handle it determines the program officer's confidence in your management. A delay with a clear explanation and a concrete correction plan is handled very differently from an unexplained shortfall.

If you need a no-cost extension (NCE): The RPPR is the right place to flag this, but it's not a substitute for a formal NCE request. Submit the NCE request separately through the appropriate channel, and note in Section F of the RPPR that you've submitted or intend to submit an NCE request and why.


Practical Writing Tips

Don't try to write the RPPR from memory. Use the data you've been collecting throughout the year. If you haven't been tracking data systematically, the RPPR will reveal that immediately.

Keep a running log. Throughout the year, log publications submitted, conferences attended, personnel changes, significant findings, and any deviations from the plan. An hour a month of logging saves a full week of reconstruction before the RPPR deadline.

Reconcile your financial data first. Before you write Section H (budget), sit down with your grants manager and reconcile your expenditures against your budget. Section H numbers should match your SF-425 financial reports exactly.

Run eRA Commons compliance checks before submission. The system flags certain errors before you submit - missing required fields, invalid formats. These checks are worth running several days before the deadline, not the night before.

Submit several days early. System outages around RPPR deadlines are a real and recurring problem. Don't count on submitting the night before or the morning of the deadline.

Have your grants manager review the financial information. The RPPR and the SF-425 financial report need to be consistent. A discrepancy between them is a flag in an audit.

For a full picture of every report type you're required to submit across the life of your grant, see Federal Grant Reporting Requirements. For the compliance framework that governs how you manage the underlying funds, see Federal Grant Compliance Requirements.


What Happens After You Submit

For NIH RPPR submissions: the program officer reviews the RPPR for completeness and satisfactory progress. If they have questions, they'll contact you. If they're satisfied, they mark the RPPR as accepted and the non-competing continuation award is processed.

If the program officer requests revisions: Respond promptly and specifically. A request for clarification usually means something in your RPPR was ambiguous or a specific item was missing. Don't take it as a sign of trouble - take it as a chance to provide the information they need.

If the program officer determines progress isn't satisfactory: They can withhold non-competing continuation funding pending a corrective action plan, or, in rare cases, recommend award termination. If you've been honest and proactive in your RPPR about challenges and corrective actions, the response from the program officer is almost always collaborative rather than punitive.


What Federal Program Officers Doesn't Tell You

Late progress reports have real costs. At NIH, the next year's award isn't processed until the RPPR is accepted, so a late report can delay funding. Repeated noncompliance with reporting terms is also the kind of history an agency can weigh when it imposes specific conditions under 2 CFR 200.208 (opens in a new tab).

Don't hide underperformance in narrative. Program officers read the numbers first. If your target was 200 participants and you served 85, saying "the program is progressing well" in the narrative while the data table shows 42.5% of target will damage your credibility. Acknowledge the gap and explain your corrective plan.

Carryforward amounts above 25% of the annual budget almost always require an explanation. Even if your agency doesn't have a formal threshold, large unobligated balances signal implementation problems and can lead to reduced future funding.

How Grantsights Checked This Guide

Source review by Grantsights: we rechecked NIH RPPR, eRA Commons, PMS payment context, and federal performance-reporting rules on June 3, 2026. The goal was to make progress reporting a funding-continuation decision, not just a writing task.

Source checkedWhat it provesApplicant action
NIH RPPR (opens in a new tab)NIH requires RPPRs for non-competing continuation awards.Submit early enough to protect the next budget period.
eRA Commons RPPR (opens in a new tab)RPPRs are prepared and submitted through eRA Commons.Verify PI, signing official, and routing permissions.
HHS Payment Management System (opens in a new tab)PMS handles grant payment drawdowns for many HHS awards.Keep reporting and payment records aligned.
2 CFR 200.329 (opens in a new tab)Federal awards require performance reporting (200.328 covers financial reporting).Report performance data, not only narrative activity.
OMB performance management (opens in a new tab)Federal performance reporting feeds public agency results.Tie project metrics to approved objectives.

Decision checklist: report targets, actuals, variance, cause, and corrective action for every objective. A bad fit progress report reads like a newsletter: good stories, no data, no explanation of missed targets. For example, one applicant who enrolled 47 of 60 planned participants should state the 78 percent result, explain the delay, and give the recovery date.

According to NIH, RPPRs document progress for non-competing continuation awards; current due timing depends on whether the award is SNAP, non-SNAP, or multi-year-funded. According to eRA, recipients submit RPPR materials through eRA Commons. According to 2 CFR 200.329, recipients must submit performance reports as required by the federal award. According to HHS, the Payment Management System supports award payment activity, which makes reporting and drawdown consistency important.

What Official Sources Don't Tell You

Official RPPR instructions tell you what fields to complete, but they do not teach the judgment call: when to disclose a problem and how much context to provide. Based on our review of NIH RPPR guidance and 2 CFR 200.329, a transparent missed target with a corrective plan is safer than a vague success narrative, because the RPPR asks you to report problems directly. Use the Grantsights database to compare reporting requirements across live awards.


Don't bother submitting a progress report that only includes narrative without the numbers. Program officers look at the data tables first, and a report that buries underperformance in paragraphs of text will damage your credibility faster than honestly reporting a missed target.

Sources


FAQ: Common Questions

When is the NIH RPPR due?

It depends on the award type. According to NIH (opens in a new tab), SNAP RPPRs are due about 45 days before the next budget period starts, non-SNAP RPPRs about 60 days before, and multi-year funded RPPRs on or before the anniversary of the budget or project period start date. Most R01s are SNAP awards, so a June 1 budget period usually means an RPPR due in mid-April. Final and Interim RPPRs are due 120 days after the period of performance ends. Check the exact date in eRA Commons, because missing it can delay release of your next year of funding.

What happens if I'm behind on my grant targets?

Disclose it honestly in Section F (Changes/Problems) of the RPPR, and show actual progress against goals in Section B. Explain the specific cause, describe your corrective action, and state your revised timeline. A disclosed delay with a concrete corrective plan is managed very differently from a shortfall discovered through monitoring or audit. Don't try to hide it in narrative - program officers will see it either way.

Do I need to report personnel changes in my progress report?

Yes. All personnel changes during the reporting period are reported in Section D (Participants) and disclosed in Section F (Changes). Key personnel changes (defined as the PI and anyone named as key personnel in the approved application) may also require prior approval from NIH before they take effect - don't wait for the RPPR to disclose these.

Can I request a no-cost extension in my progress report?

You can flag in Section F of the RPPR that you intend to request a no-cost extension, but the RPPR isn't a substitute for a formal NCE request. For NIH's first no-cost extension of up to 12 months, your institution notifies NIH in eRA Commons, and 2 CFR 200.308 (opens in a new tab) requires that notice at least 10 calendar days before the period of performance ends. Later extensions need prior approval. Work with your sponsored programs office well before that deadline.

What is the difference between a progress report and a performance report?

These terms are often used interchangeably but can mean different things depending on the agency. At NIH, the RPPR is both a progress report (covering accomplishments and changes) and a performance report (covering outcomes and impact). At community-based agencies like SAMHSA and DOL, "performance report" often refers specifically to the service delivery and outcomes data submitted through agency-specific data systems, separate from the narrative progress report. Check your NOA for what your specific agency requires.

Last updated October 9, 2026. Corrected October 9, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.