← Back to Event Tech

Case Study 02 · Leadership Meeting · Session Management

Annual Leadership
Summit

A 400-person annual leadership meeting in Vail requiring separate registration paths for internal employees and external clients, session-based agenda building, and a personalized Attendee Hub experience for both employee and client attendee types.

Platform
Cvent Registration + Attendee Hub
Event Type
Leadership Meeting — Domestic
Attendee Size
400 — Employee + Client
Key Challenges
Session management Capacity limits Employee/client split Attendee Hub personalization Real-time reporting
Results
12
Sessions managed
3
Concurrent tracks
Two audiences. Twelve sessions. Three rooms running simultaneously.

The client's annual leadership summit brought together 250 internal employees and 150 external clients in the same venue — but the two groups couldn't have the same registration experience. Employees registered through an internal link with company SSO and saw the full agenda including internal-only sessions. Clients registered through a public link and saw only client-appropriate content.

On top of the attendee separation, the event had 12 breakout sessions across three concurrent tracks, each with a capacity limit. Attendees needed to build their own agenda at registration, and the system had to enforce caps in real time and waitlist automatically when sessions filled.

The final layer: the Attendee Hub had to deliver a personalized experience to both attendee types — employees saw their full internal agenda and session notes; clients saw a curated view with no access to internal content.

✦ Attendee Separation Architecture
Employee Link
SSO Validation
Full Agenda View
All 12 sessions visible
Client Link
Public Form
Filtered Agenda View
8 client sessions only
Session Selection
Capacity Check
Auto-Waitlist if Full
Mapping every session, every cap, every communication path.

The key to making this work was treating the session configuration as its own project within the project. Each of the 12 sessions needed its own capacity setting, waitlist trigger, confirmation messaging, and Attendee Hub visibility rule. I built a session matrix in a spreadsheet first — getting client sign-off on every detail — before touching Cvent.

01
Session Matrix Build
Created a full spreadsheet mapping all 12 sessions with capacity limits, attendee type visibility, waitlist rules, and assigned check-in point.
02
Dual Registration Paths
Configured employee and client registration as separate event paths with shared backend reporting but distinct form flows and visible session sets.
03
Capacity + Waitlist Logic
Set per-session caps with automatic waitlist enrollment and triggered emails when spots opened up from cancellations.
04
Attendee Hub Configuration
Built dual Attendee Hub views — employees accessed full session content and speaker materials; clients received a curated agenda with filtered visibility. Personalized itineraries pulled each attendee's confirmed session selections automatically.
05
Staff Training
Trained the client team on Attendee Hub admin controls — how to push content updates, manage session visibility, and send targeted messages to each attendee type.
06
Live Dashboard
Set up real-time reporting dashboards so the client team could monitor session fill rates and waitlist movement throughout registration.
All sessions filled. Zero capacity overruns. Clean data throughout.

All 12 sessions filled to capacity through the automated waitlist system — no manual intervention required. The employee/client separation worked flawlessly, with zero client registrations appearing in internal-only session reports. The Attendee Hub was accessed by 94% of attendees before arrival — reducing day-of questions to the event team by an estimated 60%.

12/12
Sessions filled to capacity via
automated waitlist
400
Attendee Hub pre-event engagement rate
agendas accessed before arrival day
0
Client records appearing in internal-only
session data
💡
Build your session matrix before you build in Cvent. Having every session, cap, and rule documented and approved before touching the platform saves hours of re-configuration.
💡
Train onsite staff on the waitlist flow specifically. Day-of swap requests always happen. Teaching the client team how to push real-time Attendee Hub updates day-of means they can handle minor changes themselves without calling you.
💡
Test the employee/client separation with real email addresses. The forms look identical when you're building them — only a live test from each registration path confirms the data routing is truly separate.
← Previous
President's Club — Palmetto Bluff