When the first call doesn't answer, everyone already knows the next one
A patient dies at home at 3 a.m. A nurse is threatened on a visit. The on-call physician doesn't pick up. In each case someone has to decide who to call next — and that decision should have been made months ago, not in the moment. Care Roster gives every situation a named escalation path: ordered steps, the right number on each one, two people called at the same time where that's what the policy says, and a clear next step when nobody answers. It's on every clinician's phone, and it prints.
- No patient data required
- Call two people at once when policy says so
- Unlimited users, one flat price
The decision made in advance, not at 3 a.m.
Most agencies already have escalation policy. It lives in a binder, in a laminated sheet at the nurses' station, and in the memory of whoever has been there longest. Care Roster turns it into something a clinician can actually follow on a phone, in the dark, under pressure.
A named path for each situation
Each path gets a short title and a description of exactly when it applies — a death requiring notification, a staff safety incident, an after-hours medication problem. A clinician opens the Emergency page, finds the situation in front of them, and follows it. Nobody is left deciding whether this counts as the kind of thing you wake the medical director for, because the path says so in its own description.
Two calls at once, when the situation needs it
A step is a group, not a single person. Some incidents genuinely require reaching two roles simultaneously — the clinical supervisor and the on-call coordinator, security and the administrator on call. Put both in the same step and Care Roster labels it plainly: Call these first — at the same time. The path only advances when nobody in that step answers, so a flat list can never be misread as a sequence.
Not every step is a phone number
Sometimes the next escalation is a person's own supervisor, and there is no single number to print. Add a Direct Supervisor step and Care Roster shows it as Default — no number on file rather than inventing a contact. The instruction stays unambiguous — every employee knows who their supervisor is — without pretending the system holds a number it doesn't have.
Numbers that can't go stale
A step points at a contact record or an on-call rotation, never at a copied-out number. Update a physician's after-hours cell once and every path referencing it is correct immediately. Point a step at a rotation and it resolves to whoever is genuinely on call at the moment of the call — not whoever was on call the day the policy was written. This is the difference between a living path and a laminated one.
Anatomy of an escalation path
Take a staff safety incident — a clinician threatened during a home visit. Here is how that path is written once and followed every time.
1 · The title and when to use it
"Staff safety incident" with a description naming the trigger: a clinician feels unsafe, is threatened, or is involved in an incident during a visit. The description is what stops a path from being applied to the wrong situation, and it is the first thing a clinician reads.
2 · The first step, called together
Two targets in step one, reached at the same time — the on-call clinical supervisor and the administrator on call. Each shows its own name and a tap-to-call number. A step can hold as many people as the policy requires.
3 · The instruction attached to the step
A step can carry a short note that appears with it — "call 911 first if there is immediate danger," or "do not return to the residence." Notes render as a highlighted instruction rather than fine print, because during an incident the instruction matters as much as the number.
4 · The steps that follow
Step two, step three, and so on — each one reached only when the previous step goes unanswered. A later step can be a rotation, a named contact, or Direct Supervisor. The path ends where your policy ends, and a clinician can always see how far it goes before they start.
The old way vs. the Care Roster way
A binder page and institutional memory Problem
- The escalation policy is in a binder nobody carries on a visit
- A flat printed list reads as sequential even when two calls should be simultaneous
- Numbers on the sheet were correct the day it was laminated
- "Call the supervisor" means a different number for every employee
- New staff learn the real escalation path by asking a colleague
The Care Roster way Solved
- Every path is on every clinician's phone, one tap from anywhere
- Simultaneous steps are labeled as such and can't be misread
- Numbers resolve from the live directory and the on-call rotation
- Direct Supervisor is an explicit step, not a guess
- New staff follow the same path as everyone else on day one
Hospice escalation paths, answered
What is an escalation path?
An escalation path is a named, ordered list of who to call for one specific situation — a death at home, a staff safety incident, an after-hours pharmacy problem. Each path has a short title, a description of when to use it, and numbered steps. Step one is called first; if nobody in step one answers, the person calling moves to step two. The point is that nobody has to decide who to call while something is going wrong: the decision was made in advance, written down once, and is on every staff member's phone.
Can one step call two people at the same time?
Yes. A step is a group, not a person. If a situation requires reaching the clinical supervisor and the on-call coordinator simultaneously, both go in step one and Care Roster labels it "Call these first — at the same time." The path only moves to step two when nobody in step one answers. This matters for incidents where two roles genuinely need to know at once, and it removes the ambiguity of a flat list where a reader assumes calls happen one after another.
What if the next person to call is someone's own supervisor?
Add a step named Direct Supervisor. It carries no phone number, and Care Roster shows it as "Default — no number on file" rather than inventing one. Every employee already knows who their supervisor is, so the instruction is unambiguous even though the number differs per person. This is how agencies handle the common case where the next escalation is organizational rather than a specific individual.
Who can create and change escalation paths?
Admins and editors create and edit paths. Viewer accounts can open them, read the steps, and tap to call — but cannot change them. That split matters because escalation paths are policy: the people who own the policy maintain it, and everyone else follows it without being able to alter it mid-incident. There is no per-user charge, so every clinician can hold a Viewer account.
Do the numbers in a path go stale?
No, because a step points at a contact record or an on-call rotation rather than storing a copy of the number. When a physician changes their after-hours cell, an editor updates that contact once and every escalation path referencing it reflects the new number immediately. A step can also point at an on-call rotation, in which case it always resolves to whoever is actually on call at the moment of the call — not whoever was on call when the path was written.
Can staff reach the paths without a signal or a login prompt?
Escalation paths live on the Emergency page, reachable in one tap from anywhere in Care Roster, and staff stay signed in on their own phones. Paths also print: an admin can produce a dated sheet to post at a nurses' station or keep in a glovebox, which is what most agencies do as the paper backup. The printed copy carries the same steps and numbers as the screen.
Write the path once. Follow it every time.
Start a free 45-day trial — build your escalation paths, point each step at a real contact or rotation, and put them on every clinician's phone. No credit card, no patient data, every feature included.