ISO Compliance Insights & Best Practices
CART
ISO Compliance Insights & Best Practices
A legal hold is an instruction that freezes the normal disposal of specific records because they may be needed as evidence in a dispute, an investigation or a regulator’s inquiry. The legal questions, such as whether a duty to preserve has arisen and how far it reaches, belong to legal counsel and depend on where you operate. This guide covers the other half: the records-management mechanics that make a hold actually work, from the trigger to the release.
Nothing here is legal advice; involve legal counsel in every hold decision.
ISO 15489-1:2016 is the anchor. Clause 9.9, on disposition, sets out principles for destroying records, and one of them is that records connected to litigation, legal action or an investigation should not be destroyed while the matter is in progress or is expected to arise. The standard is guidance rather than law, but that principle reflects a simple point: a retention period answers how long records are normally needed, and a live or foreseeable matter changes the answer.
So a legal hold sits above the records retention schedule. When a class’s period ends, disposition is still blocked for any record that a hold covers. When the hold is lifted, the schedule takes over again. The schedule itself does not change; only its application to the held records pauses.
The hold also reaches further than destruction. Records in scope should not be altered, moved out of their system, renamed or tidied up, because evidence is only useful if it can still be shown to be authentic and complete.
The difficult cases are matters that have not formally started. ISO 15489-1 frames the principle around matters underway or anticipated, so the hold should start when a matter is anticipated, not only when papers arrive; legal counsel decides when that point has been reached. Legal counsel makes that call; the records function makes sure the call can be made quickly.
| Trigger | Example | Who decides |
|---|---|---|
| Proceedings started | A claim is served on the organisation | Legal counsel, at once |
| Proceedings threatened | A letter alleging breach and threatening a claim | Legal counsel, at once |
| Matter reasonably expected | A serious complaint where the customer says they are taking advice; an accident causing injury; a whistleblowing report | Legal counsel, within a set number of days |
| Regulatory inquiry | A regulator’s information request or notice of inspection | Legal counsel |
| Internal investigation | Suspected fraud, misconduct or a data breach | Legal counsel with the investigation lead |
| Audit query | An external auditor questions specific transactions | Legal counsel, if a dispute may follow |
Two rules make triggers work in practice. Anyone who becomes aware of a possible trigger reports it to legal counsel straight away and leaves related records alone in the meantime. And when in doubt, hold: releasing an unnecessary hold costs little, while a missing one can be very costly.
Legal counsel decides whether a legal hold is needed and records the decision, including any decision not to hold. Scope is then set as precisely as possible: the matter, the subject matter of the records, the date range, the classes in the business classification scheme, the systems and locations, the custodians (people and system owners), any third parties holding records, and the formats, including chat, voicemail, mobile messages and paper. When unsure, draw the scope wider.
The records manager gives the hold a unique reference and enters it in a hold register on the day it is decided. The register is what every disposition batch is checked against, so a legal hold that is not registered does not exist as far as disposition is concerned.
This is the step that fails silently. Each system owner and provider is told what to preserve and confirms in writing when it is done. The next section covers what preservation involves.
Legal counsel issues a hold notice to each custodian, in plain language, marked confidential.
Custodians confirm in writing that they have read the notice, say where they hold relevant records, and name anyone else who may hold them. The records manager chases missing acknowledgements and escalates after a set period.
Custodians are reminded at intervals while the hold lasts. New custodians, people who move into a role in scope, and newly found records are added. Open holds are reported regularly to legal counsel and a senior officer.
Only legal counsel lifts a legal hold, in writing, once the matter and any follow-up period has ended. The release is covered below.
A legal hold notice to people does nothing about systems that delete on their own. Preservation means finding every automated process that could remove or change records in scope and stopping it for those records:
Preservation covers metadata as well as content. Audit trails, version histories and capture dates can be what proves a record has not been altered, so a migration or clean-up that strips them can damage the evidence even when the documents survive. Our guide to records management metadata explains which metadata carries that proof.
A good notice is short enough to be read and specific enough to be followed. It should include:
Release needs as much care as the legal hold itself. A written release notice goes to every custodian, system owner and provider who received the original instruction. Before removing a hold flag, the records manager checks whether the same records sit under another hold; if they do, they stay held until every hold covering them has ended.
Released records go back to their normal retention class. Records whose period ended during the hold are not destroyed automatically on release. They join the next disposition batch and go through the full pre-disposition review, since clause 9.9 also asks for disposition to be checked before it happens in case requirements have changed. The release notice should say this plainly, so nobody reads “hold released” as “delete now”.
Two routine activities are where holds are most easily broken.
Destruction batches. Every batch is checked against the hold register before it is authorised, and legal counsel confirms that no other matter is underway or expected for the records listed. Held records are removed from the batch and the removal is recorded. If a hold arrives while a batch is being prepared, the records in scope come out before authorisation, not after.
System migrations and decommissioning. Clause 9.8 expects source records and metadata to be kept until the destination has been checked, and any disposal of the source to be authorised. A legal hold adds a further condition: the migration plan should list open holds, carry hold flags across to the new system, and keep held records in the old system until preservation in the new one is confirmed. Decommissioning a system that holds records under a legal hold should wait for legal counsel’s agreement.
A records management policy should name both checks, so they happen by design rather than by memory; our guide to the ISO 15489 standard shows where disposition and migration sit in its structure. For an example of how a national archive frames records management for public bodies, see the US National Archives’ federal records management pages.
Legal counsel. The records function supplies the scope information, applies the hold in systems and keeps the register, but the judgement on whether a matter is foreseeable is a legal one.
No. It suspends disposition only for records in its scope. Everything else continues on the schedule as normal.
Not if they fall within scope. Duplicates and drafts can matter as evidence, so custodians should ask legal counsel rather than decide for themselves.
On release they enter the next disposition batch and are reviewed before any action. Release never triggers immediate destruction.
Our ISO 15489 Toolkit provides 92 editable templates aligned with ISO 15489-1. For holds it includes the Legal Hold Procedure and Notice, with ready-to-use hold and release notice forms, the Disposition and Destruction Procedure, which checks every batch against the hold register, the Disposition Register, the Migration and Conversion Plan, the Migration Validation and Source Disposal Authorisation, the Email and Electronic Messaging Records Policy and the Business Change and System Decommissioning Policy. It is $99.
October 12, 2026
October 12, 2026
October 12, 2026
October 12, 2026
October 12, 2026