Static: A calendar payload is a direct event snapshot; it is not a live subscription.
What to put behind the code
A calendar event with UTC times, title, location and a concise description.
Print for the place it will live
Starting size: 3 × 3 cm. This is a starting point, not a scanning guarantee. Place it within reach on a programme or information desk.
Use a flat paper programme with an unbroken white margin. Keep the four-module quiet zone intact and use dark modules on a light background. Read the print-size guide.
Where to place it
- Programme back page
- Registration desk
- Speaker information sheet
Mistakes to avoid
- Treating a saved event as automatically updating
- Ignoring the local timezone conversion
- Using the code as an admission ticket
Before committing to a print run
Print a proof on the final material. Scan it with more than one phone, from the normal viewing position. Check the opened destination while signed out and confirm it leads to the intended page or action. A readable fallback address or contact detail helps visitors who cannot scan.
Questions about events
Will saved events update if I change the schedule?
No. A static calendar code creates a copy. Use a dynamic URL to a schedule page when timing may change.
What should I test before printing?
Scan the final events artwork on more than one phone. Check the destination or imported details, the real viewing distance and the final printed surface.