---
key: add-a-closure
title: Add a closure
audience: staff
section: operations
routes: ["/schedule/availability/closures"]
permissions: ["schedule.availability.closures.manage"]
features: ["schedule.core"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Close the whole organization or one branch for a holiday, a shutdown or a blackout window without blocking each person's schedule one at a time.
keywords: [holiday closure, shutdown, closed day, blackout, office closed, statutory holiday, shop closed]
related: [add-time-off-for-a-team-member, review-time-off-requests, reschedule-a-work-order]
---

In the sidebar, open **Operations**, then **Availability**, then **Closures**. The page address is `/schedule/availability/closures`.

## Before you start

Your admin has to give your role permission to manage closures. Without it, **Add closure** is hidden. If your role cannot see closures at all, the page says closure management is not available with your current permissions.

## Steps

1. Press **Add closure**. The **Add Closure** panel opens.
2. Under **Closure Scope**, choose **Entire organization** or **Single branch**. You can also choose **Single resource** or **Single crew** to close one lane only; that works like an unavailable block.
3. For a branch closure, pick the **Branch**.
4. Set **Start date** and **End date**. The end date is included. An organization or branch closure always covers whole days.
5. Optional: type a **Leave Type**, for example statutory holiday, and a **Public Label**, which is the name shown on the calendar.
6. Optional: add an **Internal Note** for dispatchers and managers.
7. Press **Create block**.

## What you see

The closure appears under **Operational Closures** with its dates and a chip reading **Organization** or **Branch**. On the **Time Off & Availability** calendar every lane in the closure's scope shows it, and the Schedule treats that time as unavailable.

Press a closure to open it. Change its dates or labels and press **Save changes**, or remove it with **Delete closure**.

**Filters** opens **Closure filters**, where **Branch** narrows the list to one branch. Closures for the entire organization always stay in the list.

## If something looks different

- The list says no closures are set up yet: nothing has been added. Press **Add closure**.
- The note above the list asks you to select a branch: branch closures only show for the branch you pick under **Filters**.
- Work is already scheduled inside the closure window: it stays where it is. Move it from the **Schedule**; see [[reschedule-a-work-order]].