Skip to content
Generated by AI.
Log in

How to Plan a Road Race: Route, Road Closures and One Map for the Whole Team

Szymon Jędrusik, founder of PlanPlace

Written by: Szymon Jędrusik

5 minute read

Isometric illustration of a race route through a park with checkpoints. Generated by AI.

On a map, a road race looks simple. A route, a start, a finish, a few water stations — done.

In practice, organising a sports event in a city is much more complex because the route cuts through space that is normally used by residents, public transport, delivery vehicles and emergency services.

Time adds another dimension. The same street may be open at 7:00, closed at 9:00 and reopened two hours later.

That is why a sports event plan should show not only where something is located, but also when a particular setup applies.

This is where a static drawing starts to fall short.

The route is only the beginning

Drawing the route itself usually takes relatively little time.

Most of the work begins immediately afterwards.

For every section, the team has to answer practical questions:

  • where does the route cross important intersections
  • will residents still be able to leave their streets
  • where will bottlenecks appear
  • how will an ambulance get through
  • where should volunteers be positioned
  • how should crossings be secured
  • where can water points be placed
  • where can spectators watch safely

Problems start when the route is in one map, the intersection list is in a spreadsheet, volunteer staffing is in another file and diversion arrangements are buried in messages.

After the first route change, someone has to manually check what else needs to be updated.

In PlanPlace, the map can remain the main point of reference. An intersection can have its own information, task and comment attached to it, while the whole team sees the current route.

Instead of writing “the junction near kilometre 8” in a message, the team can work directly on the exact location.

The city changes several times during the race day

For a road event, the spatial plan is also a timeline.

At 6:00, signs start to appear. At 8:00, the first streets are closed. At 10:00, runners are already using one section of the route while earlier sections may be prepared for reopening.

Trying to show all of these states on one drawing often produces a map that is difficult to read quickly.

In PlanPlace, the different moments of the event can be separated into individual plan levels.

For example:

  • a level before road closures
  • a level for the race itself
  • a level for the final stage of the event
  • a level for dismantling and reopening roads

Instead of looking at several overlapping versions of traffic management, the team can switch between clearly defined stages.

This is particularly useful for temporary traffic management, where the location of a barrier or sign matters just as much as the time at which it should appear and disappear.

Fewer spreadsheets, more information directly on the route

For a larger race, the list of route elements grows quickly.

It may include:

  • food stations
  • hydration points
  • medical stations
  • toilets
  • timing points
  • volunteers
  • officials
  • spectator zones
  • signs and barriers
  • kilometre markers
  • baggage areas and technical support

Each of these elements has more than just a location.

A water station may need a specific number of tables and staff. A medical point needs vehicle access. An intersection may require a particular number of volunteers and a specific closure time.

In PlanPlace, this information can stay attached to the object on the map.

In practice, the plan becomes more than an image. It becomes a working database for the event.

Start and finish: where chaos is easiest to create

The start and finish area is usually the most intensively used part of the entire event.

A relatively small space has to accommodate:

  • race office
  • baggage drop
  • start waves
  • warm-up area
  • timing infrastructure
  • water
  • medals
  • recovery zone
  • stage
  • catering
  • media
  • toilets
  • organiser back-of-house

That is why this part of the event is worth treating as a plan in its own right.

In PlanPlace, it can be drawn in more detail and continuously checked for collisions between different elements.

Three routes matter most:

runner before the start — entrance, baggage drop, start sector,

runner after the finish — medal, water, recovery, baggage and exit,

spectator — access to viewing areas without crossing the runners’ flow.

If all three groups meet in one narrow passage, the problem is already visible on the plan before race day.

Barriers and infrastructure should not be counted separately

At a sports event, infrastructure can be spread across many kilometres.

Barriers, toilets, signs and technical points are easy to count in the first version. Keeping the totals correct after several route changes is much harder.

In PlanPlace, objects placed on the map are included in the inventory, so the list reflects the current layout.

If the secured section becomes longer or new elements are added, there is no need to manually compare the map against an order spreadsheet.

The inventory can be exported and used with suppliers or the technical crew.

This is particularly valuable for events where infrastructure is distributed across the city rather than concentrated in one venue.

A volunteer should know exactly where to be

Sports events often rely on a large number of people who work together for only one day.

That means the organiser cannot assume everyone knows the area or remembers every instruction.

“Stand at the second junction after the roundabout” may sound clear during a briefing. On race day, it may not be clear at all.

It is much more practical to attach a task to a specific location on the map.

In PlanPlace, tasks and comments can be linked to objects or points in the plan. The team can see not only what needs to be done, but exactly where.

Task status can also show whether signs have already been installed or a particular location has been staffed.

Instead of another round of phone calls, the organiser has the information next to the location it concerns.

The same plan for the organiser, technical team and route security

A city race involves many teams:

  • organiser
  • security
  • medical teams
  • route protection contractor
  • volunteers
  • technical team
  • traffic management staff

If each group receives a separate PDF, any route change requires all materials to be updated.

With PlanPlace, everyone can work from one current plan and external teams can be given access through a link.

An external contractor does not need to see internal comments or tasks. They can simply see the current route and infrastructure.

The real difference becomes obvious when one intersection changes the day before the race.

There is no need to ask who has already received the new PDF.

The change is visible on the current plan.

What about events in a stadium?

For events held in a closed venue, the layout changes but the workflow stays similar.

Instead of kilometres of route, the plan includes:

  • sectors
  • entrances
  • buffer zones
  • evacuation routes
  • medical points
  • security positions
  • circulation routes

If the venue has several floors or tiers, separate plan levels can represent the different floors or sections.

The whole venue remains in one project rather than being split across separate drawings.

What should you check before the start?

RouteAre all intersections, narrow sections and problem points marked?
TrafficAre the different closure and reopening stages clear to the team?
Route pointsDo they have the right information, equipment and staffing attached?
Start and finishDo runner and spectator flows avoid conflicts?
InfrastructureDoes the inventory of barriers, toilets and other elements match the map?
TeamDoes every important location have a responsible person assigned?
SharingAre contractors using the current version of the plan?

The race plan should also work on event day

A map prepared only to present the route does only part of the job.

On race day, the team needs a plan where they can quickly check where a barrier is located, who is responsible for an intersection, when the road should reopen and whether a technical point is ready.

PlanPlace brings all of this information together on one plan.

The map therefore does not stop being useful when the route is approved. It can support the organiser through preparation, build-up, the event itself and dismantling.

For a road race, that is what really matters: not only knowing where the route goes, but keeping everything around it under control.

Generated by AI.

Build a plan for yourcity-wide event

One shared plan for the whole team. No more out-of-date PDFs and chaos in your inbox.