Six events for one conference
Litware runs a hybrid conference: one keynote with hall capacity of 2,500, five breakout sessions seating 200 each, and a virtual track streamed in Teams. Registration is expected to reach 3,000 and nobody knows which breakouts will be popular. The events team built six separate events - one per room - each with its own registration form and its own confirmation email. Symptoms now: the virtual track landing page says registration is not available; 400 people are registered for two breakouts that run at the same time; and there is no way to report how many of the 3,000 actually attended the keynote.
1. Argue for the event structure you would rebuild to, and state the one case in which you would keep a separate event.
Read the worked answer
Recommended: one event, six sessions
The keynote, the five breakouts and the virtual track are one conference with one audience, one brand and one agenda. Model that:
- One event holds the shared identity, dates, registration form, confirmation, event portal page and consent capture.
- Sessions within it carry the rooms, times, speakers and per-session capacity of 200. Session registration is what enforces breakout seats and produces the waitlist.
- One attendee record per registrant means attendance, no-show and session uptake are all reportable from a single registration entity instead of being stitched together from six.
What the six-event build costs you: six chances to capture consent differently, six confirmation templates to keep in sync, a person who attends the keynote and a breakout counted as two unrelated records, and - as has already happened - one event left unpublished while the others went live.
The exception
Keep the virtual track as a separate event only if it has materially different registration rules: a different audience, different consent, different pricing, or a Teams webinar registration flow that must issue its own join links to a distinct population. Different rooms are not a reason; different populations are.
2. Diagnose 'registration is not available' on the virtual track and the 400 double-booked breakouts, and say what you can and cannot prevent structurally.
Read the worked answer
'Registration not available' is a state problem, not a bug
Work through the gates in order: the event must be published; registration must be open with a valid registration start and end date; a registration form must be attached and published; and if the track is a Teams webinar, the webinar integration and its own publish step must be complete. In a six-event build the most likely cause is simply that this one was never published - the other five were. Confirm each gate on the record rather than guessing, and add a go-live checklist that runs per event.
Double-booking
Two breakouts at the same time with 400 overlaps means session times were entered without a conflict check. Do not rely on the platform to hard-block overlapping session registrations - verify the behaviour in your version, but design so the question does not arise:
- Model the agenda as non-overlapping tracks with clear start and end times.
- Limit each registrant to one session per time slot through the registration form logic, and use session capacity plus waitlist rather than over-booking.
- Provide a self-service session change path before the event, otherwise 400 people will solve it by not attending.
What you cannot prevent
People registering for sessions they will not attend. That is a capacity-planning problem solved with waitlists, reminders and check-in data, not with the registration form.
3. Litware's COO asks for a single number: how many of the 3,000 attended the keynote? Explain how you would produce it and where the number will be soft.
Read the worked answer
Producing the number
- Attendance is a session-level fact. In-person keynote attendance comes from check-in at the session, captured through the event check-in experience; virtual attendance comes from the Teams attendance report for that session.
- The two sources have different keys. In-person check-in is keyed to the registration record; the Teams report is keyed to email or display name. Reconcile on email, and expect a small unmatched tail from people who joined with a personal account.
- Report registrations, session registrations, check-ins and virtual joiners as four separate numbers with a footnote, then give the COO the headline as check-ins plus unique virtual joiners, with the reconciliation tail stated.
Where it is soft
- Virtual attendance is duration-based: someone who joined for 90 seconds counts as a joiner unless you apply a minimum-duration threshold. Pick one and disclose it.
- In-person check-in depends on scanning compliance at the door; a jammed queue at 9:00am is a data-quality event, not an attendance event.
- Room capacity of 2,500 against 3,000 registrations means some attendees were always going to be turned away - so 'attended' capped at 2,500 in person by definition, and the overflow shows up as virtual joiners or no-shows, not as a shortfall in the registration number.