Skills on AI

Active theme: Light

Medical SBAR Handoff

Use when asked to structure, write, or review an SBAR (Situation, Background, Assessment, Recommendation) clinical handoff — a single-patient communication such as nurse-to-physician or between shifts about one concerning patient — for general educational and structural guidance only, not medical advice; always follow institutional policy and consult the treating clinician or qualified health care professional for actual patient care decisions.

⚠️ Ask your doctor or health care professional. This information is AI generated for education and NOT medical advice.

SBAR (Situation, Background, Assessment, Recommendation) is a standardized structure for a single, focused clinical handoff communication — one clinician telling another about one patient, usually because something has changed or needs a decision. It's the format behind a nurse calling a physician about a deteriorating patient, or one clinician briefing a covering colleague about a specific concern.

The four parts

  • Situation — what's happening right now, in one or two sentences: who the patient is, and the immediate reason for the call. This comes first, before any history, so the receiving clinician immediately knows why the call is happening.
  • Background — the relevant context needed to make sense of the situation: diagnosis, relevant history, why this patient is being discussed today, current treatment. Only what's relevant to this call, not the full chart.
  • Assessment — the reporting clinician's own clinical read of the situation, not a restatement of the background. This is the "here's what I think is going on" part, drawing on what they've observed.
  • Recommendation — what the reporting clinician thinks should happen, or what they're specifically asking for: a bedside review, an order, a transfer, an escalation. Stated plainly enough that the receiving clinician knows exactly what's being requested.

Why Situation comes first

Under time pressure, the receiving clinician needs the urgent point immediately, not after a chronological history. Leading with Situation front-loads the thing that matters most for the decision at hand; Background is then available for whoever needs it, rather than something the listener has to sit through before reaching the point. A handoff that opens with "he was admitted three days ago for..." forces the listener to hold unprocessed detail while waiting to find out why they're being called.

Using SBAR well

Keep Situation to what's changed or what's needed right now — resist the pull to open with history. Include only Background that actually informs this specific call. Make sure Assessment adds the reporting clinician's own interpretation, not just a longer version of Background — this is often the most skipped part, and it's the part that carries the clinician's clinical judgment. Always end with an explicit Recommendation, even a tentative one ("I'd like you to come see her" or "can we get an order for X") — an SBAR without one leaves the ask implicit.

When SBAR is used

SBAR fits any moment where one clinician needs to hand a specific concern to another quickly: a phone call to an on-call physician about a change in a patient's condition, a bedside handover between colleagues covering for a break, or a structured page or message when a face-to-face conversation isn't immediately possible. It is short by design — built for the two or three minutes a busy receiving clinician actually has, not for a full case presentation.

Preparing before the call

Gather the key facts before initiating contact: current vitals or the specific finding prompting the call, the relevant background, a settled view on the assessment, and a clear idea of the recommendation before dialing or approaching the receiving clinician. A clinician who starts the call still assembling their own thinking tends to default to a long narrative, which undercuts the entire point of the structure.

Documenting an SBAR call

Many institutions expect the SBAR call itself, or its outcome, to be documented afterward — what was reported, what was recommended, and what the receiving clinician decided or ordered. This closes the loop: it creates a record that the concern was escalated and shows what response it produced, which matters if the patient's condition is questioned or reviewed later. Documentation after the call should mirror the same four parts rather than reverting to free-text narrative.

Common pitfalls

  • Starting with a long narrative history instead of the situation — the urgent point arrives too late, after the listener has already had to process unrelated context.
  • An assessment that's just a restatement of the background — no actual clinical read is added, so the receiving clinician gets facts but not judgment.
  • No clear recommendation stated — the receiving clinician is left to guess what's actually being asked of them, which slows or muddles the response.
  • Background padded with irrelevant chart detail — burying the one or two facts that matter under everything else in the record.
  • Treating SBAR as a script to read verbatim rather than a structure to think through — a rigid recitation can lose the urgency it's meant to convey.

Learn more

View medical-sbar-handoff/SKILL.md on GitHub