Registration Desk Flow
Design a smooth arrival experience.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design a registration desk flow. Attendee numbers and arrival pattern: [ARRIVALS]. Registration method (list, QR codes, tickets): [METHOD]. Staff and equipment: [STAFF_EQUIPMENT]. Plan the layout, queues, roles, and process for check-in, badges, special requirements, walk-ins and problems. Include scripts for staff, a plan for peak times, a backup if technology fails (printed lists), and a procedure for lost badges. Estimate throughput using staff numbers and time per person, with the arithmetic. Add accessibility measures and data handling rules for attendee lists, marked [VERIFY] for [JURISDICTION]. Provide a checklist for setting up and a debrief template. Also add a worked throughput example: 400 attendees arriving in 45 minutes with 4 stations at 40 seconds each, showing queue length, labelled as an illustration. Add a one-page troubleshooting card for staff covering the six most common problems: name not on the list, wrong ticket type, duplicate registration, missing badge holder, a request for an accessibility accommodation, and a guest who arrives with an unregistered companion. Treat photographs, guest details and dietary information as private. Share only what is needed, tag consent and privacy points [VERIFY] for [JURISDICTION], and keep examples invented.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.