Understanding Recurring Events and Generated Sessions
How a single recurring event creates individual, trackable service sessions.
What "recurring" means here
An event configured as recurring (a weekly Sunday service, for example) automatically generates individual service sessions, each with its own date, its own attendance record, and its own entry in Attendance History, rather than one event record that vaguely represents every week.
Why this matters
Because each occurrence is its own real session, you can check in attendance, export a report, or review history for one specific Sunday without it being tangled up with every other week's numbers.
Editing the parent recurring event's details (time, venue) going forward doesn't retroactively rewrite sessions that have already occurred, past sessions keep the details they were created with.
Best practice
Set up your recurring pattern carefully before your first session generates, correcting a recurrence pattern after weeks of sessions already exist means manually fixing sessions individually rather than a single clean change.
Related Articles
Kiosk Mode for Events: Auto-Reset and Offline Support
Turn a tablet at your entrance into a self-service registration station that resets itself between guests.
Creating and Publishing an Event
Set up an event, give it a cover image, and understand what publishing actually does.
Using QR Codes for Event Check-In
The three ways to scan people in, and what to check if a scan doesn't register.
Exporting an Attendance Report
Choose scope and color mode for a PDF export, and how bulk exports differ from a single-session export.