Bill a month of electricity from shuffled meter reads with estimates, rollovers and a meter exchange
Exact prompt
# Bill September electricity from meter reads Inputs: `meters.csv` (each account's meters, including one exchange), `reads.csv` (actual "A" and estimated "E" reads, in no order) and `tariff.json`. Bill every account for the period from the opening read date to the closing read date in `tariff.json`. - Consumption = closing read minus opening read for each account. - When a meter has both an estimated and an actual read on the same date, use the actual read. An estimated read with no actual read for that date stands. - Meters have 5 dials and roll over from 99999 to 00000. A closing read below the opening read means the meter rolled over once. - If a meter was exchanged during the period, consumption = (old meter's final reading minus its opening read) + (new meter's closing read minus its initial reading). - Energy charge: the first `tier1_kwh` kWh at `tier1_rate`, the rest at `tier2_rate`. - Bill = energy charge + standing charge for 30 days, plus VAT on the whole. - Round each bill to cents half-up only at the end; the grand total is the sum of the rounded bills. Write `out/bills.json`: `{"kwh": {"<account_id>": <kWh>}, "bill_total": {"<account_id>": <amount>}, "grand_total": <amount>}`. ## 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.
Produce tiered electricity bills for 12-18 accounts from 30-50 shuffled reads. Some closing reads exist both as an estimate and as an actual, two meters roll over past 99999, and one account had its meter exchanged mid-month, so its consumption spans two meters. Keeping the estimate, missing the rollover, or subtracting across meters each gives a wrong kWh figure and bill. 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: consumption rollover_and_exchange bill_amounts grand_total
Best model for this task so far: Claude Sonnet 5.5 (effort default (no --effort flag) · thinking off) (success, $0.05, 9s).
All runs (3)
67% pass rate across 3 eligible runs: 2 pass, 1 partial, 0 fail. Partial and failed runs are listed below with everything else.ⓘ
| Model | Cost | Time | Step-insⓘ | Autonomy | Outcome | Trustⓘ | Date | Compare |
|---|---|---|---|---|---|---|---|---|
| AClaude Opus 5.5default · thinking on | $0.12 | 18s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-21 | |
| AClaude Haiku 5.5default · thinking on | $0.0052 | 22s | 0 | Fully autonomous | partial | Trust 80% | 2026-10-21 | |
| AClaude Sonnet 5.5default · thinking off | $0.05 | 9s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-21 |
Embed this result
A live badge for this use case. It links back here and updates as new runs are published.
Get new runs and ranking changes weekly
Which models got better or cheaper on real tasks like this one.