> For the complete documentation index, see [llms.txt](https://btwb.gitbook.io/btwb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btwb.gitbook.io/btwb/admin/scheduling/the-attendance-log.md). # The Attendance Log This article explains the Attendance page — the org-wide record of every class check-in and appointment, with its filters and CSV export. ### Overview **Gym → Attendance** is the read-only history of who attended what. It has two tabs — **Classes** and **Appointments** — each listing attendance records with the client, date and time, status, the class or appointment details (type, location, coach), and the membership plan used. Check-ins themselves happen elsewhere (the [Class Reservations](/btwb/admin/scheduling/class-schedules/managing-reservations-and-check-ins.md) page, the [Appointments](/btwb/admin/scheduling/appointments.md) page, or member self check-in from the app); this page is where the results land. ![The Attendance log with its status filters](https://283006627-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZrefv5JliAQavbeRiIvd%2Fuploads%2Fgit-blob-44c17dbe17930e7802f6aadd323e42894824448b%2Fattendance-log.gif?alt=media) *** ### Reading the Log Each row's **Status** tells the story of that visit. The statuses differ slightly between the two tabs: * **Reserved** (Classes) / **Booked** (Appointments) — booked, hasn't happened yet. * **Waitlisted** (Classes only) — waiting for a spot. * **Checked In** — attended. * **Late Canceled** — canceled inside the late-cancellation window (your policy decides whether that used a credit or charged a fee). * **Canceled** (Appointments only) — the booking was canceled. * **No Show** — reserved but never arrived. **Unpaid** isn't a status of its own. A visit that isn't covered by a membership plan (for example, when staff reserved someone with no covering plan or credits) shows **Unpaid** under **Membership Used**, and a red **$** icon appears next to its status once it's checked in, late canceled, or a no-show. To find these visits, pick **Unpaid** in the Status filter. *** ### Filtering and Exporting * **Search** by client name or email to see one person's full history. * Filters: **Date** range, **Status**, **Class Type** (or Appointment Type on the other tab), **Location**, and **Coach**. The Type, Location, and Coach filters only appear when you have more than one to choose from. * **Export List** emails you a CSV of the current tab and filtered view. *** ### Notes for Admins and Coaches * A client's personal attendance history (with totals) also appears on their **client detail page**, which links here pre-filtered to them. * On plans with limited credits, a credit is used when the client **reserves** (or books), not when they check in. Canceling before the late-cancellation window gives the credit back; late cancels and no-shows keep it used unless your [Class Settings](/btwb/admin/scheduling/class-schedules/class-settings.md) (or appointment settings) waive it. Check-in only records attendance. * The **Attendance** permission is view-only — a good fit for front-desk staff who need visibility without edit access. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://btwb.gitbook.io/btwb/admin/scheduling/the-attendance-log.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.