The Pub Table Test: Getting QR Campaigns Right Where People Actually Scan

The QR code has had a strange second life. In 2026 you will find one on a pub table, a festival wristband, a parish council noticeboard and the window of a pop-up selling cinnamon buns. Most of them work. Some fail in ways that are entirely avoidable: a link that points at a desktop PDF, a code printed too small for a rainy afternoon, or a redirect that dies the moment the campaign page is moved.

That is the awkward thing about print. Once the ink is on the laminate, you cannot edit the square. But you can edit the short link behind it. That is why a QR campaign is really two campaigns: the physical design and the link management. Here is a practical checklist for UK teams who need both to hold up in the real world.

Test the destination before you test the printer

Start with the page, not the code. Open the destination on an actual phone, on mobile data as well as pub Wi-Fi. Check that it loads quickly, that the text is readable without pinching, and that the main action is obvious. A menu, a booking form, a timetable or a sign-up should be reachable in one or two taps.

Avoid sending scans to a PDF unless you have a very good reason. PDFs are fiddly on phones, hard to read in bright light and often inaccessible. If the destination is a form, test it with a real submission. If it is a map, check that the pin is correct. If it is a video, assume someone is standing outside in the cold and will not wait.

Use a short link you control. A branded domain such as yourcharity.org.uk/quiz is easier to trust than a random string from a free tool. It also gives you somewhere to redirect if the page moves.

Make the code survive rain, thumbs and bad lighting

A QR code is a piece of print design, not just a technical asset. Give it contrast, space and a sensible size. The quiet zone around the code matters: do not crowd it with logos or borders. Print it large enough for the scanning distance. A code on a table tent needs to work from a seated position; a code on a window needs to work from the pavement.

Laminate outdoor material or put it behind glass. Test it in the actual location at the actual time of day. A code that works under office lighting may fail on a dark pub table or a sunlit noticeboard. Add a short, readable URL underneath the code for anyone who cannot or will not scan. That also helps accessibility and gives people a fallback if their camera is being difficult.

Do not make the code do too much. One code should have one clear job. If you need to distinguish between tables, posters, windows and leaflets, use separate short links rather than one code with a vague promise.

Put the link on a leash with dynamic redirects

A dynamic redirect lets you change the destination without reprinting. That is useful when a venue changes, a booking page moves or a campaign ends. It is also a responsibility: do not use it to spring a surprise on people. The destination should still match what the printed material promised.

Keep redirect chains short. Every hop adds delay and another thing that can break. Set a fallback page for expired campaigns, even if it is just a friendly note with a contact route. Check redirects from different networks and devices, including older phones. If the link is going into a parish newsletter, assume someone will try it on a five-year-old handset with a cracked screen.

Measure scans without being creepy

Scan analytics are useful, but they are not a licence to hoover up personal data. Use UTM parameters or separate short links to see which placements work. Count scans by poster, table, event or noticeboard. Keep the reporting simple: total scans, unique-ish scans, device type, time of day and conversion if you have a landing page that allows it.

Be careful with location and device data. Under UK GDPR, you need a lawful basis and clear information if you are collecting personal data. For most pub, pop-up and parish council campaigns, aggregate counts are enough. Put a short privacy notice on the landing page, or link to the organisation's main notice. If you are asking people to sign up, say what you will do with their details and how they can opt out.

Use design rules that survive a committee meeting

Good QR campaigns are boring in the best way. The label says what happens next: Scan for the menu, Scan to book, Scan for the agenda. The short link is visible. The code is big enough. The destination is mobile-friendly. The privacy note exists. The campaign has an owner.

Write down the link inventory before you print. Record which short link goes on which item, who owns it, where it redirects and when it should be reviewed. That record is your link audit in miniature. It saves an enormous amount of guesswork when someone asks why the poster in the window is sending people to last year's fireworks night.

The pre-print checklist

• Does the destination work on a phone, on mobile data, without logging in?
• Is the page fast, readable and accessible?
• Is the short link branded, short and controlled by your organisation?
• Can you change the destination later with a dynamic redirect?
• Is there a fallback page if the campaign ends or the page moves?
• Is the code large enough for the real scanning distance?
• Does it have enough contrast and quiet space around it?
• Will it survive rain, glare, fingerprints and a bit of rough handling?
• Is the human-readable URL printed underneath?
• Does each code have one clear job and one owner?
• Are you collecting only the scan data you actually need?
• Is there a privacy notice or clear information at the destination?
• Have you tested the whole thing in the actual location?

If you can tick those boxes, you have done the unglamorous work that makes a QR campaign feel effortless. The square is only the beginning. The short link is where the campaign keeps living after the printer has gone home.