> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/communication-and-shift-management/schedules.md).

# Schedules

Schedules are the time-based engines of ITOC360. They determine strictly who is on-call at what specific time.

While a **Team** groups your responders together, the **Schedule** defines the rotation logic (e.g., "User A is on duty this week, User B is on duty next week"). When an incident occurs, ITOC360 checks the active Schedule to find the current on-call person and notifies them via their defined Channels.

#### Creating a New Schedule

To set up an on-call schedule for your team:

1. Navigate to Management > **Schedules**.
2. Click the **Create Schedule** button.
3. **Name:** Give the schedule a clear name (e.g., "DBA - Primary On-Call").
4. **Description:** Add context about what this schedule covers.
5. **Time Zone:** Select the operational time zone.
   * *Critical:* All shift start/end times will be calculated based on this setting.
6. **Active:** Enable this to make the schedule eligible for alert routing. Disable it to keep the schedule as a draft or temporarily stop notifications.
7. Click **Create** to finish.

#### Managing a Schedule

After you create a schedule, you can assign who is on-call for a specific time range.

1. Navigate to Management > **Schedules**.
2. Find the schedule you created and click it.
3. On the calendar, highlight the date/time range you want to configure.
4. In the modal that opens, select the **users** for this schedule.
5. Select which of their **Channels** will be included for this schedule.
6. Click **Save** to apply the assignment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itoc360.com/communication-and-shift-management/schedules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.