Does Your Legal Hold Match Your Trigger Date?

Missing evidence can sink a case. In spoliation disputes, the critical question is not just whether evidence disappeared, but when it disappeared relative to when your duty to preserve began. Get that timeline wrong, and you risk facing undeserved sanctions or failing to prove spoliation when necessary.

This checklist guides you through documenting your trigger date, implementing holds that align with it, and defending your timeline if challenged. It's based on the framework courts use when evaluating spoliation claims involving physical records.

Prerequisites

Before using this checklist, ensure:

• You've identified the custodians and record types relevant to the dispute.
• You have access to communications logs, privilege logs, and case chronology documents.
• You understand whether the records at issue are electronically stored information (governed by Fed.R.Civ.P. 37(e)) or physical evidence (governed by the court's inherent authority).
• You know which party bears the burden of proof (typically the movant seeking sanctions must provide "clear and convincing evidence").

Trigger Date Determination Checklist

1. Document the date litigation was filed or the party joined the case

Action: Record the exact date your organization filed suit, was named as a defendant, or joined as a plaintiff.

Reference: For plaintiffs, the duty to preserve arises when you decide to pursue a claim. For defendants, it arises when you're notified of potential litigation.

Good looks like: A case management file showing "Complaint filed August 5, 2022" or "Joined as plaintiff February 6, 2024" with contemporaneous documentation of internal notification to stakeholders.

2. Identify any earlier date when litigation was reasonably anticipated

Action: Search for evidence that your organization anticipated litigation before the filing date. Review:

• Privilege logs for attorney-client communications labeled "litigation advice" or similar.
• Internal emails mentioning potential lawsuits or disputes with the opposing party.
• Complaint allegations stating when you "first suspected" the conduct at issue.
• Correspondence threatening legal action or demanding preservation.

Reference: Mere suspicion of facts giving rise to a dispute shows only the "possibility of litigation," not reasonable anticipation. You must show an affirmative decision to sue or a direct threat of litigation.

Good looks like: Either clear evidence of an earlier trigger (e.g., a demand letter sent to the opposing party in April with explicit preservation language) or documented proof that no such anticipation existed (e.g., privilege log entries showing discussions were about licensing, not litigation).

3. Distinguish between topics in attorney-client communications

Action: If your privilege log shows communications with counsel before the filing date, identify the subject matter. Were they about:

• Litigation strategy against this defendant?
• General IP advice or licensing negotiations?
• Unrelated disputes?

Reference: Ambiguous log entries covering "litigation, IP advice, and licensing advice" don't establish a clear trigger date. Courts require specificity.

Good looks like: Log entries that either clearly state "litigation strategy re: Defendant X trade secret claim" or clearly distinguish non-litigation topics. If ambiguous, prepare a declaration explaining the actual subject matter without waiving privilege.

4. Document when non-party custodians were notified of the duty to preserve

Action: If a third party (like a university or vendor) holds relevant evidence, record when you notified them of the lawsuit and requested preservation.

Reference: In Terran Biosciences, the plaintiff filed suit on August 5, 2022, and notified the university custodian on August 8. The court found the university's duty arose "at the latest" on August 8.

Good looks like: A dated email or letter to the custodian stating "We filed suit on [date]. Please preserve all records related to [subject]." Follow up with confirmation of receipt.

5. Issue your litigation hold within days of the trigger date

Action: Implement your Records Freeze (litigation hold) as soon as the duty to preserve arises. In Terran Biosciences, the university issued its hold on August 16, 2022, eight days after notification.

Reference: While an eight-day lag didn't defeat the spoliation claim in this case, faster is always better. Delays create ambiguity about when evidence was lost.

Good looks like: A documented hold issued within 1-3 business days of the trigger, with proof of delivery to all custodians and a tracking system for acknowledgments.

6. Preserve the litigation hold documentation itself

Action: Retain copies of:

• The hold notice sent to custodians.
• The list of recipients and their positions.
• Acknowledgment receipts or read confirmations.
• Any follow-up reminders or clarifications.

Reference: In discovery disputes, you may need to produce "internal litigation hold correspondence and the positions of individuals who received the litigation hold."

Good looks like: A dedicated case file containing all hold-related documents, indexed by date and custodian, with metadata showing when each message was sent and opened.

7. Document any gaps in the timeline between trigger and loss

Action: If evidence goes missing, establish as precisely as possible when it was last seen and when it was discovered missing. In Terran Biosciences, the court noted: "The only conclusions that the Court can draw from the evidence presented are: (1) the lab notebooks went missing sometime after June 2022, when Dr. Thompson last saw them; (2) the lab notebooks were declared lost on October 1, 2025."

Reference: If you can't prove the evidence was lost after the duty to preserve arose, you can't prove spoliation.

Good looks like: Witness declarations stating "I last accessed the file on [date]" and "I discovered it missing on [date]," supported by access logs, move records, or other contemporaneous documentation.

Common Mistakes

Assuming reasonable anticipation too early. Allegations in your complaint that you "first suspected" wrongdoing in April don't prove you anticipated litigation in April. Suspicion isn't anticipation.

Relying on ambiguous privilege log entries. If your log lists "litigation, IP advice, and licensing" as topics, courts won't assume litigation was the primary focus. Be specific or be prepared to explain.

Failing to distinguish between parties. Your organization's knowledge isn't automatically imputed to a third-party custodian. Document when you notified them.

Confusing the trigger date with the loss date. Even if your duty to preserve arose on August 5, evidence lost on July 15 isn't spoliation. Timing is everything.

Treating all records the same. Fed.R.Civ.P. 37(e) governs electronically stored information. Physical evidence (like lab notebooks) falls under the court's inherent authority, with different standards.

Next Steps

After completing this checklist:

• Store all trigger-date documentation in a secure, litigation-ready repository.
• Train your legal operations team to recognize reasonable anticipation triggers before litigation is filed.
• Review your Records Freeze protocol to ensure holds issue within 24-48 hours of a trigger event.
• If you're moving for sanctions, prepare to meet the "clear and convincing evidence" standard for both trigger and loss dates.
• If you're defending against a sanctions motion, gather evidence showing either (a) the duty hadn't yet arisen when the loss occurred, or (b) the loss timing is too ambiguous to support sanctions.

The court in Terran Biosciences found the duty to preserve arose "at the earliest on August 5, 2022." That precision saved the plaintiffs from sanctions. Your timeline documentation should be equally precise.