Template
Use SBAR when the issue needs a decision now
The escalation should arrive with the problem already assembled.
When it fits
- A busy decision maker needs a concise escalation without reconstructing the entire history.
When to avoid it
- SBAR organizes communication; it does not turn an unverified assessment into a fact.
A template to use
Situation: [what is happening now]. Background: [minimum context]. Assessment: [working interpretation and uncertainty]. Request: [decision or action needed].
Why it matters
Lead with the current situation, then only the background needed to interpret it. State your assessment as a working judgment, including uncertainty, and finish with a concrete recommendation or request. This keeps facts, interpretation and desired action from blending into one long story.
An example
'Situation: mass update is creating blank texts. Background: reproducible after activation. Assessment: target text handling is implicated; root cause not confirmed. Request: approve a pause and debugging window.'
Check your result
The receiver can identify the current problem and the decision needed without asking what the message is actually requesting.
Keep this limit in mind
- SBAR organizes communication; it does not turn an unverified assessment into a fact.
Evidence and sources
AHRQ TeamSTEPPS uses SBAR to structure critical communication as situation, background, assessment and recommendation or request.
The structure improves organization but does not validate the sender's assessment or recommendation.
Tool: SBAR · SBAR framework