On-call scheduling

Stage in the incident loop: PAGE

On-call scheduling, traceable to who is actually on it.

A rotation is a promise made months in advance by people who will not remember making it. CallHeim keeps that promise legible: layers, overrides and time off compose into one answer to who is on call right now.

  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
Layer 1 · weekday
  • Maya
  • Maya
  • Maya
  • Priya
  • Priya
Layer 2 · weekend
  • Sam
  • Sam
Override
  • Daniel
Who is paged
  • Maya
  • Maya
  • Maya
  • Daniel
  • Priya
  • Sam
  • Sam
An example week. Layers compose from the bottom up and an override sits above all of them, so the resolved row is the one that answers “who gets paged on Thursday”.

How it works

Teams own schedules; schedules resolve to one person.

Teams with member rosters own schedules and link to escalation policies. Schedules use any IANA time zone.

Layers stack

Each layer has its own restriction — weekdays, nights, a follow-the-sun band — its own rotation length and its own roster. The topmost layer covering a moment decides who is on call at that moment.

An override wins

An Override sits above every layer for its window, so covering a shift does not require editing the rotation everyone else depends on.

Escalation reads it

A schedule answers “who”. An Escalation Policy answers “and if they don’t answer?” The two are separate objects, so changing your rotation does not mean rebuilding your escalation strategy.

Subscribe from your calendar

Subscribe to any schedule from a calendar app: a private iCal link shows the next 90 days of shifts, including overrides, and a schedule editor can reset the link at any time.

Schedules & layers

Rotations that compose

Schedules support layers, an override that sits above the layers, layer restrictions to weekdays, business hours or nights, follow-the-sun templates, time off, shift-swap requests with approval, and coverage-gap detection with suggested fills.

Layers can rotate through a team as a whole, and the people inside that team can rotate too — so “weekdays are the product team, nights are the platform team” is one schedule rather than three that can silently disagree with each other.

A schedule, stacked

Layer 1 — weekday primary

Mon–Fri 09:00–18:00, weekly rotation, 6 people

Layer 2 — nights & weekends

Everything else, weekly rotation, 4 people

Override — 14–16 March

Priya is away; Daniel covers

Example. Higher layers win, and an override wins over every layer for its window.

An on-call schedule timeline showing rotation layers and the final schedule they resolve to
On-call schedule

On-call schedule: rotation layers and the final schedule they produce, in any time zone.

Exceptions

Overrides, swaps and time off.

Overrides, swaps and time off are records the paging path reads, not a comment in a spreadsheet, so a covered shift is actually covered.

Override

A named person covers a named window, above every layer. The most common operation, made cheap.

Swap Request

One responder asks a schedule manager to approve another responder taking a shift, with the approver recorded.

Time Off

Absence, including one entry that can cover a company-wide shutdown across every schedule at once.

Coverage gaps

Coverage gaps and unreachable on-call people for the next 7 days are flagged in the console, with suggested fills.

Rotation assist

Rotation assist proposes a fairer rotation from each person’s paging history. You review it before anything changes.

Configuration history

Changes to schedules, layers, overrides and time off are recorded in the audit log.

Only swap requests carry a formal approval step. Overrides and time off are direct changes, and every one of them is recorded in the audit log.

Fatigue

A fairness number you can audit.

A published on-call fatigue score is calculated from your own paging history. It is a heuristic, not a wellbeing measure.

The four factors

  • 0.40

    Interruptions inside the sleep window

  • 0.30

    Page volume, normalized per week

  • 0.20

    Pages outside working hours

  • 0.10

    Severity pressure — the share that were high severity

Portability

Follow-the-sun templates and schedule import.

  • A follow-the-sun template builds time-banded layers for a schedule that hands off by region.
  • The importer reads your PagerDuty or Opsgenie configuration from a US or EU account, and a dry run shows you the result before anything is written to your organization. Read the migration guide →

Tiers

Who gets escalated, and how far.

Escalation policies have up to 8 tiers, each paging a person, a team or a schedule, with per-tier timeouts from 1 to 240 minutes, optional repeats and a mandatory fallback. The whole chain must fit within 24 hours.

Escalation policies answer “and if they don’t answer?” Timeouts, tiers and a mandatory fallback are configured there, not on the schedule itself.

Each person chooses how and when they are paged: ordered steps with delays, quiet hours for lower severities, a low-urgency digest instead of a page, and an organization-wide default for anyone who has not set their own.

How pages reach your team →

CallHeim

Put a rule you can read between your alerts and your on-call.

Start a 14-day trial, connect one alert source and send yourself a test page.