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

# Set up recurring event registration

> Create weekly or monthly recurring events, configure admission for each occurrence, and distinguish session bookings from multi-visit memberships.

Use **Repeating Event** for a regular series of the same activity. The template starts weekly with General Admission. A recurring schedule creates occurrences; a purchase does not automatically grant entry to every occurrence.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | Weekly |
| Admission | Paid tickets |
| First offer | General Admission · suggested price 25 in your site’s currency |
| Capacity | 100 |
| Attendees choose a time | Not enabled |

These are editable suggestions, not recommended prices or venue limits. Replace the dates, price, and capacity with your own. See [how onboarding works](./overview#complete-onboarding).

## Choose the onboarding answers

Open **Create Event** in the selected workspace.

1. Choose **Browse more templates → Advanced → Repeating Event** and name the series.
2. Set **Weekly** and choose the weekdays, or **Monthly** for the same date each month. Set the first occurrence’s start/end and **Repeats until**.
3. Choose the admission method and set the price and capacity. Use **Continue later** to review the generated schedule in the editor.

<Note>**Create my event** may publish immediately when the requirements are met. Use **Continue later** to finish setup as a draft. Review any plan or publishing message before sharing the event.</Note>

## Finish the event settings

| Where to go | What to configure |
| - | - |
| **Dates & Times** | Review [recurrence controls](/event-management/datetime#recurring), series end, and any dates requiring changes. |
| **Tickets** | State what one booking includes and check the quantities and purchase limits on individual occurrences. |
| **Individual dates** | Use [date-specific tickets](/event-management/day-specific-tickets) when an existing date needs its own offer; confirm whether it uses shared or custom tickets. |
| **Memberships** | For repeat access, configure a [membership](/memberships/overview), eligible events, and total/per-event visit limits. |
| **Widget** | Review how upcoming dates appear and how visitors choose a date using [display settings](/branding-and-design/display-settings). |

## Recurrence is not a subscription

Weekly or monthly describes the event schedule, not a recurring payment. A Class Pass or Season Pass ticket name alone does not grant multi-date admission. Configure entitlements deliberately and test them. For several selectable times on a day, use the full editor’s [time-based schedule](/event-management/datetime#time-based); the general Repeating Event onboarding card does not display the tour-specific time-slot question.

## Check the attendee experience

* Compare at least two occurrences, including dates near the series end.
* Confirm the attendee chooses the intended occurrence and sees its date on the booking.
* If using a membership, verify reservation requirements and visit limits separately.

Review the event’s saved status and [publish/share controls](/event-management/manage-events) when it is ready. Return to [all event types](./overview) to compare starting points.


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