Drone Battery Fleet Tracker

On evidence, against thresholds: visible swelling (immediate retirement — puffed packs are a fire risk, not a discount), voltage sag under load beyond your platform's norms, capacity below ~80% of new (mission math stops working), cell imbalance that persists after storage cycles, or any crash/water event. Cycle count is the leading indicator — packs past 200-300 hard cycles deserve scrutiny — but the retirement decision is condition-based, which is exactly what per-pack logging enables.

Because their risk transfers to vendors only through evidence: a contractor whose battery fleet, incidents and equipment accountability are documented is insurable and defensible; one whose records are vibes is a liability the client's own auditors will flag. Program-level records — exactly what this log builds — are increasingly itemised in RFPs and vendor agreements, which makes the thirty-second entry habit a direct revenue protector.

Everything you enter is saved in your browser's local storage on your own device — nothing is uploaded to any server. Your records stay completely private, work offline, and load instantly. Use the CSV export regularly to keep an off-device backup copy.

Always — the CSV export is a complete, lossless dump of your program record, generated locally in one click. Import it into commercial software, archive it with your files, or post-process it in a spreadsheet. No lock-in is deliberate: data you can't take with you isn't really yours.