> 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/understanding-schedules.md).

# Understanding Schedules

A Schedule is a "list of times and states that control an item". Schedules are one of the three prerequisites of *Access Groups\**. You must have the Schedules set up before you can link cardholders to Access Groups.

{% hint style="info" %}
**\*Access Groups**

A group of cardholders with identical access criteria. An Access Group also has privileges other than access, including the ability to escort visitors and to do manual overrides.
{% endhint %}

Schedules Types indicate what attribute they relate to. For example:

* **Cardholder Access** type schedules relate to access = when the cardholder has access.
* **Alarm Zone** type schedules relate to Alarm Zones = when items change state.

**Example:** Using Schedules you can set an *Alarm Zone\** to unset at the same time an associated Access Zone changes to free access.

{% hint style="info" %}
**\*Alarm Zone**

A grouping (normally geographical) of alarm points that are set and unset (or in user defined states) at the same times.
{% endhint %}

Before setting Schedules you must ensure Day categories and Calendar days (Day Categories assigned to Calendar) are already set up.

**Note:** Schedules and active Day categories in the default calendar need to stay in sync. To do this, update schedules so that they reflect the active day categories assigned to the default calendar.


---

# 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/understanding-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.
