Example: what a live situation alert looks like
A reference for how Systems Fail Lab issues Active Situation briefings — and how to act on one when a real event is unfolding.
This is a format example, not a live event
When a real situation is unfolding — a regional grid failure, an approaching storm, a chemical incident — we publish an Active Situation briefing. It is pinned to the top of this feed, carries a site-wide banner while live, and links straight to the protocols you need in that moment. This post is a permanent example of that format so you know one when you see it.
How to read a live alert
- Status line first. "ACTIVE" means the event is ongoing; "RESOLVED" means it has passed and the briefing is kept for reference.
- Act on the linked protocols, not the prose. Every alert links directly to the relevant field guides — open those first.
- Re-check, don't refresh-doom. Alerts are updated on a fixed cadence, not continuously. Check on schedule and act in between.
When in doubt, start the clock
If you are reading a real alert and unsure what to do, the first move is almost always the same: assess your window and make the stay-or-go call early, while you still have options.
— Systems Fail Lab