Marathon event UX starts beyond the finish line

Marathon event UX includes the people moving around a race as well as those running in it. For an event marketer, access information, local enquiries and the end of road restrictions belong in the experience brief alongside registration and race-day branding.

Whose experience should a race brief include?

A resident does not need to buy a ticket to be affected by an event. In an October 14, 2026 Mobiinside column, contributor Winter Note argues that running events should be assessed from the perspective of nonparticipants too. This is a discussion of that argument and its practical implications, rather than a report announcing new municipal rules.

The editorial distinction matters. Estimates of runner populations and event volumes in the original column are not presented here as independently verified statistics. A particular race's permit conditions or cancellation reasons require confirmation from its organiser and the responsible authority.

Takeaways for marketers: put access into the brief

Our recommendation is to add a local-access workstream before the campaign goes into production. A sponsor can deliver an attractive participant experience while leaving a poor impression on the surrounding neighbourhood. Treating those outcomes separately helps a team see what its audience survey cannot capture.

1. Map residential entrances, nearby businesses and transport connections around the proposed venue.
2. Identify the information each affected group needs before arrival, during the event and after restrictions end.
3. Assign ownership for updating public information when an approved operating plan changes.
4. Give field staff a shared reference so a resident receives the same answer at different points around the course.

These are planning recommendations, not a list of legal requirements. Published route information should match the approved plan. If permission is pending, creative materials should avoid making an unconfirmed route look final.

How should teams assess the surrounding experience?

Record participant feedback separately from local enquiries. The distinction is useful because the two groups may encounter different failures. A runner might praise the atmosphere while a nearby customer cannot find an open entrance to a shop. Combining those responses into a single satisfaction score can hide the operational problem.

Create an issue log that records the place, the question, the information available at that moment and the action taken. A recurring parking question may point to an information-location problem rather than a lack of promotional reach. Check whether someone approaching the site on a phone can find the answer, and whether a field worker can give that same answer.

The review should also distinguish a missing notice from an inaccurate notice. Adding more distribution does little if the underlying access instruction is wrong. A useful post-event discussion asks which decision would prevent the same problem at the next event, and who has authority to make it.

For a branded community event, define these communication tasks when setting the scope of the campaign. Best Partner's Services can provide a starting point for discussing campaign responsibilities, while the organiser retains responsibility for confirming the operating plan.