School bus pre-trip inspections on a phone: what a good app does

Every school bus gets a pre-trip inspection before its first run and a post-trip at the end of the day — lights, stop arm, crossing arm, brakes, tires, mirrors, emergency exits, first-aid kit, and the child check: walking the whole bus so no student is left on board. On paper, the forms pile up in a box, a failed item reaches the shop when someone remembers, and proving last March's inspection means digging.

Doing it on the driver's phone fixes that — if the software does the right things. Here's what to look for.

What a good inspection app does

• Your own checklist. Your state, your districts and your buses decide what's checked — the app should let you build it (and keep separate checklists for buses and vans), not force a generic one.
• Pass / fail per item, with photos. A photo of a cracked mirror or a worn tire settles arguments and helps the shop.
• Failed items go to the shop by themselves. A failed item should become a defect someone has to deal with — not a tick on a form nobody reads.
• Signed and dated. The driver signs on the phone; the record keeps who, which bus, when and what was found.
• Records you can print. An inspector or district asks for a vehicle's inspections: you should be able to print them in a minute.
• Reminders for buses not inspected. A bus that hasn't had an inspection in your interval should show up before an inspector finds it.
• The child check at the end. The post-trip should end with the child check as its own item, so it can't be skipped.

Rolling it out to drivers

1. 1Build the checklist once, with your mechanic — they know which items matter on your buses.
2. 2Run paper and phone side by side for a week, so drivers get used to it without anything getting lost.
3. 3Show drivers how a failed item becomes a defect and what happens next — they'll report more when they see things get fixed.
4. 4Look at the first month's inspections together: which items fail most, which buses, which drivers never fail anything (and why).

Doing it in FleetCommander

In FleetCommander, drivers do pre-trip and post-trip inspections on their phone from My Day — it opens in the phone's browser, with nothing to download, and can go on the home screen like an app — on your own checklists, with photos on any item and a signature. A failed item becomes a defect for the shop, which can turn into a work order; every inspection is kept with its vehicle and prints as a report. Vehicles not inspected within your interval are listed on the Compliance Center and the office is reminded. With driver attendance on, the pre-trip also clocks the driver in.

Ava (Beta), the assistant built into the app, saves a few clicks here: say Start an inspection and she opens the right vehicle's checklist; ask Which vehicles need an inspection?, Failed inspections last week or When was bus 102 last inspected?; say Open a work order for bus 102 and she gets it ready from its open defect, on a card you confirm. When the repair is done, Mark the defect on bus 102 as fixed: replaced the mirror.