Is There a “Litmus Test” for a Categorical Privilege Log

Is There a “Litmus Test” for a Categorical Privilege Log
Image: EDRM.

[EDRM Editor’s Note: The opinions and positions are those of Michael D. Berman.]


A categorial privilege log was not appropriate for a small number of documents according to Glaxo Grp. Ltd. v. Transpire Bio Inc., 2026 WL 30333478 (S.D. Fla. Oct. 9, 2026). The court wrote:

Although a “categorical” privilege log can sometimes be appropriate, there is no indication that it would be in this case because only forty-six documents or communications are at issue. Cf. TIC Park, 2017 WL 9988744, at *4 (“There is little doubt that a categorical privilege log is inappropriate in this case because this action involves less than 500 documents at issue.”).

Id. at n. 6.

The court wrote that: “The standard for testing the adequacy of the privilege log is whether, as to each document, it sets forth specific facts that, if credited, would suffice to establish each element of the privilege or immunity that is claimed.” Id. at *7 (emphasis in original).

The court required that the log contain the following information: “(1) the name and job title or capacity of the author of the document; (2) the name and job title or capacity of each recipient of the document; (3) the date the document was prepared and if different, the date(s) on which it was sent to or shared with persons other than the author(s); (4) the title and description of the document; (5) the subject matter addressed in the document; (6) the purpose(s) for which it was prepared or communicated; and (7) the specific basis for the claim that it is privileged.” Id. at *8.

The decision emphasized that the focus is on the specific description “and not on the conclusory invocations of the privilege or work-product rule, since the burden of the party withholding documents cannot be discharged by mere conclusory or ipse dixit assertions.” Id. (cleaned up).

If a log is deficient: “Absent extraordinary circumstances or dilatory conduct, courts normally give parties an opportunity to correct a deficient privilege log before determining that a privilege has been waived.” Id.

Applying these principles, the court held that the privilege log, even with supporting declarations, was insufficient and it ordered preparation of an amended log. “Looking at the declarations, they do not cure the defects in the privilege log. Although Transpire’s submitted declarations provide context regarding the overall nature of the communications and somewhat describe the position or role of each person copied, they do not add to the subject matter of each communication. The Court is thus left with two conclusory descriptions that Transpire uses for the bulk of the forty-six documents or communications in dispute.” Id.

Further, the court denied a request for in camera review: “Although Transpire and GSK both seek in camera review as alternative relief, the Court will not review the communications in camera at this time. Instead, the Court will require an amended privilege log. This way, GSK (and the Court if in camera review is ultimately necessary) will be in a better position to determine whether Transpire has carried its burden for each at-issue communication or document.” Id. at n. 7.

For more on privilege logs, please visit:

For more on in camera review, please visit:


Assisted by GAI and LLM Technologies per EDRM’s GAI and LLM Policy.

Author

  • Michael Berman

    Michael Berman is a practicing lawyer and an adjunct faculty member at the University of Baltimore School of Law.  He has published extensively, including as the editor-in-chief and a contributing author in “Electronically Stored Information in Maryland Courts” (Maryland State Bar Ass’n. 2020), co-editing two American Bar Association books on electronic discovery, as well as co-authoring law review and other articles regarding electronically stored information (“ESI”).  He has presented widely in venues ranging from local to National events and served as a Court Appointed ESI Discovery Supervisor for ESI Protocol.

    View all posts Owner, E-Discovery LLC