What Happened
In Experian Information Solutions, Inc. v. Stein Saks, PLLC, defendants faced a massive document production of over 700,000 documents. They missed the deadline to assert attorney-client privilege under the Federal Rules of Civil Procedure (FRCP). The plaintiff claimed this was a waiver, but the court disagreed.
The key issue was that the defendants' insurer denied coverage for litigation costs just as the document review was set to begin. The court opted for a case-by-case analysis instead of an automatic waiver. It ordered the defendants to produce a detailed privilege log within 14 days.
Timeline
Phase 1: Discovery obligations triggered
Defendants received requests requiring privilege review of over 700,000 documents. Under FRCP 34(b), they had 30 days to object or assert privilege.
Phase 2: Insurance coverage denial
As the review was about to start, the insurer denied coverage for litigation costs. This meant paying out-of-pocket for a team of 100-150 attorneys needed for a two-week review.
Phase 3: Late privilege assertion
Defendants missed the deadline and asserted privilege later. Plaintiff moved for waiver.
Phase 4: Court ruling
The court applied a four-factor test, found the timing failure excusable, and ordered a full privilege log within 14 days.
Which Controls Failed or Were Missing
Missing: Insurance coordination protocol
Defendants lacked a mechanism to confirm coverage commitments before discovery deadlines. Your team should ensure insurance coverage for discovery costs is secured before responding.
Missing: Contingency review capacity
Without insurer funding, defendants had no backup plan. A review of 700,000 documents requiring 16,000-21,000 attorney hours is daunting. You need pre-negotiated alternative resources or technology-assisted workflows to avoid reliance on insurer timelines.
Missing: Placeholder privilege assertions
Defendants could have filed a timely objection indicating privilege would be asserted later. This procedural gap left them seeking judicial leniency instead of demonstrating compliance.
Missing: Technology-assisted privilege review
There was no evidence of using predictive coding or metadata-based logging to ease the manual review burden. Relying solely on manual review for 700,000 documents is a resource failure.
What the Relevant Standard Requires
FRCP 34(b)(2)(C): An objection must state if any materials are withheld due to that objection. This generally requires privilege assertions within 30 days of the request.
Case law four-factor test (applied in Experian):
Specificity: Does your objection allow evaluation of privilege for each document? Boilerplate objections don't work. You need document-specific logs with details like drafter, recipients, subject, and date.
Timeliness: Was privilege asserted within 30 days? While this is a rebuttable presumption, compelling facts are needed to overcome it.
Magnitude: How large is the production? The court noted that 700,000 documents requiring a large team made timely review difficult.
Particular circumstances: Were there unique barriers? The insurer's denial at the review's start qualified. Routine budget issues don't.
The court required a "compliant, document-specific privilege log" with details like drafter/sender, recipients with titles, subject matter, and document date.
Lessons and Action Items for Your Team
Action 1: Confirm insurance coverage before discovery obligations arise
Review your litigation insurance policy now. Does it cover eDiscovery costs and privilege logging? Get written confirmation from your insurer that coverage applies to discovery, not just trial.
Action 2: Build a privilege review protocol that doesn't assume unlimited resources
Plan your privilege review workflow for a hypothetical 500,000-document production. Implement technology-assisted tools to prioritize likely privileged documents, reducing manual review by 60-80%.
Action 3: File placeholder objections when funding is uncertain
If facing a coverage dispute or budget delay, file a timely objection stating privilege will be asserted later. Courts favor litigants who preserve their rights procedurally.
Action 4: Adopt metadata-based or categorical privilege logging where proportional
Negotiate with opposing counsel for metadata or categorical logs to reduce costs while meeting disclosure obligations. Include these options in your standard agenda.
Action 5: Treat the 30-day deadline as a forcing function, not a suggestion
Even with case-by-case waiver analysis, missing the deadline weakens your position. Design your process so privilege review starts the day you receive the request.
Action 6: Document your resource constraints contemporaneously
Log the date of budget cuts, alternative funding requests, and extension requests. Courts evaluate "particular circumstances" based on facts, not narratives.
The Experian decision shows that procedural rules can bend under pressure, but they don't break easily. Your goal is to build a discovery response capability that doesn't rely on judicial flexibility.
