Incident response

Saying you're unavailable

Tell WarnFire you can't take the pager, and rotations route around you.

Sometimes you can’t take the pager. You’re ill, you’re on a plane, you’re at a wedding. Say so, and WarnFire routes future incidents to the next eligible person in each affected rotation.

You don’t need to ask anyone, and you don’t need to find someone to swap with first.

Before you begin

You need an authorized WarnFire build installed and signed in , and your responder must belong to at least one rotation. Review the affected shifts before marking yourself unavailable, especially when a rotation has only one or two members.

Mark yourself unavailable

1. In the mobile app, open Status.
2. Under Availability, tap I’m out.
3. Choose Sick, Time off, or Personal.
4. Set how long you will be unavailable and add an optional note.
5. Tap Mark me out.

The panel confirms that future incidents will route around you. Incidents already open keep the response plan captured when they opened and can still page you.

When you’re back, press I’m back.

Administrator-managed time off

An administrator can record the same person-scoped absence when a responder cannot use the mobile app:

1. Open On-call → Schedules.
2. In Time off, select Who is out and the reason.
3. Set From and Until, then add an optional note.
4. Select Mark as out.

The absence applies across every rotation that person belongs to. Use Remove in the same section if the responder returns early.

Use a time-bounded schedule override instead when one specific schedule needs a named replacement. An explicit override takes precedence over a person’s time-off record, so do not override a shift to an unavailable responder unless you deliberately intend to put that person back on call.

What actually happens

WarnFire looks at each rotation you’re in. Wherever your turn comes up, it moves to the next person in order instead. That person is on call for real — they’ll be paged, and they can see it on their own schedule.

A few things worth knowing:

It covers every rotation you’re in, not just one. Being unavailable is a fact about you, not about a schedule.

WarnFire attempts to notify people who pick up shifts during the next 30 days. That push is best-effort, so verify the handoff and contact the replacement directly before relying on the coverage change.

It takes effect immediately for new incidents. If you’re on call right now and mark yourself out, an incident opened afterward resolves the next eligible responder. An incident already open can still page you because its response plan is frozen.

If everyone in a rotation is out, that rotation has nobody on call and WarnFire says so rather than quietly picking someone. Your administrator sees it as a gap that needs filling.

Coming back

Marking yourself back is instant too. If your time off has already ended, it disappears from the panel by itself — though it stays visible for a day afterwards, so if you were skipped you can see why rather than wondering whether the pager is broken.

Good to know

• Being unavailable doesn’t remove you from a team or a schedule. Nothing is lost and nothing needs setting up again.
• It doesn’t stop you being invited to an incident by a colleague who needs you specifically, and it does not rewrite paging already captured on an open incident. It changes automatic on-call resolution for future incidents.

Verify it worked

1. Confirm that Availability says you are marked out and shows the expected end time.
2. Open View schedule and confirm that the affected rotation resolves to the next eligible responder rather than you.
3. Ask an administrator to review On-call → Schedules for any uncovered window created because every responder is unavailable.
4. When the absence ends, tap I’m back if it has not expired automatically and confirm that the active absence disappears.

Next step

If only one shift needs a named replacement, use a cover request or shift swap instead of marking yourself out across every rotation.