How do you run satellite registration at the convention centre, hotel, and opening party?
By Donghui Qian (Milo)Updated 16 November 20266 min read
Short answer
Treat each satellite desk as one shared registration list with two statuses you must never mix: badge collected and entered the venue. Give every point its own staff, device download, and written scope; keep valid QR codes in the fast lane even when flights slip; send name changes, transfers and reprints to an exception desk. Offline means the downloaded list can still scan—not that new registrations or silent cross-device merges work without the network.
Large programmes often publish more than one desk: the convention centre foyer, a hotel lobby the night before, and an opening-party entrance. That pattern shows up every year at major association and trade shows. The failure mode is the same wherever the desks sit: one person is marked “done” at the hotel, then blocked or double-handled at the centre because badge collected was treated as entered.
This field guide is for PCOs, association managers and lean conference ops. Lane maths stay in the on-site check-in guide; what “offline” actually means stays in the Wi‑Fi failure guide. Here the job is one list across several doors.
In brief: one list, two statuses, scoped desks
- Badge collected ≠ entered the venue—configure and report them separately.
- Every satellite point gets its own staff seat, device list download, and written “what we do / do not do”.
- Valid QR still uses the fast lane when flights slip; late is not a special identity.
- Name change, transfer, reprint and brand-new walk-ins go to exception—not the hotel greeter queue.
- Offline: scan and search the list already on the phone; do not invent silent dual-device dedupe.
- After reconnect, review duplicates across points in the open before the morning report.
Why satellite desks break one shared roster
A single foyer can hide bad process behind one queue. Three desks cannot. Hotel staff want to clear the lobby; centre staff want doors open; party hosts want a guest list that matches the room. If those teams share hardware but not status language, the same person is “checked in” three times with three meanings.
Design the programme as one registration record touched at several places—not as three mini-events with three exports taped together at midnight.
Badge collected versus entered: two statuses that must not collapse
| Status | Means | Typical satellite use | Must not mean |
|---|---|---|---|
| Badge collected | The physical badge (or digital pass handoff) left the desk with the right person | Hotel night-before pickup; early collection desk | They are inside Hall A |
| Entered / checked in | They passed a controlled entrance for a session block or show floor | Convention centre doors; party door if capacity is policed | They already have a badge somewhere in the city |
If your stack only has one “check-in” bit, write the rule on paper anyway: hotel marks collection; centre marks entry. Reports that count “checked in” for room sets must use the entry status, or you will overstaff empty halls and understaff the real door.
- Hotel night desk
- Collection only—unless you explicitly staff an entry gate there
- Centre main lanes
- Entry (and reprint only at the exception desk)
- Opening party
- Entry to that room; do not re-issue the week’s primary badge unless scoped
- Morning ops report
- Separate columns: collected / entered / still outstanding
Configure each point before anyone opens a laptop
01
People and seats
- Named lead per point with a phone that can reach centre ops
- Staff accounts that can only do the actions that point is allowed
- A spare phone already logged in and list-downloaded
02
List and devices
- Same paid-and-approved roster version on every device the night before
- Search-by-name tested with Wi‑Fi off at each point
- Written rule for brand-new names (usually: needs the server / centre exception)
03
Sync and reopen
- Who presses sync after a hotel shift ends
- How centre sees hotel collections before doors open
- Where conflict review happens after reconnect (one person, not three lobbies arguing)
Hotel desks: service scope so the lobby does not become HQ
Hotels are convenient and chaotic. Guests ask for agenda changes, invoice copies, roommate swaps and “can you upgrade me”. If the desk says yes to everything, the lobby becomes your command centre and the centre never sees a clean list.
- In scope: collect a pre-printed or print-on-demand badge for a name already on the approved list; confirm spelling against ID if your security plan requires it; mark badge collected.
- Out of scope at the hotel (send to centre exception or next-day desk): unpaid or pending approval, ticket transfers, name changes that reprint entitlement, group leader adding five new people, refund debates.
- Signage in one sentence: “Badge collection for [Event]. Changes and unpaid registrations: convention centre from [time].”
- Close ritual: sync, count badges left, message centre ops the outstanding list—not a spreadsheet nobody opens.
When flights slip: late is not a special identity
Travel disruption moves your arrival peak; it does not rewrite who is entitled to enter. Industry travel reporting regularly shows conference weeks under flight delay pressure—treat that as a timing problem for staffing and desk open hours, not as a reason to invent a “late” lane that mixes every exception together.
- Valid QR, already collected or ready to scan → stay in the fast lane. Late does not equal abnormal.
- Name change, transfer, reprint, pending payment → exception desk, same as at 08:00.
- Shift the roster and open times when the airline mass arrives—add a lane or open thirty minutes later; do not retrain volunteers mid-queue on new myths.
- Do not create “all late arrivals this way”. That queue becomes every problem type at once and blocks people who only needed a two-second scan.
Association programmes that already use early collection and exception desks—see the association congress door guide—should keep that shape under delay. Satellite points only multiply the cost of collapsing the two statuses.
Offline at a satellite point: honest boundaries
A hotel lobby and a party basement fail networks in different ways. The rule is the same as any door:
| Still expected offline (if the list was downloaded) | Not expected offline |
|---|---|
| Validate a code already on the device list; search by name; queue the collection or entry with the time it happened | Brand-new registration that was never on the download |
| Print from a cached template if printing is in that point’s scope | Live entitlement changes pushed from another desk you cannot see |
| Upload the queue when the connection returns | Silent merge when two offline phones scanned the same person |
Two devices offline cannot know each other’s scans. On reconnect, surface duplicates for a human. Holding the truth as a guess is worse than admitting a double hit and cleaning it once. Detail lives in the Wi‑Fi failure guide.
Opening party and the last mile
- If the party is capacity-controlled, it needs entry status for that room—not a second “badge collected” that overwrites the week.
- If the party only needs a guest list glance, say so; do not force a full check-in ritual that invents conflicts with tomorrow’s centre door.
- Sponsors and speakers often arrive from a different hotel: give them the same QR rules as everyone else, plus a named host—not a private spreadsheet lane.
Acceptance script before you trust the map
Before opening morning, run one person through hotel collection → centre entry → (optional) party entry on your devices. Then turn a network off at one point, scan, reconnect, and watch how duplicates appear. That is the same spirit as the post-show shortlist acceptance guide, applied to multi-site doors.
Frequently asked questions
Satellite registration means more than one staffed desk sharing one registration list—often the convention centre, a hotel the night before, and sometimes an opening party. Each desk must use clear statuses so badge collection is not confused with venue entry.
No. Badge collected means the credential left the desk with the right person. Entered or checked in means they passed a controlled entrance. Collapsing the two statuses is the most common multi-site failure.
Collect badges for names already on the approved list and mark badge collected. Send unpaid, pending, transfers, name changes and group add-ons to the centre exception desk. Put that scope on a sign so the lobby does not become headquarters.
Keep valid QR codes in the fast lane. Move staffing and open times if the peak shifted. Send name changes, transfers and reprints to the exception desk. Do not create one mixed “late arrivals” queue.
Only against the list already downloaded to that device: validate, search, queue with the real time, then sync. New registrations and silent cross-device dedupe do not work without a network. Review conflicts after reconnect.
Use separate statuses where the product allows; sync after each shift; assign one person to review reconnect conflicts. Do not rely on two offline phones to agree in real time—they cannot.
Read next
- On-site check-inLane maths, peaks, and desk run-sheets
- Check-in when Wi-Fi failsFour meanings of offline—and what still breaks
- Association congress doorEarly collection and exception desks before networking
- Accept the shortlist after the showSame acceptance spirit for multi-gate and offline
- Conference badge designWhat must read without a second interview
- Check-inHow this platform frames door and device check-in