--- title: Configure or update an On-Call schedule description: Create an On-Call schedule or edit an existing schedule by defining shifts and rosters. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/on-call-scheduling/create-update-schedule-oncall.html release: australia product: On-Call Scheduling classification: on-call-scheduling topic_type: task last_updated: "2026-03-12" reading_time_minutes: 8 breadcrumb: [Managing schedules and shifts, On-Call Scheduling, IT Service Management] --- # Configure or update an On-Call schedule Create an On-Call schedule or edit an existing schedule by defining shifts and rosters. ## Before you begin Role required: rota\_admin, rota\_manager ## About this task You can use the wizard to create an on-call schedule using an existing template or you can create shifts from scratch. You can create multiple shifts at given time and can preview shifts while creating them. This enables you to create rosters, define escalation policies, and review and publish shifts. After running the wizard, you can adjust individual roster, escalation, and reminder settings to fine-tune the setup. You can also enable on-call notifications by setting up rotation workflow triggers. ## Procedure 1. Navigate to **All** > **On-Call Scheduling** > **Create/Edit Schedule**. 2. In the **Define Schedule**, from the **Select Group** choice list, select the group for which you are defining the schedule. You can edit an existing shift for a selected group. If you want to create a new schedule, click **Add shift** button. **Note:** When creating a new on-call group schedule, you are redirected to oc\_creation\_wizard page instead of expert\_shell page which is no longer supported. 3. Choose an existing template for the shifts or create a new shift. 4. Select the **Allow Shift Schedule overlap** check box to allow overlapping schedules for shifts within the group. For example, if a group has a 24x7 schedule, you can create multiple schedules for the group. Shift overlap is required to have a hand-off period between shifts so that multiple shifts can be on-call for the same duration. If you select **Allow Shift Schedule overlap**, then the **Escalation rule on Shift overlap** check box appears. 5. Select the **Escalation rule on Shift overlap** check box to specify which shift needs to be notified of an escalation during a shift overlap. You can escalate to an incoming, an outgoing, or to all shifts. 6. Fill in the form fields.
| Question | Description |
|---|---|
| Name | Name of the shift that appears on the **On-call calendar** page. |
| Would you like to use an existing schedule? | Option to use an existing schedule. - Select **Yes** to use an existing or predefined shift. - Select **No** to create a new schedule. |
| Schedule | Select the value to base your schedule on. Some options are available in the base system, for example, 24x7, Workday 8-5.This option appears only if you answer **Yes** to **Would you like to use an existing schedule?**. The logged-in user's time zone is used as the basis for these schedules. If the logged-in user does not have a time zone specified, the instance time zone is used. |
| Start date | The date on which the shift is scheduled to begin. |
| Specify holidays | Option to define holidays.- Select **Yes** to define holidays for the on-call shift. You can select an existing holiday schedule. - Select **No** to not specify holidays for the shift. |
| Holiday Schedule | Specify a holiday schedule for the group. |
| Additional fields**Note:** The following fields are displayed only when the **Would you like to use an existing schedule?** field is set to **No**. | |
| Time Zone | The time zone in which the shift operates. |
| Is the shift for this schedule all day? | List of options. Specify whether this shift is an all-day shift. |
| Start | The time of day the shift is scheduled to start. The start and end time represent one shift. The date is different only if the shift spans midnight. |
| End | The time of day the shift is scheduled to end. The start and end time represent one shift. The the date is different only if the shift spans midnight. For example, for the 8 a.m. to 8 p.m. shift, the start is 2014-01-01 08:00:00 and the end is 2014-01-01 19:59:59. For the 8 p.m. to 8 a.m. shift, the start is 2014-01-01 20:00:00 and the end is 2014-01-02 07:59:59. |
| Repeats | The days that the shift repeats. **Note:** The wizard does not provide a monthly or yearly option. Creating a monthly or a yearly shift by editing the schedule manually is not advised because it is hard to determine the on-call person over a long period. In this case, create a yearly or a monthly schedule with only one roster and one member so that the same person is always on-call. Make any exceptions as a one-time change in the roster for the shift. |
| Send On-Call Reminders | Option to send [on-call reminders](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/escalation-remind-settings-oncall.md) to members of the roster. |
| Reminder lead time \(days\) | Lead time for email reminders.**Note:** This field is displayed only when the **Send On-Call Reminders** option is selected. |
| Coverage interval | Interval for updates of coverage details. Specifies whether you want to update the [subscribed](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/view-my-schedule-on-my-app-oncall.md) calendar with weekly or daily coverage details. |
| Get coverage for | Number of weeks or days for which you want to update the subscribed calendar. |
| Field | Description |
|---|---|
| Roster Name | Use the edit icon to edit the name of the [roster](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/config-roster-oncall.md) that you are adding members to. |
| Which members would you like to be in your schedule? | Move the members you want to add from Available list to Selected list. |
| Rotation start date | Date on which the rotation needs to start. |
| Rotation interval | Type of the rotation interval. Possible options are:- Daily - Weekly - Monthly **Note:** This option is available only for the 2024 schedule engine. For information about this schedule engine, see [On-Call Scheduling new schedule engine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/oncall-schedule-engine.md). |
| Rotate every | Frequency of the rotation interval.**Note:** This field appears only if the **Rotation interval** field is set to **Weekly** or **Monthly**. |
| Day of week for rotation | Day of the week on which the roster rotation should start. When this field is specified, roster rotation happens based on the specified frequency and the day of the week.**Note:** This field appears only if the **Rotation interval** field is set to **Weekly**. |
| Day of the month for rotation | Day of the month on which the roster rotation should start. Possible options are:- Last day of the month - Specific day **Note:** This field appears only if the **Rotation interval** field is set to **Monthly**. |
| Rotation day | Specific day of the month on which the roster rotation should start.**Note:** This field appears only if the **Rotation interval** field is set to **Monthly** and **Day of the month for rotation** field is set to **Specific day**. |
| Send On-Call Reminders | If selected, on-call reminders are sent to the members of the roster. |
| Reminder lead time \(days\) | Lead time for email reminders.**Note:** This field is displayed only when the **Send On-Call Reminders** option is selected. |
| Field | Description |
|---|---|
| Escalation type | Method used to determine who receives an escalation notification. Its value is automatically set to **Rotate Through Members** if a shift has only one roster. The escalation path goes through all members of that roster. If a shift has more than one roster, the default value is **Rotate Through Rosters**. The escalation path goes through all the rosters to determine who to notify. [Click **Override escalation** to change the default setting.](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/create-custom-esc-policy-oncall.md) |
| Catch-All | Specifies users who receive a notification when no other on-call users have acknowledged the escalation. The value can be none, a group manager, a shift manager, an individual, or any or all roster members. - Select **Notify Individual** to specify a member of the group to notify. - Select **Notify All** to specify a shift. All shift members are notified. |
| Field | Description |
|---|---|
| \# reminders | When escalations are configured for this group, the instance first sends this number of reminders before notifying the backup personnel. |
| Time between reminders | The interval of time between reminders. Default: 15 minutes If your choice is not in the list, select the closest value. [Edit the roster](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/update-shift-from-calendar-oncall.md) to update the number of reminders after the schedule is generated. |
| Time before escalation | The interval of time to wait before escalating a task. |