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

# Operations

> Day-to-day scheduling, bookings, classes, areas, instructors, and tasks live under Operations.

Operations is where you run the gym day to day. The same calendar shows classes, bookings against areas and instructors, and instructor time off, and the same booking dialog records reservations whether they happen at reception, on the public site, or over the phone.

The pages in this section split into three groups.

**Scheduling and reservations**. [Schedule](/operations/schedule) is the unified day/week calendar. [Bookings](/operations/bookings) and [Classes](/operations/classes) are the list views with tabs, search, and bulk actions. [Events](/operations/events) covers one-off ticketed happenings - workshops, tournaments, parties - with their own tickets, promotion, and check-in. [Booking policies](/operations/booking-policies) configures payment timing, cancellation refunds, lead times, and check-in enforcement.

**Resources**. [Areas](/operations/areas) covers your physical spaces (courts, rooms, fields), grouped by gym and ordered by drag-and-drop. Instructors live under **Staff > Instructors** in the admin; see [Instructors](/operations/instructors) for what you configure there and how it shows up on the schedule.

**Tasks**. [Tasks](/operations/tasks) is a simple to-do list scoped to your organization, with status tabs (to do, in progress, completed), priorities, due dates, and optional links to a contact, gym, or booking.

## How the pieces fit together

A booking is the unit of revenue. Every reservation - whether a member joins a class, books an area, or buys a personal-training session - becomes a booking row with a transaction attached. The schedule page reads bookings, classes, and instructor time off for the visible date range and renders them as colored blocks on the resource grid.

Classes are scheduled occurrences with capacity and instructors. When a member books a class, a booking row is created against that class. If the class fills up, the waitlist takes over (see [Booking policies](/operations/booking-policies) for the claim window).

Events are one-off ticketed happenings. When a member buys an event ticket, each seat becomes a booking row carrying the event and ticket type. See [Events](/operations/events) for tickets, promotion, and check-in.

Areas and instructors are the bookable resources. Areas have operating hours and a price per hour; instructors have a bookable flag, hourly rate, and operating hours. The schedule shows one column per resource in day view; the booking dialog asks you to pick one (area, instructor, or class) when you create a booking.

A [booking policy](/operations/booking-policies) decides the rules that apply to any given booking - when payment is required, whether check-in is enforced, refund tiers on cancellation. Policies can be org-wide or scoped to a gym, area type, class type, instructor type, or plan.

## Where to start

If you're setting up a new gym, the usual order is:

1. Create your gyms under **Settings > Clubs**.
2. Add area types and areas under [Areas](/operations/areas).
3. Invite instructors under **Staff > Instructors**; see [Instructors](/operations/instructors).
4. Configure [booking policies](/operations/booking-policies) for payment timing and cancellation.
5. Open [Schedule](/operations/schedule) and start adding classes and bookings.

If you're running an established gym, you'll mostly live on the [Schedule](/operations/schedule) page, with [Bookings](/operations/bookings) and [Classes](/operations/classes) as drill-down lists.

## Related

* [Members](/members/overview) - The contacts you book classes and sessions for.
* [Memberships](/members/memberships) - Plans that cover bookings without per-visit payment.
* [Payments](/billing/payments) and [Transactions](/billing/transactions) - The money side of every booking.
* [Check-in models](/reference/check-in-models) - Pick the right entrance flow before configuring policies.