How to Pass On Your Passwords and Accounts (Safely, Before You Need To)

If something took you out of the picture tomorrow, whether a hospital stay, an accident, or the permanent version, could the people you trust get into what they'd need? The mortgage account. Your email, which is the reset key to everything else. The photo library.

For most people the answer is no, and the fix is not dramatic. It's an afternoon of setup, done calmly, long before anyone needs it. Here's the whole plan.

Step 1: Inventory what actually matters

Skip the completist spreadsheet of every account you've ever made. List what would genuinely matter to someone handling your affairs, in four buckets:

• Money: bank, brokerage, retirement, crypto, payment apps, recurring bills
• Keys: your primary email and your phone unlock, since these two open most other doors
• Irreplaceable: photo libraries, documents, anything that exists only digitally
• Ongoing: the domain that hosts the family website, subscriptions someone should cancel

For each, note where it lives and what it would take to get in. Ten to twenty entries covers most lives.

Step 2: Put a password manager at the center

If your passwords live in your head or a notebook, inheritance means someone reconstructing your life from scraps. A password manager turns "hundreds of secrets" into "one secret," and one secret is a thing you can plan around.

Most major password managers now ship an inheritance feature, usually called emergency access. You designate a trusted contact, and if they request access and you don't veto within a waiting period you set, they get in. 1Password's approach is different but equally workable: a printed Emergency Kit, with account details plus master password written in by hand, stored in a safe or with your will.

Set one of these up. It's the single highest-value item on this page.

Step 3: Turn on the platform legacy tools

A few platforms let you decide, right now, what happens later.

• Google's Inactive Account Manager. After a period of inactivity you choose, Google shares selected data with contacts you name, or deletes the account.
• Apple and Facebook legacy contacts. A designated person can access or memorialize the account after death, with documentation.

These take minutes each, and they're the only sanctioned path into those accounts. Platforms generally won't hand credentials to family, even with a death certificate, and in many cases the law is on the platform's side. Which brings us to the gap.

The gap most checklists stop at

Do steps 1 through 3 and you're ahead of almost everyone. But two structural problems remain, and they're worth naming.

Everything-or-nothing. Password-manager emergency access typically grants your entire vault. There's no way to say "banking logins to my spouse, the business accounts to my cofounder, and the journal to no one." One trusted contact, total access, which either overshares or forces you to choose nobody.

All-or-never timing. Emergency access is binary. It hasn't triggered, or it has. There's no staging, no way to say "if I'm unreachable for two weeks, tell my brother where the documents are; if it's two months, release the credentials themselves; and notify these three people in this order."

Delivery is assumed. Every plan above quietly assumes the message arrives, that the contact still uses that email, notices the notification, and completes the process. For something that fires exactly once, unattended, years after you set it up, "assumed" is doing a lot of work.

This staged, selective, verified-delivery version of the problem is what a dead man's switch is designed for. You check in on a schedule, and if you stop, releases fire in the order and to the people you defined, with different payloads to different contacts, escalating over time, using delivery workflows built to actually get through. Aegis DMS is built around exactly this model, with trusted-contact cascades and staged release. It complements rather than replaces the password manager. The manager holds the secrets, and the switch governs who learns what, and when.

Step 4: Write the one-page map

Credentials without context are a puzzle. Write a single page for whoever will act: where the vault is, who the emergency contact is, which accounts are in which bucket, who to call at the bank. No passwords on this page, because it's the map, not the treasure. Store it with your will or wherever your important papers live, and tell the relevant person it exists.

Step 5: Re-check yearly

Accounts change, people change, trusted contacts drift. Put a yearly reminder in the calendar, and birthday week works well, to re-run the inventory and confirm your emergency contacts are still the right ones. A plan nobody maintains fails quietly, which is the same as no plan.

None of this is morbid. It's the same impulse as leaving a spare house key with a neighbor, a small practical kindness to the people who'd otherwise be locked out at the worst possible time. If the staged-release model fits your situation, Aegis DMS is free to try.