Home care agencies are getting better at understanding what happens between visits. Passive sensing, family applications, and more disciplined caregiver notes mean more information is reaching the office than ever before.
But the bottleneck has moved. The challenge is no longer simply recognizing that something has changed. It is deciding what should happen in the hour after the office becomes aware of it.
A signal without a pathway does not improve care. It simply gives the coordinator one more thing to worry about.
Every between-visit signal needs three things: a named owner, a threshold that separates noise from meaningful change, and a next step that has already been agreed upon. This article explains how to build that pathway step by step and identifies the common mistakes that prevent it from working.
TL;DR: An escalation pathway is the agreed route a between-visit signal follows within a home care agency: who reviews it, what threshold makes it actionable, and which response comes next. That response might range from briefing a caregiver before the next visit to calling the family or moving a reassessment forward. The technology creates visibility; the pathway turns that visibility into a consistent care decision.
What Is an Escalation Pathway in Home Care?
An escalation pathway is a home care agency’s agreed process for turning a between-visit signal into an action. It defines who reviews the information, what makes the signal actionable, and which response should follow.
The pathway should be documented, owned by a named person, and applied consistently across the agency.
Most agencies already have the two ends of the process. Signals arrive constantly through caregiver notes, phone calls from family members, or changes surfaced by passive sensing, which is explored in [RED: link to Week 6 cornerstone - Reading the Room Without Watching It: How Passive Sensing Detects Change].
The possible actions also already exist. Coordinators brief caregivers, contact families, and move reassessments forward every week.
What is often missing is the middle: an agreed route between noticing and acting. Without it, every signal becomes a judgment call made under time pressure, and the response can depend on who happens to be at the desk.
The same report of several restless nights might prompt a same-day family call in March and little follow-up in July. The difference may have less to do with the client than with who received the information.
Consistency is an important part of what families expect when they hire an agency. It cannot depend entirely on improvisation.
An escalation pathway is a process, not a product. An agency can build one using the people, systems, and tools it already has.
Why Escalation Pathways Matter for Care Coordinators
The window between an early change and a significant incident can be meaningful. Research helps illustrate its potential importance. In a longitudinal study of older adults, the greatest decline in daily functioning occurred during the two weeks before hospital admission.
Two weeks may provide time to investigate or intervene, but only when the change is recognized and routed while it is still emerging.
The consequences of reacting too late are also well documented. About one in five Medicare beneficiaries discharged from hospital is readmitted within 30 days.
Once a client enters a cycle of hospitalization, discharge, and readmission, the agency reacts to events rather than getting ahead of them. Scheduled care planning alone may not close this gap. If a client’s condition changes meaningfully over two weeks, that change can develop well inside a standard reassessment cycle, as discussed in The 22 Hours You Don’t See: What Happens Between Caregiver Visits.[CS1]
An escalation pathway helps make the window usable. It allows emerging changes to be reviewed and acted upon while they are still current, rather than after an incident has occurred.
There is another reason coordinators need a pathway: it distributes the burden of uncertainty.
A coordinator who carries every judgment call alone can become overwhelmed by the accumulation of “maybes.” A documented pathway turns an individual concern into a team decision made in advance. It also gives the on-call coordinator established thresholds to follow instead of requiring them to make each decision from scratch.
For agency owners, the pathway can also strengthen trust. A written escalation standard answers a question many families quietly carry:
What happens when something changes and nobody is scheduled to be there?
How to Design a Daily Activity Monitoring Workflow With Escalation Steps
The workflow below assumes that the agency receives a daily signal from one or more sources, such as passive sensing insights, structured caregiver notes, family check-ins, or a combination of the three.
Five steps turn those signals into an escalation pathway.
The final process does not require new software. It can be documented on a single page that the entire team can access.
Step 1: Define the signals worth watching
Choose a short list of pattern changes that matter for the clients you agency support< Examples include:
- Restless nights
- Later-than-usual mornings
- Reduced movement around the home
- Less activity in the kitchen around mealtimes
A short list that everyone understands is more useful than a long list nobody remembers.
Step 2: Name one owner
Every client roster should have one person responsible for reviewing between-visit signals, typically, a care coordinator.
Shared ownership may sound collaborative, but it can easily become no ownership at all.
The owner is not expected to resolve every issue personally. Their responsibility is to ensure that every meaningful signal receives a decision.
Step 3: Set thresholds
Decide in advance what counts as ordinary variation and what warrants attention.
One unusual day may simply be documented and watched. The same change continuing for several days may justify a conversation or follow-up.
Effective thresholds serve two purposes. They protect the team from alert fatigue, and they protect clients from indefinite waiting.
Step 4: Map actions to tiers
Each threshold maps to a pre-agreed response.
Depending on the severity and persistence of the change, the response might include:
- Briefing the caregiver before the next visit
- Calling the family
- Moving a reassessment forward
- Escalating the concern to the director of care or another clinical lead
The coordinator should not have to invent the response in the moment.
For example, several restless nights might trigger a briefing for the next caregiver visit. If the restless nights are accompanied by reduced kitchen activity, the pathway might call for a family conversation that week.
Step 5: Close the loop
Every escalation should end with a documented outcome.
The record should capture:
- What signal was observed
- What action was taken
- How the family or caregiver responded
- Whether the care plan changed
Closing the loop turns isolated interventions into an agency capability. Reviewing outcomes over time helps the team determine whether its thresholds are appropriate or need to be adjusted.
Common Mistakes Agencies Make With Escalation Pathways
Four common failure points account for many ineffective pathways.
Escalating everything
If every variation triggers a response, the team eventually stops responding. Thresholds help ensure that escalation remains meaningful.
Failing to name an owner
A signal sent to the entire office can quickly become nobody’s responsibility. The pathway needs a named owner, not simply a distribution list.
Treating pathway as a software purchase
Technology can surface information, but it cannot create operational accountability on its own. The pathway is an agreement between people, and it succeeds only when the team understands and follows it.
Failing to close the loop
Without documented outcomes, the agency cannot determine whether its responses were effective. The team also loses the information it needs to refine its thresholds.
These are not primarily technology problems. All four can be addressed through clear decisions, assigned accountability, and a documented process.
How Caregiver Supports the Escalation Workflow
Caregiver by Cognitive supplies the signal at the beginning of the pathway.
Its whole-home Spatial Intelligence technology uses the Wi-Fi signals already present in a client’s home to learn that individual’s normal patterns and surface meaningful changes to the care team. It does this without cameras or microphones and without requiring the client to wear, charge, or operate a device.
This improves the information available to the escalation process. Instead of relying only on secondhand reports that may arrive days later, the coordinator can see pattern changes against the client’s own baseline while the change is still current.
Families can also access relevant information through their own view, helping create shared context before the coordinator calls.
The judgment remains with the care team. Caregiver does not decide what a restless week means, and it does not replace the agency’s thresholds, care expertise, or family conversations. It helps ensure that the pathway has timely information on which to act.
The system’s understanding of an individual’s normal routines also becomes more refined as it observes patterns over time. This gives coordinators a more personalized baseline against which to consider emerging changes.
What Changes When Every Signal Has a Pathway
The following tiers provide a practical starting point that agencies can adapt to their own policies and clients.
Watch
What triggers it: One unusual day against the client’s baseline
Pre-agreed response: Document it and continue monitoring
Who acts: Signal owner
Heads-up
What triggers it: The same change continues for several days
Pre-agreed response: Brief the caregiver on what to observe during the next visit
Who acts: Owner to caregiver
Family call
What triggers it: The change continues for a week, or two signals begin moving together
Pre-agreed response: Call the family with specific observations and ask whether anything else has changed
Who acts: Owner to family
Early reassessment
What triggers it: Sustained changes across multiple signals, or the family confirms a concern
Pre-agreed response: Move the reassessment forward and review the care plan or service hours
Who acts: Owner to director of care
The exact tiers will differ among agencies. What matters is that they are defined before the signal arrives.
A monthly review of the escalation log can keep the tiers useful. If nearly every signal remains at the Watch stage, the thresholds may be too loose. If nearly every signal jumps directly to a family call, they may be too sensitive, or the intermediate steps may need clarification.
When they do, the agency’s posture changes. The family hears from the agency first, the caregiver walks in knowing what to check, and reassessments track the client instead of the calendar.
The next article in this series examines which early warning signs are worth building thresholds around and how those signs may appear before a more serious incident.
Frequently Asked Questions
When should a care coordinator escalate a behaviour change?
A care coordinator should escalate a change when it persists beyond the agency’s agreed threshold. This might mean the same pattern appearing for several days or two related changes occurring together.
One unusual day may warrant documentation and continued observation rather than immediate escalation.
For a shorter explanation, see [RED: link to Week 7 answer piece - When Should a Care Coordinator Escalate a Behaviour Change?].
Who should own escalation decisions at a home care agency?
One named person should be responsible for each client or roster, usually a care coordinator or director of care.
Ownership can rotate with schedules, but at any given time, one person should know that reviewing and routing the signal is their responsibility. When decisions are left to a committee or a shared inbox, signals can expire before anyone acts.
What is the difference between an alert and an escalation?
An alert is information. It indicates that something crossed a defined line or that someone was notified.
An escalation is a decision. A person reviews the signal against an agreed threshold and initiates the appropriate response.
Technology can generate an alert, but escalation requires human judgment and accountability.
How do agencies avoid alert fatigue with activity monitoring?
Agencies can reduce alert fatigue by focusing on patterns rather than isolated events and by establishing thresholds in advance.
A workflow based on persistent change against each client’s own baseline should produce fewer, more meaningful signals. Fatigue develops when every variation is treated as urgent, eventually training the team to ignore all alerts.
What should be documented when a signal is escalated?
The record should include four things:
- The signal and the dates on which it occurred
- The action taken
- The response from the family or caregiver
- The outcome, including any resulting care plan changes
This documentation supports accountability and helps the agency refine its escalation thresholds over time.