Reports
The reports module turns fleet data into downloadable summaries — cost, fuel efficiency, PM compliance, safety events by type, and carbon footprint. You define a report once, then either run it on demand or leave it to the system to deliver by e-mail on a schedule.
Who it's for
Anyone with analytics access can see the report list and the generated-file history: the fleet manager, dispatcher, safety manager, finance controller, executive and organization administrator. Defining new reports, running them on demand, and setting a delivery schedule is reserved for the finance controller, executive, fleet manager and organization administrator.
Defining a report
You start a report by picking one of the predefined types: fleet cost (fuel and energy spend per vehicle), fuel efficiency (litres, distance, consumption per 100 km), PM compliance (from the latest KPI snapshot), safety events by type, or ESG/carbon footprint. The only tuning parameter is the reporting window length in days (1–366, defaulting to 30), counted backward from the moment it's generated. A newly created report is on-demand only until you attach a schedule to it.
Schedule and delivery
A schedule is a cron expression plus a list of recipient e-mail addresses — activating a schedule needs both. The system checks every few minutes, for each report separately, whether the next run is due, counted from the previous generation (or from when the definition was created, if it has never run). When it's due, the report is generated automatically and e-mailed to every recipient — the message body is a readable summary with a preview of the table's first rows and a link to download the full file, which is also attached as a CSV. Turning the schedule off (or clearing the cron) returns the report to on-demand only, without losing the definition itself.
Running and downloading
You can also generate a report immediately, independent of its schedule — the file lands in that definition's generated-report history with a row count and size. The download link is temporary (it expires after a set time) and is minted on demand from the history or right after a manual run — the CSV file itself is kept indefinitely; only the download link expires.