What is required in a federal grant performance report?

Under 2 CFR 200.329, performance reports must compare actual accomplishments to the objectives established for the period, document progress toward achieving program goals, and explain why established goals were not met where applicable. Agencies set the frequency (typically annual, sometimes quarterly or semiannual) and the format. The report covers what you did, what you achieved, and what it means against the objectives in your approved application.

What is the difference between an output and an outcome in a grant report?

An output is what you produced — number of people served, sessions held, materials distributed. An outcome is the change that resulted — improvement in employment, health, knowledge, or behavior. 'We trained 200 people' is an output. 'Of 200 trainees, 140 (70%) passed certification, up from a 45% baseline' is an outcome. Program officers care far more about outcomes because outcomes show whether the program worked.

How often do you have to submit federal grant performance reports?

It depends on the award. Under 2 CFR 200.329, the awarding agency sets the frequency, but performance reports generally cannot be required more frequently than quarterly or less frequently than annually, except in unusual circumstances. Annual is most common, with a final performance report due during closeout. Your Notice of Award states the exact schedule and due dates.

What happens if you submit a federal grant report late?

Late or missing reports are a compliance problem. Agencies can withhold payments, withhold future funding actions, place restrictive conditions on the award under 2 CFR 200.208, or in serious cases suspend or terminate the award. A pattern of delinquent reports also damages your risk profile and can affect eligibility for future funding. Reports are an enforceable term, not a courtesy.

Federal Grant Performance Reporting: What to Write & Common Mistakes

Key Facts

Required by 2 CFR 200.329. Compare actuals to objectives, document progress, explain shortfalls.
Frequency is set by the agency — generally no more than quarterly, no less than annually. Annual is most common.
Outcomes beat outputs. "Served 200" is an output; "70% achieved the result, up from 45%" is an outcome. Lead with outcomes.
Your program officer reads it to judge whether the program works and whether to keep funding you.
Late reports have teeth. Payment holds, restrictive conditions (200.208), and worse for repeat delinquency.

Summary

Performance reports are where a lot of grantees underperform — not because the work was bad, but because the report doesn't show it well. The report is the only window most program officers have into your project. They weren't there. They didn't see the clients served or the research conducted. They see what you write. And they're making real decisions off it: whether the program is working, whether to fund the next cycle, what to tell their own leadership.

The regulation (2 CFR 200.329) sets the floor — compare actuals to objectives, explain shortfalls. But meeting the floor isn't the same as writing a report that helps you. The difference between a report that supports your renewal and one that quietly undermines it comes down to two things: leading with outcomes instead of activity counts, and handling shortfalls honestly instead of defensively.

What 200.329 Actually Requires

The regulation is short on this. 2 CFR 200.329 says performance reports must contain, for each program, a comparison of actual accomplishments to the objectives of the federal award established for the period; where the accomplishments can be quantified, a computation of the cost if appropriate; and an explanation of why established goals were not met, if that's the case. The agency decides the frequency and the format — and most agencies have their own templates and portals.

So three things, fundamentally: what were you supposed to accomplish, what did you actually accomplish, and where there's a gap, why. Everything else in a good report serves those three questions. The agency-specific template might ask for more, but if your report nails those three, you've satisfied the core regulatory purpose.

Outputs vs. Outcomes — The Distinction That Separates Good Reports From Filler

This is the single most important thing in this guide. Most weak reports are a list of outputs — counts of things that happened. Strong reports center on outcomes — the change that resulted.

An output is what you produced. Number of people trained. Sessions held. Brochures distributed. Hours of service delivered. Outputs are easy to count and they prove you did the work. But they don't prove the work mattered.

An outcome is the change. Did the trainees gain skills? Did clients get jobs? Did health improve? "We delivered 12 weeks of job training to 200 participants" is an output. "Of 200 participants, 156 (78%) completed the program, and of those, 109 (70%) were employed at 90-day follow-up — compared to a 45% employment rate at intake" is an outcome, and it's a far more powerful sentence. It has a numerator, a denominator, a baseline, and a result. A program officer can take that to their leadership.

