Printed QR register and proof checklist
Approve location-specific URLs and tags, then verify physical proofs, destinations and analytics receipt together.
A register of what was installed where, with change and retest evidence
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 31 Oct 2026
- Use this for
- Use before printing posters, banners and partner notices, and after distribution, installation or URL changes.
When to use it
Use before printing posters, banners and partner notices, and after distribution, installation or URL changes.
Distinguish scans, measured visits, bookings and revenue. Do not put personal identifiers in public URLs or bypass consent.
Start with the guide: Event poster QR codes: UTM setup, print checks and traffic measurementFill in the template step by step
When to use it
Start with the distribution register, finish printing and installation checks, and retest URL changes.
What to have ready
- Print IDs, partners and installation plan
- Final URLs and UTM naming rules
- QR service ownership, edit rights and expiry conditions
- Physical print proofs and analytics test results
Record each print’s URL and identifiers and check that they contain no personal information.
Scan physical proofs with actual devices and compare recognition, destination and tags.
Check consented analytics tests and test logs; distinguish no-collection conditions.
Record print, delivery and installed quantities; retain approval and retest evidence for URL or location changes.
Worked example
Fictional example, not an actual event or supplier record
Eight columns · scroll horizontally to view the complete worked example.
| Print ID and location | Approved URL and UTM | Service rights and validity | Physical proof scan | Destination and tag retention | Analytics and test condition | Verified distributed quantity | Status, change, owner and due |
|---|---|---|---|---|---|---|---|
| QR-P01 / partner A entrance | https://example.test/a / source=shop_a, medium=qr, campaign=forum, content=p01 | Account R01 / redirect through 12-01 confirmed | Paper PR01 / QA phone recognised at 11-02 10:00 | Final A-v2 / tags retained QA01 | Consented test / values match; TEST01 isolated | — | 100-copy print approval A01 / production / verify installation 11-04 |
| QR-P02 / lobby banner | https://example.test/b / source=lobby, medium=qr, campaign=forum, content=p02 | Editing owner confirmed R02 | Paper PR02 / code cropped; scan failed | — | — | — | Hold 2-copy print / designer / revised proof by 11-02 14:00 |
| QR-P03 / partner B | https://example.test/c / source=shop_b, medium=qr, campaign=forum, content=p03 | Redirect after contract expiry not confirmed | Proof not yet received | — | — | — | Hold release / marketing / conditions and proof by 11-03 10:00 |
| QR-P04 / outside meeting room | https://example.test/d / source=hall, medium=qr, campaign=forum, content=p04 | A04 / URL change approved 11-05 09:00 | Paper PR04 rescanned against new notice successfully | New D-v3 / tags retained QA04 | No-consent test not collected; consented values match TEST04 | 30 | 30 installed / distribution / hand over old URL history and A04 |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
Eight columns · scroll horizontally to view the complete blank worksheet.
| Print ID and location | Approved URL and UTM | Service rights and validity | Physical proof scan | Destination and tag retention | Analytics and test condition | Verified distributed quantity | Status, change, owner and due |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
Sources used to develop this template
EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.
- Google Analytics · URL builders: UTM fields, case sensitivity and reporting (help checked 23 October 2026)
Use the guidance to check UTM naming, case and register alignment.
- Google Analytics · Prevent PII collection: restrictions in URLs, UTM and campaign fields (checked 23 October 2026)
Use the guidance to check that public URLs do not contain personal identifiers.
- Google Analytics · Redirects and URL-tag retention
Record checks of campaign tags after redirects.