Legal hold process flowchart: scope, notice, preserve and release
Legal hold process template for recording the trigger, counsel authorisation, custodian and source scoping, notice acknowledgements, preservation exceptions, reviews and release.
What the legal hold process flowchart: scope, notice, preserve and release process is
A legal hold is operationally difficult because the relevant information is distributed across people, devices, mailboxes, collaboration spaces, business applications and routine disposal schedules. This chart begins when a potential dispute or investigation is reported, records counsel's hold decision, develops a custodian and source map, tracks acknowledgements and preservation actions, and keeps the hold under review until counsel releases it.
The template is a customizable coordination workflow, not legal advice and not a statement of when a duty to preserve arises. That question depends on the facts, applicable law and counsel's judgement. The chart deliberately makes counsel the source of scope and release instructions while legal operations, custodians, IT and records teams carry them out. Tailor the trigger channel, escalation timing, source inventory, technical actions, review cadence and release controls to your environment.
What this flowchart covers
In this template
- Five role lanes from the matter owner and legal team to custodians and IT or records administrators, across trigger, scope, notice, preservation and release
- A counsel-authorisation gate with routes for more facts or a recorded no-hold decision, without embedding a universal legal test in the diagram
- Iterative scoping of issues, dates, custodians and systems, followed by notice delivery, acknowledgement chasing and technical preservation actions
- Exception handling and periodic review loops, ending only when counsel releases the hold and approved information-management schedules are restored
When to use this template
- Hold instructions are issued through email and nobody has one view of custodians, systems, acknowledgements and exceptions
- The legal team depends on IT to suspend disposal but the requested scope is not expressed in implementable system terms
- Long-running matters retain stale custodian lists because role changes and new data sources are not reviewed
- You are documenting the handoff between counsel, legal operations, records management and technical administrators before choosing tooling
How it works
Name the authorised trigger route
Specify who receives potential disputes or investigations, how counsel is alerted and where the original trigger is stored. Counsel should define the decision criteria and escalation expectations for the matters your organisation handles.
Build a usable source inventory
Replace generic systems with the mail, messaging, file, device, backup and business-application sources you actually operate. Name both the business owner who understands the content and the administrator who can implement preservation.
Design notice and acknowledgement tracking
Use counsel-approved notice text, define the acknowledgement mechanism, and set reminder and escalation ownership. Include joiners, leavers and role changes in the refresh rule rather than treating the first recipient list as permanent.
Record technical actions and exceptions
For each scoped source, capture the requested action, administrator, completion date, confirmation and any limitation. Route unresolved limitations back to counsel so a technical gap is assessed rather than hidden in a status note.
Set review and release controls
Choose a cadence plus matter events that trigger an early review. Require counsel to approve scope changes and release, then have IT and records confirm that only the appropriate schedules are restored under your information-governance policy.
Frequently asked questions
What are the steps in a legal hold process?
A practical process records the potential matter and known facts; obtains counsel's instruction; defines issues, dates, custodians and data sources; issues notices; tracks acknowledgement; implements preservation actions; records and escalates exceptions; reviews scope and continued need on a cadence and when the matter changes; and documents counsel's release before approved disposal schedules resume.
Who should own a legal hold?
Ownership is usually shared by function. Counsel decides the legal scope and whether the hold continues. Legal operations coordinates the register, notices and confirmations. Custodians follow instructions and identify sources, while IT and records staff implement system actions. Assign named roles in your organisation and preserve the distinction between instruction and execution.
How often should a hold be reviewed?
There is no universal interval in this template. Set a cadence based on matter duration and risk, and add event triggers such as amended claims, new parties, staff departures, system migrations or closure of the matter. Counsel should confirm whether scope or continued preservation changes at each review.
Does this flowchart determine when preservation is legally required?
No. It begins with facts being reported and routes the decision to counsel. The applicable trigger, scope and duration depend on the matter and jurisdiction, so use qualified legal advice. The diagram helps a team execute and evidence the instruction once it is given.