Built in Minnesota and serving 300+ buses across the state — with Minnesota transportation law encoded in the routing engine, not left as a compliance checklist for the planner.
See it with your district's real routesMost school transportation software treats state law as documentation — something the routing planner is supposed to know and remember to apply. Minnesota deserves better than that. The statutes that govern pupil transportation here are specific, numeric, and safety-critical: mandatory-transport distances, amber-light warning distances that dictate stop spacing, a divided-highway rule that makes some crossings flatly unsafe, and a funding formula whose reporting categories every district and contractor must reconcile against, every year.
Guardian Route encodes those rules as constraints in the routing engine itself. Statutory values are floors the software will not let a route violate — a stop cannot be placed where §169.443’s warning distances can’t be met, and a student cannot be assigned a stop across a §169.444 separated roadway, no matter how much mileage it would save. District policy — walk zones, hazard criteria, fee tiers, bell schedules — is configuration on top, because §123B.88 gives every Minnesota board discretion over its own system and no two boards use it the same way.
The result is one platform — routing, live GPS, a parent app in English, Spanish, Hmong, and Somali, driver safety and attendance, and cost analytics — that fits how Minnesota actually runs school transportation: mostly contracted, heavily winter-tested, and accountable to the state on every dollar.
Four statutes shape every Minnesota route plan. Guardian Route enforces each one natively — and our guides explain them in plain English.
Districts must transport students living more than 2.0 miles from school — all grades. The same section gives boards broad discretion over routes, stops, and scheduling, which is why every district’s policy is different and why thresholds in Guardian Route are per-district configuration.
Walk zone rules, explainedThe transportation funding formula creates the practical 1.0-mile elementary / 2.0-mile secondary tiers most Minnesota boards anchor policy to — and its subdivision 5 sets the cost-allocation rules every district and contractor answers to on the MDE annual report.
Reimbursement & reporting guideA bus must run amber pre-warning signals at least 100 feet before stopping in zones of 35 mph or less, and 300 feet above 35 mph. That sets a minimum stop spacing on fast roads — Guardian Route enforces it as a non-overridable floor when placing stops.
Stop spacing requirementsOn a separated roadway, opposing traffic is not required to stop for a school bus — so a stop that requires crossing one offers a student no legal protection. Guardian Route’s crossing evaluator prohibits divided-highway crossings outright, before any other check.
Divided-highway rule, explainedNo Minnesota statute defines a snow route — winter service is board policy, which means its quality depends entirely on preparation. Guardian Route models snow routes the way the best-run districts already think about them: every vulnerable stop carries a designated replacement on a plowed, maintained road, hazardous segments are excluded from bad-weather routing, and the whole network swaps in one step — with affected families notified automatically. The 5 a.m. decision takes minutes, and parents hear about it before the bus doesn’t come.
Minnesota school transportation is a contracted market: MSBOA-member companies provide over 60 percent of the school buses used to transport Minnesota children, moving 400,000+ students every school day. Many metro districts split routes across several operators at once — which is exactly why a vendor-neutral platform matters. Guardian Route serves both sides: districts get one live map and one parent app across every operator, and contractors run all their district contracts from one multi-tenant account, with the per-route, per-category cost records Minnesota’s §123B.92 reporting rules demand.
How Guardian Route fits the metro’s largest systems — each page covers the district’s real transport profile, walk zones, current vendor stack, and the statutes that bite hardest in its geography.
SSD 1 · Hennepin County
ISD 625 · Ramsey County
ISD 11 · Anoka + Hennepin County
ISD 196 · Dakota County
ISD 279 · Hennepin County
ISD 535 · Olmsted + Wabasha County
ISD 709 · St. Louis County
ISD 834 · Washington County
ISD 281 · Hennepin County
ISD 271 · Hennepin County
ISD 284 · Hennepin County
ISD 621 · Ramsey County
Minnesota statute shapes routing directly: §123B.88 mandates transportation beyond 2.0 miles, §123B.92’s funding tiers drive the 1-mile elementary / 2-mile secondary walk-zone patterns, §169.443 sets amber-light pre-warning distances that constrain stop spacing, and §169.444 means opposing traffic never has to stop on divided highways — so students must never cross them. Guardian Route enforces these as engine constraints, with the statutory values as non-overridable floors.
Yes. The platform is multi-tenant: contractors — who provide most of Minnesota’s school bus service — run every district contract from one account with isolated per-district data, and districts get vendor-neutral tracking that survives contractor changes.
Snow routes are prepared as a parallel stop configuration before winter: each regular stop can carry a designated snow-route replacement on a maintained road. Activation is one step — the affected routes re-optimize and affected families are notified automatically.
We'll build a demo using real routes from your district — so you can see exactly how Guardian Route fits your operation before signing anything.
Already running Guardian Route? Log in to your dashboard →
We'll show you Guardian Route with your own district data.