SBAR Handoff Communication: Worked Scripts and the Failure Modes It Prevents

A physician who receives a call about a deteriorating patient needs three things fast: what is happening, enough context to place it, and what the caller wants done about it. Most bad handoff calls fail on exactly those three points — the nurse leads with a symptom instead of a bottom line, buries the one lab value that actually matters halfway through a paragraph, or never says out loud what they want the physician to do next. SBAR (Situation, Background, Assessment, Recommendation) is a fixed four-part structure built to stop that failure pattern, and it is now the default handoff format taught in most US hospital nursing orientation and used across nurse-to-physician escalation calls and shift-to-shift handoffs.

This page is written for patient-safety officers, quality directors, risk managers, and infection preventionists who own handoff-communication policy, training, and audit — not for a specific clinical decision at the bedside. The scripts below are illustrative teaching examples with generic placeholder names, not transcripts of a real call; no institution, date, or outcome is attributed to any real event. The Joint Commission’s own accreditation-manual wording for its handoff-communication requirement could not be independently verified for this page — jointcommission.org blocks automated retrieval and no archived snapshot was available — so the requirement is described at the level AHRQ’s independently reviewed Patient Safety Network primer confirms; verify the exact current standard number against your organisation’s live accreditation manual before citing it in policy.

What SBAR Stands For, Component by Component

SBAR is not a form to fill in after the fact — it is a talking order, meant to be said out loud (or typed into a page/chat message) in that sequence, every time, so the receiver always knows where to listen for what.

• Situation. One or two sentences: who the patient is, where they are, and the one-line reason for the call. This is the bottom line up front — the receiver should be able to triage urgency from this sentence alone, before hearing any detail.
• Background. The context the receiver needs to interpret the situation correctly: admitting diagnosis, relevant history, current treatment, and what has changed. Background is scoped tightly to what is relevant to the current concern, not a full chart summary.
• Assessment. The caller’s own clinical read of what is going on — vital signs and trend, exam findings, what has been tried, and the caller’s working interpretation. This is the step callers most often skip, defaulting to “I don’t know, that’s why I’m calling” — but SBAR asks for a best-guess assessment specifically because it forces the caller to synthesize the data rather than just relay it.
• Recommendation. What the caller wants: a specific order, a bedside evaluation, a change in monitoring frequency, or an explicit statement that they are not sure what is needed but believe the situation needs another set of eyes. A call that ends without a stated recommendation forces the receiver to guess what action closes the loop, which is exactly the ambiguity SBAR exists to remove.

Where the Structure Comes From

SBAR did not originate in nursing theory. It was adapted for healthcare in the early 2000s — most widely credited to work inside Kaiser Permanente — from structured briefing formats already used in aviation and military crew communication, where a fixed reporting order had already been shown to reduce ambiguity in high-consequence, time-pressured exchanges between people of different rank. The underlying insight carries over directly to a nurse calling a physician at 2 a.m.: a rigid structure is most valuable precisely when the exchange is rushed, the participants don’t know each other well, and one party may hesitate to be blunt with someone senior to them.

Worked Example: A Nurse-to-Physician Escalation Call

The scenario: a nurse on a medical-surgical floor is calling the covering physician about a post-operative patient with new-onset tachycardia and dropping blood pressure. Names are generic placeholders; this is a teaching script, not a real transcript.

Situation: “Dr. Reyes, this is Jordan, the nurse for Mr. Alvarez in Room 412. I’m calling because his heart rate has climbed to 128 and his systolic blood pressure has dropped to 84, down from 122 an hour ago.”

Background: “He’s post-op day one from a bowel resection. He’s on a PCA for pain and has been afebrile until now — his temperature just came back at 38.6°C. His last hemoglobin eight hours ago was 10.2.”

Assessment: “He looks pale and diaphoretic, his abdomen is more distended than it was on my last check, and the surgical dressing has a moderate amount of new sanguineous drainage. I’m concerned about active bleeding or early sepsis — this doesn’t look like routine post-op pain or a PCA effect to me.”

Recommendation: “I’d like you to come see him now, and I think we need a stat CBC and lactate, and I want to know if you want a fluid bolus started while we wait for you.”

Notice what the structure forced: a bottom-line vital-sign change stated first (so the physician can triage urgency in one sentence), a scoped set of relevant history rather than the whole chart, an explicit interpretation instead of a raw data dump, and a concrete ask that tells the physician exactly what closes the loop — come now, order these tests, decide on the bolus.

Worked Example: A Nurse-to-Nurse Shift Handoff

The scenario: an oncoming night-shift nurse is receiving handoff on a stable patient from the outgoing day-shift nurse, at the bedside.

Situation: “This is Ms. Chen in 208, day three post-op from a total knee replacement, currently stable, going home tomorrow if physical therapy clears her this evening.”

Background: “She’s on standard post-op pain management, oral now, and her incision looked clean and dry on my last dressing check at 1400. History of well-controlled type 2 diabetes — her blood sugars have been in range all shift on her home regimen.”

Assessment: “She’s tolerating oral pain meds well, pain is a 3 out of 10 at rest, ambulating with a walker without difficulty, and there’s nothing on my mind for tonight other than getting her physical-therapy clearance documented before the morning team rounds.”

Recommendation: “Nothing urgent — just watch for the PT note tonight, and if her pain climbs above what the current regimen covers, the order set has a step-up option before you need to call anyone.”

This handoff is deliberately low-drama, and that is the point: SBAR is not only for emergencies. Applied consistently to routine handoffs, it keeps the receiving nurse from having to ask a string of follow-up questions to reconstruct context the outgoing nurse already had in her head — the single biggest source of dropped information at shift change is exactly that gap between what the outgoing clinician knows and what they actually said.

The Failure Modes SBAR Is Built to Prevent

SBAR’s fixed order exists because unstructured handoffs fail in a small number of predictable ways. Naming them is more useful for policy and training than reciting the mnemonic, because these are the failure modes an audit tool or a training session should actually be checking for.

• Omitted critical information. Without a required structure, a caller under time pressure tends to relay whatever is top of mind rather than working through a checklist, and the item that gets dropped is disproportionately the one that would have changed the receiver’s decision — a trending vital sign, a recent medication change, an allergy. The Background and Assessment steps exist specifically to force a caller past their first impulse and through the context a receiver needs.
• Ambiguous urgency. A rambling, chronologically-ordered account (“so first I noticed this, then I checked that, then I thought maybe…”) leaves the receiver to infer how urgent the call actually is from tone and pacing rather than from an explicit statement. Leading with Situation as a one-line bottom-line is the direct countermeasure: the receiver knows within one sentence whether this is a call to act on now or a routine update.
• The buried recommendation. Many handoff failures are not failures of information transfer at all — the receiver heard everything relevant, but the call ended without either party stating what should happen next, and the ask silently defaulted to whichever party was less certain. Recommendation exists because “I told you the numbers” is not the same as “I told you what I want you to do,” and only the second one reliably produces action.
• Hierarchy-related reluctance to speak up. This is the failure mode SBAR inherited most directly from its aviation and military origins: a junior team member who has real safety-relevant information can hesitate to state it plainly to someone senior, particularly a direct recommendation (“I think this needs to be seen now”). A fixed structure that explicitly requires a recommendation from whoever is calling — regardless of seniority — gives that person institutional cover to say the blunt thing the structure asked for, rather than leaving it to individual assertiveness in the moment.

What the Evidence Actually Shows

SBAR’s evidence base is more mixed than the mnemonic’s ubiquity suggests, and a patient-safety officer building a business case for a rollout should represent it accurately rather than overstate it. AHRQ’s Patient Safety Network describes the research on SBAR used on its own as showing mixed results — the tool has not reliably demonstrated, by itself, a measurable reduction in handoff-related harm across studies. Where SBAR does show a stronger, more consistent effect is when it is bundled with other safety interventions — structured training, standardized escalation pathways, and organizational reinforcement — rather than deployed as a laminated card with no supporting program around it.

By contrast, I-PASS (Illness severity, Patient summary, Action list, Situation awareness and contingency plans, Synthesis by receiver) — a competing structured-handoff mnemonic built specifically for physician-to-physician shift signout — has a stronger evidence base behind it: a seminal multi-site study across pediatric teaching hospitals found that implementing the I-PASS bundle markedly reduced the incidence of preventable adverse events associated with handoffs, and it is now widely regarded as the reference standard for physician-to-physician signout, with proven effectiveness extending into nursing handoffs, cancer care, and pediatric emergency settings as well. That is a genuinely useful data point for a rollout decision: don’t market SBAR internally as evidence-proven in isolation, and don’t assume a laminated card alone will move an outcome metric — the effect shows up when the tool is one part of a trained, monitored program.

The Joint Commission Handoff Requirement — What It Actually Says

The Joint Commission has required a standardized approach to hand-off communication since 2006, when it first appeared as a National Patient Safety Goal (see National Patient Safety Goals: What They Cover, and Why the Term Just Changed for Hospitals for how that chapter has since evolved). The requirement, at the level independently confirmed by AHRQ’s Patient Safety Network, is that an organisation’s hand-off communication process provides the opportunity for the giver and receiver of patient information to discuss it — with elements the standard recommends including, such as an illness-severity assessment, a patient summary, action items, and contingency plans, preferably delivered face-to-face.

The requirement is a process standard, not a named-tool mandate. The Joint Commission does not require SBAR by name, and does not require I-PASS by name either — it requires a standardized, two-way process with specific informational elements, and SBAR, I-PASS, and other structured formats are all accepted ways of satisfying it. This matters for policy language: writing “our hand-off process complies with the Joint Commission’s SBAR requirement” overstates what the standard actually says. The accurate framing is that SBAR is the tool your organisation has chosen to satisfy a requirement that does not name it.

SBAR vs I-PASS: When Each Fits Better

Both are structured-handoff mnemonics; they are not competing claims about the same use case, and a program does not have to pick exactly one for every context.

• SBAR fits best for cross-role, cross-discipline, often one-off exchanges — a nurse calling a covering physician, a nurse escalating to a rapid response team (see Rapid Response Team Activation Criteria), a technician reporting a critical value to a clinician. Its strength is compactness and generality: four steps, usable by any role calling any other role, with no assumption that both parties share a common training background in the tool.
• I-PASS fits best for scheduled, same-discipline shift-to-shift signout — physician-to-physician handoff at end of shift being the setting the strongest evidence covers, though it has since been adapted to nursing and other same-discipline handoffs too. Its five elements are built for a more complete transfer of an entire patient list or care plan, which a one-line escalation call does not need and would slow down.

A hospital that already runs SBAR-based escalation calls does not need to abandon that in order to also adopt I-PASS for physician sign-out rounds; they are solving different handoff problems and can coexist in the same policy without contradiction.

Implementing and Auditing an SBAR Program

For the patient-safety officer or quality director actually standing up or maintaining an SBAR program, the tool itself is the easy part; the parts that determine whether it changes behavior are training, embedding, and audit.

• Train the recommendation, not just the mnemonic. New-hire orientation reliably teaches staff to recite “Situation, Background, Assessment, Recommendation,” but the step most often skipped in practice is Recommendation — staff report data and stop, particularly across a real or perceived hierarchy gap. Scenario-based training that specifically rehearses stating a recommendation to a senior clinician, including practice pushing back if the first response dismisses the concern, addresses the actual failure mode rather than just the recall of the acronym.
• Embed the structure in the tools people already use. A laminated SBAR card at the nurses’ station is weaker than an EHR communication note template, a secure-messaging quick-text, or a rapid-response-activation form that is pre-structured into the four fields — because a structural default changes behavior more reliably than a poster asking staff to remember a format under pressure.
• Audit for content, not just documentation. A checkbox confirming “SBAR used” in a chart audit tells you nothing about whether the Recommendation step actually happened, or whether it was clear enough for the receiver to act on. A useful audit samples real calls or documented handoffs against the specific failure modes above — was urgency stated in the first sentence, was there an explicit ask — rather than only confirming the four-letter structure was followed in name.
• Feed handoff-related events back into review. Where a sentinel event or near-miss involves a handoff, the root cause analysis should specifically examine which SBAR component, if any, was skipped or under-specified — that is the most direct way a program learns whether its handoff tool is actually working under real conditions rather than only in training scenarios. Findings and any resulting corrective action can be routed through your organisation’s Patient Safety Organization reporting pathway where applicable, preserving the work-product protection that encourages candid review.

Frequently Asked Questions

What does SBAR stand for?

Situation, Background, Assessment, Recommendation — a fixed four-part order for a clinical handoff communication, meant to be delivered in that sequence every time.

Is SBAR required by the Joint Commission?

No, not by name. The Joint Commission has required a standardized hand-off communication process since 2006, with specific recommended elements, but it does not mandate SBAR (or any other named tool) specifically — SBAR is one accepted way to satisfy that requirement.

Is SBAR or I-PASS the better choice for our hospital?

They solve different problems rather than competing for the same one. SBAR is built for compact, cross-role exchanges — a nurse calling a physician, an escalation to a rapid response team. I-PASS is built for more complete same-discipline shift-to-shift signout, most established for physician-to-physician handoff, and carries a stronger evidence base for reducing preventable adverse events in that specific setting. Many organisations run both, matched to context.

Does SBAR alone reduce medical errors?

The evidence is mixed when SBAR is evaluated as a standalone intervention. Its effect is more consistently positive when it is bundled with structured training, a defined escalation pathway, and organisational reinforcement rather than introduced as a reference card with no supporting program.

Can SBAR be used for a family member or patient reporting a concern?

SBAR was designed for clinician-to-clinician handoff, but its underlying logic — state the bottom line first, give relevant context, say what you think is happening, say what you want done — has been adapted by some programs into simplified family-activation scripts for escalating a concern about a deteriorating loved one, sometimes alongside a rapid-response family-activation pathway. Treat that as a distinct, simplified adaptation rather than the same clinical tool used unchanged.