A community health provider delivering programmes under several funding agreements faced a familiar version of a serious problem: every funder wanted evidence — activity data, outcome measures, financial acquittals — in slightly different formats, on different cycles. Each reporting round triggered a scramble across case workers' diaries, spreadsheets and inboxes. Reports arrived on time only because staff worked evenings to make it so, and the CEO could not shake the concern that one missed evidence requirement could put a funding renewal at risk.
The problem
We audited the last year of reporting rounds. The provider managed five distinct funder formats from the same underlying activity, yet the data was collected four different ways. Reconciliation between programme records and the finance ledger was manual and happened only at acquittal time, which meant discrepancies surfaced late. Roughly forty staff hours were consumed per reporting round, concentrated in two senior case workers whose client-facing time the organisation could least afford to lose. Most importantly, the evidence trail — the link between a reported number and its source documents — was informal and incomplete.
The obstacles
Three constraints framed the work. Staff capacity: any solution that added data entry to case workers' days would fail on contact. Confidentiality: client-level information is sensitive, and reporting had to aggregate without exposing individuals, under handling practices the sector's obligations demand. And funder variety: the five formats could not be standardised away, because the funders themselves required them.
What we did
The design principle was collect once, report many. We defined a single core data set — the fields common to all five funders plus the organisation's own management needs — and built the collection routine around programme workflows rather than adding to them: data captured at the point of service through forms the case workers already completed, restructured slightly to capture the structured fields once. A reporting layer then renders each funder's format automatically from that core set, with an evidence register linking every reported figure to its source records. A monthly internal pack — the same data, management-oriented — established a reconciliation routine with the finance ledger, so acquittals ceased to be archaeology. Staff received training and a one-page guide per programme; the funders received advance notice of the improved format.
The result
Every reporting round since implementation has been delivered on time, in the required format, with the evidence trail attached. The per-round effort fell from roughly forty staff hours to under ten, and the two senior case workers returned to client work. Reconciliation with finance is now routine rather than forensic, and the CEO's risk concern — an evidence gap at funding renewal — has been replaced by a documented, demonstrable trail. The organisation's board now uses the monthly internal pack as its primary operations view.
Engagement type: Defined Project (framework design, collection restructure, automation build), followed by a reporting maintenance retainer.
Why collect-once reporting matters beyond funders
The framework was designed for funder compliance, but its value extended across the organisation, and that pattern is worth explaining. Once activity data was captured in one structured form, it could serve audiences the project never targeted: the board's monthly operations view (mentioned above), programme managers comparing caseloads and outcomes between teams, and the intake team spotting referral patterns by source. The same evidence trail that satisfies an acquittal also shortens internal questions from an afternoon of digging to a lookup. This is the quiet multiplier in governance work: the discipline that satisfies an external auditor is the same discipline that gives management better answers than it had before.
For community and health providers specifically, two further points from this engagement transfer directly. Design for the busiest week, not the average one — data collection that survives a crisis week is the only kind that stays complete across a year. And involve the case workers in defining the fields: the structured fields succeeded because the people completing them shaped them, which cut the training burden to a single session and made the data trustworthy at the source rather than corrected after it.
Funder reporting shouldn't consume your clinicians
Collect once, report many — a framework we can scope for your agreements.