> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Hours Coverage

> Configure a schedule that only covers working hours, and route around the gap so an out-of-hours alert reaches someone instead of waiting for nobody.

Plenty of teams do not need someone awake at 3am for every service. A business-hours schedule says so honestly, but a schedule with deliberate gaps only works if your paging knows what to do when it lands in one.

This page covers both halves. The first is easy and the second is where teams get hurt.

***

## Half One: Restricting a Schedule to Working Hours

Working hours are set on the **rotation**, in Step 3 of schedule creation:

**Active Days** `days of week`

Which days of the week the rotation is active. Weekdays only, for a schedule that does not run at weekends.

**Active Hours** `all day or a time range`

Whether the rotation runs all day or only between specific hours.

**Timezone** `IANA timezone`

The time zone that Active Days and Active Hours are measured in. If the schedule form shows a **Time Zone** field above the rotations, it applies to every rotation. For follow-the-sun, enter each region's hours converted to that zone. If each rotation has its own **Timezone** field, set each one to that region's zone.

Full context in [Creating a Schedule](https://docs.rootly.com/on-call/schedules.md#step-3-configure-rotation-rules).

> [!TIP]
>
> For a follow-the-sun arrangement, build one rotation per region with that region's own Active Hours, rather than one rotation with a wide window. The handoffs then fall out of the configuration instead of being maintained by hand. Make the windows meet exactly: any hour between two windows is a gap, and where two rotations overlap, the one lowest in the list wins.

***

## Half Two: What Happens Outside Those Hours

Here is the part that surprises people.

> [!WARNING]
>
> **Rootly does not skip a step that has nobody on call.** An alert reaching a step that points at a business-hours schedule, outside business hours, sits there for the step's full delay before moving on.
>
> A twenty-minute delay on that step means twenty minutes before the next step is tried.
>
> With [24/7 coverage](https://docs.rootly.com/on-call/schedules.md#enabling-247-coverage) on, Rootly treats the empty window as a gap and pages the schedule's [Fallback Assignee](https://docs.rootly.com/on-call/schedules.md#fallback-assignee). If the Fallback Assignee can't be paged, for example because they have no On-Call seat, no one is paged. Without 24/7 coverage, the step pages no one.
>
> Neither is a substitute for an after-hours rotation: 24/7 coverage sends every out-of-hours alert to one person, which is a backstop rather than a plan.

The instinct is to add a 24/7 fallback as the next step in the same path. That works, in the sense that someone is eventually paged, but the delay is spent first, every single time, on every out-of-hours alert.

### The Fix: Two Paths, Not Two Steps

Model the time-of-day decision as **[Dynamic Paths](https://docs.rootly.com/on-call/escalation-policies.md#dynamic-paths)**, so the right path is chosen up front rather than the wrong step timing out:

**1. Path 1: during working hours**

Add a Time window condition to path 1 (Add condition, then Time window) and match the days, hours and time zone to the rotation. The path doesn't look at the schedule, so if the rotation's hours change later, update the Time window too.

* **Step 1:** the business-hours schedule
* **Step 2:** the 24/7 fallback, for when the business-hours responder does not answer

**2. Path 2: outside working hours**

Put the 24/7 fallback as step 1 of the **Default Escalation Path**, which runs when no other path matches. If your Default path already pages the business-hours schedule, create another path with a Time window covering the hours outside path 1's window, and make the 24/7 fallback its step 1.

* **Step 1:** the 24/7 fallback, directly

Paths are evaluated top to bottom and the first match wins. The Default Escalation Path runs only when no other path matches. Out of hours, path 1 does not match, path 2 fires immediately, and the fallback is paged with no empty-step delay.

> [!NOTE]
>
> To hold a low-urgency alert instead of waking the fallback, use a [Deferral Path](https://docs.rootly.com/on-call/escalation-policies.md#deferral-paths). Rootly checks Deferral Paths first. A matching alert waits until the deferral window ends, then pages through the path set in **After Deferral**. Only alerts from Alert Sources, Live Call Routing and the API are deferred. A policy holds at most 50 deferred alerts, and any more page at once.

***

## Check Your Work

A business-hours schedule looks fine in the UI at 2pm on a Tuesday. The failure only shows up out of hours, which is exactly when nobody is watching.

* **Use 24/7 coverage only where it belongs.** Turn on **Enable 24/7 coverage for this Schedule** only for schedules meant to be continuous. Rootly then flags gaps and pages the Fallback Assignee during them. On a business-hours schedule, every hour outside the active window is a gap. See [Enabling 24/7 Coverage](https://docs.rootly.com/on-call/schedules.md#enabling-247-coverage).
* **Check the schedule's timeline.** Open the schedule and check its timeline for the week ahead. Any stretch with no shift on it is a time when a step targeting this schedule pages no one.
* **Test outside the window.** Trigger an alert through the same alert source and route your real alerts use, at a time when the business-hours rotation is not active. On the alert timeline, confirm the after-hours path was chosen and the 24/7 fallback was paged at its first step. A manual page is not a full test: it skips Deferral Paths, and a page to one user skips the escalation policy. This is the single check that catches the empty-step trap.

***

## Related Pages

> [card] [Schedules](https://docs.rootly.com/on-call/schedules.md)
>
> Rotations, Active Days and Active Hours, and coverage gap detection.

> [card] [Escalation Policies](https://docs.rootly.com/on-call/escalation-policies.md)
>
> Dynamic Paths, Deferral Paths, and step delays.

> [card] [On-Call Shifts](https://docs.rootly.com/on-call/on-call-shifts.md)
>
> Each person's upcoming shifts, overrides, and calendar export.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.