Wedding guest list template and management guide

Separate people from invitations. A household may receive one envelope or message, but every invited person still needs an individual record for attendance, meals, accessibility, seating, and check-in. Decide whether adult children, partners at different addresses, and shared households should be one invitation unit or separate ones before outreach begins.

Give each invitation unit a stable identifier and one primary contact without treating that contact as the only guest. This makes reminders easier while preserving individual answers. When family relationships are complex, model the communication unit based on how the invitation will actually be delivered, not on assumptions about surnames or addresses.

Define the fields before collecting names from several contributors. At minimum, distinguish preferred name, formal name, invitation unit, contact route, invited events, RSVP state, meal, dietary notes, accessibility needs, plus-one permission, child status, table assignment, and check-in status. Use consistent allowed values wherever possible.

Separate blank, unknown, not applicable, and declined. An empty meal field for a confirmed guest requires action, while an empty meal field for someone who declined does not. Record who last changed a sensitive or operational field so questions can be resolved without relying on memory.

Agree on rules before names are collected. Define whether plus-ones are named, limited to established partners, or offered to specific categories, and decide how infants, children, and teenagers count toward capacity. Apply the rule consistently while allowing documented exceptions for care, safety, or family circumstances.

Write invitation language that states exactly who is included. Avoid labels such as 'family' when the intended names are narrower. For children, record whether they need a seat, meal, high chair, supervision arrangement, or event-specific invitation; age alone does not answer those operational questions.

Start from the supported template and keep one row per person. Normalize phone numbers, trim accidental spaces, preserve diacritics in names, and use the expected headers exactly. Do not combine two guests in a single name cell or hide important notes in formatting, cell colors, or comments that the import cannot read.

Validate a small sample before loading the full list. Look for duplicate contacts, repeated people under different spellings, invalid event values, and households that lost their shared identifier. Keep the original file unchanged, then save a cleaned version and an import report so corrections remain auditable.

Build segments from guest facts, not ad hoc message lists. Useful groups include invitation channel, language, event eligibility, travel needs, households awaiting response, confirmed guests missing meal choices, and people affected by a schedule change. A guest can belong to several segments without being duplicated in the master list.

Before sending, preview the exact recipients and exclude people whose state makes the message irrelevant. A reminder about the response deadline should not reach declined guests. Record the message date and purpose so collaborators can answer questions consistently and avoid overlapping follow-ups.

After counts and seating are handed off, define who may add, remove, or substitute a guest. Capture the requested change, affected events, supplier consequences, and approval before editing the operational record. A friendly request is not automatically feasible when capacity, meals, security, or transport are locked.

Propagate approved changes rather than updating only the name. Recheck catering, dietary handoffs, table capacity, place cards, transport, accommodation, and check-in. Add a timestamp or version label to exports so the venue can distinguish the current file from an earlier attachment.