Method
Device rotation checklist
How our offline wallet tracker practice sequences a hardware-wallet fleet review — from intake to signed checklist.
Hardware-wallet fleets fail quietly: a spare left with a departing colleague, a travel device that never returned to the rotation queue, firmware that lagged behind a manufacturer advisory. Our checklist exists to make those gaps visible in one sitting.
What the checklist covers
| Field | Why it matters |
|---|---|
| Serial / label | Proves the device in hand matches the register |
| Model & firmware | Flags age and known advisories |
| Passphrase present? | Yes/no only — never the value |
| Location | Safe, courier pouch, or secondary site |
| Spare mapping | Which unit replaces this one |
| Last recovery proof | Date and who observed |
| Rotation trigger hit? | Policy rule that forces retirement or reseeding |
Sequence we use on review day
- Policy alignment — We confirm which triggers your team already agrees on. If none exist, we pause and book a workshop before touching devices.
- Physical match — Every hardware wallet listed must appear on the table — or be accounted for with a signed exception.
- State capture — Firmware strings and location notes are written while the device is powered in front of authorised staff.
- Rotation candidates — Units that hit age, exposure, or staffing triggers are marked for retirement, reseed, or spare promotion.
- Handover — You keep the completed checklist. We keep only the engagement letter and invoice — never seed material.
Book the work, not the metaphor
If you need the checklist applied to your actual devices, request a hardware-wallet fleet review. If you only need the rules written, start with the workshop.