SAFE — the communication framework built for uncertainty

SBAR is one of the most widely adopted communication frameworks in high-risk industries, and with good reason. It is structured, transferable, and effective at ensuring that a clear situation generates a clear communication. But there is a category of operational scenario for which SBAR is not quite the right tool: the ambiguous situation, where what is happening is not yet clear, where options are genuinely uncertain, and where the team needs a structure for thinking as much as for communicating. For those situations, SAFE offers something that SBAR does not.

SAFE — Situation, Awareness, Facts, Execute — originated in German-language healthcare as a clinical briefing tool, and its underlying logic is sound enough to transfer directly to any high-consequence operational environment. The framework's key structural contribution is a step that SBAR combines or omits: the explicit weighing of options before committing to a recommendation. Where SBAR moves from Assessment directly to Recommendation, SAFE pauses between Facts and Execute to ask: what could we do, what are the risks of each option, and which one makes the most sense given what we currently know?

SBAR is the right tool when you know what is happening and need to communicate it clearly. SAFE is the right tool when you are not yet sure what is happening and need to think and communicate simultaneously.

The four elements of SAFE

• Situation: what is happening right now, and why are we having this conversation? This may be a clear statement of a problem, or it may be an acknowledgement that something has changed in a way that is not yet fully understood.

• Awareness: what context matters? This is broader than background — it encompasses the environment, the team's current state, the plan versus the current reality, and any factors that shape how the situation should be interpreted.

• Facts: what do we actually know, objectively and observably? This step requires disciplined separation of facts from assumptions — what is confirmed, what is inferred, and what is genuinely unknown.

• Execute: what are we doing now? This is the committed action, stated clearly, confirmed by the team, and acted upon together.

The options step — SAFE's critical contribution

Between Facts and Execute sits the most important element: the explicit comparison of options. What could we do? What are the risks and benefits of each? What buys us time, margin, or safety? This step is what makes SAFE particularly suited to ambiguous situations. It prevents premature commitment to a course of action by requiring the team to articulate alternatives before choosing. In fast-moving situations, this feels like it takes time that is not available. In reality, the two or three minutes spent comparing options explicitly is the difference between a decision made under pressure with full situational awareness and a decision made under pressure with plan continuation bias already operating.

When to use SAFE versus SBAR

Use SBAR when the situation is clear and the primary need is structured, unambiguous communication to someone who needs to act on it. Use SAFE when the situation is ambiguous, when options are genuinely uncertain, or when the team needs to think together before acting. The two frameworks are complementary: a SAFE conversation that reaches Execute can be communicated upward or outward using SBAR. Used together, they cover the full spectrum from uncertain team thinking to clear external communication.

SAFE does not end with thinking. It ends with execution. The framework is a bridge between what the team knows and what the team does — built specifically for the conditions where that bridge is hardest to construct.

↓ Download: SAFE reference card — four elements, options prompt, SBAR comparison, worked example