When an instrument cluster is replaced and the odometer starts again from a new number, do not overwrite your old readings. Add a note row with the old and new readings, work out the offset between them, and compute a true-kilometres column as displayed reading plus offset. Your lifetime kilometres and cost-per-km figures then carry on without a break.
Why does a new cluster break a vehicle log?
A log assumes the odometer only goes up. After a swap it can drop to near zero, and every distance calculation turns negative or silly. Fuel mileage, service intervals and cost per km all depend on distance between two readings, so one reset can quietly corrupt months of figures. The fix is to separate what the dashboard says from the true distance the vehicle has covered.
What is the offset and how do you work it out?
The offset is the number you add to the new cluster's reading to get the true figure. Ask the workshop to write on the job card the reading on the old cluster when it was removed and the reading on the new one when it was fitted. Offset equals old reading minus new reading at the moment of the swap. Say the old cluster showed 48,200 km and the new one was set to 0, so the offset is 48,200.
What does the sheet look like?
| Date | Displayed km | Offset | True km | Note |
|---|---|---|---|---|
| 2 Jan | 47,900 | 0 | 47,900 | Routine entry |
| 10 Feb | 48,200 | 0 | 48,200 | Last reading on old cluster, per job card |
| 10 Feb | 12 | 48,200 | 48,212 | New cluster fitted at 0; old was 48,200 |
| 18 Mar | 1,150 | 48,200 | 49,350 | Routine entry |
Check the arithmetic: between 10 Feb and 18 Mar the dashboard moved 1,150 minus 12, which is 1,138 km, and the true column moved 49,350 minus 48,212, also 1,138 km. If you spent, say, ₹2,800 on fuel in that period, the cost is ₹2,800 divided by 1,138, about ₹2.46 per km.
Which formulas do you need?
- Columns: A date, B displayed km, C offset, D true km, E note. Put headings in row 1.
- D2: =B2+C2, copied down the column.
- C3: =C2 for every ordinary row, so the last offset carries forward automatically.
- On the swap row, type the new offset by hand, replacing that row's formula.
- Distance since the previous row: =D3-D2, and lifetime kilometres: =MAX($D$2:$D$500)
Always base mileage, service-due and cost-per-km calculations on the true km column, never on the displayed one. The same formulas work in Excel and Google Sheets.
What if nobody noted the old reading?
- Use your last logged reading before the swap, from fuel or service entries.
- Estimate from your usual daily or weekly distance for the days since that entry.
- Mark the offset as an estimate in the note column, with the reasoning.
- Ask the workshop whether the old cluster's reading is recorded anywhere in their system.
What if the odometer reset without a replacement?
Treat it the same way. Record the last good reading, the new displayed reading and a note on why. If the reading is wrong rather than reset, such as a cluster showing a stuck number, do not edit history; add a note row and use an offset from the day you noticed. Anything you cannot verify should be labelled as an estimate.
Where does SpendixAI fit?
Kilometres live in your own log, because SpendixAI tracks rupees, not odometer readings. What it can hold is the cost side: attach the cluster replacement bill to its transaction as a receipt, so the workshop invoice and your job-card photo travel together.
Checklist for the day of the swap
- Get the old and new readings written on the job card.
- Photograph the job card and the invoice.
- Add the note row and the offset in your sheet before you drive away.
- Check that your next fuel row uses true km and not displayed km.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


