Plan and prepare
Begin an archive handover while the current custodian is available to answer questions. Prepare a collection overview that explains its purpose, locations, structure, sensitive sections, and outstanding problems. A list of drives is not enough; the incoming person needs to understand what the archive contains and which copy is authoritative.
Inventory the services, devices, software, and accounts required to maintain and restore the collection. Record who owns each resource and how authorized access is transferred. Use the organization's secure account process and provider instructions. Do not place passwords or recovery secrets in the public catalog or an ordinary shared meeting note.
Use a clear process
Review the maintenance calendar together: new intake, catalog updates, checksum checks, backup creation, restore testing, and rights review. Identify work that is overdue rather than presenting an artificially perfect collection. Agree on what must be completed before transfer and what the new custodian will take over.
Have the incoming custodian perform a small end-to-end exercise: locate an item, explain its source and access status, verify a copy, and restore a sample to a test location. Observe where the instructions depend on unwritten knowledge. Correct the guide while both people can confirm the intended process.
Worked example
Consider an archive maintained for years by one volunteer using a laptop, two storage devices, and an organizational cloud service. The successor needs more than the equipment. They need to know which collection is current, how the catalog relates to files, where permission evidence is held, what is missing, and how backups are verified. Start the transfer with one representative collection and trace it through the whole system. This reveals whether the overview reflects actual practice or describes a process that changed informally over time.
Decisions and exceptions
Prepare a transfer checklist with explicit acceptance points. The successor confirms that they can locate the maintenance instructions, use authorized access, identify the most recent verified backup, and find unresolved issues. The outgoing custodian confirms that personal files and unrelated private accounts are not being mistaken for project resources. If ownership or access cannot be transferred through the normal process, record the gap and resolve it before relying on the successor's ability to maintain the collection. Never use a handover document as a convenient place to expose shared passwords.
Check and improve
Define an overlap period with a clear end. During it, the new custodian performs routine maintenance while the previous custodian answers questions and helps correct documentation. At the end, confirm who now makes ordinary decisions and how the backup custodian is reached. Update role lists and permissions appropriately. Keep a concise transfer record rather than preserving every conversational detail. After one maintenance cycle, ask the successor which tasks were unexpectedly difficult. Those answers can improve the archive's next handover and reduce the risk that each change of volunteer leadership becomes a loss of institutional memory.
Solo and community application
Alone, prepare a future-custodian note and arrange access with an appropriate trusted person through a secure plan. A community archive should have an authorized backup custodian and a clear decision process when roles change. A successor should explicitly accept responsibility rather than simply receiving a box or account invitation.
Reference guidance
Library of Congress guidance supports preservation documentation, and CISA emphasizes tested recovery access. This handover process combines those principles into a stewardship routine. Record the transfer date, confirm permissions were adjusted appropriately, and schedule a follow-up after the new custodian has completed one normal maintenance cycle.