Self-Guided Walking Tour QR Codes: Stop-by-Stop Setup

Stop six is a bronze plaque on a wall behind a bus shelter. The plaque is fine. The problem is that the visitor arrived from stop three, walked past four and five without knowing they existed, and is now listening to two minutes of narration about a river she crossed ten minutes ago.

A walking tour is not a venue with a route through it. It is a set of unattended objects spread across a town, and the failures are geographic.

Number Every Stop and Say How Many There Are

Put "Stop 4 of 11" on the plaque and repeat it at the top of the page.

That one string does three jobs. It tells a visitor where they are in a sequence. It tells someone who joined at stop seven that there is something behind them. And it gives you a labeled series to measure, which is the only reason the last section here is possible at all.

Every stop page should close with the same block:

• The next stop's name and number.
• A direction and a rough distance. "Left at the fountain, 250 meters."
• A map link for people who would rather follow a blue dot. A maps link pointing at the next stop's coordinates is a two-tap escape hatch for anyone who has lost the thread.

Assume people walk the route backward, join in the middle, and do half of it. Numbering survives all three. Pure narrative sequencing does not.

Pages Built for One Bar of Signal

The route runs along a riverbank, under tree cover, through a street of stone buildings, and past a spot where three networks all show one bar. Build for that, not for the office wifi where you tested it.

A working budget for a stop page:

• A few hundred kilobytes in total. Not a few megabytes.
• One image, sized for a phone screen and compressed, never the print-resolution original.
• Text early in the document, so something is readable while the image is still arriving.
• No autoplaying video, no background video, no carousel.
• Audio behind a play button the visitor presses deliberately, so nobody burns a data allowance by walking past.
• No web font that blocks the first paint. A system font stack renders instantly, and nobody on a walking tour is grading your typography.

Then test on the route itself. Cheap phone, cellular data, data saver on, standing where the plaque is. A page that loads in 400 milliseconds at your desk can take fifteen seconds at stop nine.

The Stop With No Signal at All

Some stops will have no usable connection at any hour. What a code can and cannot do without a network is covered in offline behavior, and the practical answer for a tour is to hand people the whole route while they still have bars.

Two fallbacks worth building:

One downloadable file for the entire tour. All eleven stops, text and small images, in a single document a visitor saves at the trailhead. A PDF works if you keep it small and the text is real text rather than scans of a leaflet. Stay under a few megabytes, or people cancel the download.

A printed leaflet with matching numbers. Same stop numbers, same directions, same order. Available at the tourist office, the cafe on the corner, the visitor center. Paper has a battery life that phones do not.

Advertise both at stop one and on the entry signage, because that is the last place you can rely on a connection.

Plaques That Survive Weather, Sun, and Hands

An outdoor code is a manufactured object with a service life.

• Substrate. Anodized aluminum, etched or engraved, or a UV-stable print under outdoor laminate. Ordinary vinyl on a south-facing wall fades to unreadable within a season or two.
• Finish. Matte. A glossy plaque in direct sun reflects into the camera, and the code disappears at exactly the hour most visitors are walking.
• Height. Roughly 120 to 140 centimeters to the center for a standing adult, and reachable by someone seated. Not above a hedge that will grow.
• Standoff. Where a visitor cannot get close, behind a railing or across a road, the code has to grow to match the distance. Measure the real standing position before you size the artwork.
• Margin. Keep the quiet zone clear of the plaque's border and any decorative frame.
• Production. Substrate, resolution, and ink behavior are covered in the print notes.

The step people skip is permission. Every plaque sits on a wall, post, or railing belonging to someone, and a heritage route stitched across a town center will involve several owners. Get that in writing before the plaques are manufactured, not after.

Reading the Drop-Off Curve

Numbered stops give you an ordered series of scan counts, and the shape of that series is the most useful thing the tour will tell you.

Stop one is your ceiling. Every later number is a fraction of it, and a gentle decline is normal, because people run out of time.

What you are hunting is the single largest drop between consecutive stops. That gap is where people give up, and the cause is almost always physical:

• The direction text from the previous stop is wrong or ambiguous.
• The walk is longer than the page implied.
• There is a road crossing, a hill, or a dead end in between.
• The next plaque is mounted where nobody looks.
• The stop before it has no signal, so the visitor never got the directions.

Walk that segment yourself with the page open and you will usually find it in one pass. Then fix the destination without touching the plaque, which is what a dynamic code makes possible. The physical object stays on the wall while the page behind it changes.

Keep the collection light. Counts per stop, per day, are enough to find the broken segment. An indoor version of the same measurement problem is worked through in the museum engagement notes.

Build Stop One Properly, Then Repeat It

Make a single stop page, put it on a real plaque at the real location, and walk to it on a phone with data saver enabled at the busiest hour of the day. If it loads in under three seconds and the next-stop directions get you to the second location without a second guess, the other nine stops are the same work repeated.