Pharmacy Audit: Close the Loop, Not the Spreadsheet

The spreadsheet is not the finish line. A useful pharmacy audit defines the standard, finds the gap, changes the work and checks the result again.

Pharmacy audit guide showing an evidence, finding, action and remeasurement loop around a community pharmacy, with Pharmacy Mentor logo

A pharmacy audit is a comparison between agreed practice and the evidence of what actually happened. Its value does not sit in the number of rows collected. It sits in the decision that follows, the person who owns the change and the remeasurement that shows whether the pharmacy improved.

That distinction matters in 2026/27. Contractual audit requirements, Pharmacy Quality Scheme activity, professional assurance and a pharmacy's own improvement priorities do not automatically ask the same question. Owners need to identify the purpose and current source before copying last year's template or treating every review as one interchangeable audit.

In brief

How should a community pharmacy run an audit?

Define the question, authority, standard, population, period, exclusions and owner before collecting data. Use the smallest reliable dataset that can answer the question, protect confidentiality, analyse variation rather than only totals, agree proportionate actions and repeat the measurement after change. Keep clinical audit, operational checks, financial reviews and inspection preparation clearly labelled so the pharmacy knows what each exercise can and cannot prove.

Separate the audit types before choosing a template

“Audit” can describe several different activities in a pharmacy. A clinical audit measures care against explicit standards and seeks improvement. An operational audit may test stock, claims, records, workflow or equipment. A financial audit has a specific professional and statutory meaning. An internal check can provide useful assurance without becoming any of those formal exercises.

Write the label and purpose at the top of the plan. State who requested it, who will use the result and which decision it can support. This prevents a stock checklist being presented as clinical assurance, an inspection-readiness review being mistaken for regulatory approval or a one-off data collection being called a completed improvement cycle.

Our pharmacy clinical-governance guide places audits alongside incidents, complaints, competence, information governance and service change. An audit is one way to test a system; it does not replace the rest of the owner's assurance framework.

Check the current 2026/27 requirement

Requirements change. Community Pharmacy England's clinical audit page, updated on 1 October 2026, says pharmacy owners do not have to undertake a clinical audit in 2026/27 under the Terms of Service requirement. That does not mean every audit-related activity has disappeared.

NHS England's 2026/27 PQS clinical-services audit guidance sets out a Pharmacy First clinical pathways consultations audit and peer discussion. The wider Pharmacy Quality Scheme page describes the current quality-improvement purpose. Read the live specification and supporting documents in full before deciding eligibility, method, dates or evidence.

Other services, commissioners, organisations or professional systems may create their own audit or review needs. Keep a source register with the title, owner, publication or version date, applicable pharmacy, completion window and evidence location. Do not carry a deadline or template forward merely because it appeared in last year's calendar.

Write a question that can change a decision

A broad question such as “Are we compliant?” is difficult to measure and easy to answer too confidently. A useful audit question names the pathway, population, standard and period. It may ask whether a defined group received a documented step, whether a safety control was used when required or whether a completed service record contained the evidence needed for a later decision.

Choose topics from live signals: repeated exceptions, near misses, complaints, service data, changed guidance, new technology, capacity pressure or unexplained variation between branches. The pharmacy near-miss log guide shows how several isolated records can reveal one system condition worth testing.

State what the pharmacy will do with each possible finding. If a low result would not change the procedure, training, system, resource, supervision or service design, the question may be too vague or the owner may not yet be ready to act. Audit should create a decision route, not an archive.

Audit decisionDefine before collectionWeak substitute
PurposeRequirement, risk or improvement question“We do this every year”
StandardExact source, version and measurable criterionA locally remembered rule
PopulationIncluded cases, period, sites and exclusionsWhatever records are easiest to find
MethodFields, sample, collector and quality checksA spreadsheet with no data definition
ActionOwner, due date, resource and escalationA recommendation with no accountable person
ClosureRemeasurement date and success testFiling the first result as complete

Define the standard and measurement method

Translate the source into observable criteria without changing its meaning. Record the source, date, page or section, numerator, denominator, exclusions and any judgement rule. If a criterion needs professional interpretation, name who will make that judgement and what evidence they will use.

Choose a timeframe and sample that can answer the question. A full population may be appropriate when the numbers are small or the risk is high. A sample may be more proportionate when the records are numerous, but the selection method must avoid choosing only easy or successful cases. Describe missing records rather than silently replacing them.

Run a small pilot. Ask two people to apply the criteria to the same few records and compare their answers. A disagreement may show that the data definition, source or collection form is unclear. Correct that before the pharmacy creates a larger dataset that cannot be interpreted consistently.

Use measures that expose the process. A single pass percentage may be necessary, but it can hide where the pathway breaks. Consider stage, branch, day, role, exception type or another relevant dimension, while keeping the dataset proportionate and protecting confidentiality.

Collect defensible evidence without creating excess data

Collect only the information needed to answer the approved question. Separate patient-identifiable operational records from the analysis dataset wherever possible. Define who can access the source and the output, where files are stored, how transfers occur, how long working copies remain and how they will be disposed of.

Train collectors using examples and exception rules. Record unavailable, not applicable and not documented as different states. An empty cell should not require the reviewer to guess whether the step failed, the case was excluded or the collector forgot to enter a value.

