Sub-events
Sub-events let you model the individual days of a multi-day conference under a single parent event. Each day gets its own programming, venue overrides, and capacity while sharing the parent's currency, timezone, and branding.
Updated May 26, 2026
Sub-events let you break a multi-day event into named child events — Day 1, Day 2, or custom labels like "Welcome night" — each with its own dates, venue, and capacity. They appear as distinct sections on your attendee microsite while staying grouped under the parent in your operator dashboard.
Sub-events require the conference event format and a Pro plan workspace. If either is missing, the Sub-events tab shows a locked state. See Event tiers to upgrade your event format or workspace plan.
When to use sub-events
Use sub-events when the days of your program are distinct enough that attendees need to know which day they are attending, or when you want to cap capacity per day separately from the overall event.
Common cases:
- Multi-day conferences where Day 1 and Day 2 have different programming and attendance
- Multi-night festivals with an optional pre-event welcome night
- Retreats or academies where each day is a standalone track
Creating a sub-event
Open the event's operator page at /{slug}?tab=sub-events and select Add sub-event. Each sub-event has the following fields:
- Title (required) — the name displayed to attendees, e.g. "Day 1: Workshops".
- Day label — a short display label for the schedule (e.g. "Welcome night"). Optional; if omitted, Mercleo Events derives the label from the day number.
- Day number — controls sort order in the microsite and the operator list. Auto-incremented when omitted; you can override it when reordering manually.
- Start date / End date — the date range for this specific day.
- Venue name — defaults to the parent event's venue. Override when a specific day is at a different location.
- Capacity — the attendee cap for this day. Independent of the parent event's capacity.
- Status — one of:
draft,published,cancelled, orcompleted. Onlypublishedsub-events appear on the attendee microsite.
Mercleo Events generates a URL slug for each sub-event automatically, derived from the parent event's slug and the sub-event title (e.g. annual-summit-day-1-workshops). If the slug would collide with an existing event, a numeric suffix is appended.
Sub-events cannot be nested. Creating a sub-event under another sub-event is not supported and will return an error.
What sub-events inherit from the parent
Sub-events are children of the parent event and automatically inherit several values. You cannot override these per sub-event:
- Organization — the owning workspace
- Currency
- Timezone
- Venue type (in-person, virtual, hybrid)
- Venue address, city, and province
- Cover image
- Event settings (registration, check-in, kiosk configuration)
The fields you can override per sub-event are: title, day label, day number, start/end dates, venue name, and capacity.
Dates and timezone display
Sub-event dates are stored in UTC. When you enter a date without a time (a date-only input), Mercleo Events stores the value as UTC midnight — which can display as the previous calendar day in timezones behind UTC.
If a sub-event labeled "Day 2" appears to be dated one day earlier than expected, the root cause is a UTC midnight storage artifact. Mercleo Events renders dates through timezone-aware helpers tied to the parent event's timezone — but if your workspace timezone is behind UTC (e.g. Eastern, Central, Pacific), a date-only input entered as March 5 is stored as March 4 11:00 PM UTC and renders as March 4 in your local time. Always confirm the correct calendar date in the editor after saving.
Reordering sub-events
Drag sub-events into the order you want from the Sub-events tab and save. Mercleo Events rewrites the day number for all children in one operation — you do not need to update each one individually.
The attendee microsite respects the day number order, with ties broken by start date.
Detaching a sub-event
Detaching promotes a sub-event to a top-level event. It clears the parent relationship and the detached event becomes independent — it appears in your main events list, gets its own microsite URL, and no longer inherits any parent values.
To detach, open the sub-event's overflow menu from the Sub-events tab and select Detach from parent. The operation is non-destructive — existing registrations are preserved and transferred to the now-standalone event.
Where sub-events appear
On the attendee microsite, published sub-events appear as distinct sections under the parent event's page, ordered by day number then start date. Sub-events with draft, cancelled, or completed status are hidden from attendees.
In the operator events list, sub-events are hidden. Only top-level (parent) events appear in the main list. To manage sub-events, open the parent event and go to the Sub-events tab.