Progress reports are how funders measure, mid-grant, whether their investment is on track. But they're more than a compliance checkpoint — a well-written progress report answers the questions a program officer is already asking: Is the program delivering what was promised? Are funds being spent appropriately? Are challenges being managed? It builds trust with a funder and positions you for renewal before the grant period even ends.
If you have a report due soon, this guide covers exactly what to include, how to write a narrative section, and what program officers actually look for when they read it.
➡ Download our free Grant Progress Report Template to work alongside this guide.
For a broader overview of your post-award reporting obligations, see: Post-Award Grant Management.
What to Include in a Grant Progress Report
A grant progress report is a structured accounting of what happened during a specific reporting period, tied directly to the funded program. Here's what every section should contain.
1. Grant Summary / Cover Page
This section establishes the administrative context for the report. Be sure to include:
- Grant name and grant number (as it appears in your award letter or Notice of Award)
- Reporting period (e.g., January 1 – March 31, 2026)
- Submitting organization name and address
- Primary contact name, title, and email
- Report submission date
Some funders provide a cover sheet template as part of their reporting requirements. If they do, use it. If no template is specified, a clean header with the fields above is sufficient. Either way, make sure the grant number and reporting period are accurate before anything else, and verify if a signing official needs to approve the document.
2. Program Narrative
The program narrative describes what your organization did during the reporting period to advance the funded program. It should be tied specifically to the program objectives in your original proposal, not a summary of everything your organization accomplished during that time.
A common mistake here is writing a general organizational update instead of a grant-specific one. If an activity isn't funded by this grant or doesn't advance a funded objective, it doesn't belong in this section.
3. Progress Toward Goals and Outcomes
This is the most important section of the report. Use the exact goals, objectives, and metrics from your original proposal. Funders approved a specific scope of work, and this section is where you demonstrate how your program is delivering against it.
A few rules that matter here include:
- Report against every goal, even if you're behind. Dropping a goal between reports is one of the most common mistakes grant managers make, and program officers notice immediately.
- Use numbers. If your proposal committed to serving 200 participants, report the actual count.
- If you're behind on a target, explain why and what you're doing about it (more on this below).
A table format works well for this section and makes it easier for program officers to scan your progress at a glance. At minimum, include four columns: the goal or objective as written in your proposal, the target for the reporting period, the actual result to date, and a brief status note.
4. Financial Summary
The financial summary shows how grant funds have been spent during the reporting period and cumulatively since the grant start date. Include the following:
- A budget vs. actual comparison, line by line
- Cumulative expenditures to date as a percentage of the total award
- A brief narrative explanation of any significant variances, like lines that are significantly over or under budget relative to where you are in the grant period
If your grant agreement requires a specific financial report format, such as an RPPR submitted via eRA Commons or grants.gov, use it as specified. Deviating from a required format is one of the most avoidable reasons a report gets kicked back. If no format is specified, a clean budget vs. actual table with a short variance narrative is the standard. Two to three sentences per significant variance is typically sufficient.
5. Challenges and Adjustments
Funders don't expect every grant to run perfectly, but they do expect grantees to manage problems well. A strong challenges section names the issue specifically, provides additional information regarding program delivery impact, and describes what you're doing to address it. If a staffing vacancy slowed recruitment, say so and explain how you're backfilling. If a community event drew lower turnout than expected, name it and describe how you're adjusting outreach for the next period. A candid, solution-oriented challenges section can reassure program officers.
6. Plans for the Next Reporting Period
Close the narrative portion of your report with a brief forward-looking section that outlines what you will accomplish before the next report is due. This does two things: it confirms that your program has a clear plan for the remaining grant period, and it gives the program officer a concrete benchmark to evaluate your next submission against. It also signals that you're managing the grant proactively rather than simply accounting for what already happened.
Keep it specific and tied to your goals. "We will continue to serve clients" is not useful. "We will complete enrollment for cohort 2 (target: 45 participants) and deliver 6 of the 12 planned workshops" is. If you're behind on a goal, this section is also the right place to describe how you plan to close the gap and explain how the next period's activities will get you back on track.
7. Supporting Documentation
Attach any documentation required by your grant agreement: participant data, human subjects protections, public access compliance, attendance records, photos, testimonials, evaluation results, or financial backup. It's worth reviewing your grant agreement specifically for documentation requirements each time you submit, not just at the start of the grant period. Requirements sometimes vary by reporting period, particularly with federal funders like the NIH, and what was sufficient for your first submission may not satisfy a mid-grant or annual report.
What Is a Grant Progress Report?
A grant progress report is a formal update submitted to a funder during the active grant period, typically on a quarterly, semi-annual, or annual basis for multi-year grants. It covers both what has happened during the reporting period and what is planned for the period ahead.
The exact format varies by funder and grant type. A small family foundation might ask for a two-page narrative update twice a year. A federal research grant might require a Research Performance Progress Report (RPPR) — a standardized format used across most federal agencies that funds research. Whatever the format, the underlying purpose is the same: keep the funder informed about how their money is being put to work.
It's worth distinguishing it from a few related documents:
- Final reports: Submitted at grant closeout, a final progress report is a comprehensive accounting of everything the grant achieved over its full period. Different scope, different tone, and a different strategic purpose than a progress report. See: The Grant Closeout Process for more information.
- Financial reports: Some funders request financial reports separately from the narrative progress report. In other cases, the financial summary is a component of the progress report. Check your grant agreement for the specific requirements.
- Annual reports: An organizational annual report is a public-facing document for a general audience. A grant progress report is a compliance document for a specific funder.
For a general overview of grant reporting types, requirements, and FAQs, see: How-to Guide for Grant Reports.
How to Write the Narrative: What Funders Actually Read
Writing a strong progress report narrative comes down to a few core principles that, when applied consistently, make your report stand out and build funder confidence. Program officers read dozens of these submissions, and the ones that land are the ones that are direct, specific, and honest about both progress and challenges. Here is what they're actually looking for.
Specificity
Vague language is the most common weakness in grant progress reports. Program officers are reading for evidence that the program is delivering real results, and numbers are the clearest form of that evidence.
Instead of this: "We served a significant number of participants during the reporting period and made meaningful progress toward our goals."
Do this: "We provided 147 individual counseling sessions to 63 unique participants in Cook County between January and March 2026, representing 74% of our Q1 target of 85 participants."
The second version tells the program officer exactly what happened, where, and how it maps to the approved proposal. That's the standard to aim for across every section of your report.
Connection to the Original Proposal
Every activity you describe in the narrative should map back to a funded program objective. Program officers are reviewing your report against your original proposal. This is especially important when programs evolve mid-grant in response to community need or unexpected circumstances. When in doubt, a brief sentence connecting an activity to a funded objective is always worth including.
Candor About Challenges
When you encounter a real challenge, name it directly, explain the impact, and describe what you're doing about it. The goal is to demonstrate that your organization identifies problems early and responds to them deliberately, as it shows your organization’s management capacity. That kind of transparency is what long-term funder relationships are built on.
A Narrative Arc
Before you submit, read your report through and ask whether it tells a coherent story. Make sure each sections connects to the ones around it, so the report reads as a unified account of your program. A program officer who finishes your report with a clear picture of where things stand will feel more confident in your organization.
Before and After: What This Looks Like in Practice
Weak narrative paragraph:
"During this reporting period, our team worked hard to advance the goals of the Healthy Futures program. We held several workshops and connected with many community members. Participation was strong and feedback has been positive. We look forward to continuing this important work in the next quarter."
Strong narrative paragraph:
"During Q1 2026, the Healthy Futures program delivered 8 nutrition education workshops to 94 participants across three south side community centers, representing 94% of our Q1 target of 100 participants. Workshop attendance averaged 11.75 participants per session, exceeding our planning assumption of 10. Pre- and post-session surveys show that 81% of participants reported increased confidence in reading nutrition labels, compared to a baseline of 34% at program intake. One workshop originally scheduled for February was postponed due to a facility closure and has been rescheduled for April 3rd — no net impact on Q1 outcomes is anticipated."
The difference comes down to three things: specific numbers tied to specific targets, a clear explanation of any deviation from plan, and data that connects program activity directly to measurable outcome.
Grant Progress Report Example
Below is a sample progress report narrative for a community health program. Bracketed fields indicate where you would insert your organization's specific information.
GRANT PROGRESS REPORT
Organization: [Organization Name] Grant Name: [Funder Name] Community Health Initiative Grant Number: [Grant Number] Reporting Period: January 1 – March 31, 2026 Submitted By: [Name, Title, or Principal Investigator] Submission Date: April 15, 2026
Program Narrative
During the first quarter of 2026, [Organization Name] advanced all three funded program objectives under the [Funder Name] Community Health Initiative. [Annotation: Open with a direct, affirmative statement that confirms the grant is on track — program officers read this first.]
The nutrition education component delivered 8 workshops reaching 94 participants across three community sites. The care navigation component completed 147 individual client sessions with 63 unique participants. Outreach activities generated 312 new contacts with the target population, exceeding the Q1 target of 250.
Progress Toward Goals and Outcomes [Annotation: Use the exact goal language from your proposal. Don't paraphrase or substitute.]
Note on Goal 1: Two workshops were delayed in Q1 due to the departure of our part-time nutrition educator in February. We hired a replacement in late March and rescheduled both workshops for April. We do not anticipate any impact on our annual target of 40 workshops. [Annotation: This is how you handle a goal that's slightly behind — name the cause, explain the response, and confirm the annual target is intact.]
Financial Summary [Annotation: Match your financial reporting period to your narrative reporting period. If you're reporting Q1 narrative, report Q1 financials.]
Variance Narrative: Total Q1 expenditures were $3,870 below budget, primarily due to the personnel vacancy in February–March. The replacement hire began March 24th and is now fully onboarded. We expect Q2 expenditures to normalize to budget. No budget modification is anticipated at this time. [Annotation: Always explain personnel underspending. It's the line item program officers scrutinize most closely, because it often signals program delivery gaps.]
Download our free Grant Progress Report Template to use this structure for your own report.
Common Mistakes in Grant Progress Reports
Even experienced grant managers make these mistakes, often because progress reports get written under deadline pressure with limited time for review. Here's what to watch for before you hit submit.
Submitting late without advance notice. If you know you're going to miss a reporting deadline, contact your program officer before the deadline. A brief email explaining the delay and a realistic new timeline is almost always received well.
Using vague language when you have the data. "Many participants" when you have an attendance sheet. "Significant progress" when you have a percentage. "Strong community interest" when you have contact numbers. If the data exists, use it.
Dropping goals you're behind on. This is one of the most damaging mistakes a grant manager can make. Program officers track your goals across every report. Report against every goal, including the ones you're behind on.
Copying and pasting from the original proposal. Your proposal described what you planned to do. Your progress report should describe what you actually did. Funders notice when the language is identical, and it signals that the report wasn't written with real program data.
Ignoring the financial section. The financial summary is not optional. Even if your finance team produces the budget vs. actual numbers, the grant manager is responsible for reviewing them, understanding the variances, and writing the narrative explanation. Submitting a progress report without a complete financial section is a red flag for program officers.
How Instrumentl Helps You Stay on Top of Grant Reporting
Instrumentl tracks all of your grant reporting deadlines and due dates in one place, stores your report history so you can reference previous submissions before writing the next one, and connects your reporting obligations to your full portfolio view — so nothing falls through the cracks when you're managing multiple grants simultaneously. If you're looking to build a system that keeps your full grants portfolio on track, check out our Grant Management for Nonprofits: A Complete Guide.
