Beyond the Funding Agreement

Government-funded programs depend on information flowing from service providers to funding bodies. Providers record who received support, what services were delivered and what outcomes were observed. That information is submitted through reporting frameworks intended to demonstrate accountability for public investment.

This flow of information is necessary. Funding bodies need to understand whether programs are operating as intended, whether public money is being used responsibly and whether services are contributing to the outcomes they were funded to achieve.

But the reporting relationship should not end when the submission is accepted.

Funding bodies receive information across providers, services and populations. They are positioned to develop a broader understanding of the program than any individual provider can obtain from its own records. That understanding should flow back to the organisations delivering the work.

Reporting upwards supports accountability. Reporting back supports learning, improvement and a stronger connection to the program’s purpose. Both are necessary, but they serve different purposes.

Two directions, two purposes

Reporting from a provider to a funding body is primarily concerned with demonstrating what has occurred within the funded service.

Were the intended people reached? What support was provided? Were contractual requirements met? What outcomes were recorded? How was the funding used?

Reporting from a funding body back to providers should help them understand what is being learned across the program.

Where is demand changing? Which populations appear to be experiencing barriers? What patterns are emerging across services? What does the combined information suggest about the way the program is operating? How is that understanding influencing decisions?

These questions are related, but they are not equivalent. One is concerned with accounting for delivery. The other is concerned with using a broader body of evidence to improve delivery and strengthen understanding of the program.

A program can have a well-developed process for collecting information while having a limited process for returning anything useful. In that situation, the reporting framework supports oversight without fully supporting the work it oversees.

A broader view should produce shared understanding

An individual provider can examine its own activity, understand its local circumstances and review the progress of the people it supports. However, its information represents only part of the program.

A funding body may be able to see patterns across multiple providers, locations and population groups. It can consider how demand is distributed, where access appears uneven and whether difficulties experienced by one provider are also occurring elsewhere.

That perspective can help distinguish a local issue from a wider problem.

An increase in waiting times at one service might reflect a staffing vacancy. Similar increases across several services might suggest a broader mismatch between demand and capacity. A decline in referrals might reflect changing need, but it could also indicate a problem in the pathway through which people reach support.

The combined information does not automatically establish the explanation. It does, however, provide a basis for investigation that may not exist within any single organisation.

If providers contribute the information that makes this broader view possible, they should also benefit from what it reveals.

Returning data is not the same as returning insight

A report sent back to a provider may contain information the provider already holds. Activity totals, completed assessments and episode counts can be useful summaries, but reproducing those figures does not necessarily add to the organisation’s understanding.

The greater value lies in providing context that the provider cannot produce independently.

How does local demand relate to changes elsewhere in the program? Are particular groups underrepresented across services? Is an emerging access problem isolated or widespread? What questions arise when information from different parts of the program is considered together?

Reporting back should help providers interpret their own experience within that wider picture.

This requires more than making data available. Information needs to be organised around meaningful questions, accompanied by an explanation of its limitations and connected to decisions that someone is able to make.

A dashboard may make a pattern visible. It cannot, by itself, establish what the pattern means or what should happen next.

Information should return while it can influence the work

The timing of reporting affects its value.

An annual report can provide an account of a completed period and support governance, evaluation and future planning. However, information about an emerging service problem may lose much of its operational value if it is returned only after the year has ended.

Consider a hypothetical program in which several providers record increasing disengagement after an initial appointment.

Each provider may see a small number of cases and interpret them within its own service. Across the program, the combined information may reveal a pattern that warrants attention.

Returning that finding allows providers to examine possible explanations together. Are referral expectations clear? Are appointment arrangements creating barriers? Is the service being offered appropriate to the people referred?

The purpose is to bring the information back into the work while investigation and adjustment remain practical.

Different decisions require different reporting intervals. The relevant question is whether the information reaches the people who can use it in time to influence what happens.

Comparisons require context and interpretation

Information across providers creates opportunities for comparison. It also creates a risk of treating differences as conclusions.

Providers may work with different populations, levels of complexity and local service environments. Referral practices, workforce availability and the accessibility of other support can all influence recorded performance.

A provider supporting people with more complex needs may record longer episodes of care or slower changes in measured outcomes. Those differences require examination before they can support a judgement about effectiveness.

A ranking may show that results differ. It cannot, by itself, explain why.

