Commit & Run

Inspiration

HealthWISE teams travel constantly across regional communities, but fleet operations were spread across calendars, spreadsheets, paper logbooks, and manual admin workflows. Commit & Run was inspired by the need to make fleet access safer, faster, and more transparent, while staying practical for real-world field conditions.

What it does

Commit & Run is a fleet management platform that centralizes vehicle registry, booking workflows, trip logging, compliance tracking, and admin oversight in one place.

Key capabilities:

• Vehicle registry and status tracking
• Booking workflows with availability checks
• Trip logging for usage and odometer records
• Compliance tracking (registration, insurance, service, safety)
• Admin visibility through unified dashboard views

It also includes automated compliance monitoring that flags expiring records, sends reminders, and can block vehicles from new bookings when critical compliance has expired.

How we built it

• Backend: ASP.NET Core Web API with Entity Framework Core and SQLite
• Frontend: React + TypeScript (Vite) with feature-based modules
• Data model: rich domain entities for vehicles, bookings, trip logs, compliance, audits, incidents, users, and sites
• API approach: CRUD-first controllers plus domain endpoints like available-vehicle search
• Automation: hosted background service for scheduled compliance checks
• Quality: unit tests focused on compliance rules and notification behavior
• Delivery setup: single solution with backend + frontend, seed data, and migration-based schema evolution

Challenges we ran into

• Translating messy real-world fleet processes into clear domain rules
• Preventing booking conflicts while respecting vehicle status and compliance constraints
• Balancing hackathon speed with scalable architecture decisions
• Keeping frontend/backend contracts aligned as the domain model evolved
• Handling edge cases in reminder windows and automated vehicle blocking

Accomplishments that we're proud of

• Delivered an end-to-end working prototype across booking, trip, compliance, and admin workflows
• Implemented safety-first automation that proactively reduces compliance risk
• Built a reusable API/frontend structure that can scale beyond hackathon scope
• Seeded realistic domain data for meaningful demos
• Added tests around one of the highest-risk modules (compliance enforcement)

What we learned

• Domain clarity matters more than feature count for operational software
• Background automation is a force multiplier for admin-heavy workflows
• Strong status/enumeration modeling reduces ambiguity across UI, API, and data layers
• Realistic seed data surfaces UX and logic gaps earlier
• Even a hackathon MVP benefits from production-minded practices (migrations, tests, separation of concerns)

What's next for Commit & Run

• Add authentication and role-based access (Azure AD / SSO)
• Expand notifications to email/Teams with escalation workflows
• Introduce offline-friendly mobile trip/check-in flows for low-connectivity regions
• Integrate fuel card and finance systems for automated reconciliation
• Improve scheduling intelligence (load balancing, service-aware recommendations)
• Add richer analytics for utilization, cost centres, and fleet optimization
• Harden deployment with observability, CI/CD, and cloud-hosted environments

Built With

• .net
• azure
• c#
• react
• sqlite