Patient Hand-Off (SBAR)
Patient Hand-Off (SBAR) is a shift-change and transfer SOP for passing patient information using Situation, Background, Assessment, and Recommendation. It helps reduce missed details, confirm closed-loop understanding, and document exceptions before care changes hands.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Hospitals · Ambulatory Care · Long Term Care · Behavioral Health
Overview
Patient Hand-Off (SBAR) is a standard operating procedure for transferring patient responsibility in a structured, repeatable way. It covers the exact sequence of a safe hand-off: verify the trigger and patient identity, state the current situation, summarize relevant background, report the current assessment, give clear recommendations, confirm closed-loop understanding, and document the exchange with escalation if needed.
Use this template when a shift changes, a patient moves between units, or care passes to a different provider and the receiving role needs enough context to act without rework. It is especially useful when the patient is unstable, has pending tests or treatments, or has a known deviation from the expected plan. The SBAR format keeps the conversation focused on what matters now, while still preserving the background that explains why the current situation matters.
Do not use this template as a substitute for clinical judgment, a full transfer summary, or emergency escalation when immediate intervention is needed. If the patient is in crisis, the hand-off should be shortened to urgent facts and escalation should happen first. It is also not the right tool for casual updates that do not change responsibility. The value of this SOP is that it makes the hand-off auditable, consistent, and easier to verify under pressure.
Standards & compliance context
- This template supports Joint Commission-style standardized hand-off practices by reducing omissions and confirming transfer of responsibility.
- It aligns with ISO 9001:2015 documented information expectations by creating a consistent record of what was communicated and by whom.
- It supports patient safety controls commonly used in clinical quality programs, including identity verification, escalation, and closed-loop communication.
- If your facility uses EHR sign-out, transfer forms, or secure messaging, the documented hand-off should match the spoken SBAR content.
- Local policies, scope-of-practice rules, and unit-specific escalation pathways still govern who may hand off, accept, or escalate care.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns the hand-off into a repeatable sequence with clear ownership, verification, and escalation points.
- Verify the hand-off trigger and patient identity
-
State the current situation
The outgoing role states the immediate reason for hand-off, current patient status, and any urgent concerns. Include the current location, active issues, and what requires attention next.
-
Summarize relevant background
The outgoing role provides concise background information that affects current care. Include diagnosis, pertinent history, recent procedures, allergies, isolation status, code status, and other relevant events. Exclude non-essential details.
-
Report the current assessment
The outgoing role communicates the latest assessment findings, vital trends, pain status, lines or drains, mobility limits, pending results, and any deviations from expected condition. State objective observations and current clinical concerns.
-
Give clear recommendations
The outgoing role states the next actions, monitoring priorities, time-sensitive tasks, escalation criteria, and any follow-up needed. Identify what must happen next and who to contact if the condition changes.
-
Confirm closed-loop understanding
The receiving role repeats back critical information, clarifies any ambiguity, and confirms responsibility for the patient. Resolve discrepancies before ending the hand-off.
-
Document the hand-off and escalate exceptions
The outgoing role documents the hand-off completion, key SBAR points, and any outstanding tasks in the approved record. If information is missing, the patient is unstable, or a safety concern exists, escalate to the charge nurse, supervisor, or responsible provider immediately.
How to use this template
- 1. The sender verifies the hand-off trigger, confirms the patient identity using approved identifiers, and checks that the receiving role is ready to accept the transfer.
- 2. The sender states the current situation in one or two sentences, including the reason for the hand-off and any immediate safety concern.
- 3. The sender summarizes relevant background, including diagnosis, recent events, active treatments, allergies, isolation status, and any recent deviation from the plan.
- 4. The sender reports the current assessment, including vital trends, key findings, pending results, and the level of concern that should guide next actions.
- 5. The sender gives clear recommendations, naming the next step, the expected timing, and any escalation threshold or contingency plan.
- 6. The receiver repeats back the critical points, asks clarifying questions, and the sender documents the hand-off and escalates unresolved exceptions.
Best practices
- Use the same SBAR order every time so the receiver can find each element without guessing.
- Keep the situation statement brief and specific to the reason the hand-off is happening now.
- Include only background that changes the next decision; avoid reciting the full chart.
- State the assessment with objective findings, trend changes, and any deviation from baseline.
- Make the recommendation actionable by naming the next step, owner, and timing.
- Require closed-loop readback for high-risk items such as critical labs, isolation precautions, and pending procedures.
- Document unresolved questions, missing data, or refusal to accept the hand-off as a non-conformance for follow-up.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should this SBAR hand-off template be used?
Use it for shift change, unit-to-unit transfer, provider-to-provider transfer, and any hand-off where responsibility for patient care changes. It is also useful when a patient’s condition changes and the receiving role needs a structured update. If the exchange is routine but clinically important, this template keeps the same sequence every time. If no patient responsibility is changing, a full SBAR hand-off is usually unnecessary.
Who should complete the hand-off?
The sending role should complete the hand-off because that person owns the most current information and can explain recent changes. The receiving role should listen, ask clarifying questions, and confirm understanding before accepting responsibility. In many settings, a charge nurse, primary nurse, resident, or attending may also participate depending on the transfer. The template works best when the roles are assigned before the exchange starts.
How often should SBAR hand-offs happen?
They should happen every time care responsibility changes, not only at the end of a shift. Many teams also use them for escalation calls, transfers to higher acuity care, and discharge-related provider updates. The key is consistency: if the hand-off affects safety, it should be structured. Ad hoc updates can supplement SBAR, but they should not replace it.
Does this template support Joint Commission expectations?
Yes, it is aligned with standardized hand-off practices commonly used to support patient safety goals. It helps teams reduce omissions, verify patient identity, and create a repeatable record of what was communicated. It also supports documentation discipline expected under quality management systems. Local policy and facility-specific hand-off rules should still govern final use.
What are the most common mistakes with SBAR hand-offs?
The most common mistakes are skipping patient verification, giving too much background and not enough current assessment, and leaving the recommendation vague. Another frequent issue is failing to confirm that the receiving role understood the critical points. Teams also miss escalation when the patient is unstable or when the hand-off reveals a deviation from the expected plan. This template is designed to make those gaps visible.
Can this template be customized for different units or specialties?
Yes. You can tailor the background and assessment prompts for ICU, med-surg, emergency, perioperative, pediatrics, or behavioral health without changing the SBAR structure. Many teams add unit-specific cues such as isolation status, lines and drains, pain control, or pending labs. The core sequence should stay the same so the receiving role always knows where to find each type of information.
How does this compare with informal verbal hand-offs?
Informal hand-offs are faster but more likely to omit critical details, especially under time pressure or interruptions. SBAR creates a predictable order that helps the sender cover the same essential points every time. It also makes it easier for the receiver to spot missing information and request clarification. For high-risk transitions, the structured version is safer than memory-based conversation.
Can this be integrated with EHR workflows or hand-off tools?
Yes. The template can be paired with EHR sign-out fields, shift notes, transfer forms, or secure messaging workflows. Many teams use it as the verbal script and then document the same content in the chart or hand-off module. If your system supports checklists or required fields, this template maps cleanly to those controls. The main goal is to keep the spoken hand-off and the documented hand-off consistent.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Choose the best screen capture software with ease-of-use, editing, and sharing features that boost productivity and fit your workflow.
-
Improve client communication with four proven strategies to reduce miscommunication, speed responses, and build client confidence.
-
Learn how task management and real-time collaboration tools create an efficient business workflow — keeping teams connected, accountable, and productive.
Ready to use this template?
Get started with MangoApps and use Patient Hand-Off (SBAR) with your team — pricing built for small business.
