An owner posts a photograph of their battery screen and asks whether the state of health figure is good. The replies split at once: some say the number is fine, others say it is far too low for the age of the car. Almost nobody asks the questions that would make the argument meaningful. At what state of charge was it taken? What was the pack temperature?
A single reading can only answer one question: what the system reported at one moment, under one set of conditions. It cannot tell you whether the pack is holding up, because holding up is a property of behaviour across time. This article explains why comparable readings taken over time are more informative than any single figure, and where the honest limits of trend-watching lie.
Why one reading is a snapshot, not a diagnosis
A battery reading is produced by the battery management system, which estimates parameters such as state of health from information accumulated over the life of the pack. Those estimates depend on charge throughput, internal resistance behaviour, temperature history and how the pack has been loaded. The system recalculates them as it learns more, so they can move without anything physically changing in the cells.
Several ordinary circumstances shift the numbers without indicating a fault. A measurement taken straight after a fast charge is not equivalent to one after an overnight rest. A reading in mid-winter is not comparable to the same reading in summer, and a car left unused for weeks may present different estimates once it returns to regular use.
None of this makes a single reading useless. It does mean that treating one figure as a conclusion about battery condition asks more of that number than it can support. A scan result is information for diagnosis; it is not a diagnosis, and it does not certify a battery.
What trend-watching can realistically show you
When readings are collected under similar conditions, their relationship to one another becomes visible. A pack may hold a broadly stable state of health estimate across several months of comparable readings. Another may show more movement than expected between consecutive readings, or cell-level values that drift apart rather than staying together.
That comparison is where the practical value sits. Stability over a consistent series is a different kind of information from a single high number, and a change in the pattern is more interesting than the value at any one point. A widening divergence between the highest and lowest cell readings may justify a question rather than a conclusion.
What trend-watching cannot do is deliver a prediction. It cannot tell you how many years of service remain or what capacity the pack will have next autumn. Trend data describes what has been observed; it does not forecast the future, and no honest data set can promise a fixed degradation rate.
Building a comparable reading session
A trend is only as good as the consistency of the readings behind it. Most of the discipline is about repeating the same conditions, not running more scans. The routine below is practical rather than technical; the exact menus and parameters available depend on your vehicle and equipment.
- Pick a repeatable moment. Many owners scan after an overnight rest, with the car unplugged and at a similar state of charge each time. Whatever moment you choose, keep choosing it.
- Record the conditions, not just the figures. State of charge, ambient temperature, recent charging or loading, and the odometer reading all belong in the note.
- Save the full session, not a photograph of one line. If your tool exports a report, keep the file. A saved session preserves context that a screenshot strips away.
- Keep the intervals sensible. Monthly or quarterly readings are usually enough to reveal a pattern. Daily scanning adds noise and little else.
- Keep the records with the car. A dated folder of sessions is useful at service time and helpful if you later sell, because it shows how the readings were obtained rather than only what they said.
If you already log other readings from the car, the same habits apply. The temperature and state of charge conditions behind each session are part of the record, not background detail.
Recording conditions so the data keeps its meaning
A reading separated from its conditions loses most of its interpretive value. Six months later, a state of health figure with no context is difficult to compare with anything, including your next reading. A minimal note changes that: date, odometer, state of charge, ambient temperature and anything unusual beforehand is usually sufficient.
It also helps to note what changed between sessions. A shift that coincides with heavy fast charging, a hot spell or an extended idle period has a plausible context. A shift with nothing to explain it is simply unusual, which is a reason to look more closely rather than to panic.
Write observations in plain language and resist converting them into conclusions. "Lowest cell reading was further below the others than at the previous check" is a factual note. "The battery is failing" is a diagnosis, and a data log cannot establish it on its own. Reading a series of battery readings carefully means keeping that distinction intact. If a note concerns you, the sensible next step is a conversation with a qualified technician, and a dated series of sessions gives them far more to work with than a single value remembered from one afternoon.
Cell-level readings and the value of context
Many battery tools display data at the level of individual cells or cell groups, which is more detailed than a pack-wide figure, and easier to misread. Cell values in a healthy pack are not identical, and small differences are normal. The meaningful observation is the direction of travel across comparable sessions, not the spread at one moment.
Context matters twice over. Cell behaviour varies with temperature and state of charge, so a spread measured on a cold pack is not directly comparable with one measured on a warm pack. A single session showing a wider spread may reflect conditions rather than condition. The general principle, that cell-level battery data needs context before it means anything, applies to any system value read from a vehicle. A rising difference between cell readings is a matter for a technician to examine, not something a data log can resolve.
Where tool coverage shapes what you can compare
Your ability to build a useful series depends on which parameters your equipment can read from your vehicle. Coverage varies considerably between tools and models, which is why a general-purpose reader and a vehicle-specific device can return quite different values from the same car.
For some EV owners a dedicated model is more practical. As one example, TopTekk offers a power battery scanner for MG EV owners that reads battery state of health, cell-level battery data, charge and discharge statistics, fault codes and live data, and connects through the OBD2 port over Bluetooth. A comparable scanner designed for selected BYD models covers a similar set of parameters for that range. Both are one-time purchases without a monthly subscription and carry a one-year warranty.
Neither is a substitute for professional assessment, and neither will tell you whether a battery is good. What they can do is produce a consistent set of readings from session to session, which is what a trend needs. Before ordering, check that your exact vehicle appears in the published compatibility information.
When a trend is worth acting on
Most movement in battery data over a year is ordinary, and much of it reflects seasons and driving patterns rather than the pack itself. The question worth asking is not whether the numbers changed, but whether the change is explained in your notes.
The situations that justify professional attention are fairly consistent. A pattern that shifts without a corresponding change in usage or conditions. Cell readings that drift apart across comparable sessions. Warning messages that appear alongside the data. Any of these is a reason to have the vehicle examined by someone qualified, rather than a reason to run more scans and hope for a different number. Two points are worth holding on to: a scan does not guarantee roadworthiness and does not replace routine maintenance, and a warning about a braking, steering or high-voltage condition belongs with a qualified technician, not a data log.
Keeping the habit without overdoing it
The value of tracking comes from consistency and interpretation, not from volume. A reading every few weeks under the same conditions, recorded with those conditions alongside it, tells you more over a year than daily scans with no notes attached. The routine should be small enough that you keep it up after the novelty has passed, and saving sessions nobody reviews is accumulation rather than tracking.
Frequently asked questions
How often should I check EV battery data?
Monthly or quarterly checks under the same conditions are usually enough to reveal a pattern. More frequent scanning adds variation from temperature, state of charge and recent use without adding much information. Consistency of conditions matters more than the number of sessions.
Is a falling state of health figure a problem?
Not necessarily. The figure is an estimate produced by the battery management system and it moves with conditions and with the system's own learning. A change that coincides with a hot spell, heavier fast charging or long idle periods has a plausible explanation. A change with no explanation is a reason to have the vehicle looked at, not a reason to assume the worst.
Can battery data predict how long my pack will last?
No. A record of readings describes what has already been observed. It cannot forecast remaining service life, future capacity or replacement cost, and any tool or report that claims to predict those things from a scan is overstating what the data supports.