Managing Transitions in Mental Health Care: Case Management at Points of Highest Risk

February 19, 2026

Transitions are the pressure points of mental health pathways. People can move between crisis teams, inpatient units, community services, housing support and primary care in a matter of days, with risk rising when responsibility is unclear. Strong care coordination and continuity depends on how reliably services manage handovers, follow-up and escalation, not on how well they perform in steady-state. This needs to align with wider service models and care pathways so that responsibilities and thresholds are consistent across interfaces. This article sets out practical case management controls for transitions, including real-world delivery examples and the assurance evidence commissioners and inspectors expect.

Why transitions drive harm

Harm during transitions usually comes from predictable failure modes:

Ambiguous ownership: each service assumes another is “holding the risk”.
Time gaps: discharge happens quickly, follow-up happens slowly.
Information loss: risk history, triggers and protective factors do not transfer.
Threshold mismatch: teams apply different criteria for escalation or acceptance.
Safeguarding drift: referrals are made but outcomes are not tracked into the plan.

Transition management has to control these risks through disciplined processes that are simple enough to use every day.

The transition bundle: what “good” looks like operationally

A transition bundle is a short set of mandatory actions that must happen for certain high-risk moves (e.g., crisis step-down, inpatient discharge, service transfer, end-of-support). A practical bundle includes:

Named accountable coordinator confirmed for the next stage of care.
Risk formulation refresh (what has changed, what is stable, what needs monitoring).
Medication and physical health check (where relevant) and safety planning.
Contact plan (first contact booked, method, contingency if not achieved).
Escalation and safeguarding status transferred and tracked.
Multi-agency confirmation for complex cases (housing, substance misuse, LD/autism, domestic abuse, etc.).

Crucially, bundles need a mechanism for exceptions: if something cannot be completed, the service must document mitigations and managerial sign-off.

Operational example 1: crisis step-down with a 72-hour follow-up control

Context: A provider notices recurring incidents and emergency presentations within two weeks of crisis service discharge. Notes show referrals were “made” but follow-up is inconsistent, especially across weekends.

Support approach: Introduce a step-down protocol that requires a confirmed first community contact within 72 hours, with escalation if missed.

Day-to-day delivery detail: Before discharge, the coordinator books the first contact slot (phone or in-person depending on risk) and records it in the handover summary. If contact does not occur, staff must attempt re-contact the same day and record outcome. After 72 hours without successful contact, the case is automatically escalated to the duty manager, who decides on welfare checks, partner escalation, or re-referral to crisis support. The person’s safety plan is updated to reflect reality (who will respond, how fast, and what triggers escalation).

How effectiveness or change is evidenced: The service reports: proportion of step-downs with contact achieved within 72 hours, reasons for exceptions, actions taken, and incident rate within 14 days. Governance uses trend data to adjust rota coverage and threshold clarity.

Managing threshold mismatches across services

Threshold mismatches often create “ping-pong” between teams: a referral bounces because the receiving service reads risk or eligibility differently. Case management should include:

Referral quality checks: are the presenting risks, history, and current supports clearly stated?
Pre-acceptance contact: brief call with the receiving team to agree immediate risks and first contact plan.
Documented interim responsibility: who holds risk until acceptance is confirmed.

This is not bureaucracy; it is the mechanism that prevents people being “in limbo” while risks escalate.

Commissioner expectation: safe, time-bound transitions with accountability

Commissioner expectation: Commissioners commonly expect providers to evidence that transitions are designed, monitored and improved. They will look for:

Defined transition standards (follow-up windows, handover content, escalation rules).
Named accountability at each interface and evidence of shared working.
Performance reporting segmented by risk and pathway type.
Clear mitigation when standards cannot be met (e.g., weekend coverage, contingency planning).

Regulator / Inspector expectation: risks are understood, communicated and acted upon

Regulator / Inspector expectation (CQC): Inspectors will test whether staff understand transitional risks and can show:

Risk assessments and safety plans were updated at key points.
People and carers were involved and understand who to contact.
Safeguarding actions and outcomes fed back into ongoing support.
Leaders have oversight and learn from incidents linked to transitions.

Operational example 2: inpatient discharge into the community with a “handover proof” requirement

Context: A person is discharged from inpatient care with complex needs, but community teams do not receive a complete handover. The first appointment is missed, and risk deteriorates quickly.

Support approach: Implement a “handover proof” checklist before the case is accepted as transferred.

Day-to-day delivery detail: The receiving coordinator confirms: discharge summary received, current medication regime understood, recent risks and triggers documented, safeguarding status known, and first contact booked with an agreed contingency. If discharge documentation is incomplete, the coordinator escalates to the ward/discharge team and logs the interim risk management plan. A manager reviews any discharge where proof is not achieved within 24 hours.

How effectiveness or change is evidenced: Audit sampling demonstrates improved handover completeness, reduced missed first contacts, and fewer early post-discharge escalations. Incident reviews are used to refine the checklist and strengthen partner escalation routes.

Safeguarding and restrictive practices during transitions

Transitions can increase restrictive practice risk (e.g., unplanned police involvement, inappropriate use of exclusionary thresholds, unsafe accommodation placements). Services should ensure:

Safeguarding referrals are tracked to outcome and reflected in risk plans.
Any restrictive practice is reviewed, proportionality tested, and alternatives documented.
Multi-agency plans include clear escalation when safeguarding risk rises.

Operational example 3: transferring between community teams without losing relational continuity

Context: A person moves from an intensive community support team to a longer-term team. Engagement is fragile and linked to trust with a single worker.

Support approach: Use “overlap working” to maintain relational continuity for a defined period.

Day-to-day delivery detail: The current worker and new worker complete two joint contacts (one planning, one community-based) to transfer rapport and align the plan. The first month includes a pre-agreed contact frequency with a named escalation route. Supervisors review progress at weeks two and four to ensure contact happened and the plan remains appropriate.

How effectiveness or change is evidenced: The service measures engagement retention (contact achieved), unplanned crises, and service user feedback about understanding who is responsible. Results are reviewed at governance to determine whether overlap working reduces DNAs and escalation.

Assurance: what to measure so you can prove control

Follow-up achieved within agreed windows after transition (by risk level).
Handover completeness (sample audit against checklist).
Exceptions logged with mitigation and managerial oversight.
Incidents within 14 and 30 days of transition (trend and themes).

When these measures are embedded, transitions become controlled processes rather than hopeful handoffs.