Multi-layer rotations
Stack primary and secondary layers in one schedule. Each layer has its own participants, rotation (daily, weekly or every N days) and handoff time.
On-Call Scheduling
Always know who's
Always know who's
on call.
Rotation schedules your team trusts, with layers, overrides and handoffs at a set time in the schedule’s timezone. Built into the same platform as your monitors, incidents, and escalation policies.
Free tier included
No credit card
2-minute setup
Schedules that run themselves.
Define your rotations once. When an escalation policy reaches a schedule, Site Qwality works out whose shift it is, including any override, and notifies that person. No spreadsheet, no Slack pinned message, no human keeping score.
Overrides for any reason
Overrides put a team member on call for a set window (for a vacation, a meeting conflict, or an emergency) without changing the underlying rotation.
A timezone per schedule
Each schedule has its own timezone, and handoffs happen at the set time in that zone. For teams in different regions, use a schedule per region.
Schedules in the API
Create and read schedules, layers and overrides through the REST API. The API returns the schedule definition; it does not return the current responder.
Personal notification rules
Each team member chooses their own contact methods (email, SMS, or a Slack direct message) with separate rules for high and low urgency.
Escalation policy integration
Plug a schedule into any escalation policy level. When the policy reaches that level, the current on-call responder for the schedule is notified automatically, whoever that happens to be.
Flexible when life happens
Override a shift in
Override a shift in
seconds.
Swapping shifts shouldn't require rebuilding the schedule. Create a time-bounded override that puts a specific responder on call for a specific window. The override takes precedence, the rotation resumes afterward, and nothing else changes.
- Overrides are time-bounded and non-destructive to the rotation
- Create an override from the dashboard or the API
- Deleting an override removes it; there is no override history
Platform On-Call Override ActiveLIVE
OVERRIDE BYM. Chen
COVERSA. Patel
ENDSMon 09:00 UTC
Mon: M. Chen (override)100ms
Tue: A. Patel85ms
Wed: A. Patel70ms
Thu: R. Santos55ms
Fri: R. Santos40ms
Schedules as code
Build the rotation
Build the rotation
from the API.
Create a schedule with its timezone, then add a layer with its participants, rotation and handoff time. Escalation policies point at the schedule, so the person on shift is the one who is paged.
- POST /on_call_schedule creates a schedule
- Layers and overrides are created under the schedule
- Escalation levels target schedules or individual users
create a weekly rotationPOST /on_call_schedule
{ "name": "Platform On-Call", "timezone": "Europe/Berlin" }
POST /on_call_schedule/$SCHEDULE_ID/layer
{
"rotation_type": "weekly",
"handoff_time": "08:00",
"participants": ["$USER_A", "$USER_B"]
}
201 Created
{ "name": "Platform On-Call", "timezone": "Europe/Berlin" }
POST /on_call_schedule/$SCHEDULE_ID/layer
{
"rotation_type": "weekly",
"handoff_time": "08:00",
"participants": ["$USER_A", "$USER_B"]
}
201 Created
24/7
rotation coverage with handoffs at the time you set
TZ
one timezone per schedule, used for every handoff
3
rotation types: daily, weekly and every N days
1
on-call responder free; rotations need a responder pack
FAQ
A schedule can have multiple layers, each with its own participants, rotation (daily, weekly, or every N days), and handoff time. Layers are numbered, so you can model primary and secondary on-call in a single schedule.
An override puts a chosen team member on call for a specific time window. The underlying rotation is unaffected and resumes as normal after the override ends. Create overrides from the schedule in the dashboard or through the API.
That's handled by your escalation policy, not the schedule itself. The schedule decides who is on call; the escalation policy defines what happens if they don't acknowledge within your configured timeout.
Not today. There is no shift history view or endpoint, and a deleted override is removed rather than archived. The incident timeline records the updates on each incident.
The free tier includes 1 on-call responder. You can build schedules and escalation policies with that responder; rotations between several people need a responder pack.
For schedules, escalation policies and incident timelines, yes, with up to 25 responders for $50 a month. Atlassian stopped selling Opsgenie on June 4, 2025 and will shut it off on April 5, 2027. Site Qwality has no voice calls, no mobile app and no Opsgenie importer, so moving over is a manual rebuild. The Opsgenie alternative page has the dated comparison and the migration steps.
Site Qwality costs less with several responders: 25 responders are $50 a month, against $34 a month per Better Stack responder licence. Better Stack’s free tier is larger on several products, and it has phone-call alerts and mobile apps, which we do not. The Better Stack alternative page shows the worked costs.
Related features
Start free. No credit card.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.