Skip to content
EntryWick documentation

For a registration-team member or admin at the desk, with the person in front of them.

Walk-up registration

Someone arrives at the venue who never registered. Admin → Help desk → Walk-up, or Registrations → New registration.

Who uses it: a registration-team member or admin at the desk, with the person in front of them.

What they came to do: register that person through the event's own registration form and hand them a ticket, in under a minute.

What must be true when they leave: the person is a real registration with a ticket that scans, and anything the desk decided for them — consent they gave out loud, a full day or an approval that was overridden — has a name and, for an override, a reason on the audit log.

Decided (Pilot Day, A1)

  • The event's registration form, filled in inside admin. Its questions are asked as the public form asks them, with its logic; files, photos and signatures are not asked at the desk.
  • Email and phone are optional. Someone with neither gets a contact of their own (a phone never matches anyone, see registrations.md).
  • Consent is captured by the staff member on the person's behalf. Each consent answer records who captured it (captured_by), and the registration page shows "Agreed · date · version · captured by Sam".
  • The desk picks the type, the day(s) — each day says "— full, waitlist only" or "— full" — and the group.
  • Capacity and approval apply as on the public form: a full day waitlists or refuses; a form that needs approval holds the registration with no ticket.
  • Override (members who may approve registrations): a place even on a full day, and approved now. A reason is required and kept on the registration.walk_up audit row with the days that went over capacity.
  • Override does not get round a rule that blocks, the plan's attendee cap, or money owed.
  • On save the page shows each ticket with its code, Print (the ticket page) and Print badge where a badge template exists, then Register another.
  • Needs registrations.create; the registration's source is admin. The form's open/close window does not apply at the desk.

Open

  • Whether Check-in Staff should hold registrations.create so desk volunteers can do walk-ups (docs/decisions-pending.md).
  • Taking payment at the desk.