Who is responsible for issuing and tracking a legal hold across legal, IT, and records management?

A legal hold (sometimes called a litigation hold) is a directive to preserve potentially relevant information once litigation, an investigation, or an audit is reasonably anticipated. No single role owns the entire process. Issuing and tracking a hold is a shared responsibility across legal, IT, and records management, with each function carrying a distinct part of the work.

Where responsibility sits

Legal (the owner of the duty). The duty to preserve is a legal obligation, so counsel — in-house or outside — decides when the duty is triggered, defines the scope (custodians, date ranges, subject matter), and issues the written hold notice. Legal also makes the call on releasing the hold when the matter closes. Under the Federal Rules of Civil Procedure, failure to preserve can carry serious consequences, so legal generally retains accountability for the decision.

IT (the technical custodian). IT implements preservation in the systems where data lives: email, file shares, collaboration tools, backups, and structured databases. That can mean suspending auto-deletion, applying in-place holds, or capturing copies. IT also advises legal on where relevant data resides and what is technically feasible to preserve.

Records and information management (the lifecycle bridge). RIM connects the hold to retention schedules. A hold suspends normal disposition for affected records, and RIM ensures those records are not destroyed on their routine cycle. RIM expertise helps map data sources and identify custodians accurately.

Issuing and tracking in practice

Most organizations assign a hold coordinator — often within legal or a cross-functional e-discovery team — to manage the workflow end to end. Tracking typically includes:

• Documenting when and why the hold was triggered
• Distributing the written notice to custodians
• Collecting and recording acknowledgments
• Sending periodic reminders and updating scope as the matter evolves
• Recording the release once preservation is no longer required

A defensible process is documented and repeatable, demonstrating reasonable, good-faith steps. The Sedona Conference offers widely cited guidance on these practices; see The Sedona Conference publications.

Key takeaway

Legal owns the obligation and the decision, IT executes preservation in the systems, and records management aligns holds with retention. Clear ownership and consistent tracking are what make a hold defensible. Note that requirements vary by jurisdiction — state courts and other countries impose different standards. For related concepts, see /topics/ediscovery/.