EYT Experiences · Operator resources

Arrival & Check-In Coordination

Arrival & Check-In Coordination

Help the Company and assigned Host prepare for expected Guests, arrival exceptions and check-in where supported.

  1. Expected Guest
  2. Meeting point
  3. Arrival review
  4. Exception handoff
Arrival & Check-In CoordinationEYT · B7 · Operating frameworkExpected GuestMeeting pointArrival reviewException handoffExpected Guest → Meeting point → Arrival review → Exception handoff. Conceptual operating sequence;actual workflow availability is confirmed with the Partner.
Expected Guest → Meeting point → Arrival review → Exception handoff. Conceptual operating sequence; actual workflow availability is confirmed with the Partner.

Arrival state is operational information, not admission authority

Help the Company and assigned Host prepare for expected Guests, arrival exceptions and check-in where supported.

Prepare the expected Guest List, named Host, meeting point and provider-confirmed arrival window. A pass or a check-in status does not override venue capacity, identification requirements or the provider’s admission decision.

Prepare the arrival list before arrival

Reconcile the expected people, responsible Host, meeting point and applicable arrival window before the group travels. An organizer’s estimate and a confirmed Guest List can differ. Identify how the team handles a late addition or a Guest who cannot find the location. The useful operational goal is to reduce uncertainty at the handoff, while keeping admission conditions under the provider’s authority.

Treat an exception as a review, not an override

Late arrivals, name mismatches and unapproved plus-ones require a defined escalation path. The Host should know whom to contact and what they can communicate while the issue is reviewed. A check-in record can describe what happened, but it cannot create venue capacity or waive identity requirements. Confirm the supported arrival workflow with the Partner before assuming that a pass has a particular admission meaning.

Illustrative operating scenario

The following is a hypothetical workflow example, not an EYT customer case study. A Guest arrives after the agreed window. The Host records and escalates the situation to the company or venue contact instead of treating a visible pass as a guarantee of entry.

Prepare for split arrivals

Groups do not always arrive together. Identify whether the Host stays at the meeting point, escorts an initial group or hands late arrivals to another contact. That practical decision matters more than an arrival label on a screen. Confirm the venue’s permitted procedure rather than inventing flexibility that the provider has not offered.

Reconcile the attendance record afterward

An expected Guest, someone who reports being nearby and someone the Host has actually seen are different observations. Keep the meaning of each status clear in the supported workflow. If the team later reviews attendance, they should be able to understand what was observed instead of assuming that every prior expression of interest became an arrival.

Commercial boundary

For this workflow, the Company retains clients, suppliers, availability, pricing, approval, relevant payment collection and fulfillment. Its terms govern cancellation and refunds. Keep the tools that already work for you; no automatic integration or replacement is implied.

Nightclub QR check-in and Guest tracking: verify the handoff

Before using a QR arrival workflow, confirm the available Party Pass experience, the authorized check-in role and the fallback for a missing or unreadable code. Keep response status separate from arrival status. A recorded arrival does not grant venue admission or transfer control of ticket inventory to EYT.

Operating framework

CheckpointQuestion to resolveResponsible context
Expected listWhich Guests are expected under the plan?Company and Host
Arrival observationWhat has actually been observed?Assigned arrival Host
ExceptionWho resolves late or unmatched arrivals?Company or venue authority

Questions operators ask

Does this replace our existing operating systems?

No automatic replacement or integration is implied. Confirm the proposed workflow alongside the booking, CRM, payment and supplier systems that already work for your company.

Is every described capability available to every Partner?

No. Current availability and permissions depend on the controlled Partner workflow. Platform-model and future-direction descriptions should be confirmed during onboarding.

Who retains commercial authority?

The responsible company retains pricing, supplier approval, fulfillment and the relevant payment and cancellation decisions under its own terms.