Reading your fleet reports: a tour of 29 ready reports

A report is a decision tool, not an archive

A connected fleet generates a torrent of data every minute: positions, speeds, fuel readings, zone events, driving patterns. The value comes not from storing that torrent but from converting it into answers — and that is where systems differ: one merely "produces reports", the other builds every report around a decision. Whom do I reward? Whose fuel do I investigate? Which vehicle goes into the workshop this week?

A practical rule we recommend: before opening any report, write down the question you want answered. If you cannot find a question, you will find nothing in the report but numbers. If you can, the report becomes the shortest documented path to the answer — and its regular review becomes a management habit rather than a chore.

For the same reason, how many reports you review matters far less than how regularly you review them: three reports read every week at a fixed time, each producing actions, outweigh twenty opened at random when a problem surfaces. Only then do reports shift from a post-damage investigation tool to an early-warning system. And the platform generating the data should be the one answering the questions — not export files massaged by hand every week in side spreadsheets that go stale the moment they are created.

This guide takes a tour of the platform's ready reports: how they are organized, how to read the most important ones like an executive, and how to have them delivered automatically instead of chasing them.

The map of 29 reports

The ready reports are organized on two complementary levels:

17 vehicle-level reports answer questions about "this specific vehicle": its trips, stops and distances; speeds and violations; actual versus standard fuel consumption with fill and drain events; sensor readings such as temperature and weight; and its event and alert history. These are your detailed investigation references: a customer complaining about a delay, a fuel invoice that does not match the odometer, an incident needing a precise timeline reconstruction.

12 organization-level reports assemble the whole-fleet picture: consumption comparisons across vehicles, driver rankings by penalty points, geofence compliance, and fleet-wide maintenance and document readiness. These are the management reports: they surface the outliers — the vehicle with unexplained top consumption, the driver leading the violations list — and point your attention where it should go.

The two levels are designed to work together, top-down: start from an organization report to spot the outlier — a vehicle whose consumption jumps above its peers, say — then drill into that vehicle's own reports: its trips, fuel events and sensor readings, until you reach the cause. Starting from the details drowns you; staying at the big picture hides the culprit.

Every one of the 29 is available in Arabic and English, in the Hijri or Gregorian calendar, and as PDF or Excel — details on the reports page.

An executive reading of the key reports

The fuel report: start with two columns — actual and standard consumption — and focus on the gap, not the absolute figures. A consistent gap across the fleet usually points to calibration or an outdated standard; a gap on one vehicle calls for investigation. Then review drain events: each is documented by volume, time and location, so the question is not "is fuel missing?" but "what happened at this location at this time?". See the fuel page for the detection logic.

The trips and stops report: read it for patterns, not single trips: a vehicle covering more distance daily than its peers on the same assignments points to a route worth reviewing, and repeated long stops at one location deserve an operational question. When you need the full detail of one specific trip, replaying the route with speed coloring shows what the table cannot.

The driver behavior report: read penalty points as a trend, not a snapshot: a driver whose points climb three weeks in a row needs a conversation before the accident, not after it. Use the ranking for positive incentives too — a list used only for punishment is one drivers learn to resent.

The maintenance report: its strength is being driven by measured usage — kilometers and engine hours read from the device, not typed in — so a vehicle that has covered its scheduled distance shows as due even if the month has not passed. Review it together with document reminders (registration, insurance, periodic inspection) in one weekly session, and convert everything due into work orders immediately — details on the maintenance page.

The WASL compliance report: for transport operations regulated by the Transport General Authority, it shows your data acceptance rate at WASL and any outage windows. Read it preventively: a falling acceptance rate is an early signal of a device or coverage problem to fix before it becomes a compliance finding — more on the compliance page.

From report to action

This table condenses the reading method: each area, its question, and the action that should come out of it:

Note that the action column contains no "for information" entries — deliberately: a report that changes nothing in your following week is either being read wrong or is not one you need. Apply the test to your current routine: take the last three reports you opened and ask what action came out of each; if the answer is "nothing" three times, the problem is the reading method or the report selection — not a shortage of data.

Hijri, Gregorian, and Arabic-first

For anyone dealing with government entities or running an organization whose official reporting follows the Hijri calendar, calendar support is not a luxury. The difference between a platform that "supports Arabic" and one built Arabic-first shows in the details: Hijri is a native option on every report rather than an approximate conversion, and PDFs are produced by a genuine RTL engine so tables never break and numerals never tangle with Arabic text — a problem familiar to anyone who has exported an Arabic report from a foreign system.

When reviewing any platform, ask for a real Arabic PDF sample with a multi-column table and a Hijri date, and inspect the exported document rather than the demo screen: column alignment, numeral direction inside Arabic text, and compound location names surviving intact — three details that expose in one minute what slide decks conceal.

For dealers and service providers, reports carry your customer's logo (white-label), so your clients receive documents in their identity, not the technology vendor's. Language, calendar and format (PDF or Excel) are chosen per export or fixed in a schedule — so the CFO receives a Gregorian Excel for analysis and the operations manager a Hijri PDF for presentation, from the same report.

Scheduling and custom reports

A report you have to remember is a report you will forget. So make it a rule: every recurring report is scheduled, never requested. The platform schedules any report for automatic delivery by email or WhatsApp — the fuel report every Saturday morning, the driver ranking at the start of each month, straight to the people concerned with no manual step. And separate the two formats by audience in your schedules: Excel for those who will analyze, filter and aggregate — the accountant and the operations analyst — and PDF for those who will read, decide and sign; sending the wrong format to the wrong audience is the fastest route to reports nobody opens. Start each schedule with a narrow recipient list and widen it on request; a report landing in twenty inboxes is usually read by none of them.

And when none of the 29 matches a specific need — a report combining particular fields for a customer or a regulator — Pixa's custom report builder lets you assemble your own from the fields that matter, then schedule it like any ready report.

A practical starting plan for your first week: schedule just three reports — fuel weekly, behavior weekly, maintenance weekly — and commit to reviewing them at a fixed time with at least one action from each. After a month, your own data will tell you which other reports deserve a place in the routine. And if you would like a live tour of all 29 reports on your fleet's data, contact the Pixa team via the contact page.