
[EDRM Editor’s Note: The opinions and positions are those of Michael D. Berman and Doug Austin.]
“Metadata” and “Metadata Plus” privilege logs are useful, relatively easy to generate from a litigation review platform, and can further proportionality. See How to Create a “Metadata” or “Metadata Plus” Log Using a Litigation Review Platform – E-Discovery LLC (Aug. 7, 2024).
In Apex Grp. Capital Advisors LLC v. Related Fund Mgt. LLC, 2026 WL 3258098 (S.D.N.Y. Oct. 29, 2026), the parties agreed to a Metadata Privilege Log in their ESI Protocol, but disagreed over its application. The court found a gap in the ESI Protocol’s language and filled it with Fed.R.Civ.P. 26(b)(5)(A). It held that, if a party wants to negotiate a “metadata only” log instead of a “Metadata Plus” log, it must do so expressly.
In §VIII.B, the ESI Protocol stated that “’[f]or any Documents withheld or redacted based on a claim of privilege, the Parties agree to provide for each such document’ an enumerated list of ‘Metadata fields (if available) to facilitate the determination of the basis of privileged [sic] claimed.’”
Defendants, DRFM, et al., asked the court to order plaintiff Apex “to supplement its metadata privilege log with descriptive narratives for each entry….”
Apex replied that the ESI Protocol was an agreement that “their respective privilege logs will contain only the metadata specified in this provision and need not contain descriptive narratives.”
DRFM took the opposite position. “Defendants interpret [the ESI Protocol] as merely setting forth the minimum information required, which Defendants argue is qualified by language elsewhere in the ESI Protocol stating that ‘[n]othing in this ESI Protocol is intended to be an exhaustive list of discovery obligations or the rights of a Party … [and] additional obligations or rights … aris[ing] under the governing case law, the Federal Rules of Civil Procedure, the Local Rules … or any other applicable rules or regulations … remain.’”
This resulted in very different privilege logs:
- “Apex produced a privilege log consistent with [its] understanding.”
- “Based on that very different understanding, the Employee Defendants’ and the Related Defendants’ own privilege logs include a column containing a short description of the justification for each assertion of privilege.”
The Apex Grp. Capital Advisors court disagreed with Apex.
First, it held that the language in the ESI Protocol states only what the parties agreed to provide and: “It does not purport to specify all information to be provided on the log.” Then, the court added: “Indeed, Apex’s own privilege log includes a field not specified in Section VIII.B: namely, a designation of the type of privilege asserted (e.g., attorney-client privilege, work product protection).”
Second, and “more importantly,” the ESI Protocol “does not say that the parties have agreed that descriptive narratives need not be included in the log, or, for that matter, that they must be included; it does not address the issue of narratives one way or the other.” Then, just like it had looked at Apex’s log, the court looked at DRFM’s and added: “Apex’s contention that the parties agreed in the ESI Protocol not to include descriptive narratives is further belied by the fact that Defendants’ logs do include such information, showing that, at best, the Protocol is ambiguous on the issue.”
In short, the court found the ESI Protocol was silent or ambiguous on the “plus” field of a “Metadata” privilege log. Factually, Apex’s log did not conform to Apex’s assertion of what the ESI Protocol called for. DRFM’s log did conform with its assertion of what the ESI Protocol called for.
Finding no case on point, the court looked to analogous redaction cases and wrote that “this Court reasoned that because the parties had not reached a mutual agreement on the issue of redactions—as shown by the contrasting approaches taken in their productions— the Court’s task was ‘akin to filling a gap in the parties’ incomplete agreement.”
It then explained that in the redaction case: “To fill that gap, the Court looked to the default rule supplied by the applicable background law governing the issue in the absence of an agreement.” Where parties did not opt out of the default rule, that rule governed. Id. at *2.
Here, the privilege log rule, Fed.R.Civ.P. 26(b)(5)(A), provided the default rule:
Although Apex and the Defendants could have come to an agreement that a privilege log containing a set of metadata fields would be sufficient to satisfy their discovery obligation, they did not reach such an agreement. The Court therefore interprets the ESI Protocol against the background of applicable law, which requires a party withholding otherwise discoverable information on the basis of privilege to “describe the nature of the documents, communications, or tangible things not produced or disclosed—and do so in a matter that, without revealing information itself privileged or protected, will enable other parties to assess the claim.”
That led to the holding: “As a result, Apex must provide descriptive narratives to enable Defendants to assess Apex’s privilege claims.” The court then explained:
That the ESI Protocol appears to contemplate use of a metadata privilege log does not change this conclusion. There are different types of metadata logs. See Commentary on Privilege Logs, 25 Sedona Conf. J. at 286–94 (differentiating between metadata logs that do not contain descriptive narratives and “metadata-plus-topic” logs that do contain such narratives, and “recommend[ing]” that metadata-plus-topic logs “be considered the preferred format over a traditional log for most cases”). … [I]f Apex wanted to be able to prepare a metadata log that dispensed with the normal requirement for descriptive narratives, it was incumbent upon Apex to negotiate a specific agreement to that effect. [emphasis added].
Defendants agreed that for “some number of entries,” the information already provided was sufficient. “As for the rest, Apex proposes that the parties use a sampling process whereby it would provide narratives for a relatively small set of entries on the log.” The court rejected Apex’s sampling proposal in light of the absence of an agreement and the large number of entries that needed more information. The parties were directed to meet and confer.
The Apex Grp. Capital Advisors court added in a footnote:
Even where the parties have agreed, in the first instance, to dispense with descriptive narratives, supplementation may be necessary to enable the recipient to adequately assess the privilege assertions and the court to rule on any challenges. See Commentary on Privilege Logs, 25 Sedona Conf. J. at 288–90 (explaining that in many instances, the metadata alone “will provide information synonymous with much of what is contained in a descriptive narrative,” but that “[m]etadata will not be perfect for every document,” and that where such deficiencies “prevent a reasonable assessment of the claim, the parties can confer on those entries for which the receiving party believes it needs additional information to assess the claim of privilege”).
Cf. Fed.R.Civ.P. 29.
The 1993 Advisory Committee Note states: “This rule is revised to give greater opportunity for litigants to agree upon modifications to the procedures governing discovery or to limitations upon discovery…. Unless the court orders otherwise, the parties may stipulate that… other procedures governing or limiting discovery be modified…. Under the revised rule, the litigants ordinarily are not required to obtain the court’s approval of these stipulations.”
It should be noted that the EDRM Privilege Log Protocol (v2.0), released in 2023 and available here (and in the background document here), doesn’t necessarily require a narrative description for every entry. It emphasizes exporting metadata as-is, identifying the privilege asserted, providing a list of privilege-related individuals, and using an iterative meet-and-confer process to supply additional information about questioned entries – which is ultimately where the parties wound up after court intervention. Awareness of available resources and more specificity in the ESI protocol could have avoided this dispute in the first place.
In Apex Grp. Capital Advisors, Apex sought leave to redact some information from the publicly-filed version. The court directed that it file a sealing motion. Cf. M. Berman, A Request to File a Privilege Log Under Seal Was Denied – E-Discovery LLC (Aug. 27, 2024).
For a general discussion of the types of privilege logs, see M. Berman, Privilege Logs: New Techniques to Achieve Proportionality – The “Certification Log” – E-Discovery LLC (Mar. 4, 2024).
For an Agreement in ESI Protocol to Provide a “Metadata-Only” Privilege Log Was Enforced – E-Discovery LLC (Jul. 22, 2024).
See also:
- D. Austin, Metadata-Only Privilege Log Motion Denied by Court (Aug. 19, 2024);
- D. Austin, Commentary on Privilege Logs from The Sedona Conference (May 29, 2024);
- D. Austin, Privilege Logging is Unwieldy Thanks to Technology. Can AI Help? (Mar. 19, 2024).
Assisted by GAI and LLM Technologies per EDRM’s GAI and LLM Policy.

