Lesson 139 · The Grant Architect

139. Performance Reporting (PPR)

30 min

By the end you'll be able to

  • Structure a PPR around your approved logic model and target outcomes.
  • Explain variances honestly without triggering unnecessary alarm.
  • Reconcile PPR narratives with FFR financial data.
  • Position the PPR to support continuation and supplemental funding.

The Performance Progress Report, often filed on the SF-PPR (Standard Form Performance Progress Report) or an agency-specific equivalent such as the NIH RPPR, is where you tell the funder what the money actually produced. Where the FFR answers "did you spend the money correctly," the PPR answers "did the work happen, and is it on track to deliver the outcomes you promised." Both reports must be internally consistent, because auditors and program officers will compare them.

In this lesson you will learn to structure a PPR around your approved logic model: activities completed, outputs produced, short-term outcomes observed, and progress toward intermediate and long-term outcomes. You will learn how to explain variances honestly, including when targets were missed, when timelines slipped, and when external factors disrupted the plan. Transparent variance reporting builds funder trust. Hidden or rosy reporting destroys it, often permanently, when the truth surfaces later.

By the end you should be able to draft a PPR that a program officer reads with confidence, not suspicion. Good performance reporting positions you for continuation funding, supplemental awards, and unsolicited expansions of scope. Poor reporting raises red flags, triggers special conditions, and frequently ends the funding relationship altogether, regardless of how clean the financials look.

Common mistakes

These are the traps learners hit most often on this topic. Knowing them in advance is half the fix.

  • Drafting the PPR independently of the FFR.

    When the narrative claims significant progress but the financial report shows almost no spending, program officers notice and trust collapses. Reconcile both before submitting either.

  • Burying bad news.

    Hidden problems always surface during site visits or audits, and the credibility damage is far worse than honest variance reporting would have been.

Practice problems

Try each on paper first. Click Show solution only after you've made a real attempt.

  1. Problem 1
    Your award promised to enroll 200 participants in year one but you enrolled 140. Draft the variance narrative for the PPR.
    Show solution

    Year-one enrollment reached 140 participants against a target of 200, a 30 percent shortfall. The primary driver was a delayed hire of the outreach coordinator, which compressed recruitment from twelve months to seven and limited the number of community sessions held. To recover, the outreach coordinator is now on board, two additional community partner sites have been added, and we project closing the gap by month nine of year two. We are not requesting a target change and will report cumulative progress against the original 600-participant three-year goal.

Practice quiz

  1. Question 1
    What does the Performance Progress Report primarily answer for the funder?
  2. Question 2
    How should you handle a missed performance target in the PPR?

Lesson 139 recap

The PPR is where you tell the funder what the money produced, anchored to the logic model and reconciled with the FFR. Honest variance narratives protect long-term relationships; rosy reporting destroys them.

Coming next: Lesson 140 — Prior Approval Requests

Next, we cover the changes you cannot make to an active award without first asking permission.

Saved in your browser only — no account, no server.