RSVP Form Launch Checklist
==========================
A pre-launch checklist for hosts and planners to run through before the invitations go out, so the reply form collects attendance, meal choices, and dietary needs in one pass and the follow-up plan is already in place.

[ ] The reply path is a single link that opens on a phone and needs no account, password, or app download; a guest can finish it in under two minutes.
[ ] The reply-by date is earlier than the date you actually need, and the invitation says why (for example, the caterer's guarantee deadline).
[ ] The form asks for attendance, party size, and every attending guest's name in the same pass; there is no plan to collect meal choices later.
[ ] The guest list holds two layers: one record per invited household and one row per named individual, so seats, meals, and place cards can be counted per person.
[ ] Plus-one rules are written down before sending: who gets one, whether the plus one must be named, and whether the plus one picks their own meal.
[ ] The form enforces those plus-one rules automatically rather than relying on guests to read the fine print.
[ ] Children are handled explicitly: whether kids are invited, whether there is a children's meal, and the age at which a child counts as an adult plate.
[ ] Meal choice and dietary restriction are two separate questions on the form, never one combined field.
[ ] Menu options are described the way a guest reads them, with any option that is already vegan, gluten-free, or nut-free labeled as such.
[ ] There is a free-text field for allergies and restrictions, and a severe allergy stays attached to the named guest, not just a tally.
[ ] Guests see a confirmation of what they chose after submitting, and receive a short confirmation message they can check later.
[ ] Every guest can reopen their own reply link to change their party or meal, so changes land in the list with a timestamp instead of in your inbox.
[ ] Each household has a status field (not sent, sent, partial reply, complete, declined) and a date of last change.
[ ] A change log exists, so you can see who moved from two guests to three and when.
[ ] Contact details for every household are on file (phone and email where possible) so a bounced invitation has a second channel.
[ ] The reminder schedule is drafted before sending: a friendly nudge about a week before the reply-by date, a second on the date, and a personal text or call a few days after.
[ ] Reminder messages are segmented: partial replies, silent households, and bounced contacts each get a different message or channel.
[ ] A hard internal cutoff is set after which silent guests are marked declined and any late yes is handled as an exception.
[ ] The caterer's guarantee deadline, the buffer they build in, and what they will do with an unexpected guest are confirmed in writing.
[ ] The final headcount will be produced by filtering the list (attending guests grouped by meal), not typed into a separate document.
[ ] You know which filtered views each person needs: counts and restrictions for the caterer, totals and a seating chart for the venue, names and tables for the day-of coordinator.
[ ] Two or three real people have tested the form on a phone and confirmed that the meal descriptions are readable without zooming.
[ ] A dated copy of the guest list and the final count will be saved before the caterer summary is sent.