The Case for a Dedicated Impact Reporting Function

Financial reporting has a job title, a department, a professional qualification, and a set of external auditors attached to it in virtually every organization large enough to need one. Impact reporting, in most organizations that produce it, has none of these — it's typically assembled by whoever has spare capacity at reporting time, drawing on data that was collected as a secondary task by program staff whose primary responsibilities lie somewhere else entirely, and who are evaluated on outcomes unrelated to measurement quality.

This isn't a minor organizational quirk that will resolve itself as the field matures naturally. It's a structural asymmetry between two reporting functions with genuinely predictable downstream effects on data quality, and understanding why it persists helps clarify what would actually need to change to fix it.

Why the asymmetry exists

Financial reporting is externally mandated by law in virtually every jurisdiction, has decades — in some cases centuries — of established practice, tooling, and professional infrastructure behind it, and carries direct legal consequences for material misstatement. Impact reporting has essentially none of this institutional scaffolding to lean on. Where it exists at all in a given organization, it's frequently a function of investor or funder pressure rather than any legal requirement, which means its resourcing tends to track the intensity of that specific external pressure rather than any internal, principled assessment of what accurate and rigorous measurement would actually require to do well.

The result, consistent with what the GIIN's own Annual Impact Investor Survey has found regarding organizational capacity across the sector, is that impact measurement work is disproportionately handled by staff for whom it is explicitly not their primary function — program officers collecting data alongside actual program delivery, or investment staff compiling impact reports alongside their core deal work. This arrangement is workable, even reasonably effective, at small scale, and becomes a genuine bottleneck as portfolios and programs grow, because the marginal hour spent on measurement is always, structurally, competing against the marginal hour spent on the work that measurement is supposed to be tracking.

What borrowed capacity actually costs

The costs of treating impact reporting as borrowed time rather than as a genuinely dedicated function show up less in whether reporting happens at all — it usually does, in some form, because external pressure typically ensures at least a minimal report gets produced — and more in the consistency and rigor of that reporting over time. Metrics chosen carefully at one reporting cycle get quietly revised at the next cycle, often for defensible-sounding reasons in isolation, because no single person or team owns continuity of the measurement approach across cycles. Data collection methodology varies from one reporting period to the next because the specific person compiling the report has changed roles, or simply has less available time this cycle than they did last cycle. Verification and quality-control checks — the parts of the measurement process that feel least urgent in the moment and are consequently the easiest to skip entirely under real time pressure — are reliably the first things cut when the person responsible for reporting is also, simultaneously, responsible for something else with a harder, more immediate deadline attached to it.

None of this necessarily means the individual staff doing the work are doing it poorly given their actual constraints — many are doing genuinely admirable work under real resource pressure. It means the organizational design itself doesn't protect measurement quality from competing priorities in the way a properly resourced, dedicated function structurally would, regardless of the individual competence of whoever happens to be assigned the work this cycle.

What a dedicated function changes

A dedicated impact reporting function doesn't just add headcount to an org chart — it changes what has genuine institutional memory within the organization. Metric definitions, data collection methodology, and quality-control processes persist across successive reporting cycles rather than being informally reconstructed from scratch, or from whatever documentation happens to survive, by whoever happens to be assembling the report this particular time. It also creates a specific role whose success is explicitly and directly measured by data quality and consistency over time, rather than a role where measurement quality is an unstated, secondary concern trailing behind a different, more visible primary job responsibility.

What this means in practice

The counterargument — that dedicated impact reporting capacity is a real cost that few organizations, especially smaller funds and program-heavy nonprofits operating on genuinely thin margins, can easily justify — is real, legitimate, and not something to dismiss lightly. But it's worth being precise about exactly what's actually being traded off in that decision. The choice organizations actually face isn't between paying for a dedicated function and getting equally rigorous reporting for free through informal, ad hoc effort. It's between paying for consistency directly, through dedicated capacity, or paying for its absence indirectly, through data quality and methodology that shifts unpredictably every single time internal capacity gets reallocated toward whatever else is more urgent that quarter — a cost that's real, recurring, and often larger than it initially appears precisely because it's harder to see on a budget line than a salary line would be.