How to prepare a privilege review log for Fiduciary Duty Disputes

Prepare a privilege review log by connecting each withheld document or redaction to its source, identified client, participants’ roles, legal purpose, and asserted protection. In fiduciary duty disputes, examine board deliberations, special committee advice, controller communications, and mixed business/legal materials. Review attachments independently and distinguish unresolved questions from approved claims. The deliverable is a source-linked internal review table and a separate disclosure log that permits assessment without exposing protected advice, prepared under the applicable privilege law, procedural rules, and case-specific logging arrangements.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must explain withholding or redacting responsive materials concerning alleged disloyalty, conflicted transactions, deficient oversight, or disputed corporate approvals. Triggers include reviewing a board-portal collection, responding to document requests, and supplementing a challenged log.

The workflow addresses document-level decisions and descriptions, not a complete discovery plan. In federal district court, Rule 26(b)(5)(A) requires an express claim and a description permitting assessment without revealing protected information. Rule 26(f)(3)(D) requires discovery planning to address privilege issues, including the timing and method of compliance. Neither prescribes a universal spreadsheet format. See Federal Rules of Civil Procedure, Rules 26(b)(5)(A) and 26(f)(3)(D).

Confirm state-court or arbitral requirements separately. Procedure also differs from substantive privilege law: Rule 501 provides that state law governs privilege concerning civil claims or defenses for which state law supplies the rule of decision. Mixed federal and state claims require further analysis rather than a blanket assumption. See Federal Rules of Evidence, Rule 501. Identify entity type, relevant law, client relationships, and any disputed access to corporate advice before approving claims.

What you need

Assemble these inputs before drafting descriptions:

• Case instructions: claims, defenses, forum, applicable privilege analysis, discovery requests, logging agreements, orders, and verified submission dates.
• Source materials: native communications, complete recipient fields, attachments, board packs, minutes, committee mandates, adviser correspondence, and stable document identifiers.
• Representation records: engagement materials and other evidence identifying whether counsel represented the corporation, a committee, an individual fiduciary, or another participant.
• Role information: committee membership, officer positions, adviser functions, and changes during the disputed decision process.
• Review decisions: responsiveness, proposed withholding or redaction, asserted protection, reviewing lawyer, and unresolved questions.

Create a participant directory keyed to the communication date. A director’s later committee appointment should not determine their role in an earlier exchange. Retain unknown recipients, missing engagement records, and uncertain distribution lists as explicit gaps rather than filling them from assumptions.

Use the template

The companion template is Fiduciary Duty Disputes — Privilege review log. You can copy this table into your working document or spreadsheet.

This is an internal working table, not a service-ready log. Expand the fields if the governing protocol requires separate sender, recipient, copy, attachment, or production-number columns.

“Entry / source” contains a unique entry number, document ID, page or message location, and attachment relationship. “People / roles” identifies actual participants and their contemporaneous capacities; do not substitute “board” for identifiable recipients. “Client / purpose” identifies the proposed client and the legal task supported by the record.

“Claim / treatment” distinguishes attorney-client privilege, work-product protection, or another assessed basis, and specifies withholding or exact redactions. “Disclosure description” holds the proposed external explanation. Keep supporting analysis, uncertainties, approval, and assignments in the final two columns. Prepare the disclosure copy separately; deleting a few visible notes from the working file is not an adequate release check.

Step by step

1. Establish the logging instructions

Read the applicable rules, orders, and agreements together. Identify whether individual entries are required, specified categories are permitted, email threads receive particular treatment, or defined materials need not be logged. Do not infer an exclusion simply because correspondence postdates the complaint.

Set instructions for partially redacted documents, duplicate copies, and supplemental entries. Identify the approving lawyer and record the actual deadline source rather than a customary interval.

Record in the template: cite the governing protocol in “Evidence / gaps.” Assign unresolved format questions and verified timing in “Owner / status.” Maintain shared instructions outside individual rows where repetition would obscure the record.

2. Identify the client and each participant’s capacity

Map the communication to its contemporaneous representation. Counsel advising a special committee may have a different engagement from counsel advising the corporation, controller, or individual directors. Do not collapse those relationships into “company counsel.”

Check committee mandates, engagement records, message signatures, and distribution lists. For financial advisers, consultants, former directors, and personal counsel, document their involvement and refer its privilege significance to the responsible lawyer. A title or email domain is evidence of identity, not a completed legal analysis.

Record in the template: identify the proposed client, participants’ supported roles, and missing evidence. If authority to assert the claim is disputed, assign that issue expressly; document possession does not answer the question.

3. Separate the communication from its document family

Review the complete thread and every attachment. A board pack may contain a financial presentation, legal memorandum, and approval resolution. The covering email does not determine treatment of every component.

Locate the content supporting each proposed claim. Distinguish requests for legal advice from valuation discussion, scheduling, and business summaries. These are review distinctions, not categorical privilege conclusions. Check other copies for changed recipients, annotations, or forwarding history before treating them as interchangeable.

Record in the template: create linked entries when components receive different treatment. Cite the relevant message, page, or slide and preserve parent-child relationships. Document any permitted consolidated logging without losing component-level internal decisions.

4. Test the asserted protection against the evidence

For each claim, identify the legal purpose supported by the source, participants, confidentiality facts, and other information needed under governing law. For work product, record the asserted connection to anticipated litigation and supporting facts; an unexplained label is insufficient for review. Federal Rule 26(b)(3) addresses materials prepared in anticipation of litigation or for trial, subject to its conditions and exceptions. See Federal Rules of Civil Procedure, Rule 26(b)(3).

Fiduciary disputes may involve demands for access to corporate advice, competing representation positions, or arguments affecting protection. Assign jurisdiction-specific analysis rather than assuming either that fiduciary allegations defeat privilege or that ordinary privilege labels settle access.

