Protect the Work Product Doctrine: 6 Actions In House Counsel Need
The work product doctrine shields materials your legal team prepares in anticipation of litigation from being handed to the other side in discovery. Under Fed. R. Civ. P. 26(b)(3), that protection has two tiers: opinion work product (your lawyer’s mental impressions and strategy) is nearly untouchable, while fact work product (the underlying facts and documents) can be forced into the open if the requesting party proves substantial need and undue hardship. Share the material with the wrong person, or wait too long to document why it was created, and either tier can evaporate.
TL;DR:
Creating work product materials for litigation requires clear documentation that the purpose was litigation, not routine business, preferably confirmed by a counsel memo.
Opinion work product, such as legal opinions and mental impressions, is almost entirely protected, whereas fact work product can be ordered for production if substantial need and undue hardship are proven.
The test for “prepared in anticipation of litigation” varies by circuit, with some adopting a broad “because of” standard and others a stricter “primary motivation” approach.
Sharing work product with non-adversaries may not waive protection if done carefully, but disclosures to regulators or informal contacts risk losing privilege if they increase adversarial access.
Building habits such as separate fact and opinion files, timely documentation, privilege logs, and employer counsel involvement are key to preserving work product protection before litigation begins.
Chief Legal OfficeBuild Legal Readiness Into Daily WorkChief Legal Office helps technology companies organize legal work, manage risk, and prepare for litigation, diligence, and growth.Explore Chief Legal Office
Table of Contents
What the Work Product Doctrine Actually Protects
Opinion Work Product vs. Fact Work Product
The Anticipation-of-Litigation Test, and Why Circuits Disagree
Sharing With Others Without Waiving Protection
When Courts Force Production Anyway: Substantial Need and Undue Hardship
A Practical Checklist for Preserving Work Product Protection
Where I’ve Seen This Go Wrong, and What I’d Fix First
How Chief Legal Office Builds Litigation Readiness Into Everyday Legal Work
Sources
What the Work Product Doctrine Actually Protects
Here’s the rule, in plain terms. Fed. R. Civ. P. 26(b)(3)(A) protects documents and tangible things “prepared in anticipation of litigation or for trial” by a party or its representative, and that representative doesn’t have to be a lawyer. An investigator, a consultant, or an in-house risk manager can generate protected material, provided the purpose was litigation, not routine business. That’s the part people skip past, and it’s the part that gets misused most often. The Wex entry from Cornell’s Legal Information Institute lays this out cleanly, and it’s worth bookmarking if you ever need the rule text fast.
The doctrine didn’t come from a statute first. It came from a fight. In Hickman v. Taylor, 329 U.S. 495 (1947), the Supreme Court refused to let opposing counsel obtain witness statements an attorney had gathered while preparing a case, reasoning that lawyers need room to build a case without opposing counsel riding along for free. Nearly three decades later, United States v. Nobles, 422 U.S. 225 (1975), extended that same logic to materials prepared by a defense investigator, confirming the protection travels with the litigation team, not just the bar card.
Why does any of this exist? Because a legal system built on adversarial preparation falls apart if one side can just copy the other’s homework. A few things follow from that:
Lawyers can investigate and strategize without fear that every memo becomes evidence
Clients get more candid, complete work from counsel and consultants
Courts still get the underlying facts when a party truly cannot get them elsewhere
Opinion Work Product vs. Fact Work Product
This is the distinction that decides most discovery fights, and it’s the one clause people gloss over when they’re rushing through a document review.
Opinion work product covers mental impressions, legal theories, and strategic judgments, the actual thinking of the lawyer or team. Courts treat this as close to absolute. Almost nothing short of the attorney putting it at issue themselves gets it produced.
Fact work product covers the raw material behind that thinking: witness statements, investigation summaries, factual chronologies. It’s protected, but it’s a qualified protection, meaning a court can order its production under the right circumstances.
Who can create protected material matters more than most people assume:
In-house investigators, outside consultants, and even claims adjusters can generate work product, as long as the litigation purpose is documented
A paralegal’s factual summary prepared at counsel’s direction is covered the same as if the attorney wrote it herself
Retained testifying experts operate under Rule 26(b)(4), which limits protection for their draft reports and most attorney-expert communications; non-testifying experts retained only for consultation get broader protection
That expert carve-out trips up a lot of litigation teams. If you hire an expert to testify, assume most of your back-and-forth with them is discoverable. If you hire one purely to advise, that conversation stays closer to fully protected.
The Anticipation-of-Litigation Test, and Why Circuits Disagree
This is where the doctrine gets genuinely contested, and where sloppy documentation costs companies the protection they thought they had.
Courts don’t all use the same test for “prepared in anticipation of litigation.” The Second Circuit, in United States v. Adlman, 134 F.3d 1194 (2d Cir. 1998), adopted the “because of” test: a document qualifies if it was created because of the prospect of litigation, even if it also serves a business purpose. That’s a generous standard. Other circuits lean toward a stricter “primary motivation” test, asking whether litigation was the main reason the document exists, not just a contributing one. The Cornell Law Review’s academic treatment of Adlman walks through why that split still matters for anyone litigating across state lines.
Timing is the tell courts look for first:
A report commissioned the day after a demand letter arrives looks like litigation preparation
The same report, if it’s the fourth in a routine quarterly series your company has run for years, looks like ordinary business record keeping
Incident investigations required by regulation or internal policy, done the same way regardless of litigation risk, usually fail the anticipation test entirely
Pro Tip: Have counsel send a short engagement memo the moment you commission an investigation, stating plainly that it’s being done because litigation is anticipated. That one email, dated and specific, is often the single piece of evidence that decides whether a court honors the protection later.
A CLE paper from the Northern District of Nebraska on non-attorney work product makes a point that deserves more attention than it gets: courts weigh whether the document would have been created in substantially the same form regardless of litigation. If your answer is “yes, we do this every quarter anyway,” you’re on shaky ground no matter how you label the file.
Sharing With Others Without Waiving Protection
Attorney-client privilege and work product don’t waive the same way, and mixing up the rules is one of the fastest ways to lose protection you didn’t need to give up.
Attorney-client privilege is fragile. Share the communication with almost anyone outside the privileged relationship, and it’s gone. Work product is more forgiving. Sharing it with someone who isn’t an adversary, and isn’t likely to hand it to one, often doesn’t waive protection at all.
But “often” isn’t “always,” and government disclosures are where this gets dangerous. Companies routinely hand internal investigation materials to regulators hoping for cooperation credit, then get blindsided when a private plaintiff argues the disclosure waived protection for everyone. Westinghouse v. Republic of the Philippines addresses exactly this kind of dispute, and the courts applying its logic ask a specific question: did the disclosure meaningfully increase the chance an adversary could get the material? If yes, the disclosure can waive protection even when the recipient was a friendly government agency rather than an opposing party.
A few practical red flags before you share anything:
Sharing with a joint defense group under a signed common-interest agreement usually preserves protection, but only if the agreement is specific about scope and the parties truly share a legal interest, not just an overlapping business one
Sharing informally, over email, with a vendor or business partner who has no common legal interest, is close to a coin flip
Sharing with a regulator “informally” to build goodwill is the riskiest move on this list, and courts are inconsistent about rewarding it
The Villanova Law Review’s commentary on waiver and common-interest issues is a good next stop if your team handles frequent joint-defense arrangements. Courts scrutinize these fact by fact, so a template agreement copied from a form book is not a substitute for careful drafting.
When Courts Force Production Anyway: Substantial Need and Undue Hardship
Fact work product isn’t a permanent lockbox. Fed. R. Civ. P. 26(b)(3)(A)(ii) allows a court to order production when the requesting party shows substantial need for the material and cannot get its substantial equivalent without undue hardship.
That standard shows up most often when a witness is unavailable, has died, or has memory that’s degraded enough that a contemporaneous statement is the only reliable version of events. Courts have ordered production in cases like In re Initial Public Offering Securities Litigation, where the requesting party couldn’t otherwise access unique witness information captured only in the disputed material.
Courts refuse far more often than they grant these requests. If the witness is available for deposition, or the same facts exist in another document already produced, hardship isn’t established. Even when a court does order production, opinion work product embedded in the same file, the lawyer’s analysis layered on top of the facts, stays redacted. Protective orders and in-camera review are the usual middle ground: the judge reviews the material privately and decides what, if anything, crosses the line.
A Practical Checklist for Preserving Work Product Protection
Getting the doctrine right isn’t about knowing the case law. It’s about building habits your team follows before litigation is even on the horizon, because by the time a lawsuit is filed, it’s too late to fix how last year’s investigation was documented.
Document the anticipation of litigation at the moment you commission the work. A short, dated memo from counsel stating the litigation basis is worth more than any label you slap on a folder later.
Separate fact files from opinion files. Keep witness statements and raw investigation notes in a different folder, with different naming conventions, than legal analysis and strategy memos. Courts look at whether materials are “readily separable,” and a Cornell Wex explainer on the doctrine notes this separation is a recurring factor in production disputes.
Put privilege stamps on the file, not just the cover page. “Prepared at the Direction of Counsel in Anticipation of Litigation” on every page beats a single stamp on page one that gets lost in a production set.
Manage vendors and investigators with a written engagement letter. Spell out that the retention is for litigation purposes, who directs the work, and what happens to drafts. Don’t let a verbal handshake with an outside investigator be your only record.
Build a real privilege log, not a placeholder. Each entry should include who prepared the document, the date, the general purpose, and a brief description, without revealing the mental impressions you’re trying to protect.
Know when to call in outside litigation counsel. A fractional GC or in-house team can run the day-to-day governance, but active litigation, especially with a waiver fight already brewing, usually needs trial counsel involved early. Chief Legal Office’s business continuity framework is one way in-house teams keep this kind of governance running before a crisis, not after one.
Pro Tip: Train anyone who might commission an internal report, not just legal, to loop in counsel before the work starts. Waiver problems almost always trace back to someone outside the legal function generating a document with no idea the anticipation-of-litigation clock had already started running.
Where I’ve Seen This Go Wrong, and What I’d Fix First
The trap I see most often looks harmless at the time. A company runs an internal investigation into a safety incident or a data issue, treats it like any other operational report, circulates it to five departments, and only remembers to call it “work product” after someone gets a subpoena. By then, the document’s own history argues against protection. It reads like business as usual, because it was handled like business as usual.
A fractional GC earns its keep by fixing this before litigation exists, not after. That means training operational leaders to flag potential litigation the moment it’s plausible, not the moment it’s certain, and building the paper trail (engagement memos, restricted distribution lists, clear file separation) as a habit rather than a scramble.
If I had to name the three things every executive should require of their legal function, it’s this: insist on written documentation of litigation anticipation at the time work begins, require fact and opinion materials to live in separate files from day one, and demand a privilege log that gets updated in real time, not reconstructed from memory during a discovery dispute. None of this is expensive. It’s just discipline that has to exist before the demand letter shows up.
— Amy Natasha Osteen
How Chief Legal Office Builds Litigation Readiness Into Everyday Legal Work
Most companies don’t lose work-product protection in a courtroom. They lose it months earlier, when nobody documented why a report was commissioned or who was allowed to see it. Chief Legal Office is built to close that gap from the inside, not as a law firm you call after the fact, but as your ongoing legal department.
A dedicated legal team led by experienced attorneys, backed by paralegals and legal administrators, handles the parts of litigation readiness that founders rarely have bandwidth for: privilege-log maintenance, vendor engagement letters that state the litigation purpose up front, and file structures that separate fact investigation from legal analysis before a dispute ever starts. This approach differs from hiring outside counsel per matter or relying on a single general counsel to manage everything alone. If your team needs a working litigation-readiness playbook and someone accountable for keeping it current, look at what a fractional General Counsel engagement actually covers, and reach out to talk through what your company needs in place before the next investigation lands on someone’s desk.
Sources
For anyone who wants the source material rather than a summary, start with Fed. R. Civ. P. 26(b)(3), the rule text itself, and the Cornell Wex entry on attorney work product privilege for a clean plain-English breakdown. Hickman v. Taylor, 329 U.S. 495 (1947), and United States v. Nobles, 422 U.S. 225 (1975), are the Supreme Court foundation. For the anticipation-of-litigation split, read United States v. Adlman, 134 F.3d 1194 (2d Cir. 1998), alongside the Cornell Law Review’s analysis. On waiver, Westinghouse v. Republic of the Philippines is the case litigators cite most, and the Villanova Law Review’s commentary on common-interest agreements is worth the read before drafting one yourself.
Work Product Doctrine (Northern District of Nebraska CLE paper)
Academic review / commentary on work product doctrine and Adlman (Cornell Law Review)
Recommended
The lawyerly fine print: This article is for general information, not legal advice…
