This article explains how Arketa automatically generates classes and how Booking Windows, Delayed Scheduling, and Member Perks interact. Use this as a guide when troubleshooting schedule visibility and member vs public access.
1. Booking Windows
Booking windows control how far in advance someone can book a class.
Set globally in Settings → Booking Windows
Example: 7-day booking window = clients can only book classes occurring within the next 7 days
Arketa uses booking windows to:
Determine how far into the future to generate recurring classes
Control when classes become bookable
Important: If your booking window is short (e.g., 14 days), your schedule will only be generated that far out, which limits:
How far in advance instructors can see their classes
Ability to request subs or plan time off for classes more than 2 weeks away
2. Delayed Scheduling
Delayed scheduling controls when classes appear on the schedule and become bookable. It is configured at the recurring class series level, not at the service type level.
You set delayed scheduling when creating or editing a recurring class, for example:
Drop classes 7 days before class at 9:00 AM
Drop classes 14 days before class at noon
What it does:
Classes for a recurring series are created in the future, but only surface on the public schedule at the delay time you set
This enables “schedule drops”
3. Member Perks: Early Booking Privileges
Member Perks allow you to give members earlier access to booking than the general public.
Configure in Settings → Member Perks → Early Booking Privileges
Example:
Delayed Scheduling: classes drop 7 days before at 12:00 PM
Early Booking Privilege: 7 days early for members
Result: members can book the class 14 days before at the same release time (12:00 PM)
When a member is logged in, Arketa automatically extends their booking window based on the early booking privilege you’ve set.
Example: Public 1 Week Out, Members 2 Weeks Out
Goal
Public can book 1 week out
Members can book 2 weeks out
Recommended Setup
You have two main options:
Option 1: Extend Booking Windows
Set global booking window to a large value (e.g., 90–180 days)
This allows classes to be generated far in advance
Use Member Perks → Early Booking to give members extra days of booking access
This ensures:
The schedule is built far out (e.g., 6 months)
Members can still book earlier than the public based on your Member Perks
Option 2: Use Delayed Scheduling (Recommended for “Schedule Drops”)
Set global booking window long (e.g., 90–180 days) so classes are generated far into the future
For each recurring class series, set Delayed Scheduling to:
Drop classes 7 days before class at X time
Set a Member Perk → Early Booking Privilege:
“7 days early” for the relevant membership
Result:
Public:
Sees and can book classes 7 days before class time
Members:
See and can book classes 14 days before class time
Their access opens at the same time of day you set in delayed scheduling
“Weekly Drop” Example
Goal: All classes for the following week become bookable at once (e.g., Mondays at 12:00 PM).
Setup
For each recurring class:
Delayed Scheduling:
Drop 7 days before class at **Monday, 12:00 PM**
(or equivalent pattern)
Global Booking Window: Long (e.g., 90+ days so classes can be generated out)
Optional: Member Perk for early booking (e.g., +7 days early)
Behavior
Imagine Monday 1/19 is a class day:
On Monday 1/12 at 12:00 PM
All classes on Monday 1/19 become bookable at once
Time of class does not matter; all 1/19 classes drop at the same time
Classes on Monday 1/26:
Not bookable until Monday 1/19 at 12:00 PM, assuming a 7-day delay
If you give members 7 days early:
Members can book the 1/19 classes starting Monday 1/05 at 12:00 PM
Public can book the same classes starting Monday 1/12 at 12:00 PM
How Booking Windows & Delayed Scheduling Interact
Booking Windows and Delayed Scheduling can interact and sometimes conflict:
If Booking Window is less than the Delayed Scheduling horizon, then:
Classes may appear on the schedule earlier (due to delayed scheduling)
But may not be bookable until the booking window is reached
Example:
Booking Window: 14 days
Delayed Scheduling: 30 days before class
Result:
Class surfaces on the schedule 30 days out
Clients cannot book it until 14 days before the class date
Best Practice
When using Delayed Scheduling, we recommend:
Set Booking Window to a higher value (e.g., 90+ days)
Rely on Delayed Scheduling + Member Perks to control:
When classes appear
Who gets early access
This reduces confusion where classes appear but are not yet bookable.