Managing Persistent Underperformance in Adult Social Care: When Improvement Does Not Stabilise

Most performance concerns in adult social care respond to structured support, supervision and observation. However, there are cases where improvement does not stabilise, or where gains are short-lived and drift returns. Within performance management and capability, leaders must be able to evidence when continued support is appropriate and when a more formal decision is required. This must be done without increasing safeguarding risk or destabilising teams. It also links to role clarity and onboarding robustness within your broader recruitment systems, as recurring themes may signal mismatch rather than misconduct. This article sets out how to manage persistent underperformance safely and defensibly.

Recognising when improvement is not stabilising

Indicators that improvement has not embedded include:

• Short-term compliance during enhanced monitoring followed by relapse.
• Repeated similar errors across different contexts.
• Dependence on supervision presence to maintain safe practice.
• Inconsistent judgement under pressure despite coaching.

When these patterns emerge, leaders must reassess both individual capability and system factors.

A structured approach to persistent concerns

1. Reconfirm safeguarding controls

Before any escalation, confirm that proportionate safety controls are in place: restricted duties, additional sign-off, shadow shifts or task limitation.

2. Review evidence longitudinally

Look beyond isolated incidents. Analyse supervision notes, observation outcomes, audit results and incident trends over time. Identify patterns rather than one-off lapses.

3. Test role fit and system pressures

Consider whether the individual’s skills align with role complexity. Assess whether workload, staffing pressures or unclear care plans contribute to repeated gaps.

4. Escalate to formal stage with clear thresholds

If measurable improvement has not stabilised after defined support cycles, progression to formal capability stages may be required. Document rationale and evidence carefully.

Operational example 1: Recurrent medication documentation errors

Context: A domiciliary worker completes a structured PIP for MAR omissions. Initial improvement is seen, but errors reappear three months later.

Support approach: Senior review of all medication-related entries over six months identifies recurring pattern under time pressure.

Day-to-day delivery detail: Immediate restriction from unsupervised medication prompts is reinstated. Observation reveals task prioritisation breakdown during peak scheduling. Rota redesign trialled for two weeks, followed by reassessment. Despite system adjustments and repeat coaching, documentation inconsistencies persist.

Evidence of effectiveness or lack thereof: Audit data demonstrates recurrence despite structured support, supporting escalation decision to formal capability stage.

Operational example 2: Escalation judgement inconsistency in supported living

Context: A senior support worker repeatedly delays escalation during behavioural deterioration.

Support approach: Two cycles of supervision and observed shifts show temporary improvement.

Day-to-day delivery detail: Manager maps incident timelines across six months. Escalation checklists and rehearsal sessions implemented. Observation during high-risk periods still reveals hesitation and threshold confusion.

Evidence of effectiveness or lack thereof: Governance dashboard shows repeated near-miss escalation events linked to same staff member. Evidence supports decision to progress formal capability process while maintaining interim safeguards.

Operational example 3: Record quality relapse in residential care

Context: After initial improvement in daily notes, audit scores decline again within one quarter.

Support approach: Manager analyses supervision themes and workload patterns.

Day-to-day delivery detail: Staff member placed on structured four-week reassessment plan with weekly note sampling and one observed interaction per week. Despite clear feedback, inconsistency persists, especially on night shifts.

Evidence of effectiveness or lack thereof: Audit trend analysis shows repeated decline, and governance minutes record rationale for next-stage capability decision.

Commissioner expectation: proportionate, evidence-based escalation

Commissioner expectation: Commissioners expect providers to demonstrate that persistent performance concerns are managed decisively but fairly. They will look for evidence of structured support cycles, measurable data and proportionate risk controls before escalation.

Regulator / Inspector expectation: leadership accountability and protection from harm

Regulator / Inspector expectation (e.g. CQC): Inspectors expect leaders to protect people from ongoing risk. They will examine whether concerns were identified early, whether improvement efforts were genuine and structured, and whether final decisions were evidence-led and consistent.

Governance controls to support defensible decisions

• Longitudinal tracking of individual performance indicators.
• Senior leader review of repeated cases for consistency.
• Documented system checks to rule out organisational causes.
• Clear documentation of thresholds for formal progression.

Persistent underperformance must be addressed in a way that prioritises safety, fairness and transparency. When evidence demonstrates that structured support has not resulted in stable improvement, leaders can act confidently, knowing their decision is defensible and aligned to regulatory and commissioner expectations.

---