What to look for in school bus tracking software: a buyer's checklist
A plain checklist for schools comparing school bus tracking and dismissal software: hardware, attendance, parent alerts, your SIS, privacy, and questions to ask in a demo.
"School bus tracking software" covers a wide range of products. Some are GPS systems for district transportation departments with hundreds of routes. Some are parent apps that show a dot on a map. Some are dismissal tools that never leave the school driveway. They can all appear in the same search results, and the brochures tend to sound alike.
This checklist is for schools, especially independent and smaller K-12 schools, that run their own buses or contract them and want to know two things every afternoon: is every child on the right bus, and where is that bus now. It is written so you can use it to compare any products, including ours.
Start with the problem, not the map
Before you look at any product, write down what actually goes wrong today. Typical answers:
- The office cannot tell which buses are full and ready to leave.
- Parents call to ask whether their child got on the bus.
- Parents call to ask where the bus is.
- Bus changes do not reach the person at the curb in time.
- Nobody can say afterwards who checked a child on, or when.
A live map only addresses one of these. If most of your problems are about who is on which bus, the attendance side of the product matters more than the tracking side. Keep your list in front of you during every demo, and ask the vendor to show you each item working, not just describe it.
1. What has to be installed on the bus?
Tracking has to come from somewhere. The two common approaches are:
| Approach | What it means for you |
|---|---|
| A GPS unit fitted to each bus | Installation, power, and a device per vehicle. Works without the driver doing anything. Substitute buses need their own unit. |
| The driver's phone | Nothing to fit. The driver starts sharing location when the route begins. Needs a phone and a driver who turns it on. |
Neither is right for everyone. A large district fleet may prefer fitted hardware; a school with a few buses or regular substitutes may find phones easier.
Ask: what happens on the day a substitute bus turns up? If the answer involves moving a device between vehicles, find out who does it.
Bussin' uses the driver's iPhone or Android phone for live tracking. The driver can see when sharing is on and turn it off, and ending the route stops it too.
2. Does it know who is on the bus?
A bus on a map tells you where the vehicle is. It does not tell you whether the child is on it. For most schools, that is the question that matters at 3 o'clock.
Look for:
- Check-on at the bus, by the adult standing there, with a tap or a scan.
- A live count the office can see without a radio call.
- Changes in real time. If a child moves to another bus, does the person at the curb see it immediately?
- Absences respected. A student who went home sick should not be on the list.
- A record of who did what, with names and times, for the day something is questioned.
In Bussin', staff check students on from the staff app by tapping a name or scanning a QR code. Scanning a child onto the wrong bus shows a warning naming the bus they should be on.
3. What does the office see?
The office is where questions land. The software should let one person see the whole afternoon at a glance, ideally on a screen big enough to read from across the room.
Ask the vendor to show you:
- Every bus for this afternoon on one screen, with how many students are on.
- Which buses are ready to go.
- The buses in the order they actually line up.
- What happens on a wall display, in full screen, with editing controls hidden.
The Bussin' Status board does this in a browser, with tiles you drag into pickup order and settings for text size and contrast so it can be read from a distance.
4. What do parents get, and what do they not get?
Parent features reduce phone calls, but only if they answer the questions parents actually ask. The useful ones are usually:
- Whether their child has been checked onto the bus.
- Where the bus is now.
- An alert when the bus reaches their stop.
Ask how parents are invited (by the school, or can anyone sign up?), whether brothers and sisters show up together, and whether parents can choose which stops they hear about. Too many notifications and parents turn them all off.
The Bussin' parent app is invited by the school with a join code. It shows each child as checked in or not yet, the bus on a live map, and an "Arrived at" alert for the stops the parent switches on.
5. Does it work with your student information system?
This is the question that decides how much work the product creates for your office. If students, buses and absences have to be typed in or uploaded by hand, someone will be doing that every week, and the lists will drift out of date.
Ask specifically:
- Which SIS does it connect to today? Not "on the roadmap", today.
- What comes across? Students, grades, homerooms, bus assignments, absences?
- How often? Once a night, every few minutes, or when someone presses a button?
- Does anything go back the other way? Attendance, for example.
- What happens when a sync fails? Will anyone know?
Bussin' connects to Veracross today. Students, buses and trips are copied every 15 minutes through the school day, students marked absent in Veracross are left off the bus list, and the dashboard shows when the last sync ran and says so plainly if one is late or failed. If your school uses a different SIS, ask us directly rather than assuming.
6. Privacy and who can see what
You are choosing software that knows where children are. Treat the privacy questions as seriously as the feature questions.
- Who can see a bus's location? Staff only, or parents too? Only parents of children on that bus?
- What location history is kept, and for how long?
- Who can change settings and see credentials for your SIS connection?
- How are staff and parent accounts created and removed?
Get the answers in writing. In Bussin', only the latest position of each bus is kept, not a history of everywhere it has been, and your Veracross credentials can only be read or changed by your school's admins.
7. How much setup is it, really?
Ask for a realistic plan: what the school has to provide (rosters, bus lists, stops), who sets up the SIS connection, how staff are invited, and what hardware has to be bought. Then ask to speak to the person who will actually help you set it up.
Questions to ask in every demo
Bring this list:
- Show me a substitute bus arriving. What changes, and who changes it?
- Show me a child moving to a different bus at 2:50. Who sees it, and how fast?
- Show me a student who was marked absent this morning. Are they on the bus list?
- Show me the office screen during a real afternoon, not a slide.
- Show me what a parent sees, from invitation to the stop alert.
- Show me what happens when the SIS sync fails.
- What is kept about a bus's location, and for how long?
- What does pricing depend on, and what is extra?
A good vendor will show all of these live, with a demo school.
Where Bussin' fits
Bussin' is built for the school afternoon: staff check-on at the bus, a live board in the office, tracking from the driver's phone, parent alerts, and a Veracross connection that keeps the lists current. It is not a district routing system, and if you need to plan hundreds of routes from scratch, a dedicated routing product may suit you better.
If the checklist above sounds like your afternoon, you can see how it works end to end, read about it for schools, or book a demo and ask us every question on this list.