Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

← All emails

No. 5 · Apr 30, 2026 · On-call

Your on-call is probably paging the wrong person.

For recent deploys, at least.

When something breaks, the on-call responder is usually the first to get paged.

That works for many incidents, but not every one.

Say a feature shipped last week started throwing errors.

If that incident is picked up by the on-call responder on the default rotation, it would probably take 40 minutes to resolve.

But if the same incident is handled by the person who shipped the feature, it would probably take just 10 minutes.

This is because the edge cases and configs they worked through last week are still fresh in their mind.

That's what Follow-the-work on-call rotation is about.

It runs a rotation for a short window after each deployment, usually 48 hours or a week. During that window, the engineer who shipped the change is the first responder.

After that window, incidents route back through the regular rotation.

This way, you can reduce the MTTR on incidents tied to your recent deploys.

Follow-the-work is one of six on-call models in our guide. Shadow, Night-owl, Follow-the-sun, and two more are the other five.

See all 6 on-call models →

Get the next one in your inbox

A weekly email for engineers who carry the pager.

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh