Measuring Continuity in Mental Health Case Management: KPIs, Evidence and Assurance

Continuity in mental health case management is most often assessed after something goes wrong: a missed contact, a crisis escalation, a safeguarding incident, or a transition where no one was clearly accountable. To avoid learning only through failure, providers need measures that show whether care coordination and continuity is holding day to day, and whether performance remains reliable across different service models and care pathways. This article explains which continuity KPIs are operationally meaningful, how to audit what matters, and how to build assurance routines that commissioners and inspectors recognise as credible.

Why “activity metrics” do not prove continuity

High contact volumes or short waiting times do not automatically mean continuity is effective. Continuity is about what happens across time and across interfaces: whether the same plan is carried forward, whether risks are reassessed when circumstances change, whether exceptions trigger action, and whether responsibility is clear when services hand over. Good measurement therefore has to test reliability, not just throughput.

Define continuity in measurable terms

Most services benefit from a short internal definition translated into measures, such as:

• Contact reliability: planned contacts happen, and missed contacts trigger action.
• Plan stability: a current plan exists, is reviewed, and updates reflect risk changes.
• Escalation integrity: thresholds are used consistently and result in actions.
• Transition control: handovers are complete and follow-up occurs in time.

Once continuity is defined this way, you can choose KPIs that expose drift early.

Core KPI set: what to measure routinely

A practical continuity KPI set usually includes:

• Contact achieved rate: % of planned contacts completed within agreed windows (segmented by risk).
• Exception response time: time from missed contact to documented action/mitigation.
• Review currency: % of cases with reviews completed on schedule (and % overdue by risk level).
• Plan update quality: audit score for whether reviews capture “what changed” and “what is next”.
• Escalation timeliness: time from trigger to escalation decision (for defined triggers).
• Transition follow-up: % of transitions with first contact achieved within set window (e.g., 72 hours).

These measures work best when segmented: high-risk cohort, people with recent crises, people with safeguarding concerns, and those in transition between teams.

Operational example 1: KPI design for missed contacts that genuinely reduces risk

Context: A service has repeated incidents where people disengage after missed contacts, with risk escalating quietly. Staff record “DNA” but follow-up is inconsistent and depends on who is on shift.

Support approach: Implement a missed-contact standard with a measurable response KPI.

Day-to-day delivery detail: The service sets rules: if a planned contact is missed, staff attempt re-contact the same day, record outcome, and update the plan. If contact is not achieved within 24 hours (for defined risk levels), the case is escalated to the duty manager for a decision (welfare check, partner escalation, increased contact frequency, or crisis referral). The rota includes protected time for exception management, not just scheduled work.

How effectiveness or change is evidenced: The dashboard reports: missed contacts by cohort, % with same-day re-contact attempted, % escalated within 24 hours when required, and post-miss incident rates. Governance reviews exceptions to refine triggers and staffing coverage.

Audit methods: measure what records prove, not what staff say

KPIs tell you what is happening at scale. Audits tell you whether practice is defensible. Useful audit tools include:

• Case note sampling audit: does the record show decisions, follow-through and mitigation?
• Transition bundle audit: was handover complete, accountability confirmed, follow-up achieved?
• Escalation audit: were triggers recognised, escalation timely, and actions completed?

Audits should use a simple scoring rubric so that themes can be tracked over time.

Commissioner expectation: assurance that links continuity to outcomes

Commissioner expectation: Commissioners typically want to see that continuity is managed as a quality dimension, not left to individual heroics. They expect:

• Defined continuity standards (follow-up windows, review cycles, escalation thresholds).
• KPIs segmented by risk and pathway.
• Evidence that poor performance triggers improvement actions (staffing changes, training, pathway redesign).
• Outcome indicators linked to continuity (reduced crisis use, improved engagement stability, fewer safeguarding escalations linked to drift).

Regulator / Inspector expectation: governance demonstrates control and learning

Regulator / Inspector expectation (CQC): Inspectors will test whether governance is alive and whether leaders can demonstrate control. They will look for:

• Regular oversight of high-risk cases and exceptions.
• Audits that lead to supervision themes and improvement action.
• Evidence that risks are reassessed at transitions and after incidents.
• Learning from complaints, incidents and safeguarding processes reflected in practice.

Operational example 2: transition KPI pack that prevents post-discharge drift

Context: A service sees emergency presentations soon after discharge or crisis step-down. Reviews show follow-up is delayed and handovers inconsistent, especially across weekends and bank holidays.

Support approach: Introduce a transition KPI pack with a strict follow-up window and exception reporting.

Day-to-day delivery detail: For defined transitions, the coordinator books the first contact before the handover completes. If the person is not reached, staff must attempt re-contact and document mitigation. Any transition without first contact within the set window triggers escalation to the duty manager and is reviewed at the next risk huddle. The service also tracks “handover completeness” using a simple checklist.

How effectiveness or change is evidenced: The service monitors: % transitions with first contact within 72 hours, exception reasons, and incident rates within 14 days. Governance compares weekend vs weekday performance and adjusts rota coverage accordingly.

Assurance routines: how to keep continuity “on the radar”

Even good KPIs fail if nobody owns the response. Effective assurance routines include:

• Daily exception huddle: missed contacts, overdue reviews, open safeguarding actions, high-risk transitions.
• Weekly risk review: escalation cases, repeat crises, people with multiple service involvement.
• Monthly quality meeting: audit findings, themes, improvement actions, training needs.

Assurance should produce actions with owners and deadlines, not just discussions.

Operational example 3: measuring continuity through supervision and oversight

Context: The service is concerned about “drift” in long-running cases: plans are copied forward, risks are not revisited, and escalation happens late. Staff supervision varies by manager.

Support approach: Build continuity measures into supervision and management oversight.

Day-to-day delivery detail: Supervisors review a small number of cases each month against continuity prompts: what changed since last review, what risks increased, what actions were completed, what escalations occurred, and what is planned next. Managers track whether supervision reviews are happening and whether issues are resolved. Where recurring themes are identified (e.g., incomplete handovers), they are addressed via training and pathway changes.

How effectiveness or change is evidenced: Supervision sampling produces measurable improvement in record quality scores, earlier escalation, and reduced overdue reviews. Governance minutes evidence learning and improvements over time.

Making continuity measurement sustainable

The goal is not to create an overwhelming dashboard; it is to create a small set of measures that reliably detect risk drift and trigger action. If your KPIs are not changing behaviour, they are not the right KPIs. When measurement is aligned to daily workflows, continuity becomes a managed system rather than a variable dependent on staff capacity and memory.

---