Consider production or narrower redaction where the evidence does not support the proposed treatment. Commercial sensitivity is a separate review concern, not a substitute privilege basis.

Record in the template: state the basis, proposed treatment, supporting facts, and approval issue. Use “pending” when evidence or legal analysis remains incomplete.

5. Draft an informative, restrained description

Describe the document’s function without revealing the advice. A source-supported description could read: “Email from special committee chair to committee counsel requesting legal advice concerning the approval process for the proposed controller acquisition.”

“Legal email” provides little assessment value; summarizing counsel’s recommendation may expose the protected substance. Match the description to the actual document rather than importing purpose from a neighboring message. For redactions, explain the withheld portion, not simply the document as a whole.

Record in the template: enter the proposed description and exact internal source location. Refer descriptions that cannot be written safely or adequately to approving counsel, together with the specific difficulty.

6. Reconcile the log with withholding and production

Compare entries against responsive documents actually withheld and pages actually redacted. Investigate missing attachments, orphan entries, inconsistent duplicate treatment, and descriptions covering material already produced. A produced document may still need an entry for redacted portions under the applicable arrangement.

For federal party document requests, Rule 34(b)(2)(B)–(C) requires specific objection grounds and disclosure of whether responsive materials are withheld on an objection. The log does not replace those responses; subpoena practice requires separate analysis. See Federal Rules of Civil Procedure, Rule 34(b)(2).

Record in the template: add available production identifiers, confirm redaction locations, and assign discrepancies. A completed description does not close an unreconciled row.

7. Approve and preserve the disclosure version

Have responsible counsel resolve claims, approve descriptions, and confirm compliance with the logging arrangement. Distinguish unresolved internal rows from approved external entries without allowing that separation to conceal outstanding obligations. Assign necessary investigation, supplementation, or procedural relief with verified timing.

Check disclosure-protection orders separately. Rule 502(d) permits a federal court to protect litigation-connected disclosures from waiver in other federal or state proceedings; it does not establish that material was privileged initially. See Federal Rules of Evidence, Rule 502(d).

Record in the template: retain approval status and the version used for disclosure. Preserve corrections and reasons instead of silently overwriting decisions. Inspect the release copy for comments, hidden columns, and internal analysis.

Worked example

Fictional scenario: Northwick Components Corporation faces a fiduciary duty dispute over a proposed $74 million controller acquisition. Counsel reviews special committee records for production. All parties, amounts, documents, and descriptions below are fictional.

The collection contains a chair’s email requesting committee counsel’s advice, an attached valuation deck, and draft minutes with a counsel-advice section. Reviewers initially proposed withholding all three. Engagement E03 supports the committee representation. The available directory does not identify one recipient of the draft minutes. The dates below are fictional dates in 2026. This is an internal table, not a served log.

Separate attachment review changes NC015’s treatment: it is not withheld merely because it accompanied a legal request. NC014 has a supported purpose and representation record, but still requires approval and distribution checks. NC028 remains pending. The team must establish the unknown recipient’s role and assess its legal significance; the table neither invents missing evidence nor assumes disclosure necessarily defeats or preserves protection.

Common mistakes

• Treating a lawyer’s presence as dispositive. Assess purpose and participants, especially when general counsel also negotiated commercial terms.
• Withholding an entire board pack. Review components independently and identify supported, narrower treatment.
• Using present-day roles for earlier communications. Verify committee membership and representation at the relevant date.
• Revealing advice in descriptions. Explain the legal task without reproducing recommendations or conclusions.
• Closing pending rows to meet a deadline. Escalate unresolved claims and address submission obligations rather than relabeling uncertainty as approval.
• Serving the internal worksheet. Prepare and inspect a separate disclosure version, including hidden content and comments.

Final quality check

• Every withheld document or redaction is accounted for under the applicable logging arrangement.
• Source IDs resolve to the correct messages, pages, attachments, and production records.
• Dates, participants, and contemporaneous capacities have been checked against sources.
• Client identity, legal purpose, and asserted protection have received counsel’s assessment.
• Descriptions permit assessment without revealing protected substance.
• Entries match actual withholding, redactions, and relevant discovery responses.
• Open issues are resolved or assigned, with timing and disclosure obligations addressed.
• The disclosure copy excludes internal analysis and matches the approved version.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, redaction, and production; tabular review supports work across multiple documents. Use these capabilities to support source-centered review while retaining legal judgment over client identity, applicable law, and logging decisions. Explore its litigation capabilities or book a demo to discuss your fiduciary-dispute privilege review workflow. The template remains your team’s work product.

Frequently asked questions

Can we use one entry for an entire board email chain?

Check the governing arrangement. Internally, examine each message’s participants, purpose, and attachments. Consolidation should not obscure different claims, recipients, or treatment within the chain.

Should committee counsel and company counsel share one role label?

Only if verified relationships justify it. Record actual engagements and dates. Preserve separate clients or functions where supported, and assign uncertain representation to matter counsel.

What if the claimant demands access to fiduciaries’ legal advice?

Identify affected entries and assign analysis of governing privilege law, relationships, and the specific access argument. Neither the allegation nor a completed description resolves access. Keep the issue visible until counsel determines treatment and any necessary procedural response.

Is the internal template sufficient to serve as the log?

Not without adaptation and approval. Confirm required fields, grouping, timing, and description requirements. Remove internal analysis and reconcile the disclosure version with actual withholding and redactions.

Sources

• Federal Rules of Civil Procedure: Rules 26(b)(3), 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2), December 1, 2025 edition.
• Federal Rules of Evidence: Rules 501 and 502(d), December 1, 2025 edition.

Scope: General US professional workflow guidance as of October 13, 2026; substantive privilege decisions depend on applicable law and the case record.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.