How to apply this guide
Keep observed impact, current action and the next update time separate in a reviewable draft.
Start with
Record the symptom, affected workflow and verified time window. Say “cause under investigation” where appropriate. Include the next update time only if your team can meet it.
Check before you finish
Paste into a draft and use the incident review process for publication. Keep timestamps or links to internal evidence in the internal version.
Evidence to keep: Before sending, verify the recipient, requested action, dates and sign-off in the finished draft. This page’s key limit is: Keep observed impact, current action and the next update time separate in a reviewable draft.
Start here
A status update can be written before an incident’s cause is known. Keep facts and working theories separate so a cleaned-up version does not present a guess as a conclusion.
State what is observed
Record the symptom, affected workflow and verified time window. Say “cause under investigation” where appropriate. Include the next update time only if your team can meet it.
Compare the draft with your evidence
Check whether a formatter turned a partial impact report into an outage claim. Verify the time zone and whether a workaround is confirmed. Remove any customer names or private details that should stay internal.
Post only an approved update
Paste into a draft and use the incident review process for publication. Keep timestamps or links to internal evidence in the internal version.




