How to Demonstrate the Impact of Quality Improvement in Healthcare

How do you demonstrate the impact of quality improvement across a healthcare organisation? Build a credible evidence base that connects the changes teams test with measured outcomes, the experience of patients and staff, and the organisation’s priorities. Report financial benefits where they are supported, alongside the wider value that better care creates.

For leaders overseeing a growing improvement portfolio, this is the next challenge. Knowing which projects are underway and where teams need support is valuable, but it does not fully answer the question boards, colleagues and service users will ask: what difference is this work making?

Counting projects tells you how much improvement activity you have. It does not tell you how much improvement you have achieved.

A stronger account of impact explains what changed, who benefited, how the evidence was gathered and how confident you can be that improvement work contributed. It also makes room for work that has not yet delivered results, and for lessons that may help other teams.

Why QI impact is broader than financial ROI

Financial pressures make the business case for quality improvement important. Yet assessing QI only through money removed from a budget overlooks much of its purpose. Safer care, a better experience for families and a more workable day for staff matter even when they do not generate a cash saving.

In their paper, Building the business case for quality improvement: a framework for evaluating return on investment, Amar Shah and Steven Course describe a framework developed at East London NHS Foundation Trust (ELFT). It considers six forms of return: patient, carer and family outcomes and experience; staff experience; productivity and efficiency; cost avoidance; cost reduction; and revenue. Improving outcomes for those receiving care remains the primary purpose.

This provides a useful organising lens for demonstrating impact. The practical reporting approach below builds on that lens, rather than asking every project to produce a financial return or treating all benefits as interchangeable.

Use six domains to make improvement impact visible

1. Patient, carer and family outcomes and experience

Start with what matters to people receiving care and those supporting them. Depending on the project, this might mean fewer safety incidents, better symptom management, shorter waits or greater involvement in decisions. Agree the intended benefit with patients, carers and families wherever possible, then choose measures that reflect it.

Combine outcome data with accounts of people’s experience. A patient’s story can explain why a change matters, while repeated measurement helps establish whether that experience reflects a wider pattern. Look at results for different groups where the data allows, so an improving average does not conceal people being left behind.

2. Staff experience

Improvement may make work easier, reduce frustration or give colleagues more influence over how care is delivered. Useful evidence could include a consistent team experience measure, feedback about a redesigned process or changes in time spent on avoidable administrative work.

Training attendance and participation show engagement with improvement activity, but they do not establish that working life has improved. Ask staff what changed in practice and check whether benefits are shared across roles and shifts. Consider whether a change has moved workload to another team.

3. Productivity and efficiency

Teams may deliver a more reliable service by reducing duplication, delays or unnecessary steps. Measures might include turnaround time, missed appointments, repeated requests or the time required to complete a process. These help show whether the same resources are supporting better care.

Released time is valuable, but it needs a clear description. If a process takes less staff time, explain how that capacity is being used, such as spending longer with patients or managing demand more reliably. Do not automatically convert every minute released into a cash saving.

4. Cost avoidance

Cost avoidance concerns costs that would otherwise be incurred, including existing cost pressures that improvement helps prevent from recurring. For example, reducing avoidable incidents might reduce the need for additional staffing, repairs or other resources. The claim depends on a credible estimate of what would have happened without the change.

Agree the assumptions with finance colleagues, record the relevant activity and unit costs, and state the period covered. Keep observed expenditure separate from estimates of avoided expenditure. Where uncertainty is material, report a range rather than a single apparently precise figure.

5. Cost reduction

Cost reduction means actual costs are removed from the system. Shah and Course distinguish this from avoidance by describing the opportunity for recurrent cost removal. A faster process alone does not demonstrate this: there must be evidence that expenditure has reduced and that the change can be maintained.

Finance colleagues should validate what has been removed, when the reduction took effect and whether it is recurring or one-off. Record any implementation costs or costs transferred elsewhere, and check that quality, access and staff experience have not deteriorated as a consequence.

6. Revenue

The framework also recognises potential revenue benefits. These depend on the organisation’s context and funding arrangements, and might include income connected with additional activity or improvement expertise. More activity will not necessarily mean more income under every contract.

Separate confirmed income from opportunities and forecasts, and consider the costs of delivering it. Shah and Course explicitly caution that ELFT’s organisation-wide revenue growth cannot be causally attributed to QI. A credible report should be equally careful about the strength of any revenue claim.

Build the evidence into each project from the start

Impact reporting is harder when teams reach project closure before deciding what evidence they need. A small, consistent evidence record agreed at the outset can reduce that burden. It should connect the project’s aim, the changes being tested and the measures used to judge whether things are improving.

For each project, capture:

