Governing service quality and safety · Lesson 2

Who decides and who escalates when a handoff fails?

6 min read

Lesson objectives

  • Apply who decides and who escalates when a handoff fails? to a service case with evidence and decision limits.
Reading tools

The previous lesson separated sending a task from its acknowledged receipt. An exception appearing in a queue, however, does not solve itself. On a busy day, the sender may assume the receiving department will follow up, the receiving department may assume the quality manager watches the dashboard, and the quality manager may view the matter as purely operational. This is a gap in decision rights, not simply in communication. A decision right is authority to choose a specified action within stated limits, coupled with responsibility to record and review the reason. Writing that everyone is responsible for safety describes a general duty but does not say who calls the receiving team about an unacknowledged request or who stops a change test that produces a side effect. A manager should distinguish three decision classes: responding to an individual case that may require clinical assessment, repairing daily workflow, and changing service-level policy or resources. Each class needs the appropriate authority, evidence, response interval and substitute when the usual person is absent.

A responsibility matrix can help if it is used to test a decision rather than decorate an organizational chart. For each step ask who performs the work, who is accountable for the decision and authorizes closure, whose expertise is sought first, and who needs to be informed afterward. These roles are often abbreviated as responsible, accountable, consulted and informed. Placing two accountable people on a single exception can stall the process when each waits for the other. The opposite mistake is making the quality manager the owner of every individual case merely because that manager maintains the performance display. The manager may have neither the clinical record nor authority to select treatment. Give one operational role ownership of exception closure, and make the on-duty substitute reachable. Keep a separate path to the qualified clinical team when an individual signal could indicate urgent harm. The administrative leader does not diagnose the case. The leader makes sure the referral channel is clear and used, and checks that its use is recorded.

Test the matrix against three situations before asking people to sign it. First, a routine exception turns out to be a synchronization delay: who documents the evidence, and who authorizes closure? Second, the receiving service does not respond within the locally agreed interval: where does the case go, by which channel, and who confirms that escalation was received? Third, an observation suggests possible urgent harm: can the employee contact the clinical team immediately without waiting for an administrative meeting? Repair the right, coverage or channel wherever this walkthrough stalls. Escalation is more than emailing a senior title. The receiver must know what action is expected and how a documented response returns to the case owner. Escalation also differs from resolution: an employee may correctly escalate early while the cause remains uncertain. Penalizing an early report because uncertainty persists makes silence easier than exposing a hazard.

Review decision rights whenever reality changes: departments merge, a night shift is added, an information system moves, or request volume rises. An undated matrix without a review owner may be more dangerous than none because it suggests confidence in people who no longer hold those roles. In a short monthly review, trace one exception that closed and one that stalled. Find out who acted and who was waiting. If escalation works but a sign-off that adds no information delays resolution, remove or delegate that approval within a documented limit. If closure is quick but does not establish receipt, require receipt evidence before closing. The leader ends with two practical questions. Can an on-duty employee identify the next step within minutes? Can a later reviewer understand why the decision was made from the case record? If either answer is no, the matrix has not yet become a reliable part of the service.

The decision record should contain more than names. For a material exception, capture detection time, signal source, checks performed, escalation recipient, response, and the reason for closure or continued monitoring. If a case exceeds someone's authority, record the explicit transfer of responsibility. This allows a later reviewer to reconstruct a decision and helps leaders locate recurring waiting points. It does not justify copying sensitive records into a public spreadsheet. Use the organization's approved system and access controls, recording only the information needed for the decision and its traceability.

Lesson summary

Apply who decides and who escalates when a handoff fails? to a service case with evidence and decision limits.