Legal Hold Notice and Register

This is a ready-to-use legal hold notice, paired with a register that tracks every hold placed across the organization from issuance to release. A legal hold suspends the normal retention schedule for specific records because of actual or anticipated litigation, investigation, audit, or regulatory action; while it is in force, those records cannot be destroyed no matter what the routine schedule says. Decommissioning projects and routine retention cleanups are exactly where a hold gets missed, because both are actively looking for data to dispose of. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers, and route both the notice and the register through your normal document control. A worked filled specimen follows. Verify each cited regulation against the current source before you rely on it; the legal standard for what triggers a hold obligation is a legal determination, not a quality one, and this template supports that determination rather than making it.

Document control header

Part 1: Legal Hold Notice

Issue one notice per hold event. The notice is the instruction sent to every custodian (system owner, IT, records management, archivist) who controls records within scope. It is a short, unambiguous directive, not a summary of the underlying matter.

Field table (notice)

Notice instructions

1. Legal issues the notice as soon as litigation, investigation, audit, or regulatory action is reasonably anticipated, not only once it is filed or confirmed. Waiting for certainty is the most common way a hold is issued too late.
2. Scope the notice as precisely as the matter allows. An overbroad hold (“everything, indefinitely”) is nearly as damaging as a missed one: it silently grows the retained estate, adds cost, and trains custodians to treat holds as noise.
3. Send the notice to every custodian who could reasonably control in-scope records, including system owners of any automated retention or archival job that could otherwise sweep the data up.
4. Require acknowledgment from every custodian within a defined window (a common practice is 5 business days). An unacknowledged notice is a gap, not a formality; follow up until every custodian has confirmed.
5. Where a custodian’s system runs automated retention cleanup, confirm in the acknowledgment that the job has been suspended for the in-scope data or reconfigured to exclude it, not merely that the notice was read.
6. Log the notice in Part 2, the register, the same day it is issued.

The notice (template)

Part 2: Legal Hold Register

The register is the single place every disposition decision, and every decommissioning project, checks before destroying anything. It is the aggregate record of every hold ever placed, whether active or released.

Field table (register)

Register (blank)

How the register is used

1. Before any disposition decision, whether a routine retention cleanup or a decommissioning project’s destroy step, the responsible function queries this register for every record type and system in scope.
2. Any active hold covering the scope stops destruction for the covered portion; unheld record types in the same scope may proceed under their normal schedule.
3. When Legal releases a hold, the release is recorded here with the date and the person who released it, before any deferred destruction resumes.
4. On release, the record types formerly under hold are re-evaluated against the routine retention schedule; a lapsed clock during the hold period does not retroactively make the records eligible the instant the hold lifts unless the schedule itself is re-checked.
5. The register is reconciled on a defined cadence against open litigation, investigation, and regulatory matters tracked by Legal, to catch a hold that should have been issued but was not yet formalized.

Retention

Retain this register, and every notice it references, as a controlled record indefinitely, or per <<FILL: records retention policy reference>>. A released hold’s history is itself evidence of why a later destruction was lawful; do not purge released entries.

Acceptance criteria

The legal hold process is working when every notice was issued with a defined scope and a required acknowledgment, every custodian’s automated retention jobs were confirmed suspended or filtered for the in-scope data, the register reflects the true current status of every hold ever placed, no destruction (routine or decommissioning) proceeds without a register check, and every release is dated, attributed, and followed by an explicit re-evaluation against the retention schedule before disposition resumes.

References

Federal Rules of Civil Procedure, Rule 37(e) (failure to preserve electronically stored information; the basis in US civil litigation for the consequences of a missed hold). 21 CFR 211.180 and 211.194 (routine records retention, which a hold suspends rather than replaces). EU GMP Annex 11 and EU GMP Chapter 4 (electronic records and documentation retention). MHRA GxP Data Integrity Guidance and Definitions (March 2018).

Confirm the current version of each reference before issue, and confirm with Legal what jurisdiction-specific preservation obligations apply beyond the GxP retention framework; this template supports the operational mechanics of a hold, not the legal standard for when one must be issued.

Filled specimen

The following shows a notice and its register entry for an example hold placed during a product complaint investigation that later intersected with a planned system decommissioning. Company, system, and numbers are illustrative.

Notice (specimen)

Register entry (specimen)

The decommissioning project in this example had the affected archive segment scheduled for a destroy step; because the archive owner checked this register first, that segment was excluded and the rest of the archive’s dispositions proceeded unaffected. The hold’s release did not itself trigger destruction, because the underlying retention clock had not separately lapsed, which is exactly the check the post-release disposition column exists to force.

Common inspection findings this register prevents

• A decommissioning or routine cleanup destroyed records that were under an active hold nobody checked.
• A hold was issued verbally or by email with no formal notice, no defined scope, and no acknowledgment trail.
• An automated retention-cleanup job continued running against held data because the system owner was never asked to suspend or filter it.
• A hold’s release was undocumented, so years later nobody can show when or why the hold stopped applying.
• Records were destroyed immediately on a hold’s release without re-checking whether the routine retention clock had actually lapsed by then.
• No central register exists, so a decommissioning project has no single place to check before disposing of anything.

How to adapt this register

1. Set your document number, owner, and effective date in the header.
2. Confirm with Legal the acknowledgment window and escalation path for a custodian who does not respond.
3. Wire every decommissioning plan, destruction certificate, and routine retention cleanup procedure to require a register check as a hard gate, not a recommended step.
4. If your organization uses a legal matter management system, treat this register as the operational mirror focused on record-level scope and custodian acknowledgment, cross-referenced by matter number rather than duplicating privileged case detail.
5. Reconcile the register against open matters on a defined cadence, and confirm every “Released” row shows a documented post-release re-evaluation before assuming normal disposition resumed.