The day itself, at the door, with the queue outside: that is when a tool is judged. The Open the door screen is built for that and nothing else. You reach it from the Check-in tab of your event, and it is meant for a phone.
Scanning with the camera
- Open your event, Check-in tab, then Open the door.
- Tap Turn on the camera. Your browser asks for permission once.
- Hold the ticket QR inside the gold frame. The code is sent on its own, you press nothing.
The ticket works equally well on the attendee's phone screen, on the printed PDF, or on their badge. If the room is dark, the Light button turns on the phone torch where the hardware allows it.
Note: you can always type the code by hand, or look the person up by name. A flat phone, a forgotten ticket, a cracked screen: that is the first real incident at any door, and there is nothing unusual about it.
Looking somebody up by name
The right-hand column holds the whole list of registrations. Type the first letters of a name, then Let in. People who have not arrived yet come first: those are the ones you are looking for.
The list is loaded once when the screen opens, then kept on the device. Searching stays instant, and it keeps working without a network.
When the network drops
A basement hall, a marquee, two thousand people on one access point: the connection gives way exactly when you need it.
The screen carries on. Every scan becomes a timestamped action stored on the device, and an orange banner shows N waiting to be sent. As soon as the network is back, everything goes on its own and the banner disappears.
Two things worth knowing:
- The time recorded is the time of the scan, not of the sending. The attendance report stays accurate even after an hour-long outage.
- While the banner is there, it has not been sent yet. The screen never pretends otherwise.
Several people on the same door
You can open this screen on as many phones as you like, at the same door or at several entrances. Somebody scanned twice is only counted once: that is guaranteed on the server, not just on the screen.
A ticket already validated shows Already in in orange, with the time they came through. That is not an error, it is information.
What the three numbers say
At the top of the screen, three counters that count people, not registrations: a family purchase of four tickets brings in four people.
| Counter | What it tells you |
|---|---|
| Left | How many people are still expected. This is the one that tells you whether to open a second door. |
| In | How many are already in the room. |
| Expected | The total of non-cancelled registrations. |
They refresh on their own every five seconds, on every open device.
With sessions
If your event has sessions, pick the one your door is handling at the top of the screen. You pick it once on arrival, not at every scan.
- A ticket bought for a specific session is only valid there. Elsewhere the screen shows Wrong session in orange and names the session on the ticket: point the person the right way, do not turn them away.
- An "all sessions" ticket is scanned at every session. Day two works normally.
Badges
The Badges button produces an A4 sheet to cut up, eight badges per page, in the order of the list on screen. Each badge carries the name in large type, the session, the category and the ticket QR: the badge therefore doubles as the ticket, which saves getting the phone out every morning of a three-day conference.
A family of four gets four badges, one per person.
Print them the day before and sort them alphabetically: that is what makes the difference between a smooth entrance and a queue.
What the screen does not do yet
- It does not print badges on the spot on a label printer.
- It does not check in ticket by ticket within a family purchase: scanning any one of the family's codes brings the whole line in.