Processed locally
Your input stays in this browser.
A wedding RSVP QR code should open the couple's response form, state the RSVP deadline in print, and offer a non-QR way to reply. Test the form with a guest phone before invitations are printed, especially where meal choices, plus-ones, or accessibility needs are collected.
Put the RSVP decision in plain text on the invitation
An RSVP QR code should open a response form, while the paper invitation states the reply deadline, a typed address or contact method, and what the guest is being asked to confirm. For an 84-person reception, ‘Reply by 12 May’ is more useful on paper than a deadline hidden after a scan. The form can collect attendance, meal choice, plus-one name where invited, and accessibility needs, but it should not expose the guest list or private address in the public QR payload.
Design the 84-guest response form
Start with a named invitation or a carefully designed lookup process, then ask one household whether it will attend. A party of two with one vegetarian meal is one response record with two attendance facts, not two unrelated comments. If the deadline is 28 days before the event, send a reminder to non-responders after checking the response list; do not assume that a scan means a submission. Test confirmation wording so a guest can see whether the answer was recorded and how to correct an error.
Proof the invitation with a guest phone
Export the actual card stock artwork, scan it in normal indoor light, and complete a test response using a non-owner account. Confirm that the form opens without an editor sign-in, the confirmation reaches the right organiser, and the meal question appears only for attendees. A code that looks crisp on a laptop may fail after foil, textured paper, or a very small placement. Include a reply email, phone number, or card option for a guest who does not use online forms.
Keep calendar and RSVP jobs separate
A calendar QR code can prefill a date, time, and venue; it does not ask whether a guest will come. An RSVP form records an answer but does not automatically grant entry or update an event calendar. When both are wanted, use two clearly labelled codes or give the calendar link after a response. Combining them in one unlabeled symbol makes the guest unsure whether they are confirming, saving the date, or opening directions.
Prevent predictable guest-list errors
Do not print each guest’s private token in a code that can be photographed and forwarded unless the RSVP system is designed for that risk. Do not ask for a plus-one before explaining whether one is invited. Avoid a mandatory dietary question for a person who declines. After the deadline, reconcile the form against the invitation list and contact ambiguous records instead of guessing from a first name. Preserve a copy of the submitted answers before changing form fields.
Use the responses to make a seating decision
An RSVP code records an answer; it does not issue an entry credential or update a guest automatically when plans change. Google Forms sharing behaviour is documented by Google Forms Help at https://support.google.com/docs/answer/2839588?hl=en. The QR image cannot verify identity, force a response, or resolve a late change in plans. Treat it as one response channel and turn the final, checked count into catering, seating, and accessibility follow-up.
Reconcile households rather than counting form rows
For an 84-person reception, the useful count is people attending, not simply submitted forms. Suppose 38 households receive invitations: 25 households reply yes for 51 people, 8 reply no for 14 people and 5 have not replied. A household that changes from two guests to one must update the meal count, seating list and accessibility notes together. Keep a column for invitation status, submitted timestamp and organiser follow-up; do not infer attendance from a QR scan or an incomplete name. After the stated deadline, contact the five non-responding households through the printed fallback channel and record the final decision before giving catering a number.
Handle corrections without exposing the guest list
A confirmation page should say how a guest can correct an accidental meal choice or a misspelled plus-one name. It should not display every attendee, reveal an address or let a forwarded link edit another household's response. Test a change request using a non-owner account before printing. If the RSVP provider sends a confirmation email, check that it names the event and the submitted attendance without exposing more data than necessary. Keep the public QR payload as a route to the response process, not as a container for names, meal choices or an invitation secret that can be photographed on a refrigerator.
Freeze a final catering record
Seven days before the event, export a dated response list and calculate separate totals: 65 adults, 6 children, 11 vegetarian meals and 3 access arrangements, for example. Compare every total with the invitation record and resolve duplicate or ambiguous submissions before sharing it with catering or the venue. Keep late changes in a small change log rather than overwriting the original answer with no trace. The RSVP code can remain on the invitation after the deadline, but the destination should say that online replies are closed and show the organiser's contact route. A silent expired form makes a guest think their answer was recorded when it was not.
Use a closing message after the reply date
After 12 May, replace the active RSVP form with a page that states replies are closed, names the event and gives the organiser's chosen contact method for a genuine late change. Do not leave a form that accepts an answer the seating list will never see. Test the closing page from the printed code and include it in the final guest-record check. This preserves a courteous route for an invitee while protecting the catering total. It also makes the distinction clear: a camera can open the response channel, but only the checked and reconciled record changes the plan.
Confirm the organiser can see the response
Before mailing invitations, submit one test household response and verify that the organiser sees attendance, meals and correction contact in the same record. A confirmation page alone is not enough.
Count meal choices after attendance
Calculate meals from confirmed attendees, not from every answer ever submitted. A corrected no-response must remove its earlier choice from the catering total while preserving the change record. Google Forms Help is the named source for the current external rule or product behaviour.