Skip to content

Audit a fleet's fuel-card transactions into litres, distance and consumption per vehicle-month

Exact prompt

# Fleet fuel audit: litres, distance and consumption per vehicle per month Inputs: `vehicles.csv`, `fuel.csv` (fuel-card transactions), `odometer.csv` (monthly odometer readings). Rules: - Vehicle ids are case-insensitive and may carry stray spaces; treat "vh-012 " and "VH-012" as the same vehicle. Report ids in upper case. - A transaction with the same vehicle, timestamp, quantity and unit as an earlier row in fuel.csv is a repost of it: keep only the first. duplicates_removed = number of rows dropped this way. - Quantities in `gal` are US gallons (1 gal = 3.785411784 L). Stations in DE, FR, NL, IT and ES write decimals with a comma ("45,30" = 45.30). - A transaction belongs to the month of its local date in the vehicle's depot time zone (`depot_tz`); ts_utc is in UTC. - Distance for a month = end_reading - start_reading from odometer.csv, in the vehicle's odometer_unit; convert miles to km with 1 mi = 1.609344 km. - litres and km per vehicle-month are rounded half-up to 2 decimals from the exact sums; l_per_100km = exact litres / exact km x 100, rounded half-up to 2 decimals. - over_tank = ids of the kept transactions whose litres are strictly more than the vehicle's tank_l, sorted. - fleet_litres = exact total litres of all kept transactions, rounded half-up to 2 decimals. Write `out/fleet.json`: `{"vehicles": {"<VEHICLE_ID>": {"<YYYY-MM>": {"litres": <n>, "km": <n>, "l_per_100km": <n>}, ...}, ...}, "over_tank": [<txn_id>, ...], "duplicates_removed": <int>, "fleet_litres": <n>}` Cover every vehicle-month present in odometer.csv (months 2026-09 to 2026-11). Numbers are checked to within 0.005. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.

Roll 3,000-5,000 fuel-card transactions for 45-60 vehicles into litres, distance and L/100 km per vehicle per month. The data mixes US gallons with litres and comma decimals with dot decimals, and includes reposted duplicates and vehicle ids that differ only in case or spacing. Transactions near midnight are assigned to a month by each depot's local time zone, and some odometers read in miles. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: litres_per_vehicle_month km_per_vehicle_month miles_odometers_converted consumption month_by_depot_local_date reposts_removed over_tank fleet_litres

Best model for this task so far: Claude Haiku 5.5 (effort default (no --effort flag) · thinking on) (success, $0.0079, 33s).

Run this on another model

All runs (4)

100% pass rate across 4 eligible runs: 4 pass, 0 partial, 0 fail. Partial and failed runs are listed below with everything else.ⓘ

Runs for this use case
ModelCostTimeStep-insⓘAutonomyOutcomeTrustⓘDateCompare
DDeepSeek V4.1 Flash (Venice)thinking on$0.0147s0Fully autonomouspassTrust 80%2026-11-04
AClaude Opus 5.5default · thinking on$0.1529s0Fully autonomouspassTrust 80%2026-10-20
AClaude Haiku 5.5default · thinking on$0.007933s0Fully autonomouspassTrust 80%2026-10-20
AClaude Sonnet 5.5default · thinking on$0.0615s0Fully autonomouspassTrust 80%2026-10-20

Embed this result

A live badge for this use case. It links back here and updates as new runs are published.

UseCaseRank badge for Audit a fleet's fuel-card transactions into litres, distance and consumption per vehicle-month

Get new runs and ranking changes weekly

Which models got better or cheaper on real tasks like this one.