Most event-day disasters aren't event-day problems at all. They're decisions that should have been made weeks earlier — a registration path nobody tested, badges designed the night before, a report that was never set up. A calm event day is the product of a disciplined run-up.
Here's the phase-by-phase checklist we work through for a Cvent launch. Adjust the timing to the size of your event, but keep the order.
8–12 weeks out: foundation
- Confirm the objective, audience and key dates — everything downstream depends on this. If a build partner is doing the registration, capture it all in a written brief at kickoff.
- Map your registration types and paths (attendee, speaker, sponsor, VIP, guest) before building.
- Build the registration site and event website in Cvent Flex; keep the form lean and mobile-first.
- Stand up integrations early (CRM/marketing automation), so data flows from day one rather than being retrofitted.
- Draft the full communications plan: invitation, confirmations, reminders, know-before-you-go, and post-event.
- Decide your reporting up front — what you'll need to answer "did it work?" — so you configure for it now.
4–6 weeks out: launch and promote
- QA every registration path end to end on desktop and mobile — register a test person, complete payment, confirm the email sends — before you open.
- Open registration and send the launch campaign. Early-bird urgency helps.
- Build the Attendee Hub: branding, agenda, sessions, speakers, and the engagement features that fit (the Attendee Hub setup checklist goes step by step).
- Schedule the reminder and nurture emails; set up abandoned-registration follow-up to recover drop-off.
- Confirm venue, AV and suppliers; align on onsite requirements.
2–3 weeks out: momentum and onsite prep
- Ramp reminder communications; announce remaining speakers to keep energy up.
- Plan onsite technology: OnArrival check-in model (kiosks vs staffed), badge design and stock, and session scanning if you're tracking attendance.
- Lock the badge design and print a physical proof — screens lie about scale.
- Build and sanity-check your reporting dashboards so they're ready to populate live.
- Send any pre-event surveys to gather data and build anticipation.
1 week out: freeze and rehearse
- Freeze the registration list for onsite (with a clear walk-in policy for day-of additions).
- Run a full dress rehearsal of check-in: register a test attendee, print the badge, scan into a session — every step, in order.
- Brief the team: who owns registration, check-in, the app, AV, and problem-solving on the day.
- Confirm final numbers with the venue and caterer; print signage and materials.
- Stage and label hardware by station; pack spares and known-good backups for every critical device.
Day before / day of: execute
- Arrive early; set up and test check-in on the real hardware and network.
- Hold a final team and supplier briefing; run speaker sound-checks.
- Open early and watch the first 30 minutes of check-in — that's when you catch the issue that would otherwise repeat 500 times.
- Keep one person on data (duplicates, corrections, edge cases) so the queue keeps moving.
- Fire your Attendee Hub notifications on schedule; keep the agenda current as things shift.
After the doors close: capture the value
- Send post-event surveys while the experience is fresh.
- Pull the reporting — attendance, engagement, pipeline, satisfaction — against your original objective.
- Run a quick retrospective while it's fresh: what to keep, what to fix for next time.
The teams with calm events front-load the decisions. The checklist isn't bureaucracy — it's what lets you host instead of firefight.
The bottom line
A clean launch is a sequence, not a scramble. For the check-in side, read the Cvent OnArrival check-in checklist. Want a second pair of hands for the run-up? Talk to us.