How do you transition records management responsibilities when the records officer leaves or retires?

A records officer often holds critical knowledge that exists nowhere else: where records live, which schedules apply, who the data stewards are, and which obligations are pending. When that person leaves, the goal is to transfer both the formal responsibilities and the undocumented institutional knowledge without creating gaps in compliance or accountability.

Plan the transition before it is urgent

The strongest defense against a disruptive departure is not reacting to one. Build continuity into the program itself:

• Document the program. Keep an up-to-date records management policy, file plan, and retention schedules so the program does not depend on one person’s memory.
• Maintain a duties inventory. List recurring obligations, deadlines, system access, and key contacts in a place others can find.
• Cross-train a backup. Designate and train at least one alternate who understands the essentials.

These practices reflect a core principle in standards such as ISO 15489: records processes should be systematic, documented, and repeatable rather than personality-dependent.

Conduct a structured handover

When a departure is known, treat the handover as a defined project:

1. Identify the successor or interim owner and formally assign authority and access.
2. Hold knowledge-transfer sessions covering systems, schedules, vital records, legal holds, audits, and any open requests (FOIA, Privacy Act, litigation, e-discovery).
3. Transfer custody of accounts and credentials through proper channels, never informally.
4. Document open items with status and next steps so nothing stalls mid-process.

Pay special attention to active legal holds and pending disposition. A hold that the departing officer was tracking informally can be lost in transition, creating real legal exposure.

Preserve the departing officer’s own records

The records officer creates records too: program documentation, decision logs, and correspondence. These should be retained according to schedule, not deleted or taken when the person leaves. Confirm that any work email, files, and shared drives are reviewed and preserved per your retention rules.

Close the loop

After the handover, update the program documentation to reflect the new owner, revoke the former officer’s access, and verify that external parties know the new point of contact. A brief post-transition review confirms that no obligations slipped.

Done well, a transition becomes a routine event rather than a crisis. For more foundational guidance, see the fundamentals topic hub.