What belongs on the outside of an account recovery envelope?
Published 2026-11-19 · BasicSec editorial team · Worked example and worksheet
A volunteer coordinator opens the group binder and finds a note that says “recovery codes printed.” Which account owner should check it? Was the paper replaced when the codes changed? The binder needs enough information to answer those questions. A copy of the codes would give everyone holding the binder more access than they need.
1. Choose who reads each part
Start with one account and the role authorized to maintain it. The small-group accounts guide explains why people doing different jobs may need individual access. A volunteer who updates the duty rota might need to find the account steward. That job does not require the steward’s recovery material.
Keep the actual recovery material in the secure location approved by the account owner. Keep private contact details and the precise storage location off a widely circulated rota. A personal account holder can keep their own private recovery kit; recording a group responsibility does not give the group access to that person’s account.
2. Write a routing slip that can safely be handed over
Here is a fictional binder entry: Equipment calendar · maintenance role: calendar steward · private packet reference: EC-2 · status: owner review needed · latest custodian check: unknown. The role lets a coordinator route a question, and the reference allows the authorized steward to identify the packet. Neither field provides a way into the account. Use a role-only slip only if the group actually has an established private way to reach the role.
Two dates answer different questions. “Checked on” records when the steward last examined the private packet. “Review after” names an event such as generating a new code set. If nobody knows when the check happened, write “unknown” and assign it to the steward. A plan to verify the material is still a plan.
3. Read the provider’s replacement rule
- Google backup codes. A used code stops working. Creating a replacement set makes the previous set inactive. The account owner should review the stored set when they generate a replacement. Google’s backup-code instructions.
- Bitwarden two-step login recovery code. Bitwarden says a new recovery code is generated after the old one is used. Its instructions recommend saving the updated code securely. A change to the master password alone does not change that recovery code. Bitwarden’s recovery-code instructions.
A binder line that says “password changed” therefore tells you little about the private paper. Record the provider and the event that actually occurred. Only the authorized person needs to handle the replacement material.
Download the fictional routing slips
4. Try a paper handover without opening an account
Give a colleague this fictional message: “The calendar steward generated another Google backup-code set after packet EC-2 was prepared.” Ask which binder field should change. The answer is the packet’s status: its old set is obsolete. The steward needs to replace the private copy and record the check date after doing so. Writing the new codes into the rota would defeat the separation.
For a second example, suppose the only news is that the steward changed a Bitwarden master password. The recovery-code rule alone gives no reason to mark the two-step code obsolete. If the private packet also contains other information, the steward should review that information separately. Neither paper exercise proves a real account can be recovered.
If the group also needs to check a backed-up file, use the sample-file restore worksheet. Keep its results on the file record so they cannot be mistaken for an account recovery check.