TRACKDOWN
All postsSchool Transport · 5 min read

School Bus Safety Technology: What Every Institution Should Ask For

A checklist for school administrators evaluating a bus-tracking vendor — beyond just 'do you have GPS.'

Every vendor will tell you their buses have GPS. That's the easy part — and the least useful question to ask. Here's what actually separates adequate school transport tracking from the kind that holds up when a parent, a principal, or a regulator asks a hard question.

Is the device actually AIS-140 certified?

School and staff transport typically falls under states' AIS-140 mandate for public/institutional service vehicles. Ask for the certification documentation directly, not just a claim of compliance — and ask who prepares the RTO paperwork, because a certified device without the matching documentation still leaves you exposed at permit renewal.

Can parents and administrators both see what they need — and nothing more?

A transport in-charge needs full route history, alerts, and driver behaviour data. A parent needs to know their child's bus is on time and safe — not access to the whole fleet's operational data. Ask whether the platform actually separates these views, or whether 'parent visibility' is just a marketing line with no real access control behind it.

What triggers an alert, and who receives it?

Route geofencing should flag a bus leaving its approved route, not just arriving late. Speed alerts should go to the transport in-charge in real time, not show up in a report the next day. Ask for the specific list of alert types and exactly who they're sent to — vague answers here usually mean the alerting is more limited than the sales pitch suggests.

Is there a cabin-facing view, and what's the retention policy?

A cabin-facing dash-cam adds a layer of accountability that a location dot on a map can't — for driver conduct, and for resolving disputes if something is alleged to have happened on board. If you go this route, get specifics on footage retention and who can access it; this is exactly the kind of data handling that should be written down, not assumed.

What happens when a device goes offline?

Devices lose signal, get tampered with, or fail. The real question is what the system does about it — does it flag the gap immediately, or does no one notice until someone asks 'where's the bus' and gets no answer? Ask specifically how offline devices are detected and escalated, because this is the scenario where tracking either earns its purpose or quietly fails at the one moment it mattered.

Putting it together

None of this is exotic — it's just specific. A vendor who can answer all five questions concretely, with documentation rather than reassurance, is one worth trusting with student safety. If you're evaluating options for your institution, ask us these same five questions — we'd rather answer them upfront than have you find the gaps later.

Ready to see Trackdown on your own fleet?

Get a free walkthrough of the dashboard, a device recommendation, and a quote for your fleet size — no obligation.