The Static Timetable Problem
A timetable printed on a bus shelter or railway noticeboard is outdated the moment a service change occurs. Emergency timetable disruptions render them actively misleading. A QR linking to live timetable data always shows current service information.
QR at Bus Stops
Live timetable QR:
A QR on the bus stop pole or shelter links to a live departure board for that specific stop. The URL can encode the stop ID: `https://bustimes.org/stops/ABCD1234` or the equivalent Traveline or Transport for London page. When the user scans, they see the next live departures with real-time GPS tracking where available.
Journey planner QR:
A QR linking to a journey planner pre-populated with the bus stop as the starting point. The user enters their destination and receives the optimal route.
Ticket purchase QR:
A QR linking to mobile ticket purchase for the route(s) served by the stop. On-device purchase with a phone-based ticket eliminates cash and card machine dependency.
QR at Railway Stations
Platform information:
QR linking to live platform information for trains departing from that platform.
Delay repay:
QR on the station information board linking to the delay repay claim form. Passengers whose train is delayed can claim compensation immediately from the platform rather than remembering to do it later.
Accessibility assistance:
QR linking to the passenger assist booking system — allowing passengers with accessibility needs to request station assistance for future journeys.
London TfL QR Example
Transport for London deploys QR codes on bus stops linking to live departure data via the TfL API. The QR encodes the stop ID; the linked page shows live buses using real-time GPS data. This is a model for modern public transport QR integration — accurate, live data at the point of need.
Network Rail and TOC Applications
UK train operators increasingly include QR codes on:
- Delay repay claim letters
- E-ticket confirmation emails (QR as the ticket itself)
- At-station signage linking to live departure boards
- Refund and exchange portals
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.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
