The anticipation of litigation standard in the work product doctrine turns on whether a reasonable person, looking at the facts available when a document was created, would have concluded that litigation was likely rather than merely possible. A lawsuit does not need to be on file. But a vague worry that someone might sue someday is not enough either. Federal Rule of Civil Procedure 26(b)(3) protects “documents and tangible things that are prepared in anticipation of litigation or for trial by or for another party or its representative,” and every fight over that protection eventually comes back to when the anticipation actually began.1Legal Information Institute. Federal Rule of Civil Procedure 26 – Duty to Disclose; General Provisions Governing Discovery
What the Standard Actually Requires
The threshold is objective. Courts do not ask what the party subjectively feared; they ask what a reasonable person in the same position would have concluded from the facts on hand at the moment the document was created. The threat of litigation must have moved beyond a remote possibility into something a reasonable observer would call likely or imminent.
Two consequences follow from that framing. First, the moment of creation controls. A document is either prepared in anticipation of litigation when it is written, or it is not, and later events cannot retroactively convert an ordinary business record into protected work product. Second, materials generated for routine business or administrative purposes fall outside the doctrine even when a lawsuit is pending on the same topic. A quarterly safety inspection report that a company produces as part of standard operations is not shielded just because the company happens to be defending a safety-related suit. The connection between the document and the anticipated litigation has to be genuine, not retrofitted.
The protection is not limited to what a licensed attorney personally writes. Rule 26(b)(3) lists attorneys, consultants, sureties, indemnitors, insurers, and agents as representatives whose work can qualify. An investigator’s interview notes, a consultant’s analysis, and an insurance adjuster’s report all fit if the person was working to help a party prepare for a legal dispute. Federal Rule of Evidence 502 goes further and extends the doctrine’s coverage to the “intangible equivalent” of tangible materials, meaning oral communications reflecting litigation-related mental impressions can also fall within the protection.2Legal Information Institute. Federal Rule of Evidence 502 – Attorney-Client Privilege and Work Product; Limitations on Waiver
Events That Trigger Anticipation
Courts look for a concrete triggering event that shifts a situation from ordinary business concern into genuine litigation preparation. Common triggers include:
- Receipt of a formal demand letter from a potential adversary or its counsel.
- A serious workplace injury or catastrophic incident that a reasonable person would expect to generate claims.
- A regulatory notice of violation or the opening of a government investigation.
- A litigation hold notice from opposing counsel.
- Service of an administrative complaint or the start of an enforcement proceeding.
Government investigations count even before any civil complaint is filed. Courts have consistently held that internal investigations conducted in response to enforcement actions satisfy the anticipation standard. What matters is whether the documents were created because of a specific, identifiable threat rather than as part of business-as-usual operations. A company that begins preparing litigation materials the day after learning of a catastrophic product failure stands on solid ground. A company that labels old business documents as “litigation preparation” only after a suit lands does not, and courts are openly skeptical of after-the-fact justifications.
The “Because Of” Test and the “Primary Purpose” Test
Federal circuits are split on exactly how tight the connection between a document and the anticipated litigation must be. Which test your court uses determines the outcome for many close cases, so this is not academic.
Most circuits apply the “because of” test. It asks whether the document would have been created in substantially similar form if the litigation had not been anticipated. The Second Circuit articulated the standard in United States v. Adlman: “where a document was created because of anticipated litigation, and would not have been prepared in substantially similar form but for the prospect of that litigation, it falls within Rule 26(b)(3).”3FindLaw. United States v. Adlman The Third, Fourth, Seventh, Eighth, and D.C. Circuits use the same approach.
A minority, led by the Fifth Circuit, applies the stricter “primary purpose” test. Under this version, a document qualifies only if the main reason it exists is to aid in litigation. If a business or regulatory purpose was the primary driver, the document loses protection even if litigation preparation was a secondary motivation. Dual-purpose documents fare much worse in primary-purpose jurisdictions than in “because of” ones.
Dual-Purpose Documents
The hardest anticipation disputes involve documents created for both business and litigation reasons at the same time. Under the “because of” test, a dual purpose does not automatically strip protection. If the document would not have existed in its current form without the anticipated litigation, it qualifies even when it also serves a business function. Adlman itself involved a tax analysis memo prepared to help executives decide whether to proceed with a corporate reorganization, where the analysis focused on the tax litigation expected to follow. The Second Circuit held the memo was protected despite its clear business utility.3FindLaw. United States v. Adlman
The same memo would likely lose protection under the primary purpose test because the business decision was arguably the dominant reason for creating it. When a document has to serve both purposes, the safer practice is to separate them: one version for the business decision, and a distinct version prepared at the direction of counsel for the litigation analysis. Comingling both in one document invites a court to strip protection on the theory that the document was going to be written for business reasons anyway.
Who Has to Prove Anticipation
The party claiming work product protection carries the burden of proving the anticipation requirement is met. Once the requesting side shows the materials are relevant, the burden shifts to the withholding party to establish that the documents were prepared in anticipation of litigation.4Legal Information Institute. Attorney Work Product Privilege Proof usually comes through affidavits, deposition testimony, or discovery responses that lay out the specific circumstances triggering the anticipation.
The Supreme Court framed the policy behind that allocation in Hickman v. Taylor: “The general policy against invading the privacy of an attorney’s course of preparation is so well recognized and so essential to an orderly working of our system of legal procedure that a burden rests on the one who would invade that privacy to establish adequate reasons to justify production.”5Justia US Supreme Court. Hickman v. Taylor, 329 U.S. 495 In practice the initial burden to show relevance is easy to meet, so the real fight almost always centers on whether the withholding party can prove the litigation connection.
This is where many protection claims collapse. A conclusory statement that “this document was prepared for litigation” does not carry the burden. Courts want specifics: what event triggered the anticipation, when it arose, who directed the document’s preparation, and why the document would not have been created in the ordinary course of business. Vague descriptions or boilerplate entries in a privilege log invite challenges and often produce orders to hand the documents over.
What Getting the Timing Wrong Costs
When a court finds that anticipation had not yet begun, everything created before that point is treated as ordinary business material and produced. The consequence is not partial: a document either was prepared in anticipation of litigation or it was not, and there is no middle ground where the protection partially attaches.
Two mistakes recur. The first is treating routine, recurring records as protected simply because a related dispute exists. Standing safety reports, regular compliance reviews, and periodic audits that a company produces on a fixed schedule generally do not become work product just because litigation is on the horizon. The second is retroactive labeling. Adding “prepared in anticipation of litigation” headers to old files after a complaint arrives does not change what the document actually was when it was created, and courts routinely see through the practice.
Overreach on the other side also carries consequences. Rule 26(b)(5)(A) requires a privilege log detailed enough for the opposing party and the court to evaluate the claim.1Legal Information Institute. Federal Rule of Civil Procedure 26 – Duty to Disclose; General Provisions Governing Discovery Boilerplate descriptions draw sanctions motions and judicial frustration. Courts expect enough detail to tie each document to a specific triggering event and explain who prepared it and why, and judges frequently conduct in-camera reviews when a log is challenged. In one recent federal matter, a defendant that had withheld nearly 70,000 documents later found to be improperly claimed received a formal admonition, with a warning that similar conduct would draw more serious consequences.6Federal Trade Commission. Order Supplementing Order on Sanctions
The practical takeaway is straightforward. Identify the triggering event when it happens, note the date, and document the litigation connection from the moment new materials are created. Keep records that would have been generated anyway on their normal track and outside any claim of protection. When a document has both a business and a litigation purpose, split it into two, and have the litigation version prepared at the direction of counsel. The anticipation standard rewards clarity at creation and punishes vagueness after the fact.