How bus operators plan around road closures on their routes
A closed street can strand a whole line. How bus operators find closures and roadworks near their stops early, decide on diversions and tell drivers and riders.
Part of the guide Workflow automation
Bus operators plan around road closures by checking the streets near every stop on a line before service starts and again through the day, sorting what they find by how many stops it touches, and turning each serious closure into a diversion decision with a note for drivers and a notice for riders. The aim is to know about a closed street from a list in the control room, not from a driver radioing in with a full bus behind a barrier.
This article is for service planners, control room staff and operations managers at city bus companies, school and shuttle contractors and regional coach operators. It covers what a closure costs a bus network, how to tie closures to stops rather than to a city map, a made-up example of a morning check, the mistakes that make alerts useless, and how an AI employee does the checking for you.
Why a closure hurts a bus more than a car
A driver in a car simply takes the next street. A bus cannot. It is tied to its stops, its timetable and roads wide enough for it, so one closed block can mean skipped stops, riders waiting at a pole the bus no longer passes, and a knock-on delay that spreads to every later trip on the line. Roadworks are the slow version of the same problem: a lane closed for three weeks quietly adds minutes to every journey until someone rewrites the running times.
So the question a planner asks is never simply where the closures are. It is which of my stops sit near a closure right now, on which lines, and is it bad enough to divert.
Tie closures to your stops, not to the city
A list of every closure in a big city is long and mostly irrelevant. The useful version starts from your own stops. Upload them once as a table with a name, the line, and latitude and longitude for each, and then check the area around each stop rather than the city as a whole.
- Search around each stop, not across the city. Traffic incidents set to around each incoming place gives every stop a count of incidents within the distance you choose and the closest one, with its kind and how far it is in metres.
- Pick a distance that matches how buses move. A few hundred metres catches a closure on the street the bus uses to reach the stop. Much wider and every stop in the centre lights up at once.
- Keep only stops that are affected. A Filter on incidents_nearby greater than 0 drops the quiet ones, so the morning list is short.
- Group by line. Three stops in a row on the same line near one closure is a diversion; a single stop is usually a note to the driver.
A worked example (made up)
Say a made-up operator runs 14 lines in Lisbon with about 600 stops. The control room wants a list on screen at 05:15, before the first departures, and a second check at 11:30 for the afternoon peak. One morning the check finds closures near 9 stops:
| Line | Stops near a closure | Nearest incident | What the planner decides |
|---|---|---|---|
| Line 4 | 4 in a row | Road closure, 80 m | Divert for the day, skip two stops |
| Line 11 | 2 | Roadworks, 210 m | Tell drivers, add a few minutes |
| Line 2 | 1 | Incident, 290 m | Watch at the 11:30 check |
| Line 7 | 2 | Road closure, 140 m | Call the road authority first |
A made-up morning check for an imaginary Lisbon operator. The figures are illustrative, not measured.
Line 4 is the only real diversion. Because four consecutive stops sit beside the same closure, the planner picks a parallel street, posts a notice at the skipped stops and tells the drivers before they leave the depot. Line 11 needs nothing more than a warning. Line 2 might clear by lunchtime, which is exactly why the second check exists.
The same idea works for a regional coach company in Nairobi checking the few stops where its coaches pick up in the city, or a shuttle contractor in Toronto with a dozen pickup points around business parks.
Speeds as well as closures
A road can be open and still crawl. Traffic Flow measures the current speed and the free-flow speed on the roads around each stop, a jam factor from 0 to 10 and a level in words, at the moment the flow runs. It does not count vehicles and has no history: to see your afternoon peak, run it during the afternoon peak. Planners use it to spot stretches where running times are slipping, not to plan a single trip.
Mistakes to avoid
- Checking once a day. Closures appear and clear during the day. A morning list and a midday list cost little more and catch far more.
- A radius that is too wide. If every central stop is flagged every day, the control room stops reading the list.
- Sending the full list to every driver. Drivers need their own line, in one or two sentences. The full table belongs in the control room.
- Treating roadworks like a one-day closure. Works that last weeks deserve a timetable change, not a daily diversion.
- Forgetting the stops you added last month. Keep the stop table current, or new stops are never checked.
How to do it with an AI employee
An AI employee in xMap Flows can run this check on its own and put the result where your team already looks. The template Closures that need bus diversions, every hour is ready to start from; tram operators can use Roadworks near tram stops, every morning. Built from the blocks, it looks like this:
- Schedule: every day at 05:00 and 11:15, or every hour during service.
- My data: your stop table, with line and position for each stop.
- Traffic incidents: around each incoming place, within 300 m.
- Filter: incidents_nearby greater than 0.
- xMap LLM, working on the whole list: group the stops by line and write one short line per line saying whether it looks like a diversion or a warning.
- Email to the control room, with a map of the affected stops.
What lands in the inbox each morning is a short note, line by line, with the affected stops, the nearest incident to each and a map. On a quiet day there is nothing to send. If you want the employee to wait for a planner before anything goes to drivers, put an Approval step before the message.
Questions
Can it tell me how many buses a closure delays?
No. Traffic incidents says where a closure is and what kind it is, and Traffic Flow gives speeds and a jam factor. Neither counts vehicles, so working out the effect on your fleet stays with your own scheduling system.
How often should the check run?
Before first departures at the least, and again before the afternoon peak. Busy networks run it every hour during service so a new closure reaches the control room quickly.
Do I have to draw my routes on a map?
No. Uploading your stops with their positions is enough: the check runs around each stop. You can also draw areas on a map in the Area of interest block if you prefer to watch corridors.
Will it alert me to planned works next month?
It shows what is on online maps when it runs, which includes works already in place. Planned works far ahead are best taken from the road authority's own notices.