Picture an excursion bus leaving a festival for a canyon trailhead, a kirtan in a barn an hour past the last tower, or a retreat lodge whose wifi never reached the check-in table. On Elevate and Amplify events, the BrightStar Organizer app keeps checking people in through all of it. This guide covers how the app gets ready, what it can and cannot decide on its own, and how every device reconciles once the signal returns.
How does a device get ready before the signal goes?
The moment you open an event in the Organizer app — which is also the moment a shared iPad locked to check-in starts up, or a phone picks its entrance — the app downloads a signed list of every ticket for that event: who holds it, which pass it is, whether it is still valid, whether it is already checked in, and which entrances each pass may use. While there is signal the list refreshes every few minutes on its own. Under the event name the app tells you where it stands: “Offline-ready · updated 4 min ago”. Open each door device once while you still have signal, before you head somewhere without it.
What can a device decide with no signal?
Scanning and the guest list both keep working. Against the signed list, the app tells the door:
- 1Valid — the guest is checked in on this device and the check-in waits to sync
- 2Already checked in — with the time and the entrance, if it was before the list was downloaded
- 3Already checked in on this device — a second scan of the same code here
- 4Voided — a refunded or cancelled ticket is refused, as it is online
- 5Wrong entrance — a pass restricted to another entrance is refused at this one
- 6Can't verify offline — check name & ID — a code the list does not know, so the person at the door decides
Why is the list signed and encrypted?
The ticket list holds your guests' names and emails, and it decides who walks in, so it is protected twice. It is encrypted on the device with a key kept in the phone's secure keychain, and it carries a signature from BrightStar: if anyone edits the stored list, the app notices and stops trusting it. The check-ins waiting to sync are encrypted the same way. A list older than three days is not trusted either — reconnect once to refresh it.
What happens when the signal comes back?
Nobody needs to press anything:
- 1The app notices the connection and sends its waiting check-ins in batches
- 2The server records each one with the device's time and entrance
- 3A check-in the server already has is recognised, so a sync cut off halfway is safe to repeat
- 4The guest list switches back to the live server list
- 5The header shows how many are still waiting, and when the last sync finished
What if two devices let the same ticket in?
Two offline devices cannot see each other, so the same ticket can be let in twice — say, once at the Main Gate and once on the excursion bus. When they sync, the first check-in to reach the server stands, and the other is recorded as a duplicate entry with its own time and entrance rather than quietly dropped. The app's offline panel totals them for you — “2 duplicate entries at Excursion bus” — so you can follow up. Assigning one device per entrance keeps this rare.