---
name: nonprofit-impact-report
description: Use when asked to report an organization's outcomes and impact to funders, the board, or the public after work has happened — as distinct from [[grant-proposal]], which asks for money before the work happens, and [[donor-management]], which is ongoing relationship tracking rather than a formal report artifact.
---

# Nonprofit Impact Report

A nonprofit impact report communicates what an organization actually
accomplished with the resources it was given, addressed to funders,
the board, or the public. It looks backward at results, which is what
distinguishes it from a [[grant-proposal]]'s forward-looking case for
funding — a proposal argues what will happen if funded; an impact
report demonstrates what did happen once it was.

## Key components

- **Outcomes, not just outputs** — the actual change produced (fewer
  families food-insecure, more students reading at grade level), not
  just activity counts (meals served, sessions held), which describe
  effort without showing whether it worked.
- **Data tied to original goals** — results measured against whatever
  targets were set at the start (often the same ones stated in the
  grant proposal that funded the work), so the report can be checked
  against a stated bar rather than presented in isolation.
- **Financial accountability** — how the money was actually spent,
  broken down clearly enough that a funder can see it matches what was
  proposed, alongside the outcomes it produced.
- **Narrative and story** — a small number of concrete individual
  stories or examples that make the aggregate numbers legible, without
  substituting for the data.
- **Audience-specific framing** — the same underlying results,
  presented differently for a funder (accountability against their
  specific grant), the board (strategic oversight), and the public
  (a case for continued support), rather than one document trying to
  serve all three equally well.

## Outcomes over outputs

The most common way an impact report undersells or misleads is by
reporting outputs as though they were outcomes — "we served 500
families" describes effort, not impact, and says nothing about whether
those families were actually better off afterward. A report built
around outcomes has to say what changed and for whom, which usually
requires collecting different data than activity counts do: a
follow-up measure, a before/after comparison, a proxy indicator tied to
the actual goal. This is harder and sometimes not fully available, and
a credible report says so explicitly — naming what's directly measured
versus what's a reasonable proxy — rather than implying output data
proves an outcome it doesn't actually demonstrate.

## Common pitfalls

- **Outputs presented as outcomes** — activity counts standing in for
  evidence of actual change, without acknowledging the gap between the
  two.
- **No comparison to original targets** — reporting results in
  isolation, with no reference to what was promised or expected at the
  start, makes it impossible for a reader to judge whether the work
  succeeded.
- **One report for every audience** — using the funder-accountability
  version of the report for a public-facing appeal buries the case for
  support a general audience actually needs under detail they don't.
- **Stories with no supporting data** — an emotionally compelling
  individual story, used alone without aggregate numbers behind it,
  can't establish that the result generalizes beyond one case.
- **Spending detail that doesn't map to the proposal** — a financial
  breakdown a funder can't reconcile against what was originally
  proposed erodes trust even when the spending itself was appropriate.

## Learn more

- [[grant-proposal]] for the forward-looking funding request this
  report demonstrates the results of.
- [[donor-management]] for the ongoing relationship this report is one
  input into, not a substitute for.
- [[nonprofit-board-governance]] for the board oversight function this
  report is often prepared to support.