MISSION 02
Bus Management System
Routes, digital passes, ride attendance and fleet paperwork, in one portal instead of two queues.
CLIENT
ENGAGEMENT
STACK
THE PROBLEM
Two queues. One at a finance counter to pay for a pass, one to collect the card that proved you had. Paper was the only thing connecting a payment to a person. And none of it left a record, so nobody could say how many people actually rode a route last month.
WHAT WE BUILT
- Route and stop discovery, so students stop asking staff.
- Payment proof uploaded in the portal, with approval status visible to the student.
- A verification queue for the administration team, where approval is a recorded decision.
- A QR pass on the student's own phone, scanned online at boarding.
- Ride attendance, and the monthly and yearly audits that run off it.
- Fleet records, each vehicle carrying its documents and their expiry dates.
THE DECISION THAT MATTERED
The scan is the attendance record, so it has to be idempotent. One boarding is one row whatever the network does to the request, or the ridership numbers the audits depend on drift quietly upward.
Pass validity is derived from the approved period, never stored as a flag. A flag needs somebody to switch it off when a term ends, and one missed job means expired passes keep scanning green.