Crisis Escalation Pathways for Mental Health Clinics

A crisis escalation pathway is the clinic's agreed route from concern to action when a patient may be at urgent risk. It is written down so that anyone on shift can follow it.

It covers who is told, in what order and how quickly. It also sets out how decisions and actions are recorded.

The pathway does not tell clinicians how to assess risk. That remains a matter of clinical training, supervision and professional judgement.

A good pathway fits on one page and is easy to find, both on paper and in the system.

Clinics need a defined pathway because urgent situations leave no time to work out who should act. Without one, staff rely on memory and on whoever happens to be available.

Common gaps include an unclear on-call contact, supervisors learning about events days later and no record of follow-up. Each gap adds risk for patients and staff.

A defined pathway also supports staff wellbeing. People act with more confidence when they know what is expected and who will back them up.

A clear pathway also helps patients and families. They receive a consistent, timely response, whoever is on duty.

A crisis escalation pathway should include roles, contact routes, timeframes, documentation and follow-up. Your clinical leads should define and approve each element.

• Roles: who raises a concern, who responds and who supervises.
• Contact routes: in-hours and out-of-hours contacts, plus a named backup.
• Timeframes: how quickly each role must acknowledge and act.
• External links: how and when emergency services or other providers are contacted.
• Documentation: what is recorded, by whom and where.
• Follow-up: review appointments, safety plan updates where clinicians use them, and a staff debrief.

Build the pathway with your clinical team, test it in practice and then configure your systems to support it. The written pathway always comes first.

1. Map how urgent concerns are handled today, including out of hours.
2. Agree roles, timeframes and backups with clinical leads.
3. Write the pathway as a one-page flow any staff member can follow.
4. Configure your EHR to alert the right supervisor when a concern is recorded.
5. Run a tabletop exercise using a fictional scenario.
6. Train every role, including front-desk and virtual-care staff.
7. Review the pathway after each significant event and at least once a year.

The pathway should connect to day-to-day risk workflows. Read our guide to risk flags in mental health EHRs.

Clinics in Kenya should build pathways that reflect local emergency numbers, referral networks and staffing patterns. A pathway copied from another country may not work.

List local emergency contacts and nearby facilities that can receive urgent referrals. Check the details regularly, because contacts change.

Plan for virtual sessions too. Record the patient's location and a contact number at the start of each session, so staff can act if needed.

Records of crisis events are highly sensitive personal data under the Data Protection Act 2019, so restrict access and keep an audit trail. The Kenya Mental Health Act also shapes patient rights, so take legal advice.

Smaller clinics may share on-call cover with partner services. Write those arrangements down and test them, so responsibilities are clear before they are needed.

The pathway is working when concerns reach the right person quickly and every event has documented follow-up. Measure the process, not individual clinicians.

• Time from concern raised to supervisor acknowledgement.
• Events with a completed follow-up record.
• Debriefs held after significant events.
• Staff confidence in the pathway, gathered through short surveys.

Review these measures together as a team, in a supportive setting. The aim is learning and improvement, not blame.

Systems that support this kind of tracking are covered in our guide to what features a mental health EHR should include.

Who should own the crisis escalation pathway?

A senior clinical lead usually owns it, with support from operations. They approve changes, lead reviews and keep training current.

Should front-desk staff be trained on the pathway?

Yes. Front-desk and virtual-care staff are often the first to notice a concern. They need to know who to contact and what to record.

How often should the pathway be reviewed?

Review it after any significant event and at least once a year. Update contact details whenever staff or partner services change.

Can software replace a crisis pathway?

No. Software can route alerts, track actions and keep records. The pathway itself, and every clinical decision, belongs to the clinical team.

Have your clinical leads review any pathway before use. If someone is in immediate danger, contact emergency services. In Kenya, call 999, 112 or 911.

See how Tymira360 supports escalation alerts and follow-up tracking – Book a demo