RSVP Website · · 1 min read
Two Families, One RSVP Record: A Planning Story
An illustrative planning story about reconciling wedding replies collected by both families. The people and situation are fictional; this is a worked example, not a client testimonial.
The situation
Imagine a couple whose parents each maintain a guest sheet. A shared aunt confirms to both sides, while a cousin replies through the invitation website. When the lists are added together, three responses look like three separate invitations even though two belong to the same household.
The planning decision
The couple appoints one coordinator and gives each household a reference. Rather than deleting similar names immediately, the coordinator checks the invited people and confirms whether the replies overlap. Earlier entries remain marked as superseded so another relative can understand the correction.
The useful detail
In this example, a household confirms two adults for the reception and one adult for the ceremony. The coordinator records those counts separately. The reception caterer receives the relevant total, while the ceremony seating list receives its own export. Neither supplier needs the family's entire conversation history.
What to borrow
Use a single master record, named event columns and a dated change log. Ask callers to report corrections to the coordinator instead of creating new totals. This approach would make a duplicate visible before it reaches the catering handover. It does not remove the need for a final guest check; it makes that check easier to perform.