Registration and Check-In for a 5,000-Delegate Pharma Summit

Most registration systems answer one question: is this person on the list. A pharma summit asks four more. Is this delegate a healthcare professional or a non-HCP. Which sponsor funded their attendance, and does that create a restriction on what they may access. Did they sit in the accredited session long enough to earn the credit hour. And can you produce that evidence later without reopening a spreadsheet nobody trusts.

That changes the data model before it changes the hardware. We build the delegate record with category, sponsor attribution, session entitlements and consent state as first-class fields, not as columns bolted on the week before the event. Every scan writes an immutable event — badge ID, gate ID, device ID, timestamp, operator ID — instead of flipping a boolean on a row. If a record is disputed, you replay the events rather than argue about the current state.

• HCP and non-HCP separation drives badge colour, zone rights and reporting splits from a single source field
• Session-level attendance uses entry and exit scans, so credit hours are calculated from dwell time rather than asserted by a form
• Consent captured at registration under the DPDP Act, with the purpose written in plain language and a stored timestamp
• Sponsor scoping so a sponsor's dashboard shows their delegates and nothing else

The queue is the visible problem. The audit trail is the expensive one.

The most common failure is not technical. It is a delegate list that arrives at 22:00 the night before, in three files, with the same person present in all three under different spellings and two phone numbers. Deduplication then happens live at the desk, by a volunteer, under pressure. We treat phone number as the primary identity key and run fuzzy matching in advance, but if the list lands twelve hours before doors open, some of that cleanup will happen in public.

The second failure is venue WiFi. Hotel and convention centre networks in India are frequently sold on peak capacity that assumes browsing, not 60 devices holding persistent connections. We plan for the network to die, because sometimes it does. What we cannot fully absorb is a power situation with no UPS on the registration desk — printers lose their spool, and a badge that was printing when the power cut has to be reprinted. Ask for dedicated circuits and battery backup in the venue contract, not on the day.

The third is scope. Someone will ask for a lucky draw, a photo booth and a feedback survey on the same devices doing check-in. Each addition costs seconds per delegate. At 5,000 delegates, three extra seconds is over four hours of aggregate queue.