Template description
Four participants stand across the top: Monitor, On-call, Platform, and Communications. Monitor sends Trigger critical alert to On-call. On-call sends Request logs and metrics to Platform, and Platform returns Provide diagnostics on a dashed arrow. On-call then sends Publish status update to Communications. Only after that status does On-call send Execute temporary fix to Platform, and Platform returns Confirm remediation. On-call sends Close alert back to Monitor. Communications then sends Document postmortem to itself. Communications never messages Platform. The postmortem is not on the close arrow. On-call is the only participant who speaks to the other three.
When to use it
Use it when the communications owner is being asked to pull logs, or when a postmortem is being filed before anyone has published a status. The sequence shows the status update leaving On-call, and the postmortem as a later note Communications writes to itself.
How to adapt it
Rename the participants to your real rotations. If Platform should tell Communications directly, add that message. If the temporary fix must wait for an explicit go-ahead, insert that reply before Execute temporary fix. Move Document postmortem onto another lifeline only if a different team writes it. Keep Close alert aimed at Monitor unless your monitor closes itself.