Use this checklist before opening registration, announcing your event, or starting the first live session. Test the complete attendee journey, not only the organiser dashboard.
Public site and registration
Open the event while signed out and check the landing page, navigation, schedule, speaker pages, registration calls to action, legal links, and mobile layout.
Confirm the event domain, default language, timezone, date formats, and public event status.
Complete a test registration and make sure the attendee receives the expected confirmation and can sign in to their account.
Tickets and payments
Confirm every ticket that should be available is active, has the correct price and currency, and appears at the right time.
Check ticket access, expiry, quantity, availability, and attendee restrictions against the talks and pages the ticket should unlock.
For paid tickets, confirm a supported payment provider is connected and test the intended payment path before selling.
Talks, speakers, and video
Make sure required speakers and talks are active, each talk is scheduled, and ticket access is correct.
Check each talk's live, pre-recorded, replay, or external delivery settings and resolve dashboard warnings.
Use the talk-row Preview action to inspect attendee-facing talk pages. For live delivery, confirm the expected Launch Webinar, Open Studio, or provider-side start path and copy backup broadcast links where needed.
Emails and attendee experience
Review which attendee, speaker, host, sponsor, or affiliate templates are active and when they are scheduled to send.
Check the schedule-selection rules, mandatory talks, reminder volume, and the difference between registered attendees and completed orders.
Review any offers, giveaways, feedback questions, chat, Q&A, polls, or downloadable media that attendees should use.
Team and contingency checks
Confirm team members have only the permissions they need for content, attendee check-in, reporting, emails, and financial actions.
Make sure hosts, speakers, and moderators know where to join and who to contact if the primary delivery path fails.
Keep provider access and backup links with the people responsible for running the event.
