Fuel activity
Spend, litres and transaction counts by month, vehicle, station and supplier.
Tara NawaFuel Risk Report Guide
Start a conversation
PUBLISHED REPORT GUIDE / SYNTHETIC DEMO
A practical route through the Fuel Risk Report: where each page helps, what to inspect, and how to move from an alert to a documented review.
The published demo is ready. Open the report and put these checks to work while each view is fresh in mind.
All practice cases and report examples are synthetic. A risk signal is a lead for investigation, not proof of wrongdoing.
BEFORE YOU START
Choose a page from the left navigator in the published Power BI report. Transaction Drillthrough is there even though the bottom counter shows 10 standard pages.
Slicers apply immediately. Reporting Month is shared across pages. Fuel Station and Fuel Supplier are shared between Executive and Monthly. Other selections can be page specific.
Reset slicers clears the current page and shared selections. It does not clear every local slicer on every other page.
REPORT CAPABILITIES
Start with the fuel total, then follow the vehicle, card, station and ticket behind it.
Spend, litres and transaction counts by month, vehicle, station and supplier.
Same-day refuelling and after-hours patterns alongside the exception register.
Ranked scores, risk bands and the score components that need review.
Odometer quality, reconciliation, supplier analysis and rebates.
Forklift fuel, operating hours, litres per hour and productive utilisation in separate views.
REPORT PAGE GUIDE
Choose a topic, then select a report page to see its next checks.
11 report pages
READ THE SIGNAL
The vehicle score band summarises overall risk. Each transaction exception has its own severity. Read them separately before deciding what to investigate.
The Top 10 chart is a relative ranking. Red bars do not mean all ten vehicles have a High band.
Duplicate tickets at one station and card mismatches are High. Repeat fills and after-hours activity are Medium. Small fills and weekend activity are Low. Other flags include unusual fill size, invalid odometer readings, product mismatch and fuel-price anomalies. Confirm the rule and record context before acting.
The separate score considers consumption, spend, litres, exception count, same-day fills, after-hours and weekend activity, and invalid odometer readings. A High exception does not automatically place a vehicle in the High band.
EXCEPTION INVESTIGATION
Use the report to locate the signal, then verify the explanation with records outside the dashboard.
Choose month, vehicle, station or supplier as applicable. Keep the selected values in your case note.
Record exception type and severity. Separately record the vehicle risk band and exception status.
Open the matching transaction ID. Check ticket and station together, card, time, litres and spend.
Compare normal fills for the same vehicle, route, station or shift. Check meter validity.
Obtain receipts, invoice or settlement, card history, and dispatch or maintenance records.
Record explanation, evidence, owner and resolution. Treat the signal as unproven until reviewed.
SYNTHETIC PRACTICE CASES
All cases occur in Reporting Month 2026-07. These are practice leads, not allegations.
| Signal | Vehicle | Transaction ID | First evidence check |
|---|---|---|---|
| Duplicate ticket | DEM 1031 | 910001, 910002 | Compare receipts at NFN001 |
| Repeated fills | DEM 1032 | 910004, 910005 | Check 08:00 and 09:30 fills |
| After-hours fill | DEM 1033 | 910006 | Confirm the 22:35 shift |
| Card mismatch | DEM 1034 | 910007 | Confirm card assignment |
| Invalid odometer | DEM 1035 | 910008 | Inspect the meter record |
| Station concentration | DEM 1036 | 910009 to 910011 | Compare route and invoices |
READING RESULTS RESPONSIBLY
High, Medium and Low help prioritise review. They do not establish wrongdoing.
Check every active slicer and the current page before comparing totals across pages.
Fuel may be station or supplier filtered while monthly distance and efficiency remain all-source.
Invalid hour-meter intervals and excluded litres limit forklift L/h interpretation.
Record invoice, receipt, card, route and authorisation findings outside the dashboard.
The report is only as current as its configured data refresh. Confirm the last refresh before treating an open item as current.
WHO SHOULD USE IT
Each team can start with its own question and trace the same source transactions.
Which vehicle activity or fuel event needs a closer look?
Which costs, suppliers, rebates or reconciliations need support?
Which open exceptions can be traced to source transactions?
Where are risks concentrated, and who owns the follow-up?
How do forklift fuel and usage compare at the correct operating-hour grain?
A controlled pilot needs approved source data, confirmed rules and thresholds, a named evidence owner, and a process for recording each resolution. Human review determines whether a signal is explained, unresolved or needs escalation.