Schedules & Coverage

Schedules answer who is responsible for responding at a given time. Coverage adds the calendar and policy view needed to see whether that responsibility is continuous and actionable.

Create a schedule

Open On-Call → Schedules and provide:

• A name, such as "Backend Team Primary"
• Team members as participants
• A rotation period: daily, weekly, or custom
• A rotation start time and timezone

Rotations automatically cycle through participants. When a rotation period ends, the next person in the list becomes the primary on-call responder. Multiple rotation layers can provide backup coverage.

Overrides

Overrides temporarily assign a different person to be on call for a specific period without changing the underlying rotation schedule. Use them for vacations, swaps, or an unexpected handoff.

Inspect coverage

Use Coverage to inspect the resolved schedule calendar for a month, including shifts, handovers, availability exceptions, and coverage gaps. A coverage policy can:

• Require continuous coverage
• Set a minimum responder count
• Define a fallback responder

Members can request a shift change. Authorized administrators can approve, reject, or cancel requests and save coverage policies.

Reading coverage is non-mutating and does not notify anyone. Use Re-evaluate coverage when you intentionally want Moneat to reevaluate gaps and page the policy owners. If there are no gaps, the action reports that no paging is needed.

What to verify

Before enabling a schedule for production response, check the current responder, the next handoff, every rotation layer, and each expected availability exception. Then send a test alert through the routing and escalation path to prove that the schedule target resolves to the person currently on duty.