How to manage multiple check-in devices at the same time

At big events, a single device cannot keep up with the queue. Baila supports multiple simultaneous check-in devices with no conflict: every scan goes straight to the backend in an atomic transaction, and a ticket can only be validated once.

A typical setup

Setting it up, step by step

1. On the event page, go to the Check-in team section. Invite each person by email (the Invite button) or generate an Invite code to share in the WhatsApp group. Each of them signs in with their own Baila account when they accept the invite.
2. Each person installs the Baila app and signs in with their account. They all see the same event.
3. On the day, each device opens the event and starts scanning — no extra coordination needed.

How the system prevents duplication

For every QR Code scanned, the app sends a request to the backend, which runs inside a Postgres transaction:

1. Locks the ticket's row
2. Reads the current status
3. If VALID → changes it to USED and returns success
4. If USED → reports that the ticket has already been used, with the time of the first check-in

That stops two simultaneous confirmations: the second one hits the USED condition and is rejected.

The dashboard report

During the event, the dashboard updates in real time (every 5 seconds):

• Total check-ins done
• Check-ins per tier
• The latest check-ins, with name, tier, and time

Good practice for big events

• Split the queues by tier (floor, box, VIP) — it avoids confusion and speeds things up
• Test the local network beforehand (the venue's Wi-Fi or mobile data) — if the signal is poor, use offline mode
• Keep 1 spare device — in case a phone freezes or runs flat
• Give the scanners headphones — the audio feedback (a "green beep" = valid) speeds things up

Related articles