Serve several districts from one platform, with per-district cost records that survive audits — and rate consistency you can actually demonstrate.
See it with your own routesRunning routes for multiple districts means multiple bills, multiple rate structures, and multiple sets of questions when a business office — or a state auditor — asks how a number was built. The contractors who handle this well have one thing in common: per-district, per-route cost records that exist before anyone asks for them. Guardian Route produces those records as a byproduct of running the operation.
Guardian Route is multi-tenant by design: your whole fleet and staff in one view, with each district’s routes, students, and data isolated in its own tenant. Billing follows the same boundary — every mile, hour, and route is attributable to the contract it served.
The platform tracks cost per route and cost per rider from the operational data it already collects — GPS miles, trips run, fuel, labor. That gives each district a clean number for its own service, and gives you the margin picture per contract instead of one blended average that hides which contracts are carrying the others.
State reporting rules increasingly demand allocation discipline. Minnesota is explicit: under Minn. Stat. §123B.92, subd. 5, a district may allocate contractor expense to reporting categories based on contract rates only if those rates are reasonably consistent per hour, per mile, per route, or per student — and must be able to demonstrate that variances are appropriate if audited. Contractors whose rates and records are built per route and per category make that easy; contractors whose invoices are one lump sum make it hard, and hard is what loses renewals.
Special-education-only van contracts and similar single-category service must often be charged directly to that category rather than blended. Because Guardian Route keeps special-education and McKinney-Vento service distinguishable from regular routes by construction, the direct-charge number exists without a spreadsheet project.
When a contract comes up, the district’s question is always some version of “what are we getting for this?” Per-district service records — routes run, on-time performance, students served, cost per rider — answer it with data. That is a stronger position than any brochure.
Districts see their own service data in their own tenant. Your contractor-level view spans all contracts. What you share beyond each district’s own operational data is up to you.
State reports are category-accounting exercises — Minnesota’s §123B.92 annual report is the clearest example. Per-route, per-category cost records that exist all year make the report an export instead of a reconstruction, and keep contract-rate allocation audit-defensible.
Yes. Each contract’s service is tracked in its own tenant with its own routes and costs, so per-hour, per-mile, per-route, or per-student billing structures can each be supported by the underlying records.
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.