Clinical Audit and Quality Improvement: Related, But Not the Same

The confusion has persisted for more than 30 years. It is time to resolve it.

In 1994, as part of a job application for a research officer role with the British Medical Association's Clinical Audit Committee, Dr. Paresh Dawda wrote a paper exploring the relationship between Total Quality Management and medical audit. The central argument was straightforward: these two approaches are related, they share common ground, but they are fundamentally different in purpose, method, and application. Conflating them leads to wasted effort, missed opportunities, and frustrated practitioners.

That was over 30 years ago.

In 2026, a peer-reviewed article published in Frontiers in Health Services — Davey et al., "Clinical audit and quality improvement: rivals, partners, or one and the same?" (doi: 10.3389/frhs.2026.1768450) — is making precisely the same argument. The language has been updated. The evidence base has deepened. But the core problem it addresses is unchanged.

This is not a niche academic debate. It sits at the heart of every capability-building conversation we have with teams across primary health networks, government agencies, and provider organisations. When teams are unclear about which approach to use, and why, they choose the wrong tool for the job. That is a problem we can solve.

What They Have in Common

Before exploring the differences, it is worth being clear about what audit and quality improvement (QI) share. They are not opposites. They belong to the same ecosystem.

Both audit and QI:

• Aim to improve the quality of healthcare. Whatever their methodological differences, both approaches exist in service of better care for patients.

• Involve measurement. Neither approach operates on instinct or assumption. Data is central to both.

• Require stakeholder engagement. People need to be involved. The question is who, when, and how deeply.

• Inform a quality management system. Both generate evidence that organisations can use to understand where they are and what needs to change.

• Involve taking action based on findings. Neither is an exercise in data collection for its own sake. Both are intended to lead somewhere.

• Need evidence as a foundation. Whether you are setting a standard to audit against or designing a test of change, you need a grounding in what the evidence says.

• 
  

These commonalities explain why the two approaches are so often conflated. They look similar from a distance. But the closer you get, the clearer the distinctions become — and those distinctions matter enormously in practice.

Where They Diverge

Purpose

This is the most fundamental difference. Clinical audit is primarily a tool of assurance. Its purpose is to provide evidence about whether care is meeting agreed standards. Quality improvement is primarily a tool of improvement. Its purpose is to make and study change in a systematic way.

These are different questions.

"Are we meeting the standard?"

is an assurance question.

"How do we make care better?"

is an improvement question. Both are legitimate, but they call for different approaches.

Methodological approach

Audit follows a structured cycle: agree on or review standards, collect data on current practice, compare results against those standards, and act where gaps are identified. It is measurement-driven and retrospective by nature.

QI uses a set of principles and methods for making and studying change. Approaches include PDSA cycles (Plan-Do-Study-Act, from the Model for Improvement), Lean and PDCA methodologies, fishbone diagrams, process mapping, driver diagrams, and statistical process control. These are not data-collection tools — they are change-testing tools. The question is not only

"what is happening?"

but

"what happens when we try something different?"

This is where a question widely used in QI circles becomes instructive:

What can you do by next Tuesday?

It sounds deceptively simple. But it contains a philosophy. It asks practitioners to identify the smallest meaningful test of change they can run right now — not after six months of data collection, not after the next governance meeting, not once a full audit cycle is complete. By next Tuesday. Observe what happens, learn from it, and test again. Audit cannot be done by next Tuesday. QI, even in small ways, can.

Measurement

In audit, measurement typically involves larger data samples collected retrospectively and compared to a predetermined standard. The purpose is to establish whether performance meets the benchmark.

In QI, the philosophy is "just enough" data, collected frequently over time to detect whether a change has produced a statistically significant improvement. The aim is not to describe the past but to understand whether an intervention is working as it is being tested.

Output

Audit produces evidence of compliance or non-compliance with standards. Its primary output is a report: here is where we are relative to where we should be.

QI produces new learning and, ideally, improved processes. Even when a test of change does not produce the intended outcome, the learning generated informs the next cycle. In audit, null findings are a form of success — they mean high-quality care is being delivered and energy can be redirected. In QI, null findings are data, not a conclusion. They tell you to go back and refine your hypothesis.

Influence on change

This difference is particularly important for practitioners. In an audit, the person conducting the audit typically has limited direct influence over the changes that follow. Findings are reported; whether action is taken depends on others.

In QI, influence over change is considered from the outset. A core principle is identifying who needs to be involved in testing and implementing change, and engaging them early. This is not a procedural formality; it is a methodological necessity. Change that does not involve the people who do the work rarely sticks.

Stakeholder collaboration

In audit, stakeholder engagement tends to be most prominent after gaps are identified — when action is needed. In QI, collaboration is built into the design from the beginning. This is why QI is more suited to complex, context-sensitive problems where the people closest to the work hold essential knowledge about what is feasible and what will be accepted.

Timescales

Audit cycles typically run over four to twelve months, with repeat cycles up to 24 months. QI projects can range from four to six months for smaller tests to nine to twelve months for larger initiatives. The timelines look similar on paper, but the work within them is structured very differently.

How learning is shared

In an audit, findings are typically reported after the cycle is complete. In QI, learning is shared throughout the process to inform subsequent steps. This ongoing communication is integral to the methodology, not an add-on.

Where each is most useful

