Tag: outcome reporting

  • Reporting research outcomes to funders: from outputs to impact

    When a research grant ends, the relationship between the funder and the work it paid for does not. Funders — whether public agencies, charities or research councils — are accountable for the money they distribute, and they increasingly want to understand not merely that a project happened but what it produced and, ultimately, what difference it made. This is the territory of outcome reporting: the structured account a researcher gives, often over several years, of the publications, datasets, software, collaborations, further funding, policy influence and wider effects that flow from a grant. Done badly, outcome reporting is a dreaded administrative chore; done well, it is how the research system demonstrates its value and learns what works. This article examines how outcome reporting is evolving, drawing on the funding and finance domain of the CASRAI Dictionary.

    From outputs to outcomes to impact

    It helps to distinguish three things that reporting tries to capture. Outputs are the direct products of the research — the papers, datasets, software and patents it generates. Outcomes are what those outputs lead to — the further research they enable, the collaborations and follow-on funding they spark, the uptake of findings by others. Impact is the eventual effect on the wider world — on policy, practice, health, the economy and society. The progression matters because it reflects a genuine shift in what funders ask. It is no longer enough to list publications; funders want to trace the path from output to outcome to impact, even though that path is often long, indirect and hard to attribute. Much of the recent innovation in reporting comes from trying to capture outcomes and impact, which unfold years after a grant closes and resist tidy measurement.

    Outcome-reporting systems

    To manage reporting at scale, funders have adopted dedicated systems. In the United Kingdom and elsewhere, Researchfish is a widely used platform through which researchers record the outcomes arising from their funding over time, with funders drawing on the accumulated information to understand and demonstrate the results of their investment. In the United States, federal awards are reported through the Research Performance Progress Report (RPPR), a standardised format for progress reporting across agencies that covers accomplishments, products, participants and impact. These systems share a common purpose: to collect outcome information in a structured, comparable way rather than as scattered free-text, so that it can be aggregated, analysed and reported onward. They also share a common challenge — the burden they place on researchers — which has driven much of the effort to make reporting smarter.

    Reducing burden through persistent identifiers

    The single most important development in lightening the reporting load is the use of persistent identifiers to link information automatically rather than re-entering it by hand. The principle behind this is the well-known maxim “enter once, reuse often”. If a researcher’s outputs carry persistent identifiers — a DOI for a publication or dataset, an ORCID identifier for the researcher, a ROR identifier for their organisation, a grant identifier for the award — then the links between them can be discovered and assembled by systems rather than typed in repeatedly. A publication that records its funding grant can be connected to that grant automatically; outputs registered against a researcher’s ORCID can flow into a report without manual transcription. This turns reporting from an exercise in re-keying information that already exists into one of confirming and contextualising links the infrastructure has already drawn. The persistent-identifier ecosystem — explored across our persistent identifiers domain — is what makes low-burden, accurate outcome reporting possible.

    Narrative and the limits of metrics

    Not everything that matters can be captured as a structured field. The deepest effects of research — how it changed a field’s direction, shaped a policy, improved a practice, built a capability — often need to be explained, not merely counted. This is why narrative has become central to impact reporting. A short, evidenced account of what a piece of research led to can convey forms of value that no list of outputs can. The move towards narrative reflects a broader unease with reducing research to metrics. Several practices help impact reporting work:

    • Evidence-backed narratives. Pairing a clear account of impact with concrete evidence and links to the underlying outputs.
    • Realistic timeframes. Recognising that impact often emerges years after a grant ends, so reporting must continue beyond the grant period.
    • Honest attribution. Acknowledging that impact usually results from many contributions, not a single grant in isolation.
    • Structured links plus narrative. Combining machine-readable links to outputs with human-readable explanation, so reports are both aggregable and meaningful.

    Closing the loop with the grant lifecycle

    Outcome reporting is the final stage of a continuous process that begins when a call is published and an award is made. When information is captured as structured data throughout that lifecycle — the grant, its outputs, the people and organisations involved — reporting at the end becomes a matter of drawing together links already established rather than reconstructing a history from scratch. This is the logic of treating the whole grant lifecycle, from call to closeout, as connected structured information, a theme developed in our resources on research administration. Reporting is not a bolt-on at the end; it is the harvest of good data discipline maintained throughout.

    A consistent vocabulary for reporting

    For outcome information to flow between researchers, institutions and funders — and for the same output reported to two funders to be recognised as one thing — the elements involved must be described consistently, or reports become incomparable and links break. That consistency is what the CASRAI Dictionary provides: a shared vocabulary so that the information flowing into funder reports is understood identically wherever it originates. And because every reported output rests on real contribution, the work behind it can be described in the same shared framework — the CRediT taxonomy. Funders are right to ask what their money achieved; good infrastructure and shared vocabulary are what let researchers answer honestly without drowning in administration.