Skip to main content
An on-call schedule rotates responsibility through your team so the right person is paged at any given time. You target the schedule from an escalation policy, and Tallwatch figures out who’s on call when an incident fires.

​
Create a schedule

1

Open the on-call page

Go to On-call and click Create schedule. Name it for the team or service it covers, like Platform on-call.
2

Set the timezone and rotation

Pick the timezone the rotation runs in, then a rotation type: weekly, daily, or custom. Weekly hands off once a week, daily once a day.
3

Set when it starts

Choose the start time. Tallwatch counts forward from there to work out who’s on call at any moment.
4

Add members in order

Add the people in the order they should rotate. Each member is paired with the channel used to reach them (for example their personal Slack or email channel). The order is the rotation order.
Once saved, the schedule can be a target on any escalation policy level.

​
Overrides

Plans change. An override swaps one person for another over a fixed time range without touching the rotation itself.
1

Open the schedule

Open the schedule and add an override.
2

Pick the substitute and window

Choose who’s covering, and the start and end times. Add a reason if you want the team to know why (vacation, appointment, swap).
During that window, the substitute is on call. Outside it, the normal rotation resumes. The underlying rotation is never changed by an override, so a one-off swap doesn’t shift everyone’s turns.

​
Attach it to an escalation policy

A schedule pages people only when an escalation policy targets it. A common setup: level one alerts the team chat, and a later level targets the on-call schedule so the current responder gets paged if chat goes unanswered.
There’s no calendar feed (iCal) export in this release, so you can’t subscribe to the rotation from an external calendar app yet.