> 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/quick-tips-for-working-with-schedules.md).

# Quick Tips for working with Schedules

* Schedules allow you to set up a list of times and states that control an item or a number of items within a zone or group.
* Different schedule types control different items and therefore have different states that can be set, (e.g. a Cardholder Access schedule has grant or deny states, whilst an Access Zone schedule has multiple states; free, secure, code, dual auth options, as well as whether a PIN is needed or not).
* Before setting Schedules, ensure Day Categories and Calendar Days (Day Categories assigned to Calendar) are already set up.
* Hovering over a tab displays a tool tip. For the **Schedules** tab, a summary of the number of items on that tab; and for the **History / Notes** tab, the date and time the Schedule was last modified, and who by.

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

### Creating and editing a Schedule

* The **Add Day Category** button allows you to select a Day Category and to configure the states and times.
* Schedules with unsaved changes display in the Navigation Panel in **bold** and have a **\*** at the end of their name.
* To edit existing Day Categories, clicking on the state/time bar reveals the existing configuration.
* Clicking the **Duplicate** button ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-15b0a3b4c3d8f55433c6554f007a3b81a6736d74%2Fduplicateentries_button.png?alt=media) next to a Day Category already on the Schedule allows you to add a Day Category and have its states and times set the same as the existing Day Category. This is a quick way of setting up a number of similar Day Categories.
* The **Add a state change** button allows you to add several state changes within the 24 hour period.
* Clicking on the state reveals a list of available states.

### Cancelling Untimed Overrides

A Cancel Untimed Override entered on a Schedule acts to cancel any non-timed override in existence for all items controlled by that Schedule.

This option is available on Access Zone, Alarm Zone, HV/LF or Output type Schedules, and appears in the list of states, (i.e. via the **Add a state change** button).

### View Calendar

The **View Calendar** button presents the Schedule view of the Calendar providing the ability to check how the configured Schedule is applied on a week-by-week basis.

### More information

For more information, refer to the topic *"Schedules"* in the Gallagher Command Centre Online Help.


---

# 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/quick-tips-for-working-with-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.
