Battery-drain onboarding and handoff notes should include the device model, operating-system version, battery-health status, normal charge window, baseline workload, signal conditions, top battery-using apps, recent changes, tests already run, evidence location, safety triggers, owner, and next review. The notes should describe observations without collecting unrelated private content.
Capture a comparable baseline
Record when the device was charged and disconnected, starting and ending percentage, screen-active time, major activities, travel or low-signal periods, and whether the result was ordinary or unusual for that user. Identify recent operating-system, app, account, network, or hardware changes.
On iPhone, Battery settings show daily usage, app and system activity, on-screen and background time, and conditions such as low cellular coverage (Apple iPhone battery guide). Preserve only the diagnostic categories needed for the investigation.
Document tests and changes
For each test, record date, duration, starting state, workload, setting changed, expected result, observed result, and rollback. Change one factor at a time so the next owner can interpret the outcome. Separate a temporary workaround from a confirmed cause.
For Android development or an authorized test device, Battery Historian can correlate battery decline with events such as screen activity, CPU work, jobs, network use, and wake locks; Google also warns that the tool is no longer actively maintained and suggests newer tools where possible (Android Battery Historian guide). Note which diagnostic tool and version produced the evidence.
State privacy and safety boundaries
Do not include message content, precise location history, contacts, credentials, or unrelated screenshots. Identify whether the device is personal, shared, or organization-owned and who may authorize deeper diagnostics. Keep recovery codes and account passwords owner-controlled.
Add stop conditions for unusual heat, swelling, damage, repeated shutdown, or a manufacturer service warning. Those conditions require the manufacturer's support or an authorized service path, not another informal experiment.
Assign the next action
Classify the current state as explained by use, improved after a reversible change, still under observation, needs app investigation, or needs device support. Name the owner, due date, next controlled test, and evidence needed to close the case.
The handoff is complete when another person can reproduce the baseline, understand prior tests, protect private data, recognize safety triggers, and perform the next approved step without guessing. If workloads or conditions were not comparable, label the cause unconfirmed.
Sources
- Understand your iPhone battery usage and health — Apple Support
- Analyze power use with Battery Historian — Google