• The aim and population: what should improve, for whom, where and by when.
• The baseline and measures: definitions, data sources, collection frequency and the starting position.
• The changes tested: what was tried, when it was introduced and what the team learned.
• The results: data over time, relevant experience evidence and any unintended effects.
• The benefit claim: the impact domain, evidence, assumptions, reporting period and person responsible for validation.
• The follow-up plan: who will monitor whether the result is sustained and when it will be reviewed.

Use outcome measures to assess the intended result, process measures to understand whether the new way of working is happening, and balancing measures to detect problems elsewhere. For example, reducing appointment waits should not come at the expense of consultation quality or an unsustainable staff workload.

Time-series data is more informative than a single before-and-after comparison. Appropriate run charts or statistical process control charts can help teams interpret variation, with annotations showing when changes were tested. A favourable data point alone is not evidence of sustained improvement.

Life QI can support this work by bringing project aims, measures, charts and PDSA learning together in a shared record. Keeping the evidence connected to the project makes it easier to explain a result and revisit the learning when the original team has moved on.

Be clear about attribution and avoid overclaiming

Healthcare organisations are complex. Staffing changes, seasonal demand, new policies, other improvement programmes and changes in data collection can all affect results. An outcome improving during a QI project does not, by itself, prove that the project caused the improvement.

A defensible account starts with the proposed connection between the change and the result. Check whether the timing fits, whether the relevant process actually changed and whether the outcome was sustained. Consider alternative explanations and, where feasible, compare patterns with a similar service that did not introduce the change. Such comparisons still require care because services and populations may differ.

Match the language to the evidence. “The team observed a sustained reduction after introducing these changes” describes what the data shows. “The evidence suggests the project contributed to the reduction” makes the interpretation explicit. Reserve stronger causal statements for evaluation designs and evidence that justify them.

Financial reporting needs the same discipline. Record implementation and ongoing costs, including staff time where practicable, and disclose significant exclusions. The Shah and Course framework helps organise benefits; a formal calculation of return on investment also requires costs. Avoid presenting a total of estimated benefits as though it were a net financial return.

Above all, prevent double counting. The same released staff time should not appear as both a productivity benefit valued in pounds and an additional cash saving in a combined total. Several projects may contribute to one outcome, but that does not mean each can claim the whole benefit.

Connect project evidence to portfolio-level reporting

As explored in our article on managing a portfolio of quality improvement projects in healthcare, leaders need visibility across the work. Demonstrating impact takes that visibility further by linking portfolio summaries to the evidence behind them.

Use common impact categories and reporting definitions, while retaining measures that make sense locally. A falls project and an access project should not need identical outcomes, but both should explain their baseline, result, evidence quality and connection to organisational priorities.

A useful portfolio report answers five different questions:

• Activity: what work is underway, and which priorities does it address?
• Progress: are teams testing changes, learning and receiving the support they need?
• Measured results: which projects show improvement, no improvement or insufficient evidence?
• Organisational value: what do those results mean across the six impact domains?
• Sustainability and spread: which results have lasted, and where have changes been successfully adapted elsewhere?

Keep these layers distinct. Completing a project is a status change, while demonstrating an outcome requires evidence. Similarly, a project with promising early results should be reported differently from one with a sustained and validated benefit. Make missing or outdated evidence visible so the report does not favour only the best-documented successes.

Aggregate only where definitions, populations and time periods are compatible. Do not add percentage improvements from unrelated projects or count the same patients and benefits more than once. Where combining numbers would mislead, present a grouped view of results with a few representative case examples and links to the underlying evidence.

Life QI’s project categorisation and reporting capabilities can help structure this view, connecting individual projects with wider programmes and priorities. Consistent records make monitoring and reporting easier, but the interpretation still needs the judgement of teams, improvement leaders and finance colleagues.

Make the report useful for decisions and learning

A board or leadership report should make it easy to see what has improved, how confident the organisation can be and what action is needed next. Pair a concise view across the impact domains with selected examples showing the problem, change, result, limitations and next step. Include work that needs support as well as successes.

Review benefits after projects close. Agree who owns ongoing measurement, what would trigger a response and whether the improvement remains part of everyday work. When a change spreads, distinguish between another team adopting it and that team demonstrating a benefit in its own setting.

The strongest evidence base supports more than a retrospective account of success. It helps leaders decide where to invest, where to offer support and which changes merit further testing. It also preserves useful learning from projects that did not deliver the expected result.

Begin with a manageable set of projects, apply consistent evidence standards and review the findings with the people delivering and receiving care. Over time, this creates a clearer account of what quality improvement is contributing across the organisation, with better care at the centre and financial value described accurately alongside it.

Reference

Shah A, Course S. Building the business case for quality improvement: a framework for evaluating return on investment. Future Healthcare Journal. 2018;5(2):132-137. The six impact domains above are drawn from the ELFT framework; the practical reporting suggestions are an application of that framework.