The short versionImpact reporting is not a reporting problem. If the annual report takes three weeks of reconciliation, the fix belonged eleven months earlier.
Three weeks in a spreadsheet
The work was real all year. A volunteer shift, a donor conversation, a community event, a vendor invoice, a programme outcome — every one of them happened, and every one was recorded somewhere defensible at the time. The difficulty is that “somewhere” is a different place for each, and the connections between them were never written down, because at the time everybody involved knew them.
So the report becomes an act of reconstruction, performed under deadline, by whoever was least able to refuse it. And a figure assembled that way is defensible only in the sense that nobody can check it.
If the number takes three weeks to assemble, nobody can audit it — including you.
What has to be connected, and when
During the year, not in the fortnight before the board meeting. Four links do most of the work.
- Programme records tied to the participants, services and outcomes they produced.
- Volunteer and event activity attached to the campaign goals it was meant to serve.
- Donor engagement linked to the funding priority it was raised against.
- Dashboards that read those links directly, so the reported figure and the operational figure are the same figure.
What connected data does not do
It does not tell you whether a programme worked. Attribution is a judgement about causes, and connecting the records only means that judgement is made against a complete picture instead of a partial one. Software can assemble the evidence and summarise it; deciding what it demonstrates is the leadership's job and stays there.
The honest promise is narrower than most CRM copy makes it, and more useful: the annual report stops being an archaeology project, and the number in it is one you could defend in the room.
Written about Non-Profit CRM
