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

# Add a closure

> Close a day or a run of days for your whole organization, one location or one room, so classes show No class and send no reminders.

A closure is a day, or a run of days, when your organization, one location or one room isn't running: a holiday, a winter break, building work or an early close. Add it once and every class, appointment slot and team practice on those dates closes.

**Go to:** Schedule → More → Closures

**1. Open Closures**

In the menu on the left, click **Schedule**. Click **…** (More) next to **Add event**, then **Closures**. Click **Add closure**.

![The Closures page with the Add closure button outlined](https://mintcdn.com/hurdle/gBHeOoh1zWhu92JU/images/screenshots/schedule-closures-add.png?fit=max\&auto=format\&n=gBHeOoh1zWhu92JU\&q=85\&s=5673a6b04fab1d3c8e6ec0ca7988e7f3)

Add closure is in the top right of Schedule → Closures.

**2. Name it**

Use the name families should read, like "Winter break". Families see `No class — {name}`.

**3. Pick the dates**

Pick the date. Click **Add an end date** for a run of days.

**4. Set the hours**

Choose **All day** (the default), **Closes early** (pick the closing time), or **Set hours** (a window, like 9:00 AM to 12:00 PM). Times are in your organization's time zone.

**5. Choose what it applies to**

Under **Applies to**, choose the whole organization, one location, or one room at a location.

**6. Add a note (optional)**

Click **Add a note for staff**. Only staff see it.

**7. Review and close**

Click **Continue**. The button counts the sessions, like **Continue · 12 sessions**. Check what closes, then click **Close sessions**.

## What happens next

Sessions already on the calendar for those dates close right away. Sessions you schedule later on those dates are created closed. Past sessions stay as they were. Closed sessions send no reminders and count nothing toward payroll.

## Booked appointments

If the closure covers appointment slots that already have bookings, the review asks what to do:

* **Keep bookings** (the default): the booked families still come. The slots take no new bookings and close once their last booking is cancelled.
* **Cancel bookings**: each family gets their credit back and the usual cancellation email.

## Letting families know

Turn on **Email affected families** on the review step. Each family gets one email listing the closed dates, the closure's name and their sessions. It is off by default.

## Common questions

> [accordion] Can I add all the US holidays at once?
>
> Yes. On **Schedule → Closures**, click **Add US holidays**. See [Add US holidays](/docs/schedule/us-holidays.md).

> [accordion] Is there another way to open Closures?
>
> Yes. Go to **Settings**, stay on **General**, find **Schedule**, and click **Manage** on the Closures row.

> [accordion] Should I delete the class instead?
>
> No. Deleting a class time removes every date. A closure skips only the dates you pick, and families see "No class" instead of a missing class.

> [accordion] Can I tell families about one closed session?
>
> Yes. Open the closed session from **Schedule** and click **Let members know**. Its attendees get the usual cancellation email, with the closure's name as the reason.

## Related

* [What a closure changes](/docs/schedule/closure-effects.md)
* [Edit or delete a closure](/docs/schedule/edit-a-closure.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.