Document Hold Litigation Policy
A Document Hold Litigation Policy template for identifying hold triggers, notifying custodians, preserving records, and releasing holds when the matter ends. Use it to reduce spoliation risk and create a repeatable legal hold process.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Healthcare · Retail · Manufacturing · Financial Services · Saas
Overview
This Document Hold Litigation Policy template sets out when a legal hold is triggered, who issues it, what records must be preserved, how custodians are notified, and when the hold can be released. It is designed for HR and compliance teams that need a repeatable process for protecting potentially relevant documents, emails, chat messages, payroll files, personnel records, investigation notes, and other electronically stored information.
Use this template when a dispute is reasonably anticipated, a charge or complaint has been filed, an internal investigation may lead to litigation, or counsel instructs the organization to preserve records. It is especially useful for employment matters involving discrimination, harassment, retaliation, wage-and-hour claims, leave disputes, accommodation requests, or whistleblower allegations. The policy gives you a clear chain of action so preservation is documented and defensible.
Do not use this policy as a substitute for ordinary records retention rules, and do not apply it blindly to every complaint. Routine coaching, low-risk employee questions, or ordinary operational issues usually do not require a hold unless facts suggest a likely claim. The template also helps you define jurisdiction-specific carve-outs, escalation steps, and release criteria so the hold does not stay in place longer than necessary.
Standards & compliance context
- This policy supports preservation obligations that arise in employment disputes under federal discovery practice and should be coordinated with counsel when litigation is reasonably anticipated.
- HR-related holds often intersect with Title VII, ADA, ADEA, FLSA, FMLA, and NLRA records, so the scope should match the claim type and the documents likely to matter.
- State law overlays may affect retention, privacy, whistleblower handling, and notice practices, including California, New York, Illinois, and Washington requirements.
- If the hold involves employee medical information or accommodation files, limit access to need-to-know personnel and preserve confidentiality consistent with ADA and privacy obligations.
- The policy should not conflict with ordinary records retention schedules, but it must override deletion when a hold is active.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Purpose
Explains why the policy exists and when preservation duties begin.
-
This policy establishes the process for identifying litigation hold triggers, issuing preservation notices, preserving potentially relevant records, and releasing a hold when appropriate. The policy is intended to support compliance with the duty to preserve evidence when litigation is reasonably anticipated and to help the organization meet recordkeeping obligations that may arise in employment matters, including EEOC charges and FLSA-related disputes.
Scope
Defines which workers, systems, and record types are covered by the hold process.
-
This policy applies to all employees, managers, supervisors, contractors, temporary workers, and third parties who create, receive, store, or control company records. It applies to paper records, email, chat messages, text messages, collaboration tools, cloud storage, HR files, payroll records, timekeeping records, audio/video files, device data, and any other information that may be relevant to a claim or investigation.
Policy Statement and Legal Basis
States the organization’s preservation rule and anchors it to the legal duty to avoid spoliation.
-
When litigation is reasonably anticipated, the organization will promptly preserve potentially relevant records and suspend ordinary destruction practices for the affected information. Relevant legal considerations may include the duty to preserve evidence under federal common law, EEOC charge handling, Title VII-related claims, ADA and FMLA disputes, and FLSA recordkeeping obligations under 29 U.S.C. § 211(c) and 29 C.F.R. Part 516. The organization will also take reasonable steps to prevent alteration, deletion, or loss of relevant information.
Definitions
Clarifies terms like litigation hold, custodian, relevant records, and release so the policy is applied consistently.
-
Key terms used in this policy are defined in the Definitions section of the template data. In addition, "good-faith" means an honest, timely, and documented effort to preserve information once a hold is triggered; "documented warning" means a written reminder that failure to comply may result in discipline; and "PIP" means a performance improvement plan, which is separate from a litigation hold but may be relevant if employee performance issues intersect with a dispute.
Procedure
Lays out the step-by-step process for triggering, issuing, tracking, updating, and releasing a hold.
-
1. **Identify triggers.** A litigation hold must be considered when the organization receives or becomes aware of a demand letter, EEOC charge, agency inquiry, subpoena, complaint, threatened lawsuit, internal complaint likely to escalate, preservation request, or other facts showing litigation is reasonably anticipated. 2. **Escalate promptly.** Managers and HR must notify Legal or the designated compliance lead immediately upon learning of a trigger. Do not wait for a formal lawsuit to be filed. 3. **Issue preservation notice.** Legal or Compliance will send a written preservation notice to relevant custodians, IT, and records personnel identifying the matter, the categories of records to preserve, the date preservation begins, and any special instructions. 4. **Preserve relevant records.** Recipients must stop deleting, overwriting, shredding, recycling, or otherwise disposing of potentially relevant records. IT must suspend auto-delete or retention policies for affected systems where feasible. 5. **Collect and secure records.** The organization may direct custodians to preserve files in place, copy data to a secure repository, or image devices as needed. Access should be limited to authorized personnel. 6. **Monitor compliance.** HR, Legal, IT, and Records Management will periodically confirm that the hold remains in effect and that preservation steps are working. 7. **Release the hold.** Legal will issue a written release when the matter is resolved and preservation is no longer required. Normal retention and deletion schedules may resume only after release.
Roles & Responsibilities
Assigns ownership across HR, Legal, IT, managers, and records management so nothing is missed.
-
**Employees and custodians:** Preserve records, follow preservation notices, and ask questions immediately if unsure whether information is covered. **Managers and supervisors:** Escalate potential claims or disputes promptly and do not direct employees to delete or conceal records. **HR:** Identify employment-related triggers, coordinate with Legal, and maintain documentation of notices and acknowledgements. **Legal / Compliance:** Determine when a hold is required, define the scope, issue and update notices, and release the hold when appropriate. **IT / Records Management:** Implement technical preservation steps, suspend auto-deletion where feasible, and support secure collection and retention. **Policy holder:** The policy holder is the HR Director or designated Compliance Officer, who is responsible for maintaining the policy and coordinating periodic review.
Compliance, Discipline, and Escalation
Explains what happens when someone fails to preserve records or ignores a hold notice.
-
Failure to comply with a litigation hold may result in corrective action up to and including termination of employment, subject to applicable law and any collective bargaining agreement. Noncompliance may also expose the organization and individuals to sanctions, adverse inferences, or other legal consequences. Any suspected loss, deletion, or alteration of preserved records must be reported immediately to Legal, HR, and IT so that a good-faith investigation can begin.
Exceptions and Jurisdiction-Specific Carve-Outs
Captures state-specific or matter-specific deviations that must be handled differently.
-
**California employees:** Preserve records in a manner consistent with California privacy and data-handling requirements, including the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA) where applicable, while still meeting legal preservation obligations. **New York employees:** If a matter involves whistleblower allegations, coordinate preservation with any obligations under New York Labor Law § 740. **State-specific recordkeeping rules:** Where state law requires longer retention or special handling of payroll, time, leave, or personnel records, the longer requirement controls. **Privacy and access limits:** Preservation does not mean open access. Access to preserved records must be limited to personnel with a business need to know.
Review and Revision
Sets the cadence for updating the policy and keeping it aligned with law, systems, and practice.
-
This policy will be reviewed at least annually and whenever there is a material change in law, litigation risk, recordkeeping systems, or organizational structure. Updates must be approved by Legal, HR, and the policy holder. A written release notice should be retained with the matter file after each hold is closed.
How to use this template
- 1. Fill in the policy holder, effective_date, version, review_frequency, applicable_jurisdictions, and applicable_roles before circulating the draft for legal review.
- 2. Define the exact trigger events that require a hold, including threatened claims, agency charges, preservation letters, and counsel instructions, and assign who may authorize issuance.
- 3. Map the record sources that must be preserved, such as email, chat, HRIS, payroll, ATS, shared drives, mobile devices, backups, and investigation files, then assign custodians and system owners.
- 4. Send the hold notice, require acknowledgment, suspend auto-deletion where needed, and document any exceptions or inaccessible sources in the case file.
- 5. Review the hold on a set cadence, update the custodian list and scope as facts change, and release the hold in writing once the matter is closed and legal approves.
Best practices
- Tie every hold to a specific matter number, complaint, or investigation so custodians know exactly what must be preserved.
- Preserve the content and metadata of relevant records, not just printed copies or exported PDFs.
- Suspend auto-delete rules for email, chat, and shared drives as soon as the hold is issued.
- Use role-based custodian lists that include managers, HR, IT, and any third-party administrator with relevant records.
- Track acknowledgments and follow-up reminders so you can show the notice was received and understood.
- Document good-faith efforts to preserve inaccessible sources, such as legacy systems or archived backups, and note any technical limits.
- Release the hold in writing and coordinate the release with IT and records management so normal retention can resume.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should a document hold be issued?
Issue a hold when litigation is reasonably anticipated, a claim is threatened, an agency charge is filed, or an internal investigation is likely to lead to a dispute. The policy should define who can trigger the hold and what facts justify it. Waiting until a complaint is formally served is often too late. The template helps you document the trigger and preserve relevant records immediately.
Who should receive a litigation hold notice?
The notice should go to likely custodians, managers with relevant files, HR, IT, and any business owner who controls potentially relevant records. Depending on the matter, it may also include contractors or third-party administrators who store company records. The template makes room for role-based assignment so the list is tied to the matter, not guesswork. That reduces missed sources and overbroad notices.
How often should a hold be reviewed?
Review the hold at least annually, and sooner when the case posture changes, new custodians are added, or the matter is resolved. A stale hold creates confusion, unnecessary retention, and missed release steps. The template includes review_frequency and revision fields so the policy stays current. It also supports periodic reminders and documented acknowledgments.
What laws does this policy need to account for?
The policy should align with preservation duties under federal litigation and discovery practice, and it should not conflict with employment laws that affect records handling. In HR matters, that often means considering FLSA, FMLA, Title VII, ADA, ADEA, EEOC charge handling, and NLRA-related records. State overlays can also matter, especially for privacy, whistleblower, and retention rules. The template is designed to be customized by jurisdiction and matter type.
What is the biggest mistake companies make with legal holds?
The most common mistake is sending a notice once and never tracking acknowledgment, follow-up, or release. Another frequent gap is failing to suspend auto-deletion for email, chat, shared drives, and backups that may contain relevant data. The policy template includes procedure, escalation, and discipline sections to close those gaps. It also prompts you to define what counts as preserved information.
Can this template be used for HR investigations as well as lawsuits?
Yes, if your organization treats certain investigations as potential litigation triggers. That includes harassment complaints, retaliation claims, wage-and-hour disputes, accommodation disputes, and whistleblower reports. The policy should distinguish routine HR investigations from matters that require a hold. The template helps you define that threshold clearly.
How do we release a hold without risking spoliation?
Release the hold only after the legal or HR owner confirms the matter is closed and no appeal, audit, or related claim is pending. The release should be documented, communicated to custodians, and coordinated with IT so normal retention schedules can resume. The template includes a release step so the end of the hold is as controlled as the start. That prevents indefinite retention and confusion over what still must be preserved.
How is this different from a general records retention policy?
A records retention policy tells you how long to keep ordinary business records. A litigation hold policy overrides normal deletion and retention rules when a dispute or anticipated dispute requires preservation. This template is built for that exception process, not for routine retention. It works best when paired with a separate records schedule.
Related templates
Ready to use this template?
Get started with MangoApps and use Document Hold Litigation Policy with your team — pricing built for small business.
