Help desk

The registration team's table at the venue: the place people go when their ticket does not scan, they forgot it, or they are on the wrong day. Admin → Access → Help desk.

Who uses it: registration-team members and admins at a laptop, with a queue in front of them.

What they came to do: find the person in seconds, understand why they were turned away, and either let them in, fix what is wrong, or send them to the right gate.

What must be true when they leave: every admission from the desk is a real check-in with who did it and how, and anything unusual (an override, a day change) has a reason on record.

Decided

• Pick the event and the check-in point once; the desk remembers nothing else between searches.
• Search by name ("amina rah"), the last four digits of a phone, or the start of a ticket. Nothing is listed until you type.
• Each result shows the ticket, the day, the household size ("1 person", "4 people") and whether the ticket still works (or what replaced it). One character is not a search: the list asks for at least two.
• Check in records a real check-in at the chosen check-in point and shows the same result the scanner would.
• Someone already admitted is not offered Check in: the row says "Checked in at point, time" instead — for a ticket good for every day, on the day the desk is checking in for. A typed code still answers "Already checked in".
• A void or replaced ticket offers nothing but its status: no Check in, Print or Change day (Pilot Day, C3).
• Type a code only where the check-in point allows typed codes.
• Override appears after a refusal only for roles the check-in point lets override, and needs a reason.
• Print, household and change day open the ticket page, the household page and the person's page.
• Walk-up registers someone who never did, through the event's form, and shows their ticket to print (walk-up.md).

Open

• A desk-specific "print a badge" layout (week 11, print).