Somebody is emailing your fleet a 42-page PDF.
It goes to 14 people. 3 open it. One of them does something. Every fleet platform ships this, and every fleet quietly stops reading it inside a quarter.
The same month, addressed
Pick a recipient. Same underlying numbers, cut so that each person gets only what they can act on — and told, in one line, that nothing else broke.
Yesterday: 2 exceptions across 66 vehicles
saqr <[email protected]> · to Fahd
- VAN-042 missed the 09:00–11:00 window at Ash Shifa by 47 min
- EXC-221 left the site geofence at 22:07, outside working hours
- 64 vehicles ran to plan. No action needed on those.
- Fuel, utilisation and driver scores are unchanged week on week.
- Arrives by
- Needs flagging
- 2 of 4 lines
- Time to read
- 25s
What they do
Two conversations. The other sixty-four are explicitly not his problem today.
The comprehensive version of this is a forty-page deck. The useful version says what broke and confirms, in one line, that nothing else did.
The version most fleets get instead
One PDF, every metric, distributed to a list nobody maintains. It is not that the numbers are wrong — it is that finding the two lines that concern you costs more than ignoring it.
- 42
- pages
- 14
- recipients
- 3
- opened
- 1
- actioned
Every message above, added together, is 2.6 minutes of reading — and each line of it belongs to somebody.
6 lines across the whole distribution need somebody to do something. The other 14 exist to say that everything else is fine, which is the half most reporting leaves out — and without it, silence and failure look identical.
Four rules, and one of them is uncomfortable
The last one costs us a weekly touchpoint and an engagement metric. It is also the reason the other three keep working.
- Exceptions, then reassurance
- Lead with what broke, then say in one line that nothing else did. Without the second half, silence and failure look identical.
- One recipient, one action
- If a message implies work for two different people, it is two messages. Shared responsibility is how a report becomes nobody's.
- The channel the person actually uses
- A foreman gets WhatsApp, a director gets email, a warehouse gets a file. Insisting everyone log into a dashboard is how adoption dies.
- Nothing at all is a valid report
- If nothing happened worth telling someone, we do not invent something. A weekly message that is sometimes empty stays credible.
The reports you do not get to design
Some outputs have their format decided for you. Those are not a reporting feature — they are a compliance obligation with a deadline, and they should never involve someone rebuilding a spreadsheet.
Wasl and TGA in fullWasl submissions
Vehicle and unit registration, kept current as the fleet changes rather than reconciled once a year.
TGA operating reports
Hours, distance, speed and incident summaries in the format the Transport General Authority asks for.
Customer temperature records
The window either side of a delivery, signed, for receiving departments and SFDA submissions.
Insurer bundles
Incident file with footage, telemetry and the access log, as one download.
The best report is the one nobody reads
Because it went straight into the system that was going to ask for it anyway. Everything on the dashboards is available as a nightly drop into your own storage — the full data, not a summarised subset, and in your bucket rather than ours.
Developer documentationCSV
For the finance team who will open it in Excel and would rather you did not pretend otherwise.
Parquet
Columnar, compressed, partitioned by date. What your data engineer would have asked for.
Webhooks
Signed, retried with backoff, replayable for 72 hours.
REST API
Cursor-paginated and versioned, for anything that needs to ask rather than be told.
Every message across 4 people — daily, weekly and monthly together.
The same numbers, cut by who has to act on them rather than by which chart produced them.
The dashboard exists and is good. Nothing routine depends on somebody remembering to open it.
The rest of the platform
Live tracking
Position, speed and ignition every ten seconds.
Routing and dispatch
Plan the day, send it to the driver's phone.
Asset and trailer tracking
Trailers, generators, plant and containers.
AI dashcam
Road and cabin, clipped to the event.
Driver behaviour
Scored per driver and per trip.
Incident centre
Footage, telemetry and witnesses in one file.