PUBLISHED REPORT GUIDE / SYNTHETIC DEMO

Follow the signal.
Check the evidence.

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.

Tara Nawa Fuel Risk Report cover art showing fuel, risk, and control themes

BEFORE YOU START

The report gives you a place to begin.

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

What the report brings together.

Start with the fuel total, then follow the vehicle, card, station and ticket behind it.

01

Fuel activity

Spend, litres and transaction counts by month, vehicle, station and supplier.

02

Behavioural signals

Same-day refuelling and after-hours patterns alongside the exception register.

03

Vehicle risk

Ranked scores, risk bands and the score components that need review.

04

Controls and costs

Odometer quality, reconciliation, supplier analysis and rebates.

05

Equipment

Forklift fuel, operating hours, litres per hour and productive utilisation in separate views.

REPORT PAGE GUIDE

Find the right view for your question.

Choose a topic, then select a report page to see its next checks.

11 report pages

READ THE SIGNAL

Two labels. Different meanings.

The vehicle score band summarises overall risk. Each transaction exception has its own severity. Read them separately before deciding what to investigate.

LowBelow 15
Medium15 to 34
High35 or above

The Top 10 chart is a relative ranking. Red bars do not mean all ten vehicles have a High band.

Exception severity follows the rule

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.

Vehicle score combines several signals

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

A six step evidence trail.

Use the report to locate the signal, then verify the explanation with records outside the dashboard.

  1. 01

    Scope the signal

    Choose month, vehicle, station or supplier as applicable. Keep the selected values in your case note.

  2. 02

    Read the classification

    Record exception type and severity. Separately record the vehicle risk band and exception status.

  3. 03

    Trace the transaction

    Open the matching transaction ID. Check ticket and station together, card, time, litres and spend.

  4. 04

    Find a fair comparison

    Compare normal fills for the same vehicle, route, station or shift. Check meter validity.

  5. 05

    Verify outside the report

    Obtain receipts, invoice or settlement, card history, and dispatch or maintenance records.

  6. 06

    Document the outcome

    Record explanation, evidence, owner and resolution. Treat the signal as unproven until reviewed.

SYNTHETIC PRACTICE CASES

Six signals to trace.

All cases occur in Reporting Month 2026-07. These are practice leads, not allegations.

SignalVehicleTransaction IDFirst evidence check
Duplicate ticketDEM 1031910001, 910002Compare receipts at NFN001
Repeated fillsDEM 1032910004, 910005Check 08:00 and 09:30 fills
After-hours fillDEM 1033910006Confirm the 22:35 shift
Card mismatchDEM 1034910007Confirm card assignment
Invalid odometerDEM 1035910008Inspect the meter record
Station concentrationDEM 1036910009 to 910011Compare route and invoices

READING RESULTS RESPONSIBLY

Keep the context with the number.

01

Risk is a lead

High, Medium and Low help prioritise review. They do not establish wrongdoing.

02

Filter scope matters

Check every active slicer and the current page before comparing totals across pages.

03

Fuel and distance differ

Fuel may be station or supplier filtered while monthly distance and efficiency remain all-source.

04

Equipment needs coverage

Invalid hour-meter intervals and excluded litres limit forklift L/h interpretation.

05

Resolve with evidence

Record invoice, receipt, card, route and authorisation findings outside the dashboard.

06

Check data freshness

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

A different question for each team.

Each team can start with its own question and trace the same source transactions.

Fleet operations

Which vehicle activity or fuel event needs a closer look?

Finance and procurement

Which costs, suppliers, rebates or reconciliations need support?

Risk and internal audit

Which open exceptions can be traced to source transactions?

Executive leadership

Where are risks concentrated, and who owns the follow-up?

Equipment managers

How do forklift fuel and usage compare at the correct operating-hour grain?

Moving beyond the synthetic demo

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.

What this page shows

What to check

Navigate next