Audit is particularly well-suited to raising standards across a region or country, where the question is whether a defined standard is being met at scale, and where the priority is accountability and assurance. QI is better suited to improving specific elements of local services, particularly where the problem is complex and context-sensitive, and where the path to improvement needs to be discovered through iterative testing rather than prescribed from the top.

Why the Confusion Persists — and Why It Matters

Come back to that question: What can you do by next Tuesday?

It is a genuine test of whether a team is doing audit or QI — not because one is better than the other, but because they operate on completely different logics. Audit requires you to agree on standards, collect data, compare and report before you can act. The honest answer to "what can you do by next Tuesday?" in an audit framework is: probably nothing yet. And that is fine, when assurance is what you need.

But when what a team actually needs is to improve something — to fix a broken referral pathway, reduce a waiting time, change how a handover is conducted — and they have been directed to audit it first, the consequences are real and significant.

They design a process that asks for large amounts of retrospective data before any action is possible. They spend months accessing existing databases where data may be incomplete, hard to obtain, and only loosely connected to the local problem they are actually trying to solve. They complete the cycle, produce a report, and find themselves in a governance meeting, hoping that someone else will act on the findings. The person who did the work rarely controls what happens next. The change they wanted to make is no closer.

If that same challenge had been framed as a QI project, the team could have identified a small, testable change and run a PDSA cycle within weeks. Even if the first test did not produce the intended result, the learning would have refined their thinking and moved them closer to improvement. Unsuccessful tests of change in QI are not failures. They are data. They tell you to adjust your hypothesis and try again. That is how complex problems get solved.

The difference is not just methodological. It is motivational.

Davey et al. cite evidence that repeated misalignment between tool and intent erodes workforce motivation over time. That is not surprising. Practitioners who invest time and effort into quality work and find that it does not lead to meaningful change will eventually disengage. It is not a lack of commitment. It is the predictable result of reaching for the wrong tool repeatedly and experiencing the frustration that follows.

This is compounded at the educational level. Postgraduate medical curricula have, in some cases, substituted PDSA cycles for audit cycles as if they were interchangeable steps in the same methodology. They are not. An audit cycle assesses performance against a standard. A PDSA cycle tests a change and generates learning. Treating them as equivalents produces practitioners who are technically familiar with both terms but fundamentally unclear about when to use which — and why it matters. Competency-based portfolios can make this worse by rewarding the rapid completion of superficial audit cycles over the sustained, longitudinal engagement that genuine improvement requires.

The consequences extend beyond individual practitioners. When an audit is treated as QI, organisations lose the assurance function that an audit is specifically designed to provide. When QI is attempted without proper foundations, improvement efforts become unfocused and difficult to sustain. Both approaches are weakened when their distinct purposes are not understood and respected. And the quality management system that depends on both working well is left with gaps where the real work of improvement should be happening.

Choosing the Right Tool

The Davey et al. paper presents a decision aid to help practitioners navigate this choice and to support purposeful transitions between the two approaches when circumstances change.

The framing that guides the decision is worth stating plainly:

• If you need to know whether care is meeting an agreed standard, use an audit.

• If you need to understand how to make care better, especially in a complex local context, use QI.

• If you need both, design them as complementary activities within your quality management system — not as substitutes for each other.

• 
  

A quality management system that incorporates both approaches is more capable than one that conflates them. Audit provides the accountability infrastructure. QI provides the improvement engine. They inform each other. Audit findings can reveal where QI effort is needed. QI projects can generate evidence that informs updated standards. Used together, with clarity about what each is doing and why, they are genuinely powerful.

The Capability Building Imperative

The reason this matters so much in our work is that it sits directly beneath team motivation and confidence. Practitioners who are unclear about which method to use, who have experienced the frustration of months spent on audit when they wanted to improve something, who have been told their PDSA cycles are "really just audit" — these are practitioners who lose confidence in quality improvement as a discipline.

Rebuilding that confidence starts with conceptual clarity. Not as a theoretical exercise, but as a foundation for practical action.

In every capability-building programme we run, with every team we work

alongside, we find that taking the time to be precise about these distinctions pays dividends. Teams that understand what an audit is for, and what QI is for, make better decisions about which to use. They design better projects. They generate more useful learning. They act with greater confidence.

The fact that a peer-reviewed paper published in 2026 is still making the argument that Dr. Dawda made in 1994 tells us something important: this is not a problem that resolves itself over time. It requires deliberate, sustained effort to address through education, curriculum design, and the way we support health professionals in practice.

Working on This Together

If you are leading a team, running a training programme, or designing capability building initiatives for health professionals, the distinction between audit and QI is worth investing in — not as a conceptual nicety, but as a practical foundation for effective quality work.

At Prestantia Health, this is an undercurrent in everything we do. Whether we are working with a primary health network on practice transformation, supporting a provider organisation to build internal QI capability, or helping a team understand why their previous quality projects did not produce the change they hoped for — the clarity of this distinction is almost always relevant.

If this resonates with what you are seeing in your organisation, we would be glad to talk. Get in touch with us to explore what a tailored capability-building approach might look like for your context.

Reference: Davey et al. (2026). Clinical audit and quality improvement: rivals, partners, or one and the same? Frontiers in Health Services. https://doi.org/10.3389/frhs.2026.1768450