Account recovery inventory: set the scope, evidence, and review date
Recovery paths form a graph: email can reset banking, a phone can unlock email, a password manager can store both, and a device account can locate or erase the phone. If one node fails, circular dependencies can make every route unavailable.
The inventory should describe where recovery assets are and who owns them - Not collect passwords, full backup codes, PINs, or identity documents into an unencrypted master sheet.
Complete each item with evidence, not memory
List the priority accounts
Record service, purpose, owner, login identifier, consequence of loss, and the official recovery page or support route.
Record authenticators and fallbacks
Note passkey provider, hardware keys, authenticator devices, recovery email, phone ending, codes, trusted devices, and delegated recovery.
Draw dependency loops
Mark when account A resets B and B resets A, or when every fallback depends on the same phone, email, household, or administrator.
Fix single points of failure
Add a controlled independent method, replace stale contacts, create spare keys, protect offline codes, and clarify shared or business ownership.
Set review triggers
Review at least after a new phone, number, email, password manager, key person, family change, job change, provider migration, loss, or security incident.
Capture the exception and its safer next action
| Item or blocker | What it affects | Decision or evidence |
|---|---|---|
| Every code is on the phone | Loss removes sign-in and recovery together | Move selected recovery assets to a protected independent location |
| Former employee owns the admin login | Business access depends on an unavailable person | Transfer ownership and enroll named backup administrators now |
| Recovery email is itself inaccessible | The fallback is only apparent | Recover or replace it while the primary account is still open |
| Spreadsheet contains passwords and codes | One file can unlock the entire identity | Remove live secrets and store them in a suitable encrypted vault or offline method |
Completed example: find and break a circular recovery dependency
This hypothetical map shows a primary email that resets a password vault while the vault stores the email password. It records independent recovery assets without copying live secrets.
| Account | Recovery dependency | Safer change |
|---|---|---|
| Primary email | Phone, trusted laptop, and code stored only inside the vault | Move a sealed code copy to a separate protected location |
| Password vault | Primary email and the same phone | Register a spare hardware key and document its custodian |
| Mobile account | Primary email plus carrier PIN | Confirm the PIN and add the carrier's strongest transfer protection |
Why this example is useful: The example reveals that three listed methods still depend on the same phone and email. Independence matters more than the raw number of recovery methods.
Use these prompts when the checklist is reopened
Map dependency, not just importance
A little-used email may be critical because it resets the primary account; a family member's number may still be attached without their knowledge.
Keep recovery methods diverse
Two methods on one phone are not fully independent. Consider device loss, number loss, travel, death, incapacity, and provider outage.
Test safely
Confirm recovery addresses, phone endings, code location, spare-key access, and trusted-device status without deliberately locking yourself out.
Separate the map from the secrets
Protect the inventory, but store actual codes or keys in an appropriate vault or physical location referenced indirectly.
Sources for Account recovery inventory
Confirm current instructions and limits for this specific task before acting.
Use the inventory to find circular and single-point recovery failures
Draw the dependency between priority accounts. If email resets the password vault, the vault stores the email password, and both depend on the same phone, losing that phone can block the whole recovery plan. Add an offline recovery method or another controlled route where the provider supports it.
Record enough to act without creating a new secret store. Keep the provider, username or masked identifier, recovery channels, authentication methods, trusted devices, code location, and last test date. Do not place passwords, full recovery codes, identity documents, or unprotected answers in the working sheet.
Test recovery in a low-risk way. Confirm that contact details are current, backup codes are readable, an alternate device can reach the official recovery page, and former devices or people no longer have access. A completed row means the route was verified and has an owner and review date, not merely that a box was filled in.
Questions to settle before marking it complete
Where should I keep the inventory?+
Use a protected, recoverable location appropriate to the impact: an encrypted vault, protected document, or carefully stored paper copy. Avoid an exposed cloud note.
Should a trusted person have access?+
For selected personal or business accounts, delegated or emergency access can help. Define scope, consent, activation conditions, and revocation instead of casually sharing passwords.
How do I test without causing a lockout?+
Review settings while signed in, confirm contact ownership, locate codes and spare keys, and test a lower-risk account first. Do not remove the last working method.
Use these guides to complete the harder items
Use these connected guides to turn a checked box into a tested, documented control. Use the Security tools, checklists & protection kits hub for the complete topic pathway, then continue with Password hygiene checklist, Passkeys guide, and Lost or stolen phone plan.
The inventory also reveals candidates for safe old-account deletion.
Carry long-term ownership decisions into the digital legacy plan.
