How RouteBot Optimizes School & Employee Transport

Hi. I'm Emrah G., the founder of RouteBot. I've been building transportation software for over 10 years, and I've spent most of that time watching smart people do dumb work — not because they're bad at their jobs, but because the tools force them into it. Spreadsheets, phone calls, sticky notes on a wall map. It works until it doesn't, and it stops working around the time your operation hits 30 buses and 400 students.

RouteBot exists because I got tired of seeing the same problems at every school and every corporate shuttle operation I worked with. This post is a walkthrough of what the product actually does, with screenshots and a link to the live demo so you can try it yourself.

The problem in one sentence

Someone has to figure out which passengers ride which vehicle, in what order the stops are visited, and whether the whole plan holds together when a driver calls in sick or 20 families move in October.

In school transportation, that means students, buses, bell times, capacity limits, wheelchair requirements, and parent notifications. In corporate shuttles, it means employees, shifts, office locations, and schedule changes. The details differ. The underlying puzzle is the same: a vehicle routing problem with too many variables for a person to solve well by hand.

For the technical side of how that routing problem works — VRP, time windows, heuristics — we wrote a separate piece: Technical Analysis of School Bus Routing Software. For a decision-oriented guide on when routing software makes sense, see School Bus Routing Software: Complete Guide.

This post is about the product, not the theory.

What RouteBot does: the short version

You give it a roster (students or employees), their addresses, your vehicles, and your rules (capacity, timing, equipment). It distributes passengers across vehicles, sequences the stops, calculates pickup times, and pushes everything to drivers and parents automatically.

The distribution itself takes minutes. The part that takes days — if it takes days — is verifying that addresses are correct, not the optimization.

Student management and address sync

When you add a student (or employee) to RouteBot, you set their pickup and dropoff addresses. The system geocodes the address and places a pin on the map. If you drag the pin, the address updates. If you change the address text, the pin moves. Two-way sync, so you're never arguing about which one is "right."

From the student list, you can also connect parents and configure notification preferences — which alerts they get, via app or SMS. The available notifications:

Bus is approaching the pickup point
Bus arrived at the school
Bus left the school
Bus is approaching the drop-off point
Student did not get on the bus

These aren't generic texts. They fire from GPS data in real time, tied to the specific route and stop assignment. When a route changes, the notifications update automatically. More on the notification architecture in our trigger ladder playbook.

When you change the address, the map pin moves. When you move the pin, the address updates. It sounds simple, but bad geocoding is the single biggest source of bad routes.

Automatic passenger distribution

This is the core of what RouteBot does. You select a school, set the maximum passengers per vehicle, choose pickup or dropoff, and hit go. The system clusters passengers by proximity and road distance, assigns them to vehicles, and calculates the stop sequence and timing for each route.

For 500 students, this runs in under a minute. The output is a set of draft routes you can review, adjust, and approve before anything goes live. Drivers don't see it until you push it. Parents don't get notified until you're ready. We wrote more about the distribution process in school bus routing software, including a video demo of the 500-student run.

The optimizer is balancing two things at once: use as few vehicles as the constraints allow, and keep total distance per route as short as possible. These goals sometimes conflict — you can save a bus by cramming more stops onto fewer routes, but that increases ride time. The system finds the tradeoff; your team decides if it's acceptable.

Route optimization and shortest paths

Once students are assigned to a vehicle, the system orders the stops. This is a variant of the traveling salesman problem: given 15 stops, find the sequence that minimizes total drive time. The system uses actual road distances (from Google Maps directions data), not straight-line distance, so it accounts for one-way streets, turn penalties, and real traffic patterns.

Each stop gets a calculated pickup time based on the sequence, estimated dwell (loading time), and road travel between stops. Planners can adjust any assignment, lock specific students to specific buses, or resequence manually and re-optimize around the changes.

Real-time tracking and notifications

Once routes are live, drivers use the RouteBot mobile app to run their routes. The app sends GPS updates continuously. Parents see the bus location in their own app, with a freshness indicator showing how recent the last update is.

Notifications fire automatically as the bus hits trigger points: approaching the stop (configurable distance), arriving at school, departing school, approaching dropoff. If a student doesn't board, the parent gets a separate alert. All of this runs from the same GPS stream the driver is already sending — no extra steps.

For a detailed playbook on rolling out tracking and notifications, see school bus tracking app rollout.

It works the same for corporate shuttles

The routing engine doesn't care whether the passenger is a 7-year-old going to school or an engineer going to an office park. The constraints change (shifts instead of bell times, badge access instead of parent notifications), but the optimization is the same.

RouteBot handles both in one system. If you run school routes in the morning and employee shuttles in the afternoon — or if you're a transportation company serving both — you don't need two products. Same engine, same interface, different configurations. For how mixed fleets interact with routing, see mixed fleet route optimization.

Try it yourself

The live demo lets you add students to a school, set constraints, run the optimizer, and see routes generated in real time. No signup, no sales call required.

Try the live demo →

If you want a walkthrough with your own data, you can request a call and we'll run it together.

I also wrote about some of the technical decisions behind RouteBot on dev.to: Building Smarter School & Staff Transportation: Lessons from RouteBot.

Related reading

Written by Emrah G., founder of RouteBot. Follow on Twitter/X.

How RouteBot Optimizes School & Employee Transport (with Live Demo)