A program report is the source. Grant reports, donor reports, board reports, annual reports are all filtered views of it. Examples and template inside.
Reporting architecture
Most nonprofits produce a grant report, a donor report, a board report, an impact report, and an annual report from the same program — the same participants, the same outcomes, the same stories. Five documents, five authoring cycles, five chances for the numbers to disagree.
A program report is the source artifact: the complete record of one program. Every other report is a filtered view of it. The grant report is the program report scoped to one funder. The donor report is scoped to one gift area. The board report adds governance commentary. The annual report aggregates across all programs. This guide gives you the five-section program report template, worked examples, and exactly how to write one.
The program report is the source. Everything else is a query against it.
Definition
A program report is the structured record a program team produces about a single program: who participated, what activities ran, what outcomes those activities produced, what participants said, and what the team learned that changes the next cycle. Every other report a nonprofit publishes — grant report, donor report, board report, annual report — is a filtered view of one or more program reports. The program report is the source; downstream reports are queries against it.
A program report covers one program. An impact report is organization-wide, built by aggregating many program reports. If the two disagree, the architecture underneath is broken.
A grant report is one program report filtered to the activities a funder paid for and mapped to the funder's template. Same evidence, narrower scope.
A program evaluation report is the same five sections with depth concentrated in methodology and outcomes — what a federal grant or research-oriented funder expects.
Read by: program teams, foundation program officers, major donors, boards of directors, and the public through the annual report. See the five-section template →
The Template
This is the reusable program report template. Every audience the program serves is asking some version of the questions these five sections answer. Sector-specific metrics fit inside the template; the template itself does not change for sector.
Section 01 · Headline
One number, one sentence: the change the program produced and the population it applies to. A program officer should grasp the result in two minutes.
The rule: if you cannot pick one number for the cover, the program theory is unclear, not the data.
Section 02 · Who
Demographic breakdown captured at intake — geography, sector, equity dimensions. Read before the headline when equity is part of the program theory.
The rule: demographics belong on the first form, not a year-end reconciliation.
Section 03 · Change
Pre-post movement on the outcomes the program theory predicted, disaggregated by the demographics from section two. Real numbers; ranges when ranges are honest.
The rule: baseline and follow-up pair by persistent ID, not by name. Names break; IDs do not.
Section 04 · Voice
Themed open-ended responses with citations to the source. Two or three exemplary quotes attributed to a role. This is where renewal decisions get made.
The rule: code open-ended answers as they arrive, not at year-end.
Section 05 · Learned
Methodology in plain language — response rate, match logic, what surprised the team — plus what the next cycle changes.
The rule: reports that name what did not work get renewed more often than reports that paint everything green.
Download
The five-section template walked end to end — from clean data to a funder-ready narrative, with the language that makes each section land.
How To
Writing a program report is filling the five sections in order. The writing is fast when four decisions were made upstream — before the program ran. The steps below are the same whether the program is a workforce cohort, a training series, or a community initiative.
Step 01
Open with the single number the program moved and who it applies to. Everything else in the report explains or qualifies that one line.
Step 02
Pull the intake demographics into section two. If the program theory is about equity, this is the section the reader checks first.
Step 03
Report pre-post movement against the outcomes your theory predicted, broken out by the demographics from step two. Pair baseline to follow-up on a persistent ID.
Step 04
Add two or three themed quotes that explain the numbers, each traceable to a source response. The qualitative section is what moves a renewal.
Step 05
State response rate, match logic, and what surprised you, then name what the next cycle changes. Honesty here builds trust for the next ask.
The upstream work
Persistent IDs at intake, structured demographics, and qualitative coding on collection turn the report into a query rather than a four-to-six-week rebuild.
The same five sections answer “how to write a report on a program,” “how to write a report after a training program,” and the funder's own template — only the scope and wrapper change. The full walkthrough is in the report-writing guide.
The Taxonomy
Read the source first, the filters second. The source is what the program team actually built. Each filtered view answers a different audience's question with the same underlying evidence.
| The report | Who reads it | The question it answers |
|---|---|---|
| Program reportThe source artifact | Program team first; everyone else through filters | What did this one program do, and what did we learn? |
| Grant reportFiltered to one funder | Foundation program officer, federal grant administrator | Did the grant produce what the grant promised? |
| Donor reportFiltered to one gift area | Major donors, donor-advised funds, recurring donors | What did my gift produce? |
| Board reportGovernance commentary on top | Board of directors, finance and program committees | Should we continue, expand, or sunset this program? |
| Annual reportAggregated across programs | Public, IRS, rating agencies, prospective supporters | What did the organization accomplish this year? |
| Impact reportOutcomes only, all programs | Funders, board, public, peer organizations | What change did we produce? |
One source, five filtered views, no parallel authoring cycles. The narrative is written once; the numbers stay consistent across every audience.
Program Report Example
A nonprofit runs a 47-person workforce cohort. The five-section template, filled with that cohort's data. Numbers are illustrative of a real Sopact program report.
+0.94 average skill delta across 47 participants, six mastery skills, 100% completion.
68% first-generation, Oakland-based, career-switchers. Demographics tagged as fields at intake, not retrofit at deadline.
Pre-post movement per skill, disaggregated by demographic; first-gen participants gained +1.1, above the cohort average.
“I came in not knowing if I belonged here. I am leaving with a portfolio.” — themed, cited to the source response.
91% response rate, paired by persistent ID. The lowest-moving skill gets more contact hours next cohort.
Four live program report examples, no login — each a real Sopact report rendered as a live URL:
01 · Cohort program
Skill movement, demographics, themed reflections, methodology — filtered to the foundation that funded the cohort.
02 · Outcomes study
Quantitative rubric scores linked to AI-extracted confidence themes — the depth a federal or research-oriented funder expects.
03 · Application program
One-page brief per applicant with citations to source text — the record a foundation panel keeps for the equity audit.
04 · Portfolio
18 program reports submitted to a shared schema, aggregated into one cross-portfolio view — the annual report's source dataset.
The Architecture
Treating the program report as the source is appealing in theory and demanding in practice. Four layers have to be in place before downstream filtering becomes a query rather than a rewrite. Each is decided upstream of any reporting tool.
01 · Identity layer
Every participant gets a unique ID at intake; every later response inherits it. Names change between waves; IDs do not. The audit trail starts here.
02 · Disaggregation layer
Geography, sector, equity dimensions, federal categories tagged as fields on the first form. Cheap at intake, dramatically harder to retrofit at report time.
03 · Voice layer
Open-ended responses themed as they arrive, with citations back to the source. Participant voice in the report by default, not a workstream that gets cut at the deadline.
04 · Delivery layer
The report renders as a URL the audience revisits, not a PDF that goes stale. Filtered views are saved views against the same URL, not separate authoring projects.
Each layer is cheap on its own and difficult to retrofit later. The team that decides these four things before the first program form spends the year exporting reports. The team that decides them after the program closes spends the year rebuilding the dataset.
Anti-Patterns
Each mistake is an upstream decision, made before the program runs, that shows up downstream as reporting cost — the four-to-six week annual report cycle most teams accept as normal.
| The mistake | What it costs | Instead |
|---|---|---|
| A separate report per audience | Four authoring cycles · four chances for numbers to disagree | One canonical report, filtered per audience |
| Building demographics at report time | Board and funder numbers differ · equity audits fail | Structured demographic fields on the first form |
| Cutting the qualitative section | Coding hundreds of answers in November · the story is lost | Code open-ended responses as they arrive |
| Matching pre/post by name and email | The join falls out · the headline stat becomes a guess | Persistent participant ID inherited by every response |
| Shipping a PDF that goes stale | Read once, filed · rebuilt from scratch next cycle | A live URL the audience revisits across the year |
Every one of these is decided upstream of the first program form. Fix them there and year-end becomes a learning moment instead of an assembly factory.
A program report is the structured record a program team produces about a single program: who participated, what activities ran, what outcomes resulted, what participants said, and what the team learned that changes the next cycle. Every other report a nonprofit publishes — grant, donor, board, annual — is a filtered view of one or more program reports.
One, the headline outcome: a number plus the population it applies to. Two, who showed up: demographics captured at intake. Three, what changed: pre-post movement on the outcomes the theory predicted. Four, what participants said: themed open-ended responses with citations. Five, what was learned and what is next: methodology plus the forward-looking note.
The reusable five-section structure — headline, who, change, voice, learned. It stays stable across program types because the questions every audience asks are stable. Sector-specific metrics fit inside the template; the template does not change to accommodate sector.
Fill the five sections in order: lead with one headline outcome and its population; show who enrolled from intake demographics; show pre-post change disaggregated by those demographics; quote two or three themed participant responses with citations; close with methodology and what the next cycle changes. The work that makes it fast is upstream — persistent IDs, structured demographics, and coding on collection.
A program report is scoped to one program: one cohort, one site, one funded activity. An impact report is organization-wide across an annual cycle, built by aggregating many program reports. If the impact report numbers do not match the program report numbers, the architecture underneath is broken.
Long enough to verify the claims, short enough that a busy program officer reads to the end — six to twelve pages, or a live URL. Most teams over-produce because each audience requested an addition. The fix is one report with multiple filtered views.
A program report with methodology and outcomes emphasized for an evaluative audience — a federal grant or research-oriented foundation. It links outcomes to the program theory, discloses sample size, response rate, and match logic, and pairs rubric scores with qualitative evidence. Same five sections, depth in sections three and five.
Yes, and live URLs outperform PDFs where it matters: the funder revisits across the year, the data refreshes as the program continues, the qualitative section drills back to the source, and the audit trail is visible. PDFs still suit board books and printed donor packets, but the canonical artifact is the live URL.
Write one report, not five
The hard part of a program report is not the writing — it is having the architecture that lets one report filter into the grant, donor, board, and annual views without rebuilding the dataset each time. Our guide walks the five-section template end to end, from clean data to a funder-ready narrative.