Funding bodies hold a broader view of the program. Providers hold knowledge about the circumstances in which services are delivered. Both are needed to understand what the information means.

Reporting back should therefore create an opportunity for providers to question findings, explain relevant circumstances and identify where further examination is needed. Quantitative information may need to be considered alongside professional judgement, client experience and local knowledge.

The limitations of the data also matter. Incomplete follow-up, inconsistent definitions and small numbers can affect what can reasonably be concluded.

A useful reporting framework makes those limitations visible and allows interpretation to be informed by the people best placed to understand the work.

Strengthen the connection to the program’s purpose

Reporting back also helps providers understand their relationship with the program itself.

A provider’s most immediate experience of a funded program may be its funding agreement, service targets and reporting obligations. These define what the organisation is funded to deliver and what it must demonstrate. However, they do not necessarily help the people delivering services understand how their work contributes to the broader change the program is intended to achieve.

When information flows primarily upwards, the program can come to be understood mainly as a source of funding, accompanied by a set of conditions. The provider delivers its contracted services, submits its reports and seeks continued funding. The relationship becomes centred on the agreement.

Reporting back can strengthen that relationship by making the program’s purpose and collective contribution more visible.

When providers can see what is happening across the program, how their work contributes and how the combined evidence informs decisions, they gain a clearer understanding of the endeavour they are part of. Their services sit within a broader effort to address an identified public need.

This connection needs to reach the people delivering the work. Practitioners and frontline teams should be able to understand what the program is learning, why changes are being made and how their experience can contribute.

Over time, this can change how providers relate to the program. The funding agreement remains necessary, but the program becomes understood as a vehicle for achieving change. Funding enables the contribution; the intended public outcome gives it purpose.

That understanding creates a stronger basis for collaboration. Providers have a reason to look beyond their individual service targets, raise issues affecting the wider program and contribute to improvements whose benefits extend beyond their own organisation.

Funding bodies should explain how the information is used

Shared purpose also requires visibility of how the funding body responds to the evidence it collects.

If reporting identifies a recurring barrier to access, how has that informed program design? If unmet need becomes visible, how has it been considered in commissioning? If a data requirement provides little useful information, should it remain?

Not every finding will lead to additional funding or immediate change. Resources are constrained, priorities compete and evidence may remain uncertain.

However, providers should be able to understand what was considered, what was decided and why. Otherwise, they are asked to contribute to an evidence base without being able to see whether that evidence influences the program.

Providers should be accountable for the funding they receive. Funding bodies should be accountable for how they use the information they require.

The reporting relationship influences culture

How information is used sends a signal about what the program values.

If reporting is experienced primarily as a mechanism for identifying contractual failure, providers may become cautious about exposing uncertainty or discussing emerging problems. Attention can shift towards presenting acceptable results rather than examining what those results mean.

When information also supports investigation and improvement, providers have a practical reason to examine unexpected findings, contribute context and raise issues early.

This does not remove the need for oversight. Poor performance, unsafe practice and misuse of funding still require appropriate action.

The objective is to maintain accountability while creating room for honest examination. A program needs to identify failure, but it also needs to understand why difficulties occur and what would improve the situation.

Reporting back cannot create that culture on its own. It must be accompanied by meaningful opportunities to contribute and evidence that the funding body listens and responds.

Design the return flow into the program

Reporting back should be part of the reporting framework from the outset.

Before introducing a data requirement, it is worth asking:

• What decision will this information support?
• What can be learned by considering it across the program?
• Who would benefit from that understanding?
• When would they need to receive it?
• What context is necessary to interpret it fairly?
• How will providers contribute to the interpretation?
• How will resulting decisions and actions be communicated?

The return process should be proportionate. A focused discussion or a short analysis of a specific issue may contribute more to improvement than a comprehensive report with no clear operational use.

The aim is to return enough meaningful information to support better decisions and a stronger understanding of the program.

Complete the reporting relationship

In Data Quality as a Side Effect, I argued that information is more likely to be reliable when it supports the delivery, management and improvement of services.

The same principle applies across the funded program.

Reporting upwards demonstrates accountability for what has been delivered. Reporting back helps providers understand what their contribution is achieving, what is being learned and what needs to change.

Together, they strengthen the relationship between the funding body, the organisations delivering services and the purpose of the program.

The program becomes more than the mechanism through which services are funded. It becomes a shared vehicle for achieving the change the funding was intended to make possible.