Report both, but make outcomes the spine. If your objectives were written as outcomes (as they should have been in your application), report against them directly, in the same units, so the program officer can line up "promised" and "delivered" at a glance.

GrantMetric Analysis

Report shortfalls before the program officer notices them. If you hit 60% of a target, say so plainly, give the real number, and explain the barrier with specifics — then say what you're doing about it. A program officer who reads "we achieved 60% of our enrollment target; recruitment was slower than projected because the partner referral pipeline didn't materialize, and we've since added two community recruitment sites" trusts you more than one who reads a report that buries the miss in vague language. Defensiveness reads as concealment. Honesty with a plan reads as competence.
Make the program officer's job easy and they'll remember you. Program officers manage portfolios of grants and have to write their own summaries up the chain. If your outcome data is clean, quantified, and copy-pasteable into their reporting, you've done them a favor — and that goodwill is real currency at renewal time. Give them the numbers in a usable form. Tables for the metrics, short narrative for the why. Don't make them dig your outcomes out of three paragraphs of prose.
The performance report and the financial report should tell the same story. Auditors and program officers compare them. If your SF-425 shows you spent 90% of the budget but your performance report shows you completed 40% of the work, that mismatch raises questions — either you overspent for what you delivered, or your reporting is inconsistent. Keep the narrative aligned with the money. If spending and progress genuinely diverged for a good reason, explain it in both places.

Deadlines and Frequency

Under 200.329, agencies generally can't require performance reports more often than quarterly or less often than annually, with rare exceptions. Annual reporting is the most common arrangement for multi-year awards, usually due within 90 days after the reporting period (often tied to the budget period), with a final performance report due during closeout. Your Notice of Award has the exact schedule — read it and put every due date on a calendar with a reminder a few weeks ahead.

Don't wait until the report is due to start gathering data. The organizations that produce good reports collect outcome data continuously — they're tracking the metrics all year, so when the report comes due they're summarizing data they already have, not scrambling to reconstruct what happened nine months ago.

Common Mistakes That Get Reports Kicked Back

Reporting only activities and no outcomes. Submitting numbers with no baseline or denominator (a "70% success rate" is meaningless without knowing 70% of what). Not reporting against the specific objectives in the approved application, so the program officer can't tell if you hit your targets. Ignoring shortfalls entirely and hoping nobody notices. Using a different metric than the one you promised, which makes comparison impossible. And missing the agency's required format or portal — many agencies will reject a report submitted the wrong way regardless of content.

Performance Report Checklist

Report against your stated objectives in the same units you promised, so progress is comparable.
Lead with outcomes, support with outputs. Always include numerator, denominator, and baseline.
Address shortfalls directly — real number, specific cause, and what you're doing about it.
Align the narrative with the SF-425. Spending and progress should tell a consistent story.
Use the agency's required format and portal. Wrong format can mean rejection regardless of content.
Track data all year and submit on time — calendar every due date well in advance.

Frequently Asked Questions

What's required in a performance report?

Under 2 CFR 200.329: compare actual accomplishments to the objectives for the period, document progress toward goals, and explain why goals weren't met where applicable. The agency sets the frequency and format. Core question: what did you promise, what did you deliver, and why any gap.

Output vs. outcome — what's the difference?

An output is what you produced (people served, sessions held). An outcome is the change that resulted (improved employment, health, skills). 'Trained 200' is an output; '70% passed certification, up from 45% baseline' is an outcome. Program officers care most about outcomes.

How often must I report?

The agency decides, but generally no more than quarterly and no less than annually under 200.329. Annual is most common, with a final performance report during closeout. Your Notice of Award states the exact due dates.

What if I submit late?

Late or missing reports can trigger payment holds, withheld funding actions, restrictive conditions under 200.208, or in serious cases suspension or termination. Repeat delinquency damages your risk profile and future eligibility. Reports are an enforceable term.

Sources & Disclaimer Sourced from 2 CFR 200.329 (monitoring and reporting program performance) and 200.208 (specific conditions). Reporting frequency, format, and portals are agency- and award-specific. Your Notice of Award and program officer are authoritative for your specific requirements. GrantMetric is an independent platform not affiliated with any federal agency.