On-Call Schedule is the long-horizon view: the entire year of upcoming rotations laid out by team. Plan vacations in your own row. Balance load across the team. Export to ICS so the schedule lands in everyone's personal calendar. Less Slack-thread coordination, more "I can see when I am on."
The grid spans 52 weeks across the rows of every rotation. Each cell is a week with the responsible engineer's name. Filters narrow to one team or one engineer. The view scrolls horizontally; clicks open week details (escalation chain, quiet-hour overrides for that week).
For each engineer, the page reports total weeks on-call this year, fraction of weekends, fraction of holidays, and fraction of overnight shifts (for follow-the-sun rotations). Disparities show up immediately, when one engineer is on-call 18 weeks and another only 6, the manager has data to redistribute.
Engineers can swap shifts directly on the schedule. Drag your week to a teammate's row; the swap is proposed; the teammate accepts or declines. On approval, the schedule updates and notifications fan out (Slack and ICS). Manager approval is optional per team.
Each engineer has a personal ICS feed URL containing only their on-call weeks. Subscribe to it in Google Calendar, Outlook, or Apple Calendar. Updates (swaps, hand-offs, overrides) sync automatically. Engineers see their on-call commitments next to the rest of their life, not in a separate tool.
Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.
Long-horizon schedules turn pager rotations from a coordination tax into an obvious calendar event.