A phone list tells you who works at your community. A call tree tells the person who just found a resident on the floor at 8:40 p.m. who to call first, who to call when that person does not pick up, how long to wait, and what to say. This is a fill-in-the-blanks call tree for independent living and assisted living communities. It fits on two printed pages, it is built on roles rather than names so it survives turnover, and it comes with the one rule that makes every call tree work: no message counts until someone confirms it.
Copy the tables into a document, fill them in, print them, and post them at the front desk, the med room and the maintenance office. Then test it, which is covered at the end.
The three jobs a call tree has to do
A call tree alerts the right people, gives each of them a job, and produces proof the message landed. Most call trees in senior living do the first job and skip the other two. They say “call Sarah” without saying why Sarah is being called, and they treat a voicemail as done. In an office that costs a delay. In a building where residents cannot log off and go home, it costs a fall that nobody assessed for forty minutes.
So the template below has three columns that most trees lack: what the person being called is expected to do, how long the caller waits before moving on, and who confirms to whom.
Step 1: Define the roles (not the names)
Names change monthly. Roles change rarely. Build the tree on roles and keep the names on a separate roster sheet that gets re-verified every month. Eight roles cover almost every IL/AL community.
| Role | Who fills it in your community | Their job in an emergency |
|---|---|---|
| First responder | Whoever finds the problem: caregiver, front desk, housekeeper, dining, driver | Make the resident or area safe, start the chain, give the five facts (below). Does not need permission to call 911. |
| Nurse / care lead | AL: nurse on duty or Wellness Director. IL: manager on duty (see IL note) | Owns clinical decisions: assess, call EMS, call the physician, decide on family notification. |
| Manager on call | Rotating department head | Bridge between the shift and leadership. Decides whether to widen the response, approve agency staff, call vendors. |
| Executive Director | ED or Administrator | Notified on defined triggers only. Owns decisions with regulatory, media, police or whole-building impact. |
| Maintenance lead | Maintenance Director, then tech or contracted vendor | Building systems: power, water, HVAC, doors, alarms, elevator. |
| Family communication lead | Nurse or ED for a resident event; ED for a building-wide event | The one voice to families. Nobody else calls the family. |
| Documentation owner | Usually the nurse or manager on call | Writes the incident timeline once the scene is stable. |
| Outside contacts | 911, poison control, utility, HVAC, plumbing, elevator, phone vendor, corporate/regional | Listed on the roster with account numbers. |
Independent living note. Many IL communities have no nurse in the chain. Do not leave that row blank. Write in who plays the care-lead role after hours (usually the manager on duty), state that they may call 911 and the resident’s emergency contact without waiting for anyone, and state your welfare-check procedure for a resident who does not answer the door. Your state’s rules for unlicensed IL and licensed AL differ, so confirm the IL version against them.
Step 2: Set the three emergency levels
Staff should not judge every event from scratch. Three levels decide how wide the alert goes.
| Level | Examples | How wide the tree goes |
|---|---|---|
| Level 1 – Handled on shift | Minor maintenance issue, routine resident change the nurse handles, a small schedule adjustment | First responder → the right lead. Document. Done. |
| Level 2 – Leadership should know tonight | Fall with injury, resident sent out, medication concern, staff no-show that drops coverage, building issue that limits service, family complaint tied to an incident | First responder → care lead or department lead → manager on call → ED notified (call or text, same night) |
| Level 3 – Whole-building response | Fire, evacuation or shelter-in-place, missing resident, major power loss, flood, severe weather, police on site, outbreak concern, phone system down | Full tree: ED, all department heads, family communication lead, vendors, corporate/regional, emergency partners |
The tie-breaker is written into the guide: when in doubt, it is the higher level. A manager would rather take an early call than learn in the morning that staff waited.
Step 3: The call tree template
One row per emergency type. Every row has a first action, a first call, a backup, a wait time, an escalation trigger, a family owner and a documentation owner. Fill in the four rows below and add your own (elevator entrapment, water shut-off, phone or internet outage, severe weather warning, resident death, suspected abuse report).
| Resident health emergency | Building / utility emergency | Staffing emergency | Missing resident | |
|---|---|---|---|---|
| First action | Stay with the resident. Do not move them unless trained and policy allows. Call 911 if any Level 1 sign (below). | Check resident safety in the affected area first. Keep residents seated and calm if lights or elevators are out. | Confirm who is actually on the floor. Identify the highest-risk uncovered area (secured unit, med pass, meals). | Start the search log: time last seen, clothing, where. Check the building and grounds per your elopement procedure. |
| First call | Nurse / care lead | Maintenance lead | Scheduler / shift lead | Manager on call and nurse / care lead at the same time |
| Wait before backup | 2 minutes | 5 minutes | 5 minutes | 2 minutes |
| Backup call | Wellness Director, then manager on call | Manager on call, then contracted vendor | Manager on call, then Wellness Director | Executive Director |
| Escalate to ED when | Resident sent out, 911 called, family concern likely, any injury | Heat, cooling, oxygen, elevators, food safety, alarms, doors or phones are affected | Coverage falls below your minimum for the shift, or agency is needed | Immediately, and police per your policy if not found within ______ minutes |
| Family update owner | Nurse or ED | ED (one message to all families if longer than ______ hours) | Usually none | ED, immediately |
| Documentation owner | Nurse | Maintenance lead | Scheduler | Manager on call |
| Next update to leadership | 15 minutes | 30 minutes | 30 minutes | 15 minutes |
Level 1 signs that mean 911 before anything else: unresponsive, chest pain, difficulty breathing, stroke signs (face drooping, arm weakness, slurred speech), uncontrolled bleeding, seizure, fall with head strike or obvious deformity, choking that back blows do not clear. Staff do not describe these to a nurse first. They call.
Step 4: The confirmation rule
This is the rule that separates a call tree from a phone list. Write it at the top of the printed page:
No message is complete until a person confirms it. If the person you called has not answered, replied or confirmed within the wait time on the tree, call the backup. Do not wait. Do not stop at voicemail.
Make confirmation a single word so it works by text: “CONFIRMED.” The caller’s line is “Please reply CONFIRMED within [wait time] or I’ll move to the backup.” The receiver’s job is to reply CONFIRMED and then say what they are doing. That one line gives new staff permission to skip a leader who is not answering, which is exactly the permission they will not take on their own.
Step 5: The scripts
Under pressure people tell the story out of order and leave out the location. Every emergency call carries five facts: what happened, where, who is affected, what has been done, what help is needed. Print these four scripts on the back of the call tree.
First call, any emergency
“This is [name] in [area]. We have [what happened] at [exact location]. [Resident name or area] is involved. So far we have [action taken]. 911 [has / has not] been called. We need [specific help] now. Please confirm.”
Resident health event to the nurse
“This is [name]. I’m with [resident] in [location]. [What changed or happened]. They are [awake / not awake], [breathing normally / not], [in pain / not]. I’ve [action]. We need you [now / for a phone assessment]. Please confirm.”
Describe signs, not diagnoses: “her speech is slurred” rather than “I think she had a stroke.”
Staffing gap to the scheduler or manager on call
“This is [name]. We’re short [number] [role] for [shift / area]. Highest-risk area is [area]. Current coverage is [brief status]. We need [role] by [time]. Please confirm and advise.”
“Memory care is short one caregiver from 7 to 11 p.m. and we need coverage before dinner support” is useful. “We’re short tonight” is not.
First family update (family communication lead only)
“Hello, this is [name] from [community]. I’m calling about [resident]. Earlier this evening [brief fact]. Our team is with them now and we’re following our care process. Right now [known status]. I’ll update you again by [time], or sooner if anything changes. What’s the best number for that?”
No guesses, no blame, no outcome promised, and always a next update time. Families who know when they will hear back do not call four staff members in the meantime.
Step 6: Leadership triggers, so the ED is not the first call for everything
Calling the most senior person first sounds safe and wastes time. If a pipe bursts, maintenance needs to know before the ED. If a resident has chest pain, EMS and the nurse come before any leadership update. The ED is notified when an event meets a trigger, not by default. Fill in yours; a reasonable default list is: 911 called, resident sent out, any injury, missing resident, police or fire on site, coverage below minimum, any building system failure affecting care, any event likely to generate a family complaint or a regulatory report.
Leadership updates stay short: what happened, what is being done, who is involved, what decision is needed, when the next update is. “I’ll update you again in 15 minutes” is the sentence that lets a leader stop asking questions.
Step 7: The roster sheet
This is the only page with names on it, which means it is the only page that goes stale. Assign one owner (usually the Business Office Manager or ED assistant) and put the verification date on it.
| Role | Primary (name / cell) | Backup (name / cell) | Verified (initials / date) |
|---|---|---|---|
| Nurse / care lead – days | |||
| Nurse / care lead – nights & weekends | |||
| Manager on call this week | |||
| Executive Director | |||
| Maintenance lead | |||
| Family communication lead | |||
| Scheduler | |||
| Regional / corporate | |||
| HVAC vendor (after-hours line, account #) | |||
| Plumbing vendor | |||
| Elevator service | |||
| Electric utility outage line | |||
| Phone / internet vendor | |||
| Non-emergency police | |||
| Poison control | 1-800-222-1222 |
Step 8: Test it before you need it
A call tree that has never been tested is a guess. Two tests, both cheap.
Tabletop, 20 minutes, quarterly. Read a scenario aloud and have staff answer: a resident falls in the hallway at 8:40 p.m., the nurse is with another resident and does not answer the first call, the manager on call is driving, and the daughter calls the front desk before anyone has updated her. Who makes the first call? How long do they wait? Who calls the daughter and what do they say? Who writes the note? If two people give two answers, the tree needs work.
Live contact test, 10 minutes, monthly. Send one message down the tree: “This is a call tree test for [community]. Please reply CONFIRMED within five minutes.” Do it on a night or weekend shift at least every other time, because that is where numbers are wrong, voicemail boxes are full and the backup no longer works here. Log who confirmed and how long it took, and fix the roster the same day.
Then keep it alive: a monthly roster check in the leadership huddle, an update the same day a leader leaves, a nurse starts, a vendor changes or the phone system changes, and a five-minute walkthrough for every new hire during their first week. Every staff member, including dining, housekeeping and drivers, should be able to answer one question: “If something serious happens on your shift, who do you call first?”
The four mistakes that put residents at risk
One person is the whole plan, and everyone waits for them. A twenty-name contact list instead of an ordered tree. No confirmation rule, so a voicemail counts as done. And nobody assigned to the family, so either three people call with three different stories or nobody calls at all. The template above closes each of those on purpose: role-based backups, one path per emergency type, CONFIRMED-or-continue, and a named family communication lead per row.
One more failure point is the phone itself. During a building-wide event the front desk line lights up with families and the person answering it is the same person trying to run the tree. JoyLiving’s AI receptionist answers those inbound calls, gives families the approved status message, and routes anything urgent to the right on-call person, so the humans in the building can work the emergency. You can see how it handles a real call in the videos at joyliving.ai.
Ana Avila is a writer who covers the day-to-day operations of senior living communities: how calls get answered, how resident requests get handled, how families stay informed, and how small teams keep up with all of it.
Her work for the JoyLiving Operator Library focuses on the practical side of running a community. She writes about front desk workflows, after-hours coverage, request tracking, check-in programs, family communication, staffing, and the places where AI tools can take repetitive work off a caregiver’s plate. Most of her articles come from the same starting point: a real problem an executive director or front desk lead is dealing with this week, and what has actually worked for other communities facing it.
Ana writes for people who are busy. Her guides are meant to be read in one sitting, put to use the same day, and shared with staff without translation. She avoids jargon, explains technology in plain terms, and is careful not to oversell what any tool, including AI, can do.
A consistent theme in her writing is that technology should support the relationships at the heart of senior living rather than replace them. The measure of a good system, in her view, is simple: does a resident get help faster, does a family member get a clearer answer, and does a caregiver get more time with the people they care for.