Preserve an audit trail. Note the extraction date, systems used, filters, sample method, manual decisions, corrections and final approved dataset. If a source record changes after collection, the pharmacy should still be able to explain which evidence supported the result at the time.

Do not let the audit itself create a new safety problem. Plan collection around workload, supervision and access. Avoid printing unnecessary personal data, leaving records in shared areas or encouraging staff to complete clinical documentation retrospectively simply to improve the measured percentage.

Find the pattern behind the percentage

Begin with data quality. Check totals, duplicates, impossible values, unexpected exclusions and missing fields. Reconcile the sample back to its source. A precise-looking chart cannot repair an incorrect denominator.

Compare the result with the agreed standard, then investigate variation. Which step failed most often? Did the issue cluster around one branch, shift, service stage, record type or system change? Is the problem knowledge, interface design, capacity, equipment, unclear responsibility or an unrealistic procedure?

Talk to the people doing the work. Audit data can show where the pathway differs from the standard; observation and discussion help explain why. Avoid treating the first plausible explanation as the root cause. A training reminder will not fix a screen that hides the required field or a workload pattern that makes the intended process impossible.

Connect related evidence. Complaints, incidents and near misses may strengthen or challenge the interpretation. Our pharmacy complaints procedure guide explains how one person's experience can become service learning without turning every complaint into proof of a wider trend.

Assign action and close the loop

Write each action as a controlled change: what will change, who owns it, when it is due, what resource or approval it needs, which risk it may introduce and how completion will be evidenced. Prioritise actions by patient and service risk, not by how easy they are to tick off.

Different findings need different responses. Clarify a procedure when the decision route is ambiguous. Change an interface when the system makes the right step hard to find. Adjust capacity or sequence when the work cannot fit the shift. Train when a genuine competence gap exists, then observe practice rather than treating attendance as proof.

Choose the re-audit date while agreeing the action. Allow enough time for implementation and a representative sample, but do not leave a material risk unmonitored. Define what improvement would count, which guardrails must remain stable and what happens if the result does not move.

Build a proportionate pharmacy audit programme

Keep one register of current audit and assurance activity. Include mandatory schemes, commissioner or service requirements, risk-led internal audits and follow-up reviews. Record purpose, source, scope, owner, collection window, result, actions, remeasurement and closure. This prevents duplicated data collection and exposes overdue loops.

Balance the programme across risk and learning. Repeating the same familiar audit because the template is easy can leave a changed service or recurring incident untested. At the same time, too many simultaneous audits create fatigue and shallow actions. Prioritise the questions that can materially improve care or operations.

Use dashboards carefully. The pharmacy data analytics guide can help define measures, sources and review rhythms, but automation does not remove judgement. A live measure can support monitoring between audits; it does not automatically establish the audit standard, explain a variation or approve the response.

Share the learning in a usable form. Teams need the question, finding, change and result—not a long report with no role-specific action. Update controlled procedures and training where appropriate, keep superseded material out of use and make the follow-up evidence easy to retrieve.

Pharmacy Mentor helps owners connect governance, operations, data and growth decisions. Explore our pharmacy strategy support, or book a consultation to turn scattered evidence into an accountable improvement system.

Important: This is general operational information, not clinical, regulatory, legal or data-protection advice. Audit requirements and service specifications change and vary across the UK. Confirm the current source and obtain appropriate professional advice for the pharmacy, service and proposed audit.

Frequently asked questions

What is a pharmacy audit?

A pharmacy audit compares defined practice or outcomes with an explicit standard, identifies gaps, supports agreed action and measures again to determine whether the change improved the result. The exact method depends on whether the exercise is clinical, operational, contractual or another form of assurance.

Do community pharmacies need to complete a clinical audit in 2026/27?

Community Pharmacy England states that pharmacy owners do not have to undertake a clinical audit in 2026/27 under the Terms of Service requirement. Separate activity still exists, including the 2026/27 Pharmacy Quality Scheme clinical-services audit. Check the current requirements that apply to the pharmacy and service.

What should a pharmacy audit include?

Record the purpose, authority, standard, source version, population, period, exclusions, method, data definitions, owner, findings, analysis, actions, dates, communication and remeasurement. Keep the evidence needed to explain how the result and decisions were reached.

When is a pharmacy audit complete?

Data collection and a report are only the first part. The cycle closes when proportionate actions have owners, the change reaches practice, the pharmacy repeats the measurement and the result is reviewed, documented and either closed or escalated.

Keep exploring

More pharmacy insight

Pharmacy Business

Pharmacy Fit Out: Brief the Work Before the Walls

A low quote can become an expensive closure. Define workflow, services, access, responsibilities and handover before appointing a pharmacy fit-out partner.

Read article →
Pharmacy Business

Pharmacy Refrigerators: Buy the Storage System, Not the Box

Capacity is the easy number. Test temperature recovery, usable shelf space, alarms, service access and failure response before choosing a pharmacy refrigerator.

Read article →
Pharmacy Business

Pharmacy Benchmarking: Compare Like with Like, Then Act

A league table can make one branch look exceptional without explaining why. Build fair pharmacy benchmarks that expose useful variation and trigger a decision.

Read article →