It is 2 a.m. and you are a new nurse dialing the on-call provider about a patient who worries you. You have thirty seconds of their attention, they have never met your patient, and somewhere in the vitals, the history, and the vague sense that something is wrong, there is a message that must land. Most clinicians remember the first time they fumbled that call. Many remember the provider's silence afterward.
These moments matter more than almost any technical skill. The Joint Commission has long identified communication breakdown as a leading root cause of sentinel events, the serious, preventable harms that every hospital works to eliminate. Information that one clinician held and another needed simply failed to cross the gap, and a patient paid for it.
SBAR exists to close that gap. This guide walks through each letter with strong and weak phrasings, a fully worked escalation call, how the tool changes between handoffs and urgent calls, and the mistakes that quietly undo it.
Clinical communication fails for a structural reason, not a personal one. Nursing and medicine train their members to communicate differently: nurses are taught to report broadly and narratively, providers are trained to want the headline, the relevant background, and a decision point. Add fatigue, hierarchy, time pressure, and a phone line, and two competent professionals can finish a conversation having exchanged almost nothing that mattered.
A structured format fixes this the way checklists fix procedural omissions. It decides in advance what information travels and in what order, so that under stress the speaker does not have to compose a message and manage their anxiety at the same time. The listener benefits equally: when every escalation call arrives in the same shape, missing pieces become audible.
SBAR stands for Situation, Background, Assessment, Recommendation. It was not invented in a hospital. The format was adapted from communication protocols used aboard US Navy nuclear submarines, environments where hierarchical crews must transmit critical information quickly and without ambiguity. Clinicians and safety leaders at Kaiser Permanente adapted it for healthcare in the early 2000s, and it spread rapidly because it solved a problem every unit recognized.
It now sits inside the mainstream of US patient safety teaching. SBAR is taught as a core communication tool within TeamSTEPPS, the teamwork and safety curriculum developed by the Agency for Healthcare Research and Quality with the Department of Defense, and the Institute for Healthcare Improvement has long promoted it as a standard handoff and escalation structure. That institutional weight is worth knowing when you use it: you are not following a local habit, you are using a tool your organization is likely already committed to.
The genius of SBAR is its shape: it moves from the present (what is happening) to the past (what led here) to interpretation (what I think) to the future (what I need). That arc matches how a decision-maker naturally absorbs a case, which is why a good SBAR call feels effortless to receive.
Identify yourself, your unit, the patient, and the problem in one or two sentences. The situation statement is a headline, not a story. It should let the listener triage the call within ten seconds.
Strong: "This is Maria on 4 West. I'm calling about Mr. Alvarez in 412. His oxygen saturation has dropped to 88 percent on room air and he's newly short of breath." Weak: "Hi, sorry to bother you, it's the med-surg floor. So, Mr. Alvarez, he came in a few days ago, and his daughter mentioned he seemed a little off tonight." The weak version buries the reason for the call and forces the listener to dig for it.
Give only the history that bears on tonight's problem: admitting diagnosis, relevant comorbidities, pertinent medications, code status if it matters, and the most recent baseline for comparison. Background is where most calls bloat. The discipline is ruthless relevance: the listener needs the two facts that change their thinking, not the whole chart read aloud.
Strong: "He's day two post-op from a hip replacement, history of heart failure, and he was satting 95 on room air at midnight." Weak: a five-minute chronological retelling of the admission, which trains the listener to stop listening precisely when the critical detail finally arrives.
Say what you think is going on. This is the letter nurses skip most, usually from a fear of being wrong, and it is the one providers most need. You are not being asked to diagnose; you are being asked for your clinical read as the person standing at the bedside.
Strong: "I think he may be developing a pulmonary problem. Given the surgery, I'm worried about a clot." Also strong, and fully legitimate: "I'm not sure what's going on, but he has changed significantly in the last hour and I'm concerned." Naming your concern out loud is the assessment; certainty is not required.
Say what you want to happen and when. A call without a request leaves the next step to be guessed, and guessed next steps are where escalations stall. Be concrete: come and evaluate, order imaging, adjust a medication, transfer to a higher level of care. Then close the loop by asking the question that protects you for the next hour: "What would you like me to watch for, and at what point should I call you back?"
Here is the whole tool assembled, in the form we teach and rehearse in our communication courses.
"Dr. Chen, this is James, RN on 4 West. Situation: I'm calling about Mrs. Okafor in 408. Her heart rate has climbed from the 80s to 118 over the past three hours and her blood pressure is now 92 over 58, down from her baseline of around 130 systolic. Background: she's a 67-year-old admitted yesterday with community-acquired pneumonia, on IV antibiotics since admission. She has type 2 diabetes. She was alert and stable on evening rounds. Assessment: she's warm, her respiratory rate is up to 24, and she's more drowsy than an hour ago. I'm concerned she may be becoming septic. Recommendation: I'd like you to come and evaluate her now, and I'd like to draw a lactate and blood cultures before you arrive. Do you want anything else while I wait, and if her pressure drops below 90, what's the plan?"
Notice what that call accomplishes in under a minute: the provider knows who is calling and why, has the two background facts that matter, has heard a specific clinical concern spoken plainly, and has been handed a concrete plan to approve or amend. There is nothing to decode.
The same four letters serve two different jobs. In an escalation call, SBAR is a spotlight: one problem, tightly framed, ending in a request. In a shift handoff, SBAR is a frame for transferring the whole picture: the situation is the patient's current status, the background is the story of the stay, the assessment covers what is trending in each active problem, and the recommendation becomes the plan and the watch-list for the oncoming nurse.
Handoffs fail differently than escalations. Escalations fail by burying the concern; handoffs fail by omission and interruption, the detail that never got said because a call bell rang mid-sentence. That is why high-reliability units protect handoff time and pair the spoken SBAR with a written or printed structure the receiver can check against.
Knowing the format and producing it at 2 a.m. with a deteriorating patient are different skills, and only rehearsal converts one into the other. Three methods work reliably.
First, script before you dial. For non-emergent calls, take ninety seconds to jot the four letters on paper before picking up the phone. A downloadable version of the exact worksheet we use in class is free on our SBAR template page. Second, narrate routine information in SBAR shape even when nothing is wrong: give your charge nurse a two-line SBAR about an uneventful patient. Format fluency built on calm cases is what survives stressful ones. Third, rehearse the hard calls in simulation, where an educator can play the impatient provider, the dismissive response, and the clarifying question, and then debrief exactly where your message thinned out. Structured communication under pressure is a core thread in our clinical training programs for both students and practicing staff.
Burying the concern is the classic failure: the real worry finally appears in minute three, after the listener has mentally filed the call as routine. Lead with it. If you are worried, the word "worried" belongs in your first two sentences.
Skipping the recommendation is nearly as common. A call that ends with "so, I just wanted to let you know" transfers information but not momentum; nothing is now scheduled to happen. Always end with a request and a callback threshold.
Apologizing for calling is the quietest mistake. "Sorry to bother you" frames clinically necessary escalation as an imposition and teaches you, call after call, to hesitate. You are not interrupting the provider's work; the deteriorating patient is the provider's work. Finally, resist padding the background to sound thorough. Irrelevant detail is not neutral; it dilutes the two facts that matter and burns the attention you need for your assessment.
Is SBAR only for nurses calling providers? No. It works in any direction information must travel: shift handoffs, transfers between units, calls to rapid response, reports to charge nurses, even communication with families when structured clearly. Any situation where one person holds a picture another person needs is SBAR territory.
What if the provider interrupts before I finish? Answer the question asked, then return to the structure: "To give you the quick background..." Interruptions are usually the listener hunting for information the format would have delivered anyway. As your first ten seconds get sharper, interruptions become rarer.
What if I do not know what I think is wrong? Say exactly that. "I can't put my finger on it, but she has changed in the last hour and I'm concerned" is a strong assessment. Experienced clinicians treat a bedside nurse's explicit worry as meaningful data, and structured escalation systems are built to honor it.
Should I write the SBAR down before calling? For any non-emergent call, yes. Ninety seconds of scripting produces a faster, calmer call and prevents the post-call realization that you forgot the most important detail. In true emergencies, the practiced format carries you without notes, which is precisely why practice matters.
Reading about SBAR builds understanding; rehearsing it against realistic pressure builds the reflex. Wahero Health Institute teaches structured communication inside our clinical courses and simulation scenarios, for nursing students, new graduates, and experienced teams alike. Start with the free SBAR template, then bring the practice to your program or facility.
Educational content only
This material is published by Wahero Health Institute for professional education and is not individual medical advice, a care protocol, or a substitute for clinical judgment. Always follow your facility's policies, your state's nurse practice act, and your own scope of practice, and confirm medication doses against a current authoritative reference before administration. See our Terms of Use.
