Rewrite a Crisis Update With CERC
Convert a vague incident update into a credible message with knowns, unknowns, actions, and next update timing.
An outage update is technically accurate but does not help customers or internal teams act. CERC: be right, credible, empathetic, action-oriented, and time-bound. The common trap is using vague system language that avoids false claims but leaves the reader with no usable picture. Step 1 Name the affected users and function: some EU users cannot export reports. Impact scope matters more to the audience than internal subsystem names. Step 2 Separate reassurance from uncertainty: data is not lost; root cause is still under review. This avoids both panic and overclaiming. The reader gets a usable reason instead of having to…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in