> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/workspace/business-calendars.md).

# Business Calendars

Business Calendars define the working schedules that control two things in Siit: when SLA clocks run, and who requests get routed to.

Instead of a single workspace-wide schedule, you can create multiple calendars — one per team, location, or shift — and attach each one where it applies.

<figure><img src="/files/822TnlqRmIvT9INOT0ks" alt=""><figcaption></figcaption></figure>

### SLA timing

Each SLA Rule references a Business Calendar. SLA timers only count down during that calendar's working hours — evenings, weekends, and public holidays don't count toward breach. Different rules can use different calendars: your EU team's SLAs run on CET hours, your US team's on ET hours, your P1 incidents on a 24/7 calendar.

<figure><img src="/files/f0jYAObi27fhkRThFykw" alt=""><figcaption></figcaption></figure>

### Availability-based routing

Admins are assigned a Business Calendar within an inbox, defining their working hours in that context. Siit routes requests only to admins currently within their calendar's active hours — not to someone who clocked out two hours ago.

Because calendars are set at the inbox level, the same admin can operate on different schedules in different inboxes. An admin covering EU hours in the IT inbox can follow a different calendar in an on-call inbox.

For how calendars interact with inbox assignment methods, exclusions, and routing rules, see [Assignment](/request-management/assignment.md).

<figure><img src="/files/dKns80GZ6XYDhIHCh9q2" alt=""><figcaption></figcaption></figure>

***

*Related:* [*SLAs*](/service-catalog/slas.md) *·* [*Assignment*](/request-management/assignment.md)