> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/oncall-schedules/introduction-to-on-call-schedules.md).

# Introduction to On-call schedules

On-call schedules define who is on-call and when. Members rotate automatically on daily, weekly, or custom intervals.

On-call schedules define who responds to incidents and when. Spike rotates your team automatically on daily, weekly, or custom intervals you set.

<figure><img src="https://1743514643-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Ln3jS1bJTTsE3yoEcOu%2Fuploads%2Fgit-blob-c68bdf1ba601bd2c06631420bb4d1217ec2d6fb7%2FOn-call%20calendar.gif?alt=media" alt="Example of daily rotation among 2 members on Spike"><figcaption><p>Example of daily rotation among 2 members.</p></figcaption></figure>

## FAQs

### Who should use on-call schedules?

Any team with more than one member. Schedules distribute on-call responsibility so no single person is always on call.

### Who can create schedules?

Admins and members can both create and edit schedules. Use fine-grained access control to manage on-call permissions.

### Does being on-call mean I receive all alerts?

No. You receive alerts only from escalation policies that include you. Being on-call doesn't automatically route all incidents to you.