> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/settings/special-event-dates.md).

# Special event dates

Special Event Dates lets you mark days that affect traffic management work, such as public holidays, anniversary days, daylight saving changes or the days cruise ships are in port.

To open it, go to **Settings** → **Special Event Dates**.

## How special event dates appear

* Special event dates appear with a light pink background on calendar date pickers.
* The event's category and name are displayed in the day header on the [Calendar](/eboard/calendar.md).

## Categories

Events are organised into categories, each with its own colour. Every organisation starts with the **NZ Public Holidays** category, which includes national public holidays, regional anniversary days and daylight saving changes.

Each category lists its events with the **Event Name** and the **Date(s)** it falls on.

## Keep public holidays up to date

Click **Update Public Holidays** to load the latest New Zealand public holiday dates.

## Add your own category

1. Click **Add Category**.
2. Enter a name and choose a colour (for example "Cruise Ship").
3. Add each event with its name and date(s).
4. Click **Save**.


---

# 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://wiki.roaddirect.co.nz/eboard/settings/special-event-dates.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.