> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/schedules/creating-a-new-schedule.md).

# Creating a new Schedule

Perform the following procedure to create a new Schedule:

1. Click the **New Schedule** button on the Viewer Navigation Panel, and then the type of Schedule you require, (i.e. Access Zone, Alarm Zone, Cardholder Access, HV/LF, Notification or Output Schedule).

   **Note:** The Notification Schedule type only appears as an option if your site is licensed for Notifications.

   The new Schedule is added to the Viewer Navigation Panel, and the Schedule Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d84b43e0b1356dddf7e5fb5bb7c7d102aeb26efa%2Fscheduleconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Schedule, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Schedule to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-5ea28b89c753564de542b1b9c1b328d1e0fc8c60%2Fselectdivisionforviewer_popup.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Schedule at a later stage.
5. Click the **Close** button.

   The Schedule Configuration pop-up closes.

   There are two tabs, (i.e. **Schedules** and **History/Notes** ). The **Schedules** tab displays by default.

   The "Schedule Times" section provides a grid where 'From' times and states can be entered/edited for each Day Category. Initially the grid will be blank.
6. Add and remove any other Day Categories required for this Schedule. See [Adding Day Categories to Schedules](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/schedules/adding-day-categories-to-schedules.md) and [Removing Day Categories from Schedules](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/schedules/removing-day-categories-from-schedules.md) for procedure.

   **Note:** Ensure you are consistent in the use of day categories between calendars and schedules.
7. Add, remove or change the times and states of each Day Category as required. See [Changing times and states within Schedules](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/schedules/changing-times-and-states-within-schedules.md) for procedure.

   **Note:** If the times and states for one Day Category are required for another Day Category, these can be duplicated (copied) to another Day Category to speed up the process. See [Duplicating Day Category entries](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/schedules/duplicating-day-category-entries.md) for the procedure.
8. The "Scheduled Items" section shows a list of items that the schedule is attached to. The items listed will depend on the Schedule type, as follows:

   <table><thead><tr><th width="150">Schedule Type</th><th>Description of Listing</th></tr></thead><tbody><tr><td>Cardholder Access</td><td>Access Groups that have some zone access controlled by the Schedule.</td></tr><tr><td>Access Zone</td><td>Access Zones associated with the Schedule.</td></tr><tr><td>Alarm Zone</td><td>Alarm Zones that are controlled by the Schedule.</td></tr><tr><td>Output</td><td>Output items that are controlled by the Schedule.</td></tr><tr><td>Notification</td><td>Cardholders that have the Schedule on a filter/schedule assignment.</td></tr><tr><td>HV/LF</td><td>Alarm Zones (assigned to a Fence Zone) associated with the Schedule.</td></tr></tbody></table>
9. Click the **View Calendar** button.

   The Calendar View pop-up appears.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f3856043b37d4d4a93834d2e9ab09f53b9400744%2Fcalendarview_popup.png?alt=media)

   This screen is "read-only" and displays the following:

   * Weekly view of the states in existence for the Schedule
   * Each day will display the active Day Category
   * Scroll mechanism(s) to change the active week view (Monday will always be the left-most column)
   * A **View Calendar** drop-down to view any Special Calendars that may exist

     **Note:** Special Calendars do not appear in the **View Calendar** drop-down for Notification Schedules.
   * An ability to quickly find the next occurrence of a particular Day Category

   **Note:** If state changes are so close together due to there only being a short interval between them, the time cannot be displayed legibly inside the interval. Therefore, by hovering the mouse over the day, a summary of the times and states for that particular day display.
10. Click the **Close** button.

    The Calendar View pop-up closes.
11. If you want to record any note(s) about the Schedule, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
12. Click the **Save** button.

    A new Schedule has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Schedules**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Schedules.

**Note:** If a schedule has items which depend upon it for proper operation, you are prompted for confirmation and cannot delete it even when **Yes** is clicked. A message explaining why you cannot delete the schedule displays.
{% endhint %}

{% hint style="info" %}
**Duplicating Schedules**

Operators privileged to create schedules can also duplicate schedules, which makes the task of setting up multiple schedules that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% endhint %}


---

# 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://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/schedules/creating-a-new-schedule.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.
