Transport GPS Audit Console

Delhi Public School Group · Daily compliance & monthly mileage · for the Transport Auditor

GPS Compliance Report

1 · Upload the daily GPS reports

Drag the daily GPS PDFs for all five schools into the box below — one or many at a time. Three vendor formats are auto-detected: Travel Daily Summary (B-DigitalNow — Sason, Gondia, Chhindwara), Travel Summary Report (Mahasamund) and Trip Summary (Raipur). The console reads each vehicle row, matches the registration to the Fleet Master, and builds one combined compliance sheet.

Drop GPS report PDFs here or click to choose files
Accepted: Travel Daily Summary / Travel Summary Report / Trip Summary PDF exports. Parsed values stay editable — correct any cell before sending the report.

Fuel fill entries

Record every diesel/petrol fill with the odometer reading at the pump. The console computes month-wise kilometres, km/L and ₹/km per vehicle. Mileage needs at least two fills (tank-to-tank) or an opening reading.

Fleet Master — registration ↔ bus ↔ route

This is the ground truth the audit compares against. DPS Sason is pre-loaded from the finalized route plan. Add the other schools' buses the same way: the registration number must match the GPS report (punctuation is ignored), and Planned km / First stop & required time come from each school's finalized route sheet. Deadhead allowance = normal parking-to-first-stop + post-drop kilometres tolerated before an EXCESS flag.

Audit thresholds

Daily routine (2 minutes)

1. Download the daily GPS PDF from each school's GPS portal — all three vendor formats are auto-detected.
2. Drop all four PDFs on the Daily GPS Audit tab.
3. Review the flags, correct any mis-read cell directly in the table.
4. Print / Save as PDF and mail it, or use Copy e-mail summary for a text digest.

What the flags mean

LATE START first ignition was after the time the bus was required at its first stop.
KM SHORT GPS distance is less than the planned route length — physically suspicious, since parking-to-route deadhead should always add kilometres. Possible skipped stops.
KM EXCESS GPS distance exceeds plan by more than the bus's deadhead allowance — check for detours or private use.
END ≠ SCHOOL the vehicle's last ignition-off was not at the school — verify fuel vouchers or explain.
OVERSPEED maximum speed crossed the limit set in Fleet Master → Audit thresholds.
ALERTS device alert count at or above the threshold.
NOT IN FLEET the registration is not in the Fleet Master — either add the bus or investigate the vehicle.
NO MOVEMENT the vehicle never ignited / ran 0 km on a working day — confirm whether it was off-road, spare, or a dead GPS device.
READ — no plan targets set vehicle read and matched, but its Fleet Master row has no planned km / required time yet, so only speed & alert checks ran.

Monthly routine

Enter every fuel fill (date, litres, amount, odometer) as bills arrive. On month-end, open Monthly Fuel & Mileage, pick the month, and print the mileage report: km run, litres, km/L and ₹/km per vehicle, school-wise.

Where the data lives

Everything is saved inside this browser (no server). Use Export settings (JSON) on the Fleet Master tab for a backup, or to move the console to another computer. Clearing browser data erases saved entries — keep a monthly JSON export.