The recurring scheduler creates a whole block of events in one pass instead of adding them day by day. It lives on a client's Calendar tab, so like everything on the calendar it applies to one client at a time.
Open it from a day's + menu under Recurring → Schedule events, or from the Schedule events button at the bottom of the Filters panel.
Schedule recurring events
- Choose an event type: Workout (pick one from your library), Progress photos, Body metrics, or Automation (configure the automation event).
- Under Repeat on, toggle the weekdays the event should land on. At least one is required.
- Pick the starting week. It defaults to the current week, or to the week of the day you opened the scheduler from.
- Set Repeat every and For the next.
- Check the live "Creates N events" summary, then click Create events.
Each created item appears on its day in the client's schedule, exactly as if you'd added it to that day by hand.
Recurring schedule settings
| Setting | What it does | Values | Default |
|---|---|---|---|
| Event type | What gets created on each date | Workout, Progress photos, Body metrics, Automation | Required |
| Repeat on | Which weekdays the event lands on | Monday–Sunday, at least one | None selected |
| Starting week | The first week of the pattern | Any week | Current week, or the week you opened it from |
| Repeat every | Gap between scheduled weeks | 1, 2, 3, or 4 weeks | 1 week |
| For the next | How long the pattern runs | 1 to 52 weeks | 4 weeks |
Weeks run Monday to Sunday everywhere in the calendar, including the Repeat on day picker.
How past dates are handled
Dates that have already passed are skipped. If the starting week is in the past, scheduling begins from the current week, which shortens the run. Any individual date earlier than today is dropped.
If every date in the pattern is in the past, nothing is created and you'll see "All scheduled dates are in the past. Please select future dates."
Things to watch out for
The "Creates N events" summary counts every slot in your pattern and doesn't subtract skipped past dates, so the number actually created can be lower than the summary showed. Check the calendar after saving if the count matters.
Recurring automation events are judged against the client's own timezone: occurrences before today in their timezone are skipped, and if all of them are in the past the request is rejected.
There's no way to edit a recurring block as a group. Each occurrence becomes its own item on the calendar, so removing or moving one leaves the others alone — and undoing a run means deleting the items individually.