> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedules

> Reusable business-hours calendars that decide when a routing endpoint is open.

## Overview

A schedule is a reusable calendar that answers one question: *is this open at a given moment?* Endpoints reference a schedule to decide whether to dial their destination or fall back.

Each team starts with a seeded **Business default** schedule (Mon–Fri 09:00–17:00 in the team timezone, all Australian states' public holidays excluded). You can edit it, duplicate it, or create new schedules — for example "Showroom hours" or "Steve weekly".

***

## Fields

| Field                   | Type            | Required | Default             | Description                                                                      |
| ----------------------- | --------------- | -------- | ------------------- | -------------------------------------------------------------------------------- |
| Name                    | string          | Yes      | —                   | Schedule name, e.g. "Service drive hours".                                       |
| Timezone                | IANA timezone   | Yes      | team timezone       | Timezone the hours are evaluated in (e.g. `Australia/Sydney`).                   |
| Weekly hours            | per-day windows | No       | Mon–Fri 09:00–17:00 | One or more open windows per weekday. A day with no windows is closed.           |
| Exclude public holidays | boolean         | No       | `true`              | When on, holidays for the selected states are treated as closed.                 |
| Holiday states          | state toggles   | No       | all states          | Which states' public holidays to apply (NSW, VIC, QLD, SA, WA, TAS, NT).         |
| Date overrides          | list            | No       | empty               | One-off closures or special hours for specific dates.                            |
| Set as team default     | boolean         | No       | `false`             | New endpoints, locations, and departments inherit the default unless overridden. |

***

## Weekly Hours

Set open windows per weekday (Monday–Sunday). A day can have multiple windows — for example `09:00–12:00` and `13:00–17:00` to model a lunch break. Removing all windows from a day marks it closed.

***

## Public Holidays

Turn on **Exclude public holidays** and select the states that apply to this schedule. On a public holiday in any selected state, the schedule reports closed for that day. National holidays apply across all states.

***

## Date Overrides

Date overrides handle one-off exceptions for a specific date:

* **Closed** — the schedule is closed that day (e.g. a training day or office closure).
* **Custom hours** — the day uses the override's windows instead of the usual weekly hours (e.g. `09:00–13:00` on Christmas Eve).

Each override is a date (`YYYY-MM-DD`) with an optional reason.

***

## 7-Day Preview

The editor shows the next 7 days of open windows in the schedule's timezone, marking closed days, public holidays, and date overrides — so you can confirm the schedule behaves as expected, including across daylight-saving transitions.

***

## Inheritance

Endpoints do not have to reference a schedule directly. When an endpoint has no explicit schedule, it inherits one in this order:

1. The endpoint's own schedule (if set)
2. The endpoint's **department** default schedule
3. The endpoint's **location** default schedule
4. The team's **default** schedule

Each schedule is self-contained — changing the team default never alters a schedule that was set explicitly elsewhere.

***

## Next Steps

* [Endpoints](/routing/endpoints) — Attach a schedule to a transfer destination
* [Locations](/routing/locations) and [Departments](/routing/departments) — Set default schedules for inheritance