Recurring series can give participants a series portal rather than making every date feel like a completely separate event. This helps returning participants see the dates they are linked to and manage availability where the series allows it.
What the series portal is for
- Showing the participant their series status and linked occurrences.
- Letting participants mark specific occurrences unavailable when the workflow allows it.
- Showing payment and credit information across the series where configured.
- Keeping series-level information separate from one-off event portals.
Before sharing a series link
- Confirm the occurrence dates and public wording are current.
- Check whether participants can choose dates, mark themselves unavailable, or only view confirmed dates.
- Review payment and credit handling so participants are not asked to pay against the wrong occurrence pattern.
Good organiser checks
- Make sure occurrence dates are correct before sharing the series application or portal link.
- Check whether participants can choose dates during application.
- Review unavailable dates before finalising attendance, payment, pitch, or arrival planning.
For recurring events, check both who is approved and which dates each person is approved for.
Managing trader applications for a market or festival?
Collect trader, stallholder, food vendor, exhibitor and trade stand applications, then review documents, track payments, approve applicants and check them in from the same event.
Related articles
Choose Manual or Online Applications
Decide whether participants are added by staff, apply through public forms, or use both routes for the same event.
Manage Event Application Forms
Create, edit, pause, close, and share event-specific application forms for different applicant groups.
Build Event Application Questions
Ask clear questions, collect useful files, and avoid making applicants fight the form before your team even reviews them.

