A funder report that is a query, not a month of copy-paste — every outcome against a pre-committed target, every number paired with a verbatim quote, every claim graded before it ships.
For: program teams — nonprofit or social enterprise, running a training cohort, a scholarship class, a fellowship, or an accelerator — who owe a funder or grantmaker an impact report and dread the month it takes to produce one.
Why: the funder report is usually a year-end scramble — re-export every system, reconcile mismatched IDs for days, copy numbers into a deck that is stale on arrival, and ship claims nobody can trace to a source.
Outcome: a cited impact report that is a query, not a month of copy-paste — the cohort rolled up to your theory of change, every outcome against a pre-committed target, every number paired with a verbatim participant quote, every claim graded evidenced, unproven, or missing.
This is Chapter 12a of the Case Intelligence series — the capstone. In Chapter 11 you scored every candidate–role pair against one rubric and the funnel narrowed to 29 placements. Every earlier chapter was quietly stocking the shelves for this one: intake captured the baseline, the midpoint tracked it, exit closed the pair, the notes explained the drop-offs, the SROI chapter priced the change. Whether your participants are trainees, students, founders, or grantees, the method is identical.
As always, the first two steps are [DIY] — structuring the report and committing to targets are thinking work for any AI chat window. The last two are [SENSE] — because a chat window cannot quote transcripts it never received, and cannot grade a claim against waves it cannot see.
Here is the ritual most teams know by heart. At grant close, someone exports the case-management system for the intake data. Then the survey tool, for the mid and exit numbers. Then the spreadsheet where the follow-up wages were pasted. Then the notes nobody has read since March. Each export carries a different ID scheme, so reconciling them takes days. The numbers that survive get copied into a deck — and the moment they are copied, they are stale. Worst of all, the claims ship uncited: "confidence rose" with no participant's words behind it, "82% employed" with no way to trace which participants, in which wave, measured how.
That ritual is not a staffing problem; it is the collect-then-clean architecture doing exactly what it was built to do. When every field was scored the moment it arrived, and every score and quote sits on one persistent ID, the report does not get assembled at cohort close — it gets queried. The report was being written the whole time; close is retrieval.
One more thing decides whether the report can be trusted: what a funder actually asks. Not how many workshops you ran — whether the program changed lives, at what cost, for whom, and whether you can prove it. Outcomes against targets, the funnel with its drop-off, cost per outcome, a defensible SROI, equity coverage, variance named plainly, and a citation behind every number. Activity counts are not on that list, and funders can tell the difference.
Draft the skeleton before you touch any data — the same outline every reporting cycle, so this year's report is comparable to next year's. Deciding the sections before seeing results also removes the quiet temptation to organize the report around whatever happened to look good.
Here is my program, the outcomes the grant promised, and my funder's reporting requirements: [paste all three].
Build my report outline from these sections only, dropping any that don't apply: outcomes vs targets; the funnel with honest drop-off; cost per outcome; SROI carried from an existing sourced calculation; equity and subgroup coverage; grant variance; theory-of-change rollup; citations policy. For each section you keep, say in one line what funder question it answers and what data it needs. Apply the activity-count test mechanically: if a section's headline number could grow while participants' lives stayed unchanged — sessions delivered, hours mentored — cut it, or demote it to variance explanation.
Structure is where honesty gets decided. If "beneficiaries served" means the funnel with its drop-off, the report can be trusted; if it means the largest number anyone touched the program, it cannot.
From your theory of change, pick the outcomes the grant funded and commit — before the results are in front of you — to one indicator and one target each: a confidence gain of +2.5 on the same scale, a median wage of at least $20 an hour at follow-up, 70% completion, 30 placements. Each indicator must point at a store and wave that already collects it; a target with no collection point is a coverage gap to name, not a number to improvise at close.
Here is my theory of change, and the stores and waves I already collect: [paste both].
Before any results exist, commit my reporting targets: only the outcomes the grant funded, one indicator and one checkable numeric target per outcome — no ranges of convenience, no "directional" targets. For each, name the store and wave that already collects the indicator; if nothing collects it, write NO COLLECTION POINT so it becomes a named coverage gap instead of a number improvised later. Flag any indicator whose scale changes between waves, and never delete a hard-to-hit target — a reported miss is worth more than a soft target hit.
A target chosen after the results is a target that cannot be missed — which is to say, not a target. Committing first means a miss ships as a miss, and funders have read enough reports to recognize a program that measures itself from one that grades its own homework.
From here on, this is what the product does — not a prompt you run. A chat prompt can format whatever you paste into it, but it cannot cite what it never received — and at close, nobody re-reads five waves of open text to find the right quote. Here, the citations were built when the data landed: every field scored on arrival, every open-text answer preserved in the participant's exact words beside its numbers, on the same record, same ID. Look at one claim as it sits in the store at cohort close:
Nothing in that card was produced for the report. The intake wage was captured at intake, the follow-up wage two waves later, the quotes scored on arrival, the join guaranteed by the ID. In a collect-then-clean stack, pairing a number with a quote at report time means a human searching transcripts for something usable — slow, and quietly biased toward the most quotable participants. Here the pairing predates the report, so the citation is whatever the record actually says.
Now the close itself. In Sense you ask over all the stores at once, in plain language:
Study the placement row. Twenty-nine against a target of thirty ships as a near-miss, with the variance attached from the requisition store — 25 roles unfilled on citizen-only and CDL hard fails while 29 credentialed candidates sat surplus. A scramble-built report would have rounded that story off; a queried one attaches it. And the comparison numbers carry their own asterisk: 82% of completers employed at follow-up versus 45% of non-completers is a comparison, not a causal claim, and the report says so. A report that names its own gaps reads as more credible than one that pretends to none — because it is.
Reporting activity instead of change. Sessions delivered, workshops run, hours mentored — funders skim past all of it looking for the outcome. Let activity appear only where it explains a variance.
Choosing targets after seeing the results. A target set at close is a ratification, not a commitment, and experienced funders can smell it. Commit first, and let 29-against-30 ship as exactly that.
Shipping numbers without words, or words without numbers. A number alone is an assertion; a moving quote alone is an anecdote. The unit of funder evidence is the pair — figure plus verbatim quote on the same ID — and the pairing has to happen on arrival.
Blending measured and benchmarked value. An SROI that mixes observed wage gains with modeled proxies in one undifferentiated number invites the one diligence question that unravels the report. Carry the split intact.
Hiding the coverage gaps. The outcome you never measured does not disappear because the report omits it — it becomes the question you cannot answer on the call. Grade every claim, and let MISSING appear in print.
A funder impact report that is a query against data scored on arrival: the cohort rolled up to your theory of change, each outcome against a target you committed to in advance, the funnel told honestly, cost-per-outcome and a defensible SROI carried intact, equity coverage stated in numbers, every claim paired with a verbatim quote on the persistent ID, and every claim graded so nothing unsupported ships. Cohort close is an afternoon of queries and one human read-through — not a month of re-export and reconciliation.
Take your most recent funder report and grade its claims: for each one, ask whether there is a figure and a participant's own words behind it, on the same record. Count how many survive as evidenced. That count is your current citation rate, and it is the single number this chapter exists to raise.
Program teams who lose a month every year to the report scramble and still ship claims they privately cannot source. Development directors who have watched a funder probe one uncited number and discount the rest. Evaluators who want targets committed before results, quotes beside figures, and gaps stated instead of smoothed. If your last report was assembled from six exports and hope, the fix starts here.
Write your funder report in Sopact Sense — sopact.com/academy.
Next in the series: How to Turn a Cohort into a Social-Enterprise Investor Report — the same records, an investor lens: blended value, unit economics, and the path to self-funding.
Open Sopact Sense, paste your program description, and put it to work.
Try it in Case Intelligence →
