Reports
Weekly/monthly — Fleet Ledger snapshots · Utilisation/Revenue/Costs derived from Ledger, not silos.
Rider Retention — Ledger-derived
30d
82%
60d
71%
90d
60%
12 riders at high churn risk
Rahul Kumar · High
downtime · unresolved_service
Amit Verma · High
low_utilisation · payment_issue
r-3 · Medium
long_commute
r-4 · Medium
missing_equipment
r-5 · High
downtime · low_utilisation
r-6 · High
payment_issue
r-7 · High
unresolved_service · long_commute
r-8 · Medium
downtime
r-9 · High
low_utilisation · missing_equipment
r-10 · High
payment_issue · downtime
r-11 · Medium
long_commute · unresolved_service
r-12 · High
downtime · payment_issue
Churn reasons: repeated downtime · low utilisation · unresolved service · long commute · payment issue · missing equipment — derived from Vehicle downtime + Trip/Booking utilisation + Service open + Evidence missing
Derivations (no new silos)
Utilisation = Fleet + Trips/Bookings · Revenue = Bookings + Payments · Costs = Service + Payments + ownership (sbi-120/fofo-100 fixtures) · All via Organization → Fleet → Hub → Zone → Vehicle/Rider → Request → Work → Event → Ledger