Multi-layer rotations
Stack primary and secondary layers in one schedule. Each layer has its own participants, rotation period, and handoff time — combine them for follow-the-sun or shadow rotations.
Rotation schedules your team trusts — with layers, overrides, timezone-aware handoffs, and a single answer to "who do I page right now?" Built into the same platform as your monitors, incidents, and escalation policies.
Define your rotations once. Site Qwality tracks whose shift it is, routes alerts to the right person, and hands off automatically at the end of each period — no spreadsheet, no Slack pinned message, no human keeping score.
Stack primary and secondary layers in one schedule. Each layer has its own participants, rotation period, and handoff time — combine them for follow-the-sun or shadow rotations.
One-click overrides let any team member cover for a colleague — for a vacation, a meeting conflict, or an emergency — without disrupting the underlying rotation.
Each participant has their own timezone. Handoffs happen at the right local time for everyone. Build a round-the-globe rotation without doing timezone math by hand.
A single API call or dashboard glance returns the current on-call responder for any schedule — useful for chat-bot integrations, runbooks, and automated tooling.
Each team member chooses their own contact method — email, SMS, push, or a configured channel — with separate urgency rules so critical pages always break through.
Plug a schedule into any escalation policy level. When the policy fires that level, the current on-call responder for the schedule is notified — automatically, whoever that happens to be.
Swapping shifts shouldn't require rebuilding the schedule. Create a time-bounded override that covers a specific responder for a specific window. The override takes precedence, the rotation resumes afterward, and nothing else changes.
Runbooks, Slack bots, and automated tooling all need to know the current on-call responder. One REST endpoint returns the answer for any schedule, in real time, accounting for overrides — so you never hardcode a name anywhere.
rotation coverage with zero manual handoffs
every shift shown in the responder's local timezone
call to find the current on-call for any schedule
free tier — on-call scheduling included from the start
A schedule can have multiple layers, each with its own participants, rotation period (daily, weekly, or custom), and handoff time. Layers are evaluated in order so you can model primary and secondary on-call in a single schedule.
An override replaces the scheduled responder for a specific time window. The underlying rotation is unaffected and resumes as normal after the override ends. Overrides can be created by any team member and show up clearly in the calendar view.
That's handled by your escalation policy, not the schedule itself. The schedule routes the alert to the current on-call responder; the escalation policy defines what happens if they don't acknowledge within your configured timeout.
Yes. The schedule history shows who covered each shift, including overrides. This is useful for postmortems and for auditing incident response.
Yes — on-call scheduling is available on the free tier. You can build rotations, create overrides, and integrate schedules with escalation policies without a paid subscription.
Every product starts free — uptime, cron, synthetic, logs, RUM, incidents, and status pages. No credit card required.