Complex care leaders often say they have “tiers,” yet day-to-day delivery looks the same for everyone: variable contact frequency, inconsistent escalation, and no clear exit criteria. That is not an acuity pathway; it is a caseload list. A real acuity pathway converts risk into time-bound service intensity—who does what, how often, with what escalation triggers—so the program can deliver safe care at scale and prove it is targeting resources where they matter most.
To ground this work within your broader operating model, start with Risk Stratification, Triage & Acuity Pathways and then align the pathway design to Complex Care Service Design & Delivery Models. This guide focuses on the mechanics: step-up rules, step-down rules, escalation workflows, and the governance checks that keep pathways consistent across teams and sites.
What an acuity pathway must control (or it’s not a pathway)
At minimum, an acuity pathway must control four operational levers: (1) contact frequency and modality (phone, virtual, home, clinic); (2) role intensity (RN, behavioral specialist, care coordinator, peer support); (3) required reviews (clinical supervision cadence, case conference frequency, medication review triggers); and (4) escalation and safety protocols (who is on-call, what constitutes urgent response, when to involve partners). If those levers are not explicitly tied to acuity tiers, the system will default to individual preference rather than risk-based delivery.
Building blocks for step-up and step-down logic
Define the “stability indicators” that justify step-down
Complex care cannot step down safely unless “stability” is observable. Providers typically define a small set of stability indicators tied to the person’s risk profile: days since last ED visit, medication reconciliation completed and maintained, symptom stability (condition-specific), adherence signals, housing stability, caregiver reliability, and behavioral incident frequency. Step-down should be conditional: stability must be sustained for a defined period, and the plan must specify what will be monitored after intensity decreases.
Define the “deterioration signals” that trigger step-up
Step-up triggers must be specific and operational: missed critical appointments, repeated medication discrepancies, acute symptom changes, new safeguarding concerns, rising crisis contacts, or caregiver breakdown. A common governance mistake is vague triggers (“worsening condition”) that leave staff unsure when escalation is required. Step-up works best when triggers are linked to a response package: same-day clinical review, increased visit frequency, partner coordination, and time-limited higher-intensity support.
Oversight expectations you need to design for
Expectation 1: Right service, right intensity, right time (resource stewardship)
Commissioners and health system partners will expect acuity pathways to demonstrate resource stewardship: higher intensity is reserved for those with higher risk and time-sensitive need, and intensity reduces when stability is achieved. Operationally, that means pathway rules must be reflected in staffing models, scheduling patterns, and documented decisions. If your program cannot show that intensity is adjusted based on risk and outcomes, it will be challenged as inefficient or clinically unsafe.
Expectation 2: Standardization with controlled clinical judgment
Oversight bodies generally accept that clinical judgment matters, but they expect it to be used within a controlled framework. That means pathway overrides should be permitted only with clear documentation (what trigger is being treated as exceptional, what alternative intensity is being used, and when it will be reviewed). Consistency is a safety feature: it protects people from variability and protects staff from blame when decisions are challenged after an adverse event.
Operational Example 1: Step-up pathway after repeated missed home visits and “could not locate” events
What happens in day-to-day delivery
When a person misses a scheduled home visit, the frontline worker records the missed contact in the case record and triggers a same-day “missed contact protocol.” The protocol includes: immediate phone outreach, a second attempt by an alternate staff member, and a supervisor notification if the person remains unreachable. If two “could not locate” events occur within a defined window, the case automatically steps up: the care coordinator schedules a joint visit with a clinician or supervisor, checks safety risks (food, heat, medication access), and coordinates with relevant partners (housing staff, caregiver, primary care) per consent. The step-up decision and revised contact plan are documented with a time-bound review date.
Why the practice exists (failure mode it addresses)
Repeated missed contacts are a common precursor to deterioration, medication lapse, eviction risk, or safeguarding issues—especially in complex care where needs are high and stability is fragile. The practice exists to prevent “silent disengagement,” where a person becomes unreachable and the system assumes low need until a crisis occurs.
What goes wrong if it is absent
Without a step-up rule, missed contacts are treated as administrative noise. The case drifts with sporadic outreach attempts, and the first clear signal of risk becomes an ED admission, a police call, or a safeguarding referral. Staff are then criticized for “not escalating,” but there is no pathway rule to point to. The program’s reliability suffers because it cannot demonstrate it responds predictably to early warning signals.
What observable outcome it produces
Evidence includes reduced time-to-reengagement after missed contacts, fewer crisis presentations following disengagement, and audit trails showing that missed-contact thresholds consistently triggered step-up actions. Programs can also track the proportion of missed contacts resolved within 24–72 hours and correlate improvements with reduced unplanned utilization and safeguarding incidents.
Operational Example 2: Tiered medication safety pathway for polypharmacy and high-risk transitions
What happens in day-to-day delivery
At intake and after any hospital discharge, the pathway requires a medication safety sequence: a same-week reconciliation (preferably within 72 hours), confirmation of the current regimen with prescribers/pharmacy as needed, and a structured “teach-back” with the person and caregiver. High-risk flags (e.g., anticoagulants, insulin, sedatives, multiple prescribers) automatically place the case on a higher-intensity medication monitoring sub-pathway, which includes a second check-in, symptom monitoring prompts, and a documented plan for who to call if side effects appear. Clinical supervision reviews a sample of these cases monthly to confirm adherence to the sequence.
Why the practice exists (failure mode it addresses)
Medication harm often occurs because information changes during transitions and does not reconcile across prescribers, discharge paperwork, and what the person actually takes at home. The pathway exists to prevent adverse drug events, duplicate prescribing, and avoidable readmissions by ensuring medication changes are verified and understood quickly after risk peaks.
What goes wrong if it is absent
Without a tiered medication pathway, staff may rely on outdated lists, miss discontinuations, or fail to identify interactions. The person may resume old meds, double-dose, or stop critical therapy due to confusion. These failures present as falls, hypoglycemia, bleeding events, delirium, or symptom destabilization—often leading to repeat ED use. Oversight review then finds inconsistent documentation and an inability to show that medication risks were proactively managed.
What observable outcome it produces
Programs can evidence impact through reconciliation completion rates within target timeframes, reduced medication discrepancy rates on audit, fewer medication-related incidents, and lower 7–30 day readmissions for high-risk transition cohorts. The pathway should also produce clearer documentation: what changed, who confirmed it, what education was provided, and what monitoring was put in place.
Operational Example 3: Step-down with an “exit ramp” plan and rapid re-entry triggers
What happens in day-to-day delivery
When stability indicators are sustained, the case enters a step-down review. The team documents the stability evidence (e.g., no ED in 60 days, symptom stability, resolved housing risk), reduces contact frequency in a planned way, and creates an “exit ramp” plan that lists ongoing supports, who owns each part, and what the person should do if problems return. Crucially, the plan includes rapid re-entry triggers (specific events that automatically step the person back up) and a named contact pathway so re-entry does not require a fresh referral. The program schedules a light-touch check-in after step-down to confirm stability is holding.
Why the practice exists (failure mode it addresses)
Step-down is where programs often fail: intensity reduces without a plan, and people bounce back into crisis because early warning signs were not monitored and re-entry is bureaucratic. The practice exists to prevent “cliff-edge discharge,” preserve gains, and ensure the program can flex intensity up and down without delay.
What goes wrong if it is absent
Without an exit ramp and re-entry triggers, step-down becomes abandonment from the person’s perspective. When risk rises again, the person returns to the ED or re-enters services through a fragmented route, often repeating assessments and losing time. The provider also loses the ability to demonstrate that step-down decisions were safe, because there is no recorded logic tying stability evidence to reduced intensity and no plan describing how risk would be detected early.
What observable outcome it produces
Evidence includes sustained stability post step-down (lower bounce-back to ED, fewer crisis contacts), documented exit plans on audit, and measurable re-entry timeliness when triggers occur. Programs can track the proportion of step-down cases requiring step-up within 30–90 days and use that data to refine stability indicators and monitoring processes.
Governance checks that keep pathways real
To prevent pathways drifting into “nice documents,” leadership teams typically implement: (1) a monthly pathway adherence audit (did contact frequency match tier; were triggers documented and acted on); (2) supervision prompts tied to pathways (what tier is this person in and why; what would trigger step-up); and (3) capacity review aligned to tier distribution (do we have the right mix of roles for the acuity profile). These checks turn pathway design into operational reality.
Acuity pathways are ultimately a promise: the program will match intensity to risk in a way that is timely, consistent, and measurable. When step-up and step-down are operationalized with clear triggers and audit discipline, complex care becomes safer for the person, safer for staff, and easier to defend to funders who want proof that resources are being used where they deliver the greatest stability impact.