A recovery plan and recovery material are different things. The material may enable access; the plan describes responsibilities, dependencies and the instructions that apply. Keeping that distinction intact lets you organise the work without placing secrets in another browser field or document. This guide concerns the plan only. It is not a procedure for creating, entering or testing a real wallet backup.
Identify the arrangement being planned
Start with a neutral account or device label and the exact product or service involved. Record the type of recovery method documented for that arrangement. Do not assume that the method used by a previous wallet, a different hardware model or a service login applies here. Similar product names can conceal different formats and dependencies.
Add a link to the relevant official instructions and the date checked. “Uses a backup” is too broad to be useful. “The method and any additional dependencies need confirmation in this model’s documentation” identifies a specific research task without exposing sensitive information. Leave the plan incomplete when the supporting instructions are incomplete.
Keep secret material out of the worksheet
Do not enter recovery words, private keys, passwords, passphrases or access codes. Avoid screenshots that include them. A note about a dependency can say that an additional secret is required without containing the secret itself. Likewise, a planning label should not become a detailed map that exposes sensitive storage locations to every reader of the document.
Bitcoin’s security guidance discusses backup, software maintenance and the importance of planning for access. Apply the underlying responsibility carefully: the actual procedure must match the wallet and arrangement. A generic browser planner cannot inspect whether a backup is complete, correctly recorded, readable or compatible with a recovery tool.
Assign the work, not just the equipment
Make rows for reviewing instructions, maintaining the relevant device, checking documentation availability and arranging appropriate specialist advice where needed. Give each row an owner and review date. Buying a durable recording product does not assign these jobs. A material specification also does not establish that a particular backup format fits the product.
If more than one person is involved, distinguish who may read the planning record from who has authority over an account or recovery process. Those are different permissions. Questions about inheritance, legal authority or a shared financial arrangement need suitable professional support; a name typed into a worksheet does not create that authority.
Rehearse with a fictional interruption
Choose a tabletop scenario such as replacing a phone or discovering that an old documentation link has moved. Ask which instructions and responsibilities would need attention. Record missing information without initiating a live recovery, connecting an unfamiliar tool or entering actual backup material. A rehearsal can reveal gaps while remaining an exercise in planning.
End with a dated list of unresolved questions and the person responsible for each. Store the planning record according to its sensitivity, and review it when the arrangement changes. Do not label the plan tested merely because you have read it. Its value is a maintainable account of responsibilities and dependencies. The actual recovery material belongs in the appropriate product-specific protection process, outside this worksheet and outside ordinary collaboration notes.
Custody Planning Workbook helps you organise your own notes in this browser. Keep credentials and recovery material out of your project.