What your family will see

You’re building this for someone else’s worst month. This page shows the packet from their side, in the order they’ll meet it. It’s useful both for your own peace of mind and for deciding what to write in the editable parts.

First: not the vault. A letter.

When the recovery completes and the packet renders, the first screen is not a wall of accounts. It is:

Your letter, if you wrote one. Most owners write a short note for this page. It’s the single most appreciated feature we have, and it costs you ten minutes. Write the letter.
The executor checklist. A one-page, ordered list of what to do first. It begins with the things that decay fastest, and the first warning is in bold: do not cancel the phone line — that number receives the reset codes for everything else.

The executor checklist

A typical checklist reads like this (yours is generated from your actual accounts):

Keep the phone number active: transfer or assume the account, don’t cancel ([carrier playbook] is linked)
Order 10+ certified death certificates; everything downstream wants one
Secure the devices: don’t wipe, don’t “helpfully” factory-reset anything
Access the password manager via [its playbook]
Start the Google and Apple legacy processes (web forms, not phone calls)
Notify banks through their estate services; the packet lists which banks
Watch for these autopays and subscriptions (list follows)
If crypto exists: read the wallet playbook before touching anything

Each line links to the relevant account card and playbook. Nothing assumes technical skill; anything unavoidable (“export the vault”) is spelled out click by click.

The account cards

Then the map: one card per account, each showing what the account is, what strategy applies, and what to do.

Native mechanism (Google, Apple, Bitwarden…): “a legacy process exists; here’s the link, here’s what to bring.” Usually a death certificate and a web form.
Vault secret (wallets, password manager, device passcodes): “the secret is in this packet, here; here’s how to use it safely.”
Legal process (banks, brokerages, credit cards): “call this institution’s estate line; you do NOT need a password, and you should not use one even if you find it.”
Your instructions, verbatim, wherever you wrote them. This is the human context no automation can supply: “the mortgage autopays from Chase on the 1st”, “the storage unit key is in the garage cabinet.”

The playbook snapshot

Every packet carries frozen copies of the playbooks as they existed when you last exported, so a survivor opening the packet years later still has complete instructions, clearly timestamped. If Google has changed its process since, the snapshot still names the mechanism and the search terms; a stale map of the right territory beats no map.

The letters folder

Beyond the practical letter on page one, the packet can hold private letters: to specific people, for specific occasions. They’re encrypted with everything else, and released only with everything else. What you put here is between you and them.

What they will never see

Bank passwords, brokerage logins, credit card numbers: the packet doesn’t contain them, deliberately, and page one of the banking section explains why in two sentences: the legal process is faster than it sounds, and using a dead person’s login can create real problems for the living. (Why we don’t store bank credentials.)

Preview it yourself

The app can render your packet exactly as survivors will see it: same executor checklist, same cards, same letters (yours will be the only eyes on them until the real day). Preview it after any big change. If something reads wrong from their side of the table, you’re the only person who can fix it, and today is the only day you can be sure of having.