Ask a precise question
Every report takes a date range and, where it applies, a vehicle or a driver — so “fuel for TLA-1025 in March” is one screen, not a spreadsheet.
Reports are definitions, not bespoke screens — which is why there are 167 of them, why each has its own filters and summary lines, and why every one exports to CSV, Excel or PDF. They read from daily rollups, never from raw pings, so a year of history stays fast.
Activity, utilisation, idle time, stops, downtime, health score
Theft events, refills, tank levels, pump-wise fuel, km per litre
Trip log, delays, stops, cost, revenue, profit and loss
Each import, export and return round: distance, fuel, cost and profit
Attendance, working hours, violations, licence and CNIC expiry, ranking
Entries, exits, dwell time, unauthorised entries, zone violations
Service due, overdue, repair history, part-wise cost
Expiring and missing papers, route permits by province
History, trend and resolution, by type, vehicle and driver
Nine families, 167 reports — each report counted once.
One engine runs all 167, so they all behave the same way.
Every report takes a date range and, where it applies, a vehicle or a driver — so “fuel for TLA-1025 in March” is one screen, not a spreadsheet.
A summary line above the rows: litres, kilometres, rupees, counts — the figure a manager asks for before the detail.
CSV and Excel for the accountant and the broker, or PDF for the file. The export is the same rows you see.
Reports read from daily and monthly rollups and from each trip’s compressed route — never from millions of raw pings.
Ten reports answer most of what an owner asks in the first month. The other 157 are there when the questions get sharper.
Tracker installation, console setup and onboarding — handled for you.