> ## Documentation Index
> Fetch the complete documentation index at: https://docs.warrn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# On-call

> Schedules, rotations, escalation, and overrides for a team.

Each team can have one or more on-call schedules. A schedule decides who is reachable when an alert fires for one of the team's services.

## Schedules

A schedule is a recurring rotation through a list of people. You can have multiple schedules per team if different groups cover different hours or services (e.g. "Weekday primary", "Weekend primary", "Database secondary").

## Rotations

Rotations cycle the on-call person on a fixed cadence:

* **Daily** - new person every 24 hours.
* **Weekly** - new person every 7 days.
* **Custom** - any length you specify.

## Escalation policies

An escalation policy decides what happens if the primary on-call doesn't acknowledge an alert within a window. The next person up gets paged, and so on. You can stack as many levels as you need and choose the wait time at each level.

## Overrides

Overrides are temporary swaps - vacation cover, handoffs, "I've got tonight." They only apply for the window you specify and don't change the underlying rotation.

## Fallback

If no one is on-call (no schedule, or everyone is overridden out), Warrn pages the team's admin. This is the last-resort fallback, not the steady state. Set up a schedule even if it has only one person on it.