Using Audits and Observations to Assure Practice Quality Across Shifts and Teams

February 1, 2026

Audits are one of the most common assurance tools in adult social care, but they often fail to change practice because they focus on paperwork rather than what is happening day to day. Effective assurance combines audits with observation, supervision and clear accountability for improvement. This article builds on Quality Standards & Assurance Frameworks and the operational baseline provided by Policies & Procedures, showing how audit and observation should work as one system.

What audits can and cannot prove

Audits can confirm whether records exist, whether processes are followed, and whether required documentation is complete. However, audits rarely prove:

how staff speak to people
whether choice is meaningfully offered
whether risks are managed consistently in real time
whether restrictive practice is reducing

This is why audits must be paired with observation and practice-focused checking.

Designing audits that drive improvement

Audits are most useful when they are:

Targeted – focused on key risks and priorities, not everything at once
Consistent – same method, same scoring, clear standards
Action-linked – findings lead to specific actions with owners and timelines
Re-tested – follow-up audits confirm improvement

If audits do not result in change that can be evidenced, they become a compliance ritual rather than a quality tool.

Commissioner expectation

Commissioner expectation: Commissioners expect providers to demonstrate active oversight of quality risks and to show that audits lead to improvement. They look for clear action plans, accountability, and evidence that repeat issues are reducing over time.

Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): CQC expects providers to know what is happening in services, not just what policies say should happen. Inspectors will look for triangulation between records, observation, staff understanding, and the experience of people using services.

Making observation a core part of assurance

Observation is where assurance becomes real. Practical observation focuses on the quality of interaction and support delivery, such as:

consent and choice in personal care
how staff respond to distress
medication prompts and safe administration practice
recording quality and accuracy after events

Good observation is specific and supportive, not “gotcha” monitoring.

Operational example 1: Medication practice assurance in homecare

Context: A homecare provider has accurate MAR documentation but receives concerns about missed prompts and variable practice between staff.

Support approach: The provider introduces combined assurance: MAR audits plus in-the-moment observations for medication support where appropriate.

Day-to-day delivery detail: Senior carers conduct short “medication support observations” during selected visits, checking identity confirmation, prompting approach, documentation timing, and what happens when a person refuses. Findings are discussed in supervision and used to tailor refresher training for specific staff.

How effectiveness or change is evidenced: Evidence includes improved consistency in practice, fewer medication-related incidents, supervision notes documenting competency improvement, and clearer refusal documentation with timely escalation where required.

Operational example 2: Observing dignity and pace of care in residential settings

Context: A service has few dignity complaints, but leaders suspect inconsistent practice on busy shifts. Families report that some staff seem rushed.

Support approach: The provider introduces short, structured dignity observations focused on privacy, consent, pace, tone and respect.

Day-to-day delivery detail: Team leaders observe personal care interactions (with appropriate consent and sensitivity), then provide immediate reflective feedback. Where rushed practice is observed, leaders review staffing deployment, task allocation and shift routines. Supervision focuses on balancing time pressure with person-centred practice.

How effectiveness or change is evidenced: Evidence includes improved observation scores, staff reflection notes, reduced negative family feedback, and stronger consistency across shifts.

Operational example 3: Assurance of incident learning and follow-up

Context: Incidents are recorded, but learning is inconsistent. Some teams implement changes, others repeat the same issues.

Support approach: The provider audits not just incident completion but “quality of learning”: was there analysis, action, and follow-up review?

Day-to-day delivery detail: Monthly incident review meetings use a consistent template. Leaders pick two incidents for deeper learning review, checking whether support plans were updated, whether staff were briefed, and whether effectiveness was reviewed after changes. Repeat incidents trigger a structured learning discussion.

How effectiveness or change is evidenced: Evidence includes fewer repeat incidents, better action documentation, updated risk controls, and team learning records showing changes embedded.

Closing the loop: from findings to embedded change

The strength of an assurance system is not the audit tool; it is the follow-through. Effective follow-through includes:

named owners for actions
clear deadlines and escalation routes
re-testing to confirm improvement
recorded learning shared across teams

This is what demonstrates oversight to commissioners and inspectors.

How to show audit and observation are working

In commissioning and inspection conversations, the most persuasive evidence is a clear story: what was found, what was done, and what changed. Providers should be able to evidence:

themes over time (not one-off snapshots)
actions completed and tracked
improvement demonstrated through re-checking
triangulation with feedback and lived experience