Checking People In
The register is the screen you work from on the door. Open it from Profile > Bookings > Customer Bookings > Events, pick the event, then press Open register in the Attendance block.
It works one session at a time. Choose the session you are running and the whole list narrows to the people booked onto it. A line under the session's progress bar says how many of the event's participants and bookings it covers.
A long event, one date at a time
On an event with more than 14 dates, such as a weekly class, the register opens on today's date, or the next one to come. Instead of a row of sessions, it has a date picker with arrows either side to step to the previous or next date. Each date in the list shows how many have checked in.
Only the people on the dates you open are loaded, so the register stays quick on a phone or tablet at the side of the pitch. Opening another date brings its people in alongside the ones already loaded. The line under the progress bar then says how many participants and bookings that date has, rather than comparing it with the whole event.
On the app, Change shows the dates a month at a time, starting from the month of the date you're on.
More than one person on the door
Several staff can run the same register at once, on different phones or tablets. A check-in, collection or note made by one appears on everybody else's straight away. If a colleague makes a change the register can't show in place, such as cancelling a booking, a banner says what happened and offers to refresh.
Above the list, On the desk names who else has the register open, for example "On the desk: you and Dan.". On a long event, a colleague working on a different date has it shown beside their name, such as "Dan (18 Nov)". The count on each date stays right whichever date you have open.
The three tabs
The register has up to three tabs:
- Not checked in: booked on, not arrived
- On site: arrived, not yet collected
- Picked up: handed back to whoever came for them
A collected child leaves On site, which is the whole point of the third tab. On a session with no children booked onto it, Picked up is not shown at all, because nobody on that list can ever be collected. At the end of a session the question anybody asks is who is still here, and a register that only knows who arrived cannot answer it.
Picked up is recorded per session, so a child collected on Saturday has not been collected from Sunday. Undoing a check-in clears the collection with it, so a row can never claim somebody never arrived and was collected.
Handing a child back
Collect does not hand the child over on its own. It opens a short step first, because this is the one thing on the screen you cannot take back once it has actually happened:
- The collection password is shown in full, to read back to whoever is standing there. If no word was agreed for that booking, the step tells you so rather than showing nothing.
- Name who is collecting. The booker and the emergency contact are each one tap; anybody else gets typed in, with their relationship to the child if you want it.
- Confirm collection.
The step will not finish without a name. "Collected at 15:44" on its own tells nobody anything, which is the gap this closes. The relationship is optional: "Mum" adds nothing to a name you already know.
Where no password was agreed for that booking, the step says so and asks you to confirm you are releasing them on your own judgement. It never blocks the handover: the booking with no word is usually the one where drop-off was chaotic, and a register that refuses to let a child go because of its own missing field helps nobody. What it does is record that the handover was an exception, so a checked one and an unverified one stop looking identical afterwards. Where a word was agreed, nothing extra is asked of you.
Three people end up on the record, in three different roles: the staff member who checked the child in, the staff member who released them, and the adult who took them. They are often three different people on anything longer than an hour, and open an attendee to see all three.
What is different for a child
Everything above applies to children only, and that is enforced on the server rather than just hidden in the app:
- Only a child can be collected. The button does not appear on an adult's row, and the request is refused if it is made anyway.
- A collection password only exists on a booking with a child on it.
- A child is anybody under 18, worked out from the date of birth if the booker did not tick the box.
Checking in is the same for everybody. Receiving a child carries nothing like the risk of releasing one, so the extra steps all sit at the collection end.
Collecting a whole booking at once
Where a booking has two or more children still on site, the On site tab gives you Collect all above their rows. It opens the same step once: the word to read back, who is collecting, confirm. The panel lists the children it covers, so you can check it against who is standing there before you press anything. Each child is still recorded separately, and the booker gets a message about each one.
Adults on the booking are never swept up by it, and the per-child Collect stays on every row. That one matters more than it looks: one sibling going home with another family while the rest leave with their own parent is exactly the arrangement a single bulk button cannot describe.
What the booker is told
Whoever made the booking is told shortly after somebody on it is checked in, and told again when a child is collected, with the collector named. Both wait a couple of minutes before they go, and are dropped entirely if you undo the tap in the meantime: a thumb landing on the row above is an ordinary thing on a busy register, and a push notification cannot be unsent. Both land in the app and as a push notification rather than an email, because a parent wants to know within seconds and a week of sessions would fill an inbox.
The same record sits on their own booking page: who is on site, who has been collected, at what time, and by whom. If a parent ever queries a handover, you are both reading the same thing.
Bookers can switch this off under Check in & collection in their notification preferences, so some will have. A booking made as a guest has no account behind it and nobody to notify.
Finding somebody
Scan the QR code on a ticket, type the ticket code, or search a name. All three do the same thing: they open the whole booking, with nobody checked in yet.
That is deliberate. A parent dropping three children off scans one ticket, and you need all three in front of you rather than one checked in and two still on the list. From there, check people in one at a time, or use Check in remaining to do the whole booking at once.
The person whose ticket was scanned is highlighted inside the booking, so you are not matching a ticket code against a list of names. The highlight stays until you check them in or collect them, even on a tab that would otherwise hide them. On the app, the camera closes as soon as it reads a code.
Where a session sells more than one ticket tier, each row shows the tier that person bought, so a VIP queue and a Standard queue can work off one list.
A ticket for the wrong day
If the ticket is valid but not for the session you are running, the register offers the swap there and then: they give up the session they booked and move onto this one. It hands you the booking and stops, without marking anybody present, because on a children's event the collection password has to be agreed with whoever is standing there first.
On a long event, the register only knows about the dates you have opened. A ticket booked only for a date you haven't opened isn't found until you open that date, so step to the date on their ticket first.
If every session on that ticket has already been attended there is nothing to swap. That is not a wrong day, it is an extra day nobody has paid for, and the register says so. See Selling a Place on the Door.
Collection passwords
Any booking with a child on it carries a collection password. Agree it with whoever drops them off, type it in, and the register puts it in front of you again at the moment somebody arrives to collect.
One word for the whole booking, not one per child. A parent dropping three children off says one thing once.
It is stored as plain readable text on purpose. You are comparing it to what the person at the gate says, so it is a note rather than a password protecting anything, and everybody who can read it already holds those children's emergency contact details.
What you can see on the door
Open a person in the register and you get what an incident actually needs: their date of birth and age, whether they are a child, the Booker's number, the emergency contact with their relationship and number, and the answers to the event's booking questions.
The emergency contact can be corrected from the door as well. "Ring her mum today, not me" gets said to whoever is taking the child in, and a number nobody can fix leaves a stale one in front of the next person who needs it.
The booking's Desk notes show here too, so an allocated coach reads "collect from reception, not the gate" without having to ask. See Managing Event Bookings.
Money owed on the door
A seat sold on the door stays owed until it is settled, and the register shows it twice: amber on the attendee's own row, and totalled in a band above the list so whoever is closing up knows whether there is money to collect at all.
Who can run the register
Everybody who can reach the event's bookings page: you, your Admins, your Booking Managers, and any coach you have allocated to the event. A coach gets the attendee list, the register and announcements, and none of the controls that move money.
Check-in stays open for a short grace period after the last session finishes, then closes. After that the button reads View register: you can still open it to see who turned up, who was collected and by whom, but nothing on it can be changed.