What should an SOP's handoff section specify regarding escalation?

• A. Who to contact and when to escalate if a handoff is delayed or incomplete.
• B. It should avoid any escalation to minimize complexity.
• C. It should specify only the receiving department.
• D. It should rely on informal verbal notices.

Answer: (A)

The key idea here is that escalation in an SOP handoff must be clearly defined: who to contact and when to escalate if a handoff is delayed or incomplete. This creates a predictable, auditable path that keeps work moving and prevents critical information from slipping through the cracks. By naming the specific on-call or responsible individuals and tying escalation to concrete triggers (for example, a delay beyond a defined SLA or missing data in the handoff), everyone knows exactly who has authority to intervene and how quickly action should be taken. It also supports accountability and continuity of operations, since there is a documented chain of responsibility and timelines to follow.

Choosing not to escalate, restricting escalation to just the receiving department, or relying on informal verbal notices all introduce ambiguity and risk. Without a clear escalation rule, delays can go unaddressed, information can be lost, and downstream teams may be left without guidance on next steps. That’s why specifying who to contact and when to escalate is the best approach.