How to manage an attendee list from A to Z

The attendee list: much more than a spreadsheet

The attendee list is the central document of any event. It drives confirmations, room setup, catering, badges, and check-in on the day. Yet it is often managed improvisationally, with inconsistent data, duplicates, and forgotten updates.

This guide covers the full lifecycle of a list, from the first registration to the final export after the event.

---

Phase 1: Define the data to collect

Before opening registration, decide which information you actually need. The rule: only collect what you will use.

Essential fields

• First and last name: in two separate columns (easier sorting and personalized messaging)
• Email address: your main communication channel before the event
• Attendance status: confirmed, waiting list, cancelled

Useful fields depending on context

• Company / organization: useful for B2B events
• Job title: for networking events
• Dietary requirements: if catering is planned
• Accessibility needs: to anticipate welcoming people with disabilities
• Reference: promo code, referring partner, registration channel

What is better to avoid

• Phone number if you do not use it — attendees know it and it slows registrations
• Date of birth unless legally required
• Any field you do not already know how you will use

---

Phase 2: Collect registrations

Via an online form

This is the most efficient method for open events. A few rules to maximize registrations:

• Short form (5 fields maximum if possible)
• Automatic email confirmation right after registration
• Clear confirmation page with practical information (date, venue, access)
• Unsubscribe link visible in the confirmation (GDPR legal requirement)

Via manual invitations

For invite-only events, you manage the list yourself. Create a tracking sheet with columns: First name, Last name, Email, Status (Invited / Confirmed / Declined / No reply), Follow-up date.

Handling last-minute registrations

Plan a clear process for late requests: waiting list, manual validation, or direct registration depending on capacity. Communicate that process as soon as registration opens.

---

Phase 3: Clean and validate the data

This is the most underestimated step. A clean list makes everything else easier.

Detect duplicates

The same attendee may register twice (email change, forgotten first registration). Check duplicates by email before finalizing the list.

Normalize names

"MARTIN Jean", "jean martin", "Jean MARTIN" are three formats for the same person. Standardize to Capital first letter, lowercase for the rest (PROPER() in Excel / Google Sheets).

Validate email addresses

Typos are common. The most frequent: .cmo instead of .com, @gmial.com, spaces before or after the address. Use your form tool’s email validation, or visually check addresses that look suspicious.

Handle special characters

First names with accents (Élodie, Noémie), hyphens (Marie-Claire), particles (de La Fontaine) — check they display correctly in your check-in tool to avoid search issues on the day.

---

Phase 4: Manage changes until the day

Cancellations

Define a clear cancellation policy (deadline, possible refund) and an internal notification process. Every cancellation must update the central list.

Changes

An attendee who changes preferred first name, transfers registration to a colleague, or reports a dietary need late — these requests always arrive. Centralize every change in a single version of the file.

Versioning

Keep a copy of the list at D-7, D-3 and D-1. If something goes wrong, you can go back to an earlier version to understand what changed.

---

Phase 5: Prepare the list for check-in

The final version

By D-1 at the latest, freeze the list. No more changes without approval from one designated person. Communicate this “lock” to teams receiving add requests.

Sort the list

For paper check-in: sort alphabetically by last name. For a digital tool: order does not matter — search handles everything.

Prepare the “unconfirmed” list

Keep aside waiting-list attendees, unvalidated registrations, and “probable” guests. That list is the reference if someone shows up and is not on the main list.

Test the import

If you use a check-in tool, import your list 24 to 48 hours before the event. Check that all characters display correctly, duplicates were detected, and search works on a few test names.

---

Phase 6: Check-in on the day

Organize the welcome space

• Plan a separate lane for attendees with a QR code and those without
• For large events: split welcome alphabetically (A-M / N-Z) or by category (speakers, press, attendees)
• Have a separate “issues” desk so the main queue is not blocked

Handling unregistered attendees

Have a clear procedure: do you accept on-site registration? If yes, what minimum information do you collect? Who has authority to accept an unregistered guest?

No-shows

On average, 20 to 30% of registrants do not show up. Anticipate that in your organization (catering, seating, printed materials).

---

Phase 7: After the event

Export the attendance report within 24 hours: who was there, who did not show, attendance rate by category. That data will help you with:

• Invoicing if attendance conditions payment
• Training follow-up (certificates, funding justifications)
• Event analysis (compare attendance rates from one edition to the next)
• Segmentation for post-event communications

In practice with Gatesly: centralize the list, check-in and export so you manage a single tool from D-30 to the final report. See plans →