1. The Core Pattern
The server issues a signed QR containing: visitor name (optional), allowed zones, valid-from and valid-until timestamps, and a random unique ID. The gate reader validates the signature and expiry offline or with a quick server ping.2. One-Time vs Multi-Use
* One-time: invalidated after first use, ideal for single-visit guests. * Multi-use with expiry: valid for a contractor working for one week, checked each entry against the server.3. Revocation
Server-side revocation works only when the reader has connectivity. For offline or low-connectivity gates, use short expiry windows so revoked passes expire quickly.4. Display
Send the QR to the visitor by email before arrival. Display it on their phone or print it, and include name and date so security can cross-check visually.5. Audit Log
Every scan event creates an immutable audit entry. This is valuable for investigating incidents or satisfying health-and-safety requirements.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.Codes that stay in circulation need occasional attention. Links change, pages move, and printed materials fade, so review each live code on a regular schedule and confirm it still opens the right destination. When a destination changes, update a dynamic code or reprint a static one on the same day, and remove old codes from circulation so nobody scans a dead link. Keep a simple register of where each code appears, what it points to, and when it was last tested, because a code nobody owns is a code nobody fixes.