A guest list that survives the whole engagement
Updated September 18, 2026
A guest list is a small database that four people edit, that nobody backs up, and that has to be right on exactly one day. It usually starts in a spreadsheet, gets copied into a phone, and ends as three documents that disagree.
None of what follows is about software. It is about the four decisions that decide whether a list is still usable a year later.
Decide what a row is
A row is a person, or a row is an invitation, and you have to pick. If a row is a household — “Los Martínez, 4” — you will not be able to seat them, because four is not four names, and you will not be able to tell who answered.
The version that survives: a row per person, with the household as a group they belong to. Invitations and seats hang off people, and “Los Martínez” is still one envelope.
Name the plus-ones
“+1” is not a person. It cannot be seated, cannot be given a meal, and cannot answer an RSVP. The moment a guest tells you who they are bringing, that plus-one becomes a person with a name — and everything downstream starts working.
Until then, keep it as a seat on the invitation rather than a row on the list. A row called “+1” is a row you will have to reconcile later.
Write names the way people will search them
Two surnames are normal in Mexico, and the one a guest gives on an RSVP form is usually the first. A list that stores “Ana Gabriela Martínez Solís” in one field cannot be searched by somebody typing “Solís”.
Keep the given names and the surnames apart, and accept either when somebody looks themselves up. It costs nothing at the start and is close to unfixable at the end.
Decide who may edit it
A list that four people edit is fine. A list that four people each have a copy of is not, and that is what happens the first time somebody exports it to work on a plane.
Pick one place the list lives. Everything else — the phone, the printout, the planner's spreadsheet — is a view of it, and should be regenerated rather than edited.
- One place, shared, with the people who need it invited to it.
- Exports are snapshots, never the source.
- If somebody sends you a corrected spreadsheet, apply the corrections; do not adopt the file.