Guest List Excel Import: From Messy Spreadsheet to Clean Check-In

The Guest List That Arrives as Chaos

It always arrives 48 hours before the event, and it never arrives once. Marketing sends an Excel with English headers, the sales team sends one with Vietnamese headers, and someone’s assistant sends a screenshot of a screenshot. Column names read “Họ tên”, “Full name”, “Tên”, and — memorably — “người đi chung???”.

The instinct is to fix it by hand: hours of copy-paste that introduce exactly the typos you were trying to remove. The better move is an import pipeline that treats the mess as normal — auto-detects what each column means, validates every row, and shows you exactly what will happen before anything is saved.

What a Good Import Must Handle

Judge any import wizard against this list:

• Auto-mapping with human review. The system guesses which column is name, email, phone, tier — Vietnamese headers like “Họ tên”, “Số điện thoại”, “Hạng vé” included — and shows you the guess to correct. Unmapped columns are listed as “will be skipped”, not silently dropped.
• Reserved fields and custom questions as targets. Organization, title, dietary needs, plus one — and your event’s own custom questions — should all be available as mapping destinations, so no column of real information is lost.
• Row-level validation with reasons. Invalid email, unknown ticket tier, missing required field — each error row explains itself, and only that row is skipped. One bad row never poisons the batch.
• A faithful preview. Before committing, you should see exactly what the import will create — including families nesting under their primary guests — not a leap of faith.
• Duplicate detection. If an email already belongs to a guest in the event, the row is still imported (the QR code is the identity) but reported as a duplicate for you to de-duplicate deliberately.

Linking Families in the File

The part that defeats most imports: rows that are plus-ones of other rows. Two file conventions solve it:

A companion-of column — each companion references the primary guest’s row number in the file (the same number the review table shows). Forward references work, guests without email can be primaries, and the link is validated while you review: the target must be an error-free primary row.

A number-of-companions column — a row with 2 creates the guest plus two blank companions who inherit the email and ticket tier, each with their own QR code and each counted in the total.

The two columns are mutually exclusive on a single row, and both consume the primary’s companion allowance — a later companion-of reference in the same batch still respects the cap. Your capacity is protected even from your own spreadsheet.

On events running count-only companions, the import switches accordingly: no link column, companions ride as numbers — which is exactly what the “Số người đi kèm” column in your messy file already wanted to be.

No Event Yet? Start from the File

The most underrated import feature: creating the event and its guests from a single file. The review screen derives the whole event from it — event name, one custom question per non-fixed column (organization, title, gender… become first-class event questions), a ticket-tier column whose distinct values become the event’s tiers, the companion allowance and mode, and a default check-in setup with one door and a linked scanner, provisioned automatically.

The event defaults to today, companions default to walk-in, and everything else folds behind an advanced-options toggle. For the organizer staring at a spreadsheet and a deadline, the path is: file in, event out.

The Import Checklist

1. Download the guest list Excel template and look at its sample rows — they demonstrate every pattern, including a linked companion and a companion count.
2. Keep the row number column visible while you fix errors — it’s the reference for companion links.
3. Fix error rows in the file, not in your head — correct the cell and re-upload; the wizard is idempotent until you press import.
4. Read the skipped/duplicate advisory on the final screen — that list is your cleanup worklist, and it’s shorter than the original mess.
5. Sanity-check the totals: rows read vs. guests imported vs. skipped. The numbers should tell one story.

Limits worth knowing: Excel (.xlsx) or CSV up to 5 MB and 10,000 rows per batch — larger lists split cleanly by department, which the department heads will thank you for anyway.

Conclusion

A messy guest list is not a failure of process; it is the process. The difference between chaos and a clean import is a pipeline that auto-maps columns, speaks both Vietnamese and English headers, validates row by row, links families by row number or count, and shows you the outcome before committing. QRS imports Excel and CSV with auto-mapping, companion links, full validation, and event-from-file provisioning — your guest list can stay exactly as messy as it arrived.