Inspiration
HealthWISE: FleetWISDOM was inspired by a simple problem with real operational impact: community health teams rely on shared vehicles every day, but many booking, compliance, and maintenance workflows still live in spreadsheets, inboxes, and tribal knowledge. We wanted to turn that friction into a single, accessible system that helps staff find vehicles faster, helps managers keep the fleet compliant, and gives the organisation a clearer picture of how its vehicles are being used.
What it does
FleetWISDOM is a Progressive Web App covering the full fleet lifecycle: vehicle records, bookings with conflict detection, pre- and post-trip checks, fuel and expense logging, incident reporting, compliance alerts, and operational reporting. Drivers can find and book available vehicles in seconds, managers get real-time visibility into fleet status and compliance, and the whole organisation gains a single source of truth for utilisation and cost. To frame the goal simply:
Fleet utilisation
booked vehicle hours available vehicle hours × 100
How we built it
We structured the project as a monorepo with a React + Vite frontend, an Express + TypeScript API, Prisma-backed data access, and a shared TypeScript package to keep domain models aligned across the stack. We leaned on seeded demo data (100 vehicles, 10 locations, 20 drivers, 30+ bookings) and a structured backlog so we could move quickly while still keeping the experience grounded in realistic fleet operations.
Challenges we ran into
Our biggest challenge was balancing breadth with polish. Fleet management touches many domains at once — bookings, safety, maintenance, finance, and governance — so scope expansion was a constant risk. The hardest decisions were choosing what to make end-to-end complete, what to stub for later, and how to keep the system coherent while simultaneously integrating authentication, seeded operational data, deployment planning, and documentation.
Accomplishments that we're proud of
We are proud of delivering a coherent, end-to-end fleet management experience within a hackathon timeframe. Booking conflict detection, compliance alerting, real-time fleet visibility, and structured reporting all work together on top of a consistent shared data model. We also established a clean monorepo architecture with a shared package, clear build order, and a one-command local setup that any team member can run from scratch.
What we learned
One of the biggest things we learned was how much product design and technical architecture affect each other in a hackathon. Features like booking confidence, compliance alerts, and real-time fleet visibility only feel useful when the shared data model is consistent and the user flows stay simple. We also learned how valuable a shared package and a clear build order are in a monorepo, especially when frontend and backend teams need to iterate quickly without drifting apart.
What's next
The foundation is in place to extend FleetWISDOM into a production-ready platform. Near-term priorities include deeper AI-assisted maintenance scheduling, mobile-native push notifications for compliance deadlines, multi-tenant support for organisations managing several fleets, and integration with telematics providers for live odometer and location data. We also want to expand the reporting suite so fleet managers can benchmark utilisation, cost per kilometre, and safety trends over time.
Log in or sign up for Devpost to join the conversation.