Count people, then group households
Give each person a separate row and connect people who share an invitation with a household label. A household of four is one envelope but potentially four seats and meals. Separate invited, accepted, declined and awaiting reply instead of leaving blanks to mean several things. Record the agreed policy for additional guests before invitations go out, so different family members do not offer conflicting answers to the same question.
Ask only for useful details
Collect the name to print, a contact route, attendance reply and relevant meal preference. Ask the guest directly when a detail is unclear rather than making assumptions from a surname or family relationship. If someone requests a practical accommodation, discuss what information the venue actually needs before passing it on. Avoid adding private family commentary to a working list. Share each supplier only the details required for their role.
Close the loop on changes
Set a reply deadline early enough to meet the venue’s confirmed headcount deadline. Keep a short follow-up list rather than repeatedly messaging everyone. For example, if a household changes from three attendees to two, update individual attendance, meals and seating together. Mark the date of the latest change and identify the person responsible for telling suppliers. Before sending a final count, resolve unknowns explicitly instead of quietly treating unanswered invitations as either acceptance or refusal.
Take it with you
- Count individuals even when invitations go to households.
- Keep unanswered replies separate from confirmed attendance.
- Pass changes to the person who updates supplier counts.
AI Wedding
Wedding planning and dress inspiration
AI previews and style suggestions are illustrative, not fit assessments or objective judgments of appearance. Planning records do not replace supplier confirmations. Feature access and any paid options depend on current in-app terms.