Every wedding produces the same set of phone calls. Where exactly is the venue. What time does the ceremony start. Is there parking. What is the dress code. Which hotel did you say.
Someone in the family ends up answering these forty times over three weeks.
A QR code on the invitation solves nearly all of it, and it has become one of the more sensible uses of the technology I have seen.
What to put behind the code
Build one simple page with everything on it. Not a fancy site, just a clear page.
A map link that opens directly in navigation, not a screenshot of a map
The full schedule with times for each function
Parking instructions, especially if the venue is difficult
Nearby hotel suggestions with a rough price range
Dress code, if there is one
A phone number for the person handling arrangements
That page then goes behind one code. Guests scan once and stop calling.
RSVP without the chasing
The second best use is a code pointing at a short RSVP form. Name, number of guests, which functions they are attending, any food restriction.
The answers land in one place instead of arriving as scattered WhatsApp messages that someone has to compile at midnight. For anyone who has tried to count attendance from a chat thread, this alone is worth doing.
Keep the form short. Four questions. People fill in short forms on phones and abandon long ones.
Photos, in both directions
Before the wedding, a code can share the schedule. After it, the same code can point to the photo album.
If you use a dynamic code you can change the destination afterwards with no reprinting. If you use a static one pointing at a page on your own site, you can change the redirect and get the same result.
There is also the reverse version. A code on the tables pointing at a shared upload folder, so guests can add their own photos. You end up with hundreds of pictures the official photographer never took, from angles they could not reach.
Making it look like part of the card
This is where a personalized qr code generator earns its place. A default black square on a gold-bordered invitation looks like an accident.
Match the code colour to the invitation. Deep maroon, navy, forest green, whatever the card uses, as long as it stays clearly darker than the background.
You can soften the corners of the pattern and drop a small monogram in the centre. Just keep the logo under about a fifth of the middle area, and keep the empty margin around all four edges.
Then test the styled version. Every design change costs a little readability, and a code that looks perfect in a design file sometimes fails on paper.
Printing without regret
Give your printer a vector file, not a small image. A code stretched from a low resolution file prints with soft edges and fails on older phones.
Keep it at least two and a half centimetres square on an invitation card. Bigger on a welcome board at the venue.
And print one test card before the full run. Scan it under normal indoor light, from a phone that is not the newest model in the house. Four minutes of checking against a print run of three hundred cards is an easy trade.
Add a line of text
Do not leave a bare square on a card. Older relatives will not know what it is for.
Scan for directions and details is enough. Six words. Put them right under the code, in the same font as the rest of the card.
Where to make it
For a wedding you need one or two codes, styled to match, downloaded in print quality. There is no need for a subscription.
I use a custom QR code generator for these because the colour and shape controls are on the same screen as the preview, so you can match the card's palette while looking at the result rather than guessing.
Not just weddings
Everything above works for a birthday party, a housewarming, an engagement, a conference, a school reunion.
Same principle every time. One page holding every answer, one code pointing at it, one short line of text telling people why to scan.
One code, not five
Resist the urge to print separate codes for the map, the RSVP, the gift registry and the photos. An invitation with four squares on it looks cluttered and guests will not know which to scan.
One code, one page, everything on that page with clear headings. It is easier to design, easier to explain, and far easier to fix if something changes, because you only update the page.
Keep the old information too
A wedding guest list usually spans four generations, and not everybody in it is going to scan anything. That is fine, and it is not a reason to skip the code.
Just keep the essentials printed on the card as well. Venue name, date, start time, one phone number. The code carries the detail; the card carries the basics. Guests who scan get everything, guests who do not still know where to be and when.
This is the balance most invitations get wrong in one direction or the other. Either everything is crammed onto the card, or the card says almost nothing and assumes a phone.
The phone calls stop. That is the entire benefit, and anyone who has hosted a large event will tell you it is a considerable one.
0 Comments