Do not represent every date as a disconnected product. Preserve one reportable offering identity, then use occurrences for the actual dates and ticket options for the purchasable attendance packages. This keeps repeat attendance, revenue, capacity, calendar, and customer history comparable.

Before you beginConfirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.

Step by step

  1. For a one-off event, create one offering and one occurrence with exact start, end, timezone, venue, status, attendee instructions, and calendar visibility. Create one or more event_ticket choices only when pricing or admission differs.
  2. For a repeating after-school program, choose the Afterschool series template or create one recurring offering. Store the normal weekly cadence as an RFC 5545 rule in a valid IANA timezone, then materialize durable concrete dates before date-specific enrollment, check-in, or calendar evidence. Capture school, grade, dismissal method, and authorized pickup only in correctly classified registration questions.
  3. Model holidays, weather closures, rescheduled dates, and one-date overrides with Manage exceptions. The durable instance keeps original_start_at and its stable identity even when its effective time changes; attendee calendars receive the correct EXDATE or RECURRENCE-ID evidence instead of a second unrelated event.
  4. For each camp date, create separate early-arrival, morning, supervised lunch-and-recess, afternoon, and late-pickup occurrences as applicable. The camp template uses stable session kinds early_care, morning, lunch_bridge, afternoon, and late_care with editable local times.
  5. Create morning and afternoon half-day ticket options for their respective occurrences. Create one full-day option that admits morning, lunch_bridge, and afternoon and allocates both half-day pools. Early arrival and late pickup remain independent tickets or add-on entitlements with their own capacity unless intentionally bundled.
  6. Give lunch, early care, late care, rooms, equipment, bus seats, and other scarce resources explicit occurrences or capacity pools. Do not infer entitlement or capacity from overlapping times, ticket wording, or a free-text description.
  7. For a multi-day camp, repeat the daily occurrence pattern under the same offering or use a carefully reviewed recurrence rule. Decide whether the ticket covers one day, selected days, or the whole week, and connect it only to those occurrences.
  8. For a conference, create the conference as the offering and keynotes, workshops, meals, expo blocks, or breakouts as occurrences. Normalize rooms, tracks, speakers, sponsors, and staff. Use selection groups for choose-one or bounded attendee agendas, and give limited sessions their own occurrence-level capacity pools.
  9. Use ticket eligibility and order limits for age bands, membership eligibility, staff or speaker passes, household limits, or other supported rules. Eligibility does not replace legal consent, waiver, or identity verification.
  10. Use calendar views to inspect collisions across events, deliveries, service appointments, work, and custom company entries. The master calendar is an operational schedule; capacity is still enforced by event pools rather than by visual overlap.
  11. Before publication, test each purchasable path and list the resulting occurrences, concrete instances, pools, participant seat count, receipt line, portal schedule, and calendar download. Correct the model instead of adding manual notes to explain inconsistent entitlement.
  12. For a broad recurrence edit, expand the desired local-time series and call the staged reconcile-series operation in batches of at most 500 concrete instances, up to 10,000 for one reconciliation. Reuse the returned reconciliation_id, send a new Idempotency-Key per batch, and set is_final_batch only after the complete replacement window is staged.
  13. Large conferences use the same records as small camps. The builder supports one-at-a-time session authoring and validated CSV import, and the registration definition supports up to 10,000 sessions through paging, search, and bounded batched writes. Never put the whole agenda into one browser request.
  14. A limited conference session receives its own occurrence capacity pool even when no ticket option preallocates it. That unallocated pool lets attendee agenda selection enforce the physical room limit without falsely treating all conference-pass sales as reserved seats in every breakout.
  15. The Event reports screen labels its first 100 session rows as partial. Use the full CSV/export path for a complete large-conference result and preserve occurrence, instance, track, room, participant, ticket, and lifecycle identifiers.
  16. A no_overlap rule compares selections only within the same active selection group. Use separate groups for independent choice sets; do not assume one group’s conflict policy globally blocks every simultaneous session in the offering.

Screen and contract reference

Control or areaWhat it means
One-off patternOne offering with one dated occurrence.
Series patternOne offering with a recurring or multi-date occurrence schedule.
Camp patternMorning, afternoon, full-day, multi-day, extended-care, and resource capacity modeled explicitly.
Conference patternOne offering with many sessions and optional session-specific ticket or capacity rules.
Session kindStable classification such as morning, afternoon, keynote, workshop, meal, or general.
Recurrence ruleNormal repeating schedule definition on an occurrence.
Recurrence exceptionCancellation, reschedule, or field override for one original series date.
Occurrence instanceDurable materialized date used by date-specific enrollment, check-in, and calendar evidence.
Full-day bundleOne ticket option linked to both morning and afternoon occurrences and pools.
General-admission passTicket option admitting multiple conference occurrences.
Master company calendarUnified schedule for event occurrences and other company calendar entries.
early_care / late_careOptional arrival and pickup occurrences with independent entitlement and capacity.
lunch_bridgeSupervised full-day bridge between the morning and afternoon occurrences.
Selection groupMinimum/maximum attendee session-choice rule, optionally rejecting overlapping selections.
reconcile-seriesVersion-checked staged replacement of a recurring series and its concrete instances without fixed-offset DST drift.
Conference session importValidated CSV path for normalized session rows; definitions may span up to 10,000 sessions through bounded pages and batches.
Unallocated occurrence poolSession-level physical capacity available for attendee selection without being preallocated to every pass product.
no_overlap scopeTime-conflict validation among selections that share the same active selection group, not a global offering-wide prohibition.

Expected result

The schedule represents the real one-off, series, camp, or conference pattern; recurrence exceptions preserve history; morning, afternoon, and full-day entitlements consume the correct pools; and attendee calendars show only the dates purchased.

Troubleshooting

  • Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
  • Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
  • Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.