From Chronology to Command Clarity
Explain how to rewrite a chronological pressured update into BLUF plus SBAR.
A client asks if tomorrow's migration is still safe. The before update narrates the timeline; the after update gives the decision path. Before: the update follows the sender's timeline and buries the recommendation. After: the decision appears first, then the SBAR support, then the confirmation request. The first sentence changed from history to BLUF: proceed, pause, or decide by a stated time. That tells the client what the message is for. Background was trimmed to facts that affect the decision. SBAR is not a dump; it is a relevance filter. Assessment became explicit. The reader no longer has to infer…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in