How to set up an event in Ticket Validation

Each step maps to one screen in the drawer:

• Event details: name, location, description.
• Date & time: single-day or multi-day, calendar dates, default start and end times. Times are entered in the location’s time zone (the UI shows a reminder).
• Types: which ticket types from your account apply to this event.
• Validation: who scans at the door, how much of the ticket pool they may access, and default validation window versus custom scanning times.

After the event exists, you add tickets via import from the event (see step 5). Scanning behavior on phones is covered in How to use the mobile app.

From Events, start Create event. Give the event a clear name, pick a location from the list, and add a short description if you want.

Choose Single-day or Multi-day, then pick the date or date range. Set default start time and default end time for the event runtime. The form expects times in the venue’s time zone, not your laptop’s.

Multi-day events get one row per calendar day so each show night can have its own start and end if needed.

Default validation scanning times usually follow these event times until you change them on the Validation step. Fine-grained rules (different windows per ticket type or source) are configured there as well.

Select every ticket type that should exist for this event. Types are defined under account Ticket types and tied to sources; you are only choosing which of those rows apply here.

Examples:

• Regular / General Admission
• VIP
• Staff

If a type is missing, go back to account setup and create it, then return to this step.

The last wizard step is labeled Validation in the app. Here you:

• Add validators (users of type Validator from your account) and choose full access or restrict by ticket type or ticket source. The UI helps you see whether the selected types are covered.
• Set whether scanning hours follow the event schedule or use a custom validation window, and add exceptions by type or source when needed.

This guide stays focused on where those controls live during event creation. Exceptions, custom windows, and scanner messaging are all handled in the same Validation step.

When the event is saved, open it from the event list and use Import tickets. Upload a CSV, choose the ticket source, and map columns to the system fields. Sources must already exist under account Ticket sources.

Column formatting, exports from third-party platforms, and cleaning data before upload are covered in How to prepare tickets for import. Dedicated guestlist flows are described in How to create and import a guestlist.

The site also hosts a sample CSV and barcode format reference if you need them during mapping.

1. Confirm account-level sources, types, locations, and validator users.
2. Run the create-event wizard through all four steps and save.
3. Import ticket files and fix any mapping errors before doors open.
4. Adjust validation exceptions if a ticket group needs different scanning hours.
5. Have validators sign in on devices using mobile app guidance.

• Cannot select a location: create or fix the venue under Locations first.
• Times look wrong: check the location time zone, not only the clock values.
• Missing ticket type in the list: create the type under account Ticket types, then edit the event and add it.
• Submit blocked on validators: ensure every selected ticket type is covered by someone’s access rules, or add a full-access validator when policy allows.
• Validator overlap error: that person is already assigned to another event whose dates overlap this one. Adjust dates or assign someone else.
• Import fails or wrong columns: follow prepare tickets and re-export from your ticketing system.