Four lists, one event
The client's sales conference has an online registration form for their staff, a spreadsheet of VIP guests from the CEO's office, a separate list of partner delegates from their channel team, and a steady trickle of emails saying things like "please add Priya and swap Tom for Jas". Each list has its own columns. One has first and last name together. One has no job titles. One uses personal email addresses for people who also registered with their work ones.
Your coordinator copies everything into a master spreadsheet every morning. Duplicates slip through, a partner delegate gets two hotel rooms, and a swapped attendee still receives the joining instructions because the old row was never removed.
Why the master list is never quite right
Corporate clients do not have one owner of the guest list. Several departments invite people, and each one sends what it has in whatever shape it has.
- The same person appears with different emails or name spellings across sources.
- Substitutions and cancellations arrive as free-text emails, not structured changes.
- Each source has different fields, so the master list has gaps nobody notices until badges or rooming lists are due.
- Copying into a spreadsheet leaves no history of who changed what and when.
- Every downstream list (badges, rooming, transfers, dietary) is a separate export of the master that drifts once it is sent.
Where a messy list hurts
It hurts wherever names turn into commitments: hotel rooms booked for people who are not coming, badges printed for the wrong person, a VIP left off the seating plan, meals ordered for the old number. The client sees the mistakes and assumes the agency is disorganised, even though the list came from them in pieces.
It also eats time at the worst point. The last fortnight before an event is when the list changes most, and your coordinator is still copying and pasting.
Then there is the data itself. Delegate lists hold names, phone numbers, dietary and access needs, sometimes passport details for travel. Copies of that list sitting in several inboxes and on laptops are hard to account for when a client asks where their people's data went and when it was deleted.
One attendee record, fed from every source
- Each event has one attendee record in a database you own, not a spreadsheet passed around.
- Imports accept the client's spreadsheets as they are; you map their columns once per client and reuse the mapping.
- Your registration form, whether your own or from a platform with an export or API such as Eventbrite, feeds the same record.
- A matching step flags likely duplicates by name, email domain and company, and a person decides whether to merge.
- Change emails from the client go to an event inbox, where the substitution or cancellation is proposed as a structured change and approved by your coordinator.
- A completeness view shows missing fields per attendee (dietary, arrival date, room needs) against what this event requires, and can send each attendee a personal link to fill their own gaps.
- Badges, rooming lists and transfer manifests are generated from the record at the moment you need them, so they are never out of step.
| Source | Arrives as | Handled by |
|---|---|---|
| Staff registration | Online form | Direct feed into the record |
| VIP list | Spreadsheet from the client | Saved column mapping |
| Partner delegates | Spreadsheet, different layout | Second mapping, duplicate check |
| Swaps and cancellations | Emails | Proposed change for approval |
The morning list check, without the copying
Each morning your coordinator opens the event and sees what changed overnight: two new registrations, one swap proposed from an email, three possible duplicates to decide. It takes minutes rather than an hour. When the hotel asks for the rooming list, it is produced from the current record. If the client asks when a delegate was cancelled and by whom, the history shows it.
Recognise your attendee list here?
- You rebuild a master attendee spreadsheet from several client lists.
- Duplicates or swapped delegates have caused double bookings.
- Missing information is found only when a downstream list is due.
- Badges, rooming and dietary lists are separate files that drift apart.
- You cannot say when a particular delegate was added or removed.