Free checklist · print or save

The one-page emergency handoff checklist

If you went unreachable tomorrow, could someone keep your life and work moving? This is the single page that answers that — what to document, where to point to your keys (never the passwords themselves), and who to name. Fill it in, print it, and keep it where your trusted person can find it.

1. The accounts that actually matter

List only what someone would truly need — not everything you own.

Email — the master key, since it resets everything else
Password manager — the vault, and how its emergency access is set up
Banking, payment, and invoicing logins
Accounts you hold on someone else's behalf (clients, family, a group)
Domains, hosting, and anything that bills automatically
Devices and their unlock codes

2. Where the keys live — not the passwords

Never write the actual passwords on this page. Point to where they are.

Which password manager holds everything, and how to unlock it in an emergency
Where the master password or recovery kit is kept (a safe, a sealed envelope)
Where any two-factor backup codes are stored
Who already has partial access, and to what

3. Who steps in

Name real people, and tell them they've been named.

The person who confirms you're genuinely unreachable (your confirmer)
Who receives what — match each account or task to a specific person
A backup for each role, in case the first can't act
Their current phone and email, so they can actually be reached

4. What you want done

The instructions someone could follow without you in the room.

The first three things to do, in order
Clients or people to notify, and what to tell them
What to keep running, what to pause, what to shut down
Anything that's time-sensitive (renewals, payroll, deadlines)

5. Keep it current

A plan that's a year out of date is worse than none.

Review it every 6 months and after any big change
Confirm your named people still agree and are reachable
Re-check that the keys are still where this page says they are

One catch: a checklist only works if someone knows it exists and notices when you go quiet. That’s the part Proceedly automates.