Use SBAR (Situation, Background, Assessment, Recommendation) for handoff communications — structured context transfer prevents information loss

Why This Is a Rule

Handoffs are where information dies. The person transferring responsibility has a rich mental model of the work — what's been done, why certain choices were made, what risks exist, what they'd recommend next. Unstructured handoffs transmit a fraction of this model: "Here's where things stand, let me know if you have questions." The recipient doesn't know what questions to ask because they don't know what they don't know. Critical context evaporates.

SBAR (Situation, Background, Assessment, Recommendation) was developed in healthcare — specifically the US Navy's nuclear submarine program and later adapted for hospital nursing handoffs — precisely because handoff failures in those contexts cause deaths. The four-part structure forces the handoff to include not just current state but also context, judgment, and proposed action. Situation: What's happening right now? (Current state of the work.) Background: What led to this point? (Decisions made, constraints encountered, history that matters.) Assessment: What do I think about this? (Risks, concerns, interpretation of the current state.) Recommendation: What should happen next? (Proposed action, priorities, things to watch for.)

The structure works because it externalizes the four layers of understanding that experts hold implicitly: facts (S), context (B), judgment (A), and action implications (R). Without the structure, handoffs default to facts only — "here's the current status" — losing the three layers that actually enable the recipient to make good decisions.

When This Fires

• When transferring responsibility for work to another person (colleague, contractor, successor)
• When handing off to your future self after a break (vacation, context switch, end of day)
• When escalating an issue to someone with decision authority
• When documenting the state of an ongoing project for team visibility

Common Failure Mode

Status-only handoffs: "The project is at stage 3, the client sent feedback yesterday, the deadline is Friday." This covers Situation but omits Background (why is it at stage 3? Were there setbacks?), Assessment (is Friday realistic? What are the risks?), and Recommendation (what should the recipient prioritize? What should they avoid?). The recipient has facts without context, which is only marginally better than no handoff at all.

The Protocol

(1) When handing off work, structure your communication in four parts: S — Situation: "The [work item] is currently [state]. [Key facts about current status]." B — Background: "We got here because [relevant history]. Key decisions were [choices and reasons]. Constraints include [limitations]." A — Assessment: "I believe [interpretation]. The main risk is [risk]. I'm [confident/concerned] about [aspect]." R — Recommendation: "I recommend [next action]. Watch for [potential issue]. Priority is [what matters most]." (2) Include all four parts even when some seem obvious — what's obvious to you is often not obvious to the recipient. (3) For self-handoffs (end-of-day notes, pre-vacation documentation), write SBAR as if you'll have zero memory of the context when you return. (4) Keep each section concise: 2-3 sentences maximum. SBAR is a structure for completeness, not a license for verbosity.