Litigation Support, Legal Hold, and Canned Responses
When Disputes Become Real
In Lesson 5, you triaged NDAs into Tier 1/2/3. A Tier 3 NDA — one with RED flags like residuals clauses or asymmetric injunctive relief — sometimes surfaces issues that escalate to litigation. This lesson covers what happens when a dispute becomes real, and how the /respond command handles both litigation holds and the seven categories of routine legal correspondence that consume most legal ops time.
Every legal function hopes to avoid litigation. Most cannot. When a dispute escalates from commercial negotiation to formal proceedings — or when proceedings become reasonably foreseeable — the organisation's obligations change fundamentally. Document preservation obligations attach. Communication protocols tighten. The stakes shift from commercial compromise to legal exposure that can dwarf the original contract value.
Litigation support is the set of processes by which a legal department prepares for, manages, and responds to disputes. The Legal Plugin's /respond command, combined with the /brief command for legal research, provides structured workflow support for the two most operationally demanding phases of dispute preparation: legal hold management and document discovery support.
A legal hold (also called a litigation hold or preservation notice) is a directive issued by an organisation's legal department requiring the preservation of all documents, electronically stored information (ESI), and other materials that may be relevant to a pending or reasonably anticipated legal dispute. Once a legal hold is triggered, the organisation must suspend routine document destruction policies (including automated deletion schedules) for all materials within the hold's scope. Failure to preserve relevant materials can result in sanctions, adverse inference instructions (where the court assumes the destroyed evidence was unfavourable), and in severe cases, default judgment. Legal holds are triggered when litigation is "reasonably anticipated" -- not when a lawsuit is actually filed. A demand letter, a regulatory investigation notice, or a significant customer complaint may all trigger the obligation.
How /respond Handles Legal Hold Notices
The /respond command includes a litigation hold workflow that automates the administrative burden of issuing, tracking, and enforcing preservation notices across the organisation. The workflow does not make any decisions about litigation strategy -- that is exclusively attorney work. It manages the operational mechanics: identifying custodians, issuing notices, tracking acknowledgements, sending reminders, and escalating non-compliance.
/respond type:"litigation-hold"
matter:"[matter name or reference]"
scope:"[description of relevant topics, date ranges, custodians]"
trigger:"[event that triggered the hold -- demand letter, complaint, etc.]"
instructing-attorney:"[name of lead attorney]"
The agent produces:
- Hold notice -- a formal preservation notice for custodian distribution, identifying the matter, the scope of materials to preserve, the categories of ESI covered (email, documents, chat messages, database records, backup tapes), and the custodian's obligations. Drafted for attorney review and approval before distribution.
- Custodian list -- identified from the matter scope, cross-referenced against the organisation's directory. The agent flags custodians who have left the organisation (requiring IT coordination to preserve their data) and custodians in jurisdictions with specific preservation requirements.
- Acknowledgement tracker -- a tracking log for custodian acknowledgements, with escalation triggers: 3 business days (reminder), 5 business days (manager notification), 7 business days (General Counsel notification).
- Suspension notice to IT -- a request to suspend automated deletion policies for email, document management systems, and backup rotation schedules within the hold scope.
Governance Rule: Litigation Strategy Is ALWAYS Attorney-Only
This governance rule is absolute and non-negotiable.
The agent may draft hold notices, track custodian acknowledgements, compile document indices, and prepare chronologies. The agent must never:
- Assess the merits of a claim or defence
- Recommend settlement positions or ranges
- Draft substantive legal arguments or pleadings
- Advise on privilege assertions or waivers
- Communicate with opposing counsel or the court
- Make any determination about which documents are responsive to a discovery request
These are attorney functions protected by legal professional privilege and governed by rules of professional conduct. The agent's role in litigation support is purely operational -- the administrative and logistical infrastructure that enables the legal team to focus on strategy rather than coordination.
Worked Example: Triggering a Litigation Hold at DataFlow Systems
Scenario: DataFlow Systems Ltd, a 200-person SaaS company headquartered in London, receives a demand letter from CloudMesh Technologies Inc. (a Delaware-incorporated competitor) alleging that DataFlow's new "AutoPipeline" feature infringes CloudMesh's US Patent No. 11,432,876 relating to automated data pipeline configuration. The demand letter requests cessation of the allegedly infringing feature and damages of USD 2.4 million. DataFlow's General Counsel, Priya Sharma, determines that litigation is reasonably anticipated and instructs the legal operations team to initiate a legal hold.
/respond type:"litigation-hold"
matter:"CloudMesh v DataFlow -- Patent Infringement Claim"
scope:"All documents, emails, Slack messages, code commits, design
documents, product specifications, and meeting notes relating
to the AutoPipeline feature, including all prior art research,
development history, and competitor analysis. Date range:
January 2024 to present. Include all backup and archive
copies."
trigger:"Demand letter from CloudMesh Technologies Inc. received
14 March 2026, alleging infringement of US Patent
No. 11,432,876."
instructing-attorney:"Priya Sharma, General Counsel"
What to expect: The agent produces a complete litigation hold package. Your output will vary, but look for these sections:
| Section | Intent | What to Verify |
|---|---|---|
| Hold initiation header | Matter reference, trigger event, instructing attorney, DRAFT status | Confirm the hold is marked DRAFT pending attorney approval — the agent never distributes without attorney sign-off |
| Preservation notice | Formal notice for custodian distribution with scope, date range, and obligations | Check that the scope matches what you provided and includes an explicit "if in doubt, PRESERVE IT" instruction |
| Recommended custodians | Departments and individuals who should receive the notice | Should identify all departments with potential access to in-scope materials, including departed employees whose data needs preservation |
| IT suspension request | Request to suspend automated deletion policies within hold scope | Should cover email, chat, code repositories, document storage, and backup rotation |
| Acknowledgement tracker | Escalation schedule for non-responding custodians | Should include a 3-day reminder, 5-day manager escalation, and 7-day General Counsel escalation |
| Governance footer | Dual boundary: attorney review required AND litigation strategy is exclusively attorney work | Confirm both governance statements are present |
The specific custodian departments, IT systems, and escalation timelines depend on the matter scope and your organisation's structure. Focus on the four outputs (notice, custodians, IT suspension, tracker) and the governance boundary. The teaching point is that the agent handles the operational infrastructure while the attorney retains all strategic decisions.
The agent produces the operational infrastructure -- the notice, the custodian list, the IT suspension request, and the tracking mechanism -- in minutes rather than the hours this typically requires. Priya Sharma reviews the package, adjusts the custodian list based on her knowledge of who was involved in the feature's development, approves the notice language, and instructs distribution. The strategic decisions -- whether to engage US patent litigation counsel, whether to conduct a freedom-to-operate analysis, whether to respond to the demand letter or wait -- remain exclusively hers.
The agent reviews, triages, drafts, and flags. The licensed attorney advises, decides, and signs.
When PayGulf Technologies receives a legal claim, Fatima Al-Rashidi's litigation hold workflow includes steps that DataFlow's Priya Sharma does not face. A DFSA-regulated entity operates under notification obligations that attach the moment material litigation becomes reasonably foreseeable — not just preservation obligations, but regulatory reporting obligations.
The DFSA requires regulated firms to notify the regulator of any material litigation or regulatory action that could affect the firm's ability to meet its regulatory obligations or that could cause significant reputational harm. The threshold for "material" is a judgment call that Fatima must make — and it is a judgment the agent cannot make for her. The agent flags the question: "This matter may trigger DFSA notification requirements under GEN Rule 11.10. Attorney assessment required." Fatima then evaluates whether the claim's value, nature, or potential reputational impact crosses the materiality threshold.
The preservation scope also expands for a regulated payment processor. A standard litigation hold preserves documents, emails, and code related to the disputed matter. PayGulf's hold must also encompass regulatory compliance records — DFSA filings, AML transaction monitoring logs, sanctions screening records, and payment system audit trails — that a non-regulated company would not maintain or need to preserve. If the claim involves payment processing failures, PCI DSS compliance documentation and card scheme incident reports become part of the hold scope. These are records that standard commercial preservation templates do not cover.
If the claim involves cross-border payment data, a further complication arises: PCI DSS data retention rules may conflict with the litigation hold. PCI DSS requires that cardholder data not be stored beyond business necessity, while the litigation hold requires preservation of all potentially relevant materials. Fatima must determine how to satisfy both requirements simultaneously — typically by isolating payment data under restricted access controls that satisfy PCI DSS while preserving it for litigation purposes. The agent identifies the conflict; Fatima designs the resolution.
Canned Responses and /respond
Beyond litigation holds, the /respond command handles seven categories of routine legal correspondence. Each category has a structured template, jurisdiction-appropriate language, and built-in escalation triggers that stop the templated response when human judgment is required.
The Seven Response Categories
| Category | Command | Typical Use |
|---|---|---|
| Discovery hold | /respond type:"discovery-hold" | Preservation notices to custodians |
| Privacy inquiry | /respond type:"privacy-inquiry" | Routine privacy questions from employees/customers |
| DSAR response | /respond type:"dsar" | Data subject access request acknowledgement |
| Vendor question | /respond type:"vendor-question" | Contract term clarifications, renewal queries |
| NDA request | /respond type:"nda-request" | Standard NDA routing for incoming requests |
| Subpoena/legal process | /respond type:"legal-process" | Acknowledgement and routing of legal process |
| Insurance notification | /respond type:"insurance-notification" | Incident notification to carriers |
Universal Escalation Triggers
The agent stops the templated response and routes to an attorney when any of these conditions are detected:
- Potential litigation — the inquiry suggests the sender is considering legal action
- Regulator inquiry — the communication comes from a regulatory body
- Binding commitments — the response would create contractual obligations
- Criminal liability — the situation involves potential criminal exposure
- Media attention — the matter involves or may attract press coverage
- Unprecedented situation — no template exists for this type of inquiry
Before running /respond type:"discovery-hold" for the DataFlow scenario, predict: what sections will the template include? What will it refuse to include — and why? The governance boundary means the agent will produce the operational infrastructure but will not touch litigation strategy.
Flashcards Study Aid
Try With AI
Setup: Use these prompts in Cowork or your preferred AI assistant.
Prompt 1: Reproduce
I am General Counsel at a 200-person fintech company. This
morning I received the following notice:
"The Financial Conduct Authority hereby notifies your firm
that it has commenced an investigation into potential breaches
of the Consumer Duty rules (FCA PS22/9) in relation to your
automated lending product 'QuickLend'. The investigation
covers the period from 1 January 2025 to present. You are
required to preserve all documents and communications relating
to the design, testing, deployment, marketing, and customer
outcomes of the QuickLend product."
47 employees across Product, Engineering, Marketing, Compliance,
and Customer Support may have relevant documents. Our data is
spread across Gmail, Slack (channels: #quicklend, #lending-ops,
#compliance-reviews), GitHub (quicklend-* repositories),
Confluence (Product and Compliance spaces), and Salesforce
(customer complaint records).
Run the litigation hold workflow using /respond and verify:
1. Are the custodian notifications correctly scoped to the
FCA's investigation period (1 January 2025 to present)?
2. Does the preservation scope cover ALL the ESI categories
the FCA notice requires — including Salesforce customer
complaint data, which is easy to overlook?
3. Does the IT suspension request address automated deletion
policies for each system (Gmail retention, Slack message
retention, GitHub branch cleanup)?
4. Does the custodian acknowledgement escalation timeline
account for the regulatory urgency (FCA investigations
typically expect immediate preservation)?
What you are checking: The FCA investigation scenario is more
complex than a standard demand letter — the scope is defined
by the regulator, not by you. Verify that the agent's output
matches the investigation scope exactly, rather than defaulting
to a generic preservation template.
What you are learning: A regulatory investigation imposes externally defined preservation obligations -- you do not get to choose the scope the way you might with a commercial dispute. Running the workflow against a specific FCA notice tests whether you can verify the agent's output against a defined regulatory requirement, which is a fundamentally different skill from designing a policy from scratch.
Prompt 2: Adapt
A 200-person technology company received a patent infringement
demand letter 6 months ago but never issued a formal litigation
hold. The company's routine data retention policy automatically
deleted emails older than 90 days and rotated backup tapes
monthly. The plaintiff has now filed a lawsuit and requested
discovery of all documents relating to the allegedly infringing
feature.
Explain:
1. What is "spoliation of evidence" and has it occurred here?
2. What is an "adverse inference instruction" and could the
court impose one?
3. What are the possible sanctions (monetary, evidentiary,
case-dispositive)?
4. How would the outcome differ if the company had used
/respond to issue a litigation hold on the day the demand
letter arrived?
5. Draft a remediation plan: what should the company do NOW
to mitigate the damage?
Reference actual case law if possible (e.g., Zubulake v. UBS
Warburg, Pension Committee v. Banc of America Securities).
What you are learning: Understanding the consequences of failing to preserve evidence makes the litigation hold workflow concrete rather than abstract. The sanctions regime -- monetary penalties, adverse inference instructions, even default judgment -- demonstrates why the operational infrastructure the agent provides (notices, tracking, IT suspension) is not administrative overhead but litigation risk management.
Prompt 3: Apply
In a patent infringement dispute, classify each of the
following tasks as either OPERATIONAL (the agent can handle)
or STRATEGIC (attorney-only). For each, explain your reasoning:
1. Drafting the preservation notice for custodians
2. Deciding whether to engage outside patent litigation counsel
3. Tracking which custodians have acknowledged the hold notice
4. Assessing whether the patent claims actually cover our product
5. Compiling a chronological index of all code commits to the
disputed feature
6. Recommending a settlement range
7. Sending a reminder to a custodian who hasn't acknowledged
8. Determining which documents are privileged
9. Drafting an IT suspension request for backup rotation
10. Deciding whether to file a declaratory judgment action
For the operational items, describe what the agent's output
would look like. For the strategic items, explain what
professional conduct rule or legal principle makes them
attorney-only.
What you are learning: The operational/strategic distinction is the most important governance concept in litigation support. Items 1, 3, 5, 7, and 9 are operational -- the agent produces the infrastructure. Items 2, 4, 6, 8, and 10 are strategic -- they require legal judgment, create privilege, or involve court-facing decisions. Correctly classifying these tasks is the skill that makes litigation AI safe and effective.
What You Built
- A litigation hold package with hold notice, custodian list, acknowledgement tracker, and IT suspension request
- Seven canned response categories configured for /respond (DSRs, discovery holds, privacy inquiries, vendor questions, NDA requests, subpoena/legal process, insurance notifications)
- Universal escalation triggers identifying when to stop templated response and involve an attorney
- The operational vs. strategic governance distinction for litigation support tasks
- Understanding of ESI preservation obligations and the duty to preserve electronically stored information
Continue to Lesson 9: Meeting Prep and Vendor Management ->