Early/late window issues

Staff see an early or late check-in message on the Scanner App, even though the booking is valid. This means your check-in timing rules do not allow check-in at that moment. Here's how to find and adjust them.

Symptom

• The Scanner App shows that check-in has not yet opened for that booking.
• The Scanner App shows that the check-in window has already closed.
• The event builder shows a timing warning while you configure the activity.

How the window works

• Early Check-in Window (minutes) opens check-in before the slot start.
• Check-in End Date Calculation Method decides when check-in closes.
• If you use Slot end date, check-in stays open until the slot ends.
• If you use personalized, the close time depends on the Late Check-in Window (minutes) after the slot start.

If something's blocked

A few common causes and how to fix them:

• Attendee arrived before the early window opened — wait until the window opens, or increase Early Check-in Window (minutes) in the activity's check-in settings if you want to allow earlier arrivals.
• Attendee arrived after the late window closed — increase Late Check-in Window (minutes), or switch to Slot end date so check-in stays open until the session ends.
• Timing feels wrong even though the settings look reasonable — re-check the slot start time and campaign timezone before changing any window values.
• Custom end method configured but no late window set — go to the activity's Slots → Check-in Settings and add a late window value.
• Both windows are set to zero in custom mode — set at least one window above zero, or switch to Slot end date instead of the custom method.

Related