> 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/quick-tips-for-adding-day-categories-to-schedules.md).

# Quick Tips for adding Day Categories to Schedules

* Clicking the Add Day Category button presents a browse tool of available Day Categories, (i.e. unused Day Categories) to select from.

  **Note:** If all Day Categories are added to the Schedule, the browse tool will be blank.
* The state/time bar represents scheduled times within a 24 hour cycle, (i.e. 00:00 - 24:00). It is close to accurate but will be scaled according to available space. It can be used as an indicator of obvious errors in the data entry and a quick visual comparison between the different Day Categories.
* Clicking on the state/time bar reveals a pop-up which provides detail of the states set for the Day Category. From here you can alter states for different times during the 24 hour cycle.
* The state and time period it is scheduled for will appear as a "Tool Tip" when you hover the cursor over the state/time bar, as shown below:

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cf23114e925f7d34cfe691c10883ffd0de8fc0af%2Fstatetime_tooltip.png?alt=media)
* A **Cancel Untimed Override** state does not have a time interval. So it can easily be recognised as a cancel override, it appears as a black marker on the state/time bar, as shown below:

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


---

# 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/quick-tips-for-adding-day-categories-to-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.
