Discovery Litigation: How to Prioritize Requests That Matter
.png)
Discovery can win (or lose) a case long before trial. In discovery litigation, the teams that move fastest are not the ones who request “everything,” they are the ones who request the right things, early, and in a form that can be used in motions, mediation, and depositions.
Below is a practical way to prioritize discovery requests so you spend your limited bandwidth on what actually changes leverage and outcomes.
Start with the end in mind: your case theory in one page
Prioritization is impossible until the team agrees on what “matters.” A simple rule: every discovery request should map to at least one of these goals:
- Prove an element you must win.
- Defeat an element the other side must win.
- Establish damages with admissible support.
- Increase settlement pressure (credibility, risk, or valuation).
- Lock in testimony for impeachment.
If a request does not clearly serve one of these, it belongs in “later” or “never.”
Use proportionality as your filter (and your shield)
In federal court, proportionality is not a vibe, it is black-letter rule. FRCP 26(b)(1) ties discoverability to relevance and proportionality, including the amount in controversy, access to information, and burden versus benefit. When you prioritize around proportionality, you also draft requests you can defend (or attack) in a discovery conference.
If you want a clean citation point for internal guidance, start with the text of Rule 26(b)(1).
Build a “proof map” before you draft a single request
A proof map is a small table that links claims and defenses to the best sources of evidence. It keeps the team from over-requesting and helps you sequence discovery.
| What you must prove (or defeat) | Best evidence sources | First request types to prioritize | Why it matters early |
|---|---|---|---|
| Liability facts and timeline | Emails, incident reports, policies, photos/video, key witness statements | Targeted RFPs + interrogatories + preservation letter | Establishes the narrative and identifies who to depose |
| Causation disputes | Medical records, prior injury records, expert-relevant data, alternative cause docs | Authorizations/subpoenas + targeted RFPs | Determines whether you need experts and what they must address |
| Damages and valuation | Billing, wage loss docs, mitigation evidence, comparable contract/value records | RFPs + third-party subpoenas | Sets demand/offer range and settlement posture |
| Credibility and impeachment | Prior inconsistent statements, training records, disciplinary files (where permitted), metadata | Narrow RFPs + deposition exhibits planning | Creates leverage and reduces surprise |
| Insurance/indemnity/coverage | Policies, reservation of rights, indemnity contracts | Early RFPs or disclosures | Affects who pays and settlement ceilings |
A simple scoring model: value, urgency, and friction
For each proposed request set, give it a quick score from 1 to 5 in three buckets:
- Outcome impact: Will this evidence change liability, damages, or leverage?
- Time sensitivity: Will it disappear, be overwritten, or affect deadlines (experts, mediation, dispositive motions)?
- Collection friction: How hard will it be to obtain, review, and use (ESI burden, privilege, third parties)?
Then prioritize high impact + high urgency, even if friction is moderate.
| Priority tier | Typical score pattern | What you do next |
|---|---|---|
| Tier 1 (now) | High impact, high urgency | Draft narrowly, serve early, and prepare to enforce |
| Tier 2 (soon) | High impact, lower urgency or higher friction | Sequence after initial responses and meet-and-confer |
| Tier 3 (later) | Lower impact or duplicative | Hold unless the case pivots |
What usually belongs in Tier 1 in discovery litigation
While every case is different, Tier 1 requests often share one trait: they clarify the story and preserve proof.
1) The smallest set of documents that proves the timeline
Prioritize the documents that pin down “who knew what, when”:
- Core communications (date-bounded emails/texts/chats) among key custodians
- Incident reports, internal tickets, QA logs, or complaint files
- Policies and procedures that define the standard of care or contractual obligations
- Photos/video and any chain-of-custody or retention documentation
Drafting tip: name custodians and date ranges. Overbreadth invites delay, objections, and expensive review battles.
2) The identity of the right people (and what they touched)
Before you schedule depositions, you need to know who owns the facts. Use early interrogatories or Rule 30(b)(6) topics (where applicable) to surface:
- Individuals involved in the event, decisions, approvals, or post-incident handling
- Systems used (CRM, EMR, Slack/Teams, ticketing, payroll, timekeeping)
- Where data lives and how long it is retained
This is how you avoid taking a deposition, then learning there was a better witness all along.
3) Damages proof that will survive scrutiny
A demand or mediation brief is only as strong as the documents behind it. Prioritize requests that allow clean exhibits:
- Itemized medical billing and treatment chronology
- Wage loss documentation and employment records
- Mitigation evidence (appointments, restrictions, job search, accommodation process)
If you are defense-side, prioritize requests that test causation and apportionment (prior conditions, alternative causes, gaps in treatment) within the bounds of privacy and court rules.
Sequence discovery to reduce motion practice
You do not have to serve everything at once. Sequencing often produces faster, cleaner results.
Phase 1: Clarify and preserve
Focus on the timeline, key custodians, and the smallest set of high-value ESI and documents.
Phase 2: Expand based on what you learn
After initial responses, add second-wave requests that target contradictions, missing custodians, and newly identified systems.
Phase 3: Lock it in for deposition and motions
Use requests for admission (where strategically appropriate) to narrow issues and authenticate documents, and tailor deposition exhibits to what was actually produced.
ESI specifics: ask for the form you can use
Many discovery disputes are really “format” disputes. If ESI matters, your requests should specify usable production: metadata where relevant, load files when appropriate, and clear handling of attachments and families.
For a widely used framework on reasonable ESI practices, see the Sedona Principles.
Where AI helps without changing your strategy
Prioritization is a legal judgment call, but AI can reduce the grind that makes teams over-request in the first place. For example, after you receive productions, tools like TrialBase AI can help you move faster from documents to case-ready work product by turning uploaded materials into medical summaries, deposition outlines, demand letters, and trial-focused documents. When the team can digest records quickly, it becomes easier to run tight, targeted follow-up requests instead of broad fishing expeditions.
If you are trying to shorten the time from “production received” to “deposition-ready,” this is where an intelligent workflow can pay off.
A final gut-check before you serve
Before any request goes out, ask two questions:
- If we get this tomorrow, what decision will we make next week? If you cannot answer, deprioritize it.
- If the judge reads only this request, does it look reasonable? If not, narrow it until it does.
Discovery is not about volume. In discovery litigation, it is about precision, timing, and building a record you can actually use when it matters.
