← Back to Event Tech

Case Study 03 · Incentive Travel · Conditional Logic

Top Performers
Incentive Trip

A 175-person luxury incentive trip to Jackson Hole, WY requiring a registration build with advanced conditional logic, spouse/guest gating, activity selection with capacity limits, and a full SOP framework built for future reuse across the program series.

Platform
Cvent Registration + Attendee Hub
Event Type
Incentive Travel — International
Attendee Size
175 + guests
Key Challenges
Guest gating logic Activity selection Dietary & accessibility SOP development Future-proofing
Results
0
Data errors
6
Activities managed
One registration that had to work for two people — in the right order.

The client ran an annual incentive trip series, and this iteration added two new layers of complexity: a spouse/guest registration that had to be completed after (and linked to) the primary attendee, and an activity selection module where each of the 6 excursions had a capacity limit and needed to capture dietary and accessibility requirements per participant — not just per registration.

An additional ask from leadership: whatever was built needed to be documented well enough to hand off to a new team member for the next year's program. The build had to be both functional and teachable.

✦ Guest Gating + Activity Logic
Primary Registrant
Personal Info + Passport
Activity Selection (self)
Conditional: Bringing a guest?
Yes → Guest Link Triggered
Guest: Personal Info + Passport
Activity Selection (guest)
Capacity Check
Build it right. Then document it so anyone can run it next year.

This project was as much a systems design challenge as a Cvent build. Beyond the registration logic, I knew I was building something that needed to outlast my involvement. That meant every decision had to be deliberate and documented in real time.

01
Logic Mapping
Mapped the full conditional tree — every "if bringing a guest" branch, every activity capacity rule, every field required per person vs. per registration.
02
Per-Person Data Capture
Configured activity selection to collect dietary restrictions and accessibility needs separately for the primary registrant and their guest — not as a combined single entry.
03
Activity Capacity Management
Set individual caps on all 6 excursions with automatic waitlist and notification triggers. Configured admin override for manual adds when needed.
04
Attendee Hub Build
Built out the Attendee Hub with personalized itinerary views — each attendee saw their specific activity selections and room assignment.
05
SOP Documentation
Wrote a full build SOP: step-by-step Cvent configuration guide, QA checklist, launch protocol, and post-event reporting runbook — all built to be handed off.
06
QA + Handoff
Ran 20+ test scenarios including edge cases (guest without activity selection, activity at capacity, accessibility flag), then walked the client team through the SOP.
Zero errors. A reusable system. A client who came back.

All 175 primary registrants and their guests completed registration with zero data errors — every activity selection captured per person, every dietary flag accounted for, every passport collected on time. The SOP was used the following year by a new team member who had never touched Cvent, and they launched on their own with one 30-minute onboarding call. The client renewed the program for a third year.

0
Data errors across all registrations
and activity selections
1 call
All it took to onboard
a new team member to the SOP the following year
Year 3
Client renewed the program
the system was built to scale
💡
Capture data per person, not per registration. When dietary and accessibility data is collected at the registration level rather than per attendee, it creates a mess for the catering team. Always build the form to collect what operations actually needs.
💡
Document while you build, not after. Writing the SOP from memory after the event is slower and less accurate. Screenshotting decisions as they're made takes minutes and saves hours.
💡
A well-built SOP is a retention tool. Clients who feel like the process is in their hands — not just yours — trust you more, not less.