The on-call handoff is where incidents get dropped

A lot of incidents that go badly do not go badly because nobody noticed. They go badly because the person who noticed handed off their shift, and the context did not travel with them. The next person on-call inherits a pager and none of the story, and a problem that was half understood starts over from zero.

The handoff is the seam in your on-call coverage, and seams are where things tear.

What gets lost

When a shift ends mid-investigation, the outgoing engineer carries a head full of context. What they ruled out, what looked suspicious, which dashboard they were watching. If all of that lives only in memory, it leaves with them. The next person reopens the same dead ends and re-learns what was already known.

Hand off the story, not just the pager

A good handoff is not you are on now. It is a short summary of anything open, anything being watched, anything fragile right now. Even two lines per active concern saves the next person from starting cold. The goal is that the incident does not notice the shift changed.

Keep the context in the incident, not the person

The reliable fix is to stop relying on memory for the handoff. When the timeline, the notes, and the state of an incident live on the incident itself, the handoff is just pointing at it. Vigiles keeps that record on every incident, so whoever picks up the pager picks up the full story with it.

Coverage is only as strong as its handoffs. Make the story travel, not just the alert. Start free, or see how incident management works.