Privilege Log Field Reference

X DLC-M07-001 · Privilege Log Field Reference.xlsx — Excel

FileHomeInsertPage LayoutFormulasDataReviewView

A1 ƒ_x Standard privilege-log field-reference matrix across federal & leading state venues, plus log-format compatibility

DLC-M07-001 · Field Matrix

Privilege Log Field Reference

Matter:

Venue:

Required Recommended Optional Always consult local rules and any protective/ESI order in place.

	A	B	C	D	E	F	G	H
1	Standard Fields — Jurisdictional Expectations
2	Field	Fed (26(b)(5))	SDNY	N.D. Cal.	D. Del.	CA	NY (CPLR)	Notes
3	LogID	Req	Req	Req	Req	Req	Req	Sequential per production or per log.
4	Bates (or Placeholder)	Req	Req	Req	Req	Req	Req	Placeholder Bates for withheld docs; slipsheet in production references.
5	DocType	Req	Req	Req	Req	Req	Req	Email / Memo / Chart / Draft / etc.
6	DateSent	Req	Req	Req	Req	Req	Req	ISO 8601 UTC.
7	Author	Req	Req	Req	Req	Req	Req	Full name + affiliation (attorney flag).
8	Recipient(s) (To)	Req	Req	Req	Req	Req	Req	Full names + affiliations.
9	Cc	Req	Req	Req	Req	Rec	Req	Same treatment as To.
10	Bcc	Rec	Req	Rec	Rec	Rec	Rec	If Bcc exists on original.
11	Subject	Req	Req	Req	Req	Req	Req	Redact if reveals privilege; else verbatim.
12	DescriptionOfPrivilege	Req	Req	Req	Req	Req	Req	Non-privileged description sufficient to assess claim. See DLC-M07-002.
13	PrivilegeType	Req	Req	Req	Req	Req	Req	A/C, WP, Common Interest, JD, Other.
14	Custodian	Rec	Req	Req	Rec	Rec	Rec	Whose file it was pulled from.
15	FamilyID	Rec	Req	Req	Rec	Rec	Rec	Parent-attachment grouping.
16	FileType / OrigFileName	Rec	Rec	Rec	Rec	Rec	Rec	Helpful, especially for non-email items.
17	RedactionFlag / Y-N	Rec	Req	Rec	Rec	Rec	Rec	Distinguish withheld-in-full from redacted.
18	RedactionReason	Rec	Req	Rec	Rec	Rec	Rec	Only for redacted (partial) log entries.
19	Log Format Compatibility
20	Format	Fed	SDNY	N.D. Cal.	D. Del.	CA	NY	Notes
21	Document-by-document (narrative)	OK	OK	OK	OK	OK	OK	Default; most burdensome.
22	Metadata-only log	If Agreed	OK	OK	If Agreed	If Agreed	If Agreed	Common for high-volume email productions.
23	Categorical log	If Agreed	OK (per FTC v. BI)	If Agreed	If Agreed	Rare	Rare	Best supported in SDNY post-FTC v. Boehringer Ingelheim.
24	Threading-based (parent-only)	If Agreed	OK	OK	If Agreed	If Agreed	If Agreed	Inclusive-email approach. Requires stipulation.
25	Threading & Populations
26	All-emails approach: every message in every thread that meets the privilege criterion is logged separately. Highest row count. Safest for older courts, some judges.
27	Inclusive-emails approach: only the "last message in a branch" (containing all prior messages in that branch) is logged. Row count often 30–60% smaller. Requires stipulation or protocol acceptance.
28	Categorical approach: groups of similar privileged materials described in aggregate (e.g. "All communications between counsel X and client Y between dates A–B regarding matter Z"). Only accepted post-stipulation or under specific local practice.

Practitioner reminder. Jurisdictional treatments evolve. Standing orders may modify the defaults above — especially for AI use, categorical logs, and inclusive-thread treatments. Read the standing order, then check with local counsel, then log.

Field Reference Population Notes Log Templates Changes Ready · 100%