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

Continuity of care is often described in warm terms—“joined-up support”, “holistic planning”, “one team around the person”—but commissioners and inspectors increasingly expect providers to evidence continuity in a way that stands up to audit. This article sits within Care Coordination, Continuity & Case Management and should be read alongside Service Models & Care Pathways, because continuity measures only make sense when aligned to how pathways actually function.

Why continuity needs measurable indicators

In mental health support, drift is rarely obvious on day one. It shows up as missed reviews, poor follow-through on actions, unclear escalation, repeated crisis contacts, and “handovers” that are not really handovers at all. Without measurable indicators, providers can believe continuity is strong while the person experiences confusion, repeating their story, or falling between services.

Good measurement does not mean creating a complicated dashboard. It means selecting a small set of indicators that reflect what continuity looks like in practice, then using governance to act on what the data shows.

What to measure: practical continuity KPIs

1) Timeliness and reliability of key processes

• Review adherence: % of care plan reviews completed within the agreed timeframe (and reasons for exceptions)
• Post-transition contact: % of people receiving a planned contact within 48–72 hours after a step-down, discharge or placement change
• Action closure: % of multi-agency actions closed on time (with escalation for overdue actions)

2) Safety and escalation effectiveness

• Crisis recurrence: number of unplanned crisis presentations per person over 3–6 months (trend, not just count)
• Escalation responsiveness: time from identified risk escalation to documented decision/action
• Safeguarding linkage: % of safeguarding concerns where learning actions are captured and tracked to completion

3) Experience of continuity

• Story repetition indicator: short feedback prompt on whether the person had to repeat key information to new staff/services
• Understanding of the plan: whether the person (and carers where appropriate) can describe their goals and what happens if things worsen

Operational examples of continuity measurement in practice

Operational example 1: Proving continuity after crisis step-down

Context: A provider supports adults with severe mental illness who experience periods of crisis team involvement. The risk point is the week after crisis input ends.

Support approach: The service introduces a “step-down continuity bundle”: a structured plan, a time-limited increased contact schedule, and an escalation checklist.

Day-to-day delivery detail: Staff record step-down dates and the first planned follow-up contact window (48 hours). The manager runs a weekly report of anyone missing the follow-up window and reviews reasons in supervision. The same report flags whether relapse indicators were documented and whether the person has a named point of contact.

How effectiveness or change is evidenced: Over three months, the service demonstrates improved follow-up timeliness (e.g., moving from inconsistent practice to near-universal completion), and a reduction in unplanned crisis re-presentations. Audit notes show case managers escalated early when a person disengaged, rather than waiting for crisis.

Operational example 2: Multi-agency action tracking and closure

Context: A person is supported across housing, community mental health services, and a voluntary sector peer support provider. Actions are agreed but frequently not delivered.

Support approach: The provider introduces a shared action log for multi-agency reviews, with named owners and due dates.

Day-to-day delivery detail: The case manager updates the log weekly and flags overdue actions in a brief internal governance huddle. Where external actions are overdue, escalation is documented: reminder, manager-to-manager contact, and escalation to commissioning/contract routes where appropriate.

How effectiveness or change is evidenced: The provider evidences improved action completion rates and, crucially, an audit trail demonstrating that gaps were identified and escalated. Minutes show decision-making and responsibility were clear, rather than assumed.

Operational example 3: Using “near-miss” learning to strengthen continuity

Context: A near-miss occurs: a person is discharged from a short-term intervention service, but the receiving service does not contact them for several weeks. The person deteriorates but avoids admission.

Support approach: The provider treats continuity failures as learning events, not just individual performance issues.

Day-to-day delivery detail: The service completes a short learning review: what failed, what the early warning signs were, and what process changes are needed. A revised transition checklist is introduced, and managers add a “handover confirmed” field to transition documentation. Supervisors check compliance monthly.

How effectiveness or change is evidenced: Subsequent audits show fewer transition gaps and improved documentation of ownership during handovers. Governance records show learning actions are tracked, not simply noted.

Explicit expectations to design around

Commissioner expectation: measurable assurance and contract-relevant evidence

Commissioners typically want continuity evidence that links to risk reduction, outcomes and service stability. They expect providers to show how coordination is monitored, how gaps are identified, and what actions are taken when continuity risks emerge.

Regulator / Inspector expectation: oversight of risk and decision-making

Inspectors test whether providers can evidence safe management of risk, timely review, and learning from incidents. Continuity is often assessed through the audit trail: whether actions are followed through and whether the person’s support remains coherent during change.

Building continuity assurance into governance

Continuity KPIs only matter if they drive action. Providers typically embed assurance through:

• Monthly continuity audit: sample-based review of care coordination records and transitions
• Case file quality checks: focusing on escalation, action tracking and review timeliness
• Performance review meetings: reviewing trends and agreeing improvement actions
• Board reporting (where relevant): summarised continuity risk and learning themes

Keeping measurement meaningful (and not bureaucratic)

The goal is not to create a compliance burden. Good measures focus on the few points where continuity breaks: transitions, overdue actions, missed reviews, and delayed escalation. If teams can see the indicators and understand what they mean, measurement supports practice rather than replacing it.

---