The Simplest QR RSVP System
You do not need paid event software to build a QR RSVP system. A Google Form + Google Sheets + a QR code is fully functional for most events up to 300 guests.
Step 1: Create a Google Form with: Name, Email, Number of guests attending, Dietary requirements, Any other notes.
Step 2: Enable email notifications in Google Forms (Responses > Enable notifications).
Step 3: Copy the form URL and generate a static QR.
Step 4: Print the QR on invitations, posters, and any digital communications.
Step 5: Monitor responses in the linked Google Sheet.
Cost: £0. Setup time: 20 minutes.
RSVP QR on Physical Invitations
On a physical invitation:
- Include the QR prominently on the lower half of the card
- Label it clearly: "Please RSVP by [date] — scan to confirm attendance"
- Include the form URL as text for guests without smartphones
- Test scan from arm's length before printing
Confirmation and Reminder Automation
Google Forms does not send automatic confirmations to respondents. For a professional experience, use:
- Jotform or Typeform (free tier): Send a branded confirmation email on submission
- Google Forms + Zapier: Trigger an email via Gmail on each response
- Paperform or Tally.so: Include automated confirmation emails in free tiers
A confirmation email should include: event name, date, time, location (with Google Maps link), dress code, and a calendar invite attachment.
Managing Waitlists via QR
When your event is at capacity, update the RSVP QR destination (use a dynamic QR) to point to a waitlist form rather than the standard RSVP. If a confirmed guest cancels, contact the first person on the waitlist and issue them a confirmation QR.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
