Registration and
Attendee Management.

What event registration includes

The part organisers most often leave unassigned is the operator layer: the people at the desk who handle the guest whose name is spelled differently, who registered twice, who brought an unregistered colleague, or who is on no list at all. Those cases are a predictable percentage of any event, and they are resolved by a briefed human with authority, not by a platform. Event registration and accreditation sets out where that scope sits.

Pre-registration, on-site, or both

Pre-registration only. Fastest throughput, because the record already exists and check-in is a lookup. Requires a hard cut-off and a stated policy for anyone who arrives without a registration — and that policy will be tested, usually by someone senior.

On-site registration only. Appropriate for small events and for public-access formats where you cannot know the audience in advance. Slowest per guest, and the queue grows faster than people expect, because data entry time does not reduce with practice as much as it should.

Both, on separate desks. The usual correct answer for anything above a few hundred guests. The error is running them on the same desks: a single walk-up registration takes several times longer than a check-in, so one of them in a shared queue stalls everyone behind it. Split the lines and signpost them clearly in both languages.

Accreditation tiers and access control

Tiers exist to answer one question at a threshold: can this person go through this door. Define them by access, not by status.

• List every controlled threshold first — main hall, stage and backstage, VIP area, media area, exhibition floor, catering, crew-only zones — then decide which tiers pass each one.
• Keep the number of tiers small. Every tier is a badge design, a stock line, a briefing point and a chance for a steward to guess wrong.
• Make tiers visually unmistakable at a distance and in low light: colour plus a word, never colour alone, and never two similar colours.
• Decide the escalation rule for a person who should have access and does not have the badge — who grants it, how, and who records it.
• Brief the stewards on the thresholds, not on the tier chart. A steward needs to know who comes through their door, not the whole matrix.
• Plan crew accreditation separately, with its own cut-off, because it is submitted earlier and changes more often.

The stewarding and threshold operation itself sits in crowd and site operations.

Sizing desks against the arrival curve

Three variables set the per-desk rate, and all three are controllable. Lookup method: a scanned QR code is faster than a name search, and a name search in two scripts is slower than one. Badge handling: handing over a pre-printed badge is faster than printing on demand, which is faster than writing. Conversation: a desk that also answers questions, hands out materials and directs people is not a check-in desk, it is an information desk, and it should be a separate position.

Then plan for the shape, not just the volume. A conference with a 09:00 start has a sharp peak at 08:35–08:55. An exhibition open for eight hours has a long flat curve and needs fewer desks for more total guests. A ceremony with a VIP arrival has two peaks and a mandatory separate route for the second one.

• Estimate the peak ten-minute arrival and design to it.
• Measure the per-desk rate in a dry run, with real staff and real hardware, not from a vendor's figure.
• Add a problem desk, off the main line, for the complicated cases.
• Add a late desk, because arrivals after the start need a route that does not disrupt the session.
• Staff in shifts, since the peak is short and the day is long.
• Language cover on every desk, Arabic and English.

Badge production

• Pre-printed for confirmed registrations: fastest at the desk, needs alphabetical organisation and a plan for the ones nobody collects.
• Print on demand for walk-ups and corrections: flexible, slower, and dependent on printers, stock and someone who can clear a jam under pressure.
• Both, which is what most events of any size actually run.
• Design for reading at a distance. Name large, organisation smaller, tier unmistakable. A badge nobody can read across a table has failed at its only job.
• Bilingual where the audience is mixed, with the name in the script the guest uses.
• Spare stock, spare ribbons, spare printer. Printers fail at the peak, not in the quiet hour.
• Collection at the exit if lanyards or holders are being reused, with a visible bin and a steward asking.

Layout and the queue nobody planned

Registration layout is a flow problem disguised as a furniture order. Draw it on the floor plan before anything is ordered.

• Desks positioned so the queue forms away from the entrance, not across it. A queue that blocks the door creates a second queue outside it.
• Queue route drawn, with the overflow position marked and barriers specified to make it.
• Daylight and heat considered if any part of the queue is outside — in a Saudi summer an outdoor queue is a welfare issue within minutes, not an inconvenience.
• Signage at every decision point, in both languages, readable at walking pace: pre-registered here, new registration there, problems over there.
• A clear exit path from the desk to the hall, so processed guests leave the registration area instead of standing in it.
• Separate VIP and media routes where the event has them, with their own desk or a host holding their badges.
• Power and network at every desk position, confirmed on the plan rather than assumed from the venue.

Failure modes and the offline fallback

Registration has four predictable failures. Each has a cheap mitigation that has to exist before the day, because none of them can be solved in front of a queue.

• Connectivity fails. Mitigation: a local copy of the attendee list on each device, or a printed list, and a rule for what to do with new registrations until the link returns.
• A printer fails. Mitigation: a spare printer, pre-printed blanks and a marker. A handwritten badge is better than a stopped queue.
• A guest is not on the list. Mitigation: a problem desk, a named approver reachable by phone, and a policy decided in advance rather than improvised at the threshold.
• Arrival is twice the forecast. Mitigation: a contingency desk position with furniture, power and network already in place, and two staff who can be redeployed to it.

Test all four during the dry run. An offline fallback that has never been switched on is a plan, not a fallback.

Data, privacy and what not to collect

Registration is the point where an event collects personal data, and the discipline that matters is restraint: collect what the event needs to run and what the organiser will actually use.

• Collect what you will use. Every additional field reduces completion and creates an obligation.
• Keep sensitive fields out unless there is a specific operational need, and never collect identity-document numbers because the form had a space for them.
• State the purpose on the form, in both languages, in a sentence a person can read.
• Define who sees the list during the event, and make sure that is fewer people than it would be by default.
• Agree the handover and retention at the end: what the organiser receives, in what format, and what the contractor deletes.
• Keep analytics free of personal data. Attendance counts and arrival patterns are useful; names, emails and phone numbers have no business in a reporting tool.

OnePass delivers registration and accreditation as part of event execution in Saudi Arabia, alongside site operations and event management, and the broader planning sequence is in the event planning checklist.