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

# Static schedules

Static schedules work like regular calendars and do not support recurring shifts. Use simple schedules if you have no recurring pattern in your on-call organization and want to regularly update your schedule.

## Create a static schedule

To create a static schedule, navigate to **On-call schedules,** click on **Create new on-call schedule** and chose **Create static schedule**.

![Week view](/files/-MR4O4ewnWW8Q5J_MxXq)

![Month view](/files/-MR4OUA-Km3koNb4mjMy)

Enter a name for the schedule, pick a timezone (by default the account-level timezone) and choose a default shift duration. The default shift duration is the duration of a shift that is set when you drag a user to the schedule. Follow the instructions below to create shifts.

### Creating shifts

Shifts can be created in two ways:

1. By dragging users from the left and dropping them to the calendar on right
2. By selecting dates on the calendar. To do so, click and drag your pointer over some dates (see below).

![](/files/-MR4Ooe34ut9iiGYGgZq)

As in recurring schedules, only one user per schedule can be on-call at a time. Also note that you shifts cannot be created retroactively.

### Gap detection

If your on-call coverage is 24/7, we recommend to activate gap detection by selecting **Show gaps when saving**. In this case, you will get a warning when you are about to create a schedule with gaps.

![](/files/-MR4QnS7QUwWo7yXu2ms)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/static-schedules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.