Digital Executor Plan
A digital executor plan is a written set of instructions that tells a trusted person what to do with your online accounts and digital records when you cannot manage them. The plan matters because many services restrict access to account content, even when family members can prove identity. Health-related records, pharmacy portals, patient portals, and insurance logins often sit behind separate authentication systems, so your executor needs more than usernames.
In practice, the plan usually covers three categories: account inventory, access and recovery steps, and instructions for handling content. For example, a patient portal account may require a specific request process, while a cloud photo library may have a different recovery path. If you share a device with a spouse or caregiver, the plan should also describe what is stored locally versus in the cloud, because local access can disappear when a phone or laptop is wiped.
Many people start with a password manager export, then stop. That gap matters: a list of passwords does not explain what to do next when a service refuses to share data. I have seen plans that include “contact support” without the exact account identifiers, which turns a time-sensitive task into a long back-and-forth.
Main Problems And Pain Points
People often get the scope wrong. They document only social media or email, then forget the accounts that hold health and billing information, such as insurer portals, pharmacy apps, telehealth accounts, and medical device companion apps. Those services frequently use separate logins, and some store data in formats that are not easily transferable.
Another common failure is mixing “access” with “authority.” A digital executor may have permission to act under a will or power of attorney, but many platforms still require their own verification steps. That means your plan should include both legal documents and service-specific instructions, because the service’s policy determines what happens after verification.
Supporting technologies also create dependencies. Two-factor authentication (2FA) can block access if the plan does not include recovery codes, the phone number used for SMS, or the authenticator app details. Password managers help, but they still require a way to sign in and unlock vaults. If your plan relies on a single device, a lost phone can break the chain.
Finally, people underestimate how long account closure and data requests can take. Some services respond quickly to deletion requests, while others require identity verification and may take weeks. If your plan does not state timelines and priorities, your executor may spend time on low-impact accounts while urgent ones remain unresolved.
Solutions And Advice
Document Accounts With Identifiers
Create an inventory that lists each account category and the identifiers needed to locate it. Include the service name, the account email or username, the approximate sign-in method (email link, password, SSO), and whether 2FA is enabled. Add a short note about what the account contains, such as “patient portal messages” or “insurance claims history.” A simple spreadsheet works, but a password manager “secure note” can reduce exposure if you store it with encryption.
Use a consistent naming convention so your executor can scan quickly. For example, prefix rows with “HEALTH,” “FINANCE,” “COMMUNICATION,” and “DEVICES.” On my own planning template, I label the first column “Service + Region” because some insurers and clinics use different portals by state or country, and that detail affects the correct support channel.
For each account, record whether you want the executor to download data, request deletion, or close the account. If you have a health-related subscription, note whether it is tied to autopay and which bank account funds it. That reduces the chance of continued charges after incapacity.
Record Access Paths And 2FA
Write down how each account is accessed today, including 2FA recovery methods. Include the location of recovery codes, whether they are printed, stored in a vault, or saved in a secure note. If you use an authenticator app, record which app name and whether it is on a phone, tablet, or computer. Mention the phone number used for SMS 2FA, since that number can become unavailable after a carrier change.
For outcomes, aim for a plan that lets an executor complete sign-in steps within one sitting for accounts that support normal recovery. For services that require formal requests, the goal shifts to reducing delays by having the correct identifiers ready. If your plan lacks recovery codes, the executor may need to wait for service-specific verification, which can take multiple days to weeks.
Include device-level access notes too. If your executor needs access to a laptop or phone, document the passcode storage method and whether the device uses a biometric lock. If you use full-disk encryption, state that the device may require the passcode to decrypt, and that a factory reset will erase local data.
Map Legal Authority To Services
List the legal documents that authorize your executor or agent, such as a will, durable power of attorney, and any healthcare directive. Do not assume that legal authority automatically grants platform access; platforms often require their own forms and verification. Your plan should include where copies are stored, who has them, and the document dates.
For the service side, document the exact process you want followed. Some platforms provide “inactive account” or “digital legacy” features, while others require a death certificate and a request form. If you have used a service’s legacy setting, record the date you enabled it and the email address tied to the setting. I once reviewed a plan where the legacy setting existed, but the executor did not know it was tied to a different email address than the one used for daily login.
When you cannot predict a service’s process, write a decision rule: “If the service refuses access, request deletion of account content and preserve only billing records for X months.” That rule prevents the executor from improvising under stress.
Set Priorities And Timelines
Assign priorities based on risk and time sensitivity. Health-related accounts often rank high because they may affect ongoing prescriptions, billing disputes, and communication with care teams. Finance accounts rank high because autopay can continue. Low-risk accounts, like old forums, can wait.
Use a short timeline in the plan: what to do in the first 24–72 hours, what to do within two weeks, and what can wait beyond a month. For example, within 72 hours your executor might secure device access, stop urgent autopay where possible, and identify active healthcare portals. Within two weeks, they might submit formal requests for data or deletion where required.
Include a “stop list” too: accounts you do not want closed immediately because they contain records needed for insurance appeals. This is where people often get it wrong, closing everything at once and then discovering they needed a message thread for a claim.
Case Examples
Example 1: Patient Portal And Pharmacy App
An anonymized reader keeps a spreadsheet of accounts and adds a note that their patient portal uses 2FA via an authenticator app on a phone. The plan includes the phone model, the fact that the authenticator app is named “Authy” (version noted as 23.1 in the plan), and where recovery codes are stored in a password manager vault. The executor’s first step is to unlock the phone and sign in to the patient portal to download recent visit summaries and medication lists.
In the same plan, the reader records that the pharmacy app uses a separate login tied to a different email. The executor follows the plan’s priority rule: they request prescription refill history within the first two weeks, then submit a formal data request for message history if the portal requires it. The plan avoids a common trap: it does not assume that downloading data from one app covers the other.
Example 2: Incapacity And Shared Devices
An anonymized couple shares a tablet for family communications and uses separate email accounts for healthcare. The plan states that the tablet is protected by a passcode stored in a secure note, and that the tablet’s local files are encrypted. The executor is instructed to check whether the tablet has a “recently used” session for the healthcare email, because that can reduce the need for account recovery.
The plan also lists the insurer portal login method and notes that it uses SMS 2FA to a phone number that belongs to the spouse. The executor is told to contact the carrier to confirm whether the number remains active during incapacity. This detail prevents a delay caused by a deactivated number, which can block sign-in even when the executor has the correct password.
Comparison Table And Checklist
Use the checklist below to decide what to document first. The table compares common plan components by their typical impact and failure modes.
| Plan Component | Helps With | Typical Failure Mode | What To Add |
|---|---|---|---|
| Account Inventory | Finding services quickly | Missing health/billing accounts | Add account purpose + region |
| Password Access | Signing in when allowed | Vault locked or device lost | Record unlock method + backups |
| 2FA Recovery Details | Passing authentication | Recovery codes not found | Store codes in a secure vault |
| Legal Authority | Platform verification | Executor lacks documents | Store copies + document dates |
| Priority Timeline | Reducing wasted effort | Everything handled at once | Define first 72 hours actions |
Step-by-step checklist you can copy into your plan:
- List every account that touches health, billing, prescriptions, or communications.
- For each account, record login method and whether 2FA is enabled.
- Store recovery codes and note where they are kept.
- Record device access details needed to sign in (passcode storage, encryption notes).
- Attach legal document locations and dates.
- Write a priority timeline for first 72 hours, two weeks, and beyond one month.
- State what to download, what to request, and what to delete or close.
- Schedule a review date (for example, every six months; I use 2026-03-15 as a placeholder in my template).
Common Mistakes
One mistake is storing sensitive details in plain text files that multiple people can access. If your plan includes passwords or recovery codes, treat it like a high-risk document. A safer approach is to store credentials in a password manager vault and keep only pointers in the plan, such as “vault name” and “how to unlock.”
Another mistake is assuming that a digital executor can read everything once they have a password. Many services restrict content sharing and require formal verification. Your plan should include a fallback path when a service denies access, such as requesting deletion or preserving only billing records.
People also forget to update the plan after account changes. A new phone number, a changed authenticator app, or a moved email address can break recovery. Add a review step after major life events, like switching carriers or changing insurers, because those changes often affect 2FA and portal access.
Finally, plans sometimes omit the “what not to do” section. If your executor closes accounts that hold medical records needed for appeals, the delay can become expensive. A short instruction like “do not close insurer portal until claim disputes are resolved” prevents avoidable harm.
FAQ
What is a digital executor plan?
It is a written set of instructions and records that helps a trusted person manage your online accounts and digital records during death or incapacity, including account inventory, access steps, and service-specific actions.
What should be documented for health portals?
Record the portal name, login method, 2FA type, what data it contains (messages, visit summaries, prescriptions), and whether you want downloads, deletion requests, or preservation for insurance disputes.
Do passwords alone work for account access?
Passwords often help only for accounts that allow normal recovery. Many platforms still require identity verification and legal documentation, so your plan should include both credential access and the service’s request process.
How should 2FA recovery be handled in the plan?
Document where recovery codes are stored, the authenticator app used, and the phone number tied to SMS 2FA. If the plan relies on a single device, note what happens if that device is unavailable.
How often should the plan be updated?
Review it on a fixed schedule and after major changes that affect login access, such as switching phone numbers, changing email addresses, replacing a phone, or updating legal documents.
Author's Insight
A digital executor plan works best when it treats online access as a chain with multiple links: account inventory, authentication recovery, legal verification, and service-specific policies. Credentials reduce friction for sign-in, but they do not override platform rules for sharing or deleting content. The plan should therefore include both “how to sign in” and “what to do if the service blocks access.” A practical approach is to test the plan’s steps with a trusted person using a low-risk account, then adjust the documentation when recovery steps fail.
Key Takeaways
Document an account inventory that includes health and billing portals, not just email and social media. Record 2FA recovery details and device access notes so an executor can complete sign-in steps. Map legal authority to the platform verification process, and add a priority timeline to prevent wasted effort. Store sensitive credentials with encryption and keep the plan updated after changes to phone numbers, email, or devices.
