Race direction · road marathon
Mile nineteen
In the voice of a race director for a mid-size city marathon with a substantial international field.
A marathon is the worst possible shape for a public address system. The event is twenty six point two miles long and my PA covers about four hundred feet of it, at the finish, where the people who most want to hear something are stuck behind a barricade and mostly cannot anyway.
Everywhere else on that course — and there are spectators everywhere else on that course, thats the joy of the thing — there is no information at all. You stand at mile nineteen for two hours holding a sign. You do not know where the lead pack is. You do not know if your runner has already come through. You do not know if they pulled somebody at fifteen with cramps. You know nothing, in a city, at a public event, for two hours.
We put the finish line call on a channel, free, and put the QR code on every course marshal's vest and every mile marker sign. Spectators at nineteen now hear the same call as the people at the finish. Its a small thing and the feedback was completely out of proportion to how small it was.
The part I actually want to write about is the languages. We have got a big Brazilian contingent, a growing Japanese one, and a lot of Mexican club runners who come as a group. Their families travel for this. Somebody flies from São Paulo to watch their daughter run and then stands at a barricade for four hours understanding nothing that comes out of a speaker.
The call is now in whatever language they pick. Portuguese, Japanese, Spanish, Korean. Same announcer, same moment. And it changed the finish area in a way I did not anticipate — the crowd reacted at the right time. For years the finish had this weird dead quality where a big moment would happen and a third of the crowd would just not react, and I had privately chalked that up to culture or reserve or whatever. It was not that at all. They did not know it had happened. Nobody had told them in a language they use.
Two operational notes for anyone doing this on a course. Test your data coverage along the route, not at the finish — the finish is where you have got infrastructure and mile nineteen is where you dont, and mile nineteen is the whole point. And keep it strictly separate from your medical and course-safety comms. Those stay on the radio system where they belong, and I would say the same thing to anybody who asked me about it, including if it made this a smaller idea.
About this piece
Constructed, not collected. The voice here is an assumed role rather than a person, and nothing in it is an interview or an account of a real race, director, field or event.
Medical, course-safety and operational communications belong on purpose-built radio systems, not on consumer data service. Available languages are set by the underlying translation service and change over time — confirm current coverage before promising a specific language to a specific community. Data coverage along a long point-to-point course is uneven by nature; survey it before you rely on it.
Start a channel on BYOPA — free, and one race day will tell you where your coverage actually fails.