How to prepare a privilege review log for Shareholder Disputes

Prepare a shareholder-dispute privilege log by identifying the client and represented capacities, reviewing each communication’s purpose and distribution, separating attachments and mixed business/legal content, and reconciling withholdings and redactions against production records. Record the asserted protection and a factual description that permits assessment without disclosing protected substance. The deliverable is a disclosure log supported by a restricted internal review table, with representation questions, missing evidence, and contested treatment resolved or assigned to counsel before release.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must account for withheld or redacted records concerning disputed board approvals, controller transactions, shareholder voting, valuations, or distributions. It is particularly useful where directors hold multiple roles or different lawyers advise the corporation, a committee, and individual participants.

In federal district-court litigation, Rule 26(b)(5)(A) requires express assertions and descriptions enabling assessment without revealing protected information. It does not prescribe universal log columns or resolve substantive entitlement to protection. Check the applicable orders and logging protocol against Rule 26(b)(5)(A). (uscourts.gov)

Do not import federal procedure into every state action, arbitration, or inspection proceeding. Delaware Section 220, for example, imposes purpose, particularity, and related-record requirements for stockholder inspection. Confirm entity type, incorporation, forum, and applicable statutory version before adapting this workflow. See 8 Del. C. § 220. (delcode.delaware.gov)

What you need

Assemble these materials before substantive review:

• Scope and procedure: requests or inspection demands, responses, protective orders, logging agreements, and court directions.
• Representation evidence: engagement materials and reliable records identifying corporate, committee, director, and shareholder representation during relevant periods.
• Source records: emails with headers, board-portal records, director messages, minutes, valuation drafts, attachments, and stable family identifiers.
• Participant register: names, employers, board positions, advisory roles, and dates of role changes.
• Production records: review decisions, redaction locations, production identifiers, withheld families, and collection gaps.

Keep representation evidence and counsel’s reasoning in a restricted working file. Do not assume that marking the working table “privileged” determines its legal protection.

Use the template

Copy the Shareholder Disputes — Privilege review log table into your working document or spreadsheet. Use it internally, then prepare the disclosure version from approved fields required by the governing protocol.

Give separately reviewed attachments their own rows. Retain stable IDs for withheld records without production numbers. In People/capacities, distinguish sender, recipients, copied recipients, and relevant roles; use a linked participant register where necessary.

Client/purpose contains internal analysis of representation and requested legal service. Basis/status distinguishes proposed assertions from approved determinations. Safe description contains proposed disclosure text, not counsel’s reasoning. Source/pinpoint identifies headers, message segments, pages, or representation evidence supporting the decision.

Treatment/link records withholding, redaction, production, or pending review and links to the production record. Issue/owner states the unanswered question and responsible reviewer. Add protocol-required fields rather than treating these nine columns as mandatory or exhaustive.

Step by step

1. Establish scope, timing, and logging method

Identify covered requests, custodians, transaction periods, and batches. For a disputed controller buyout, distinguish committee deliberations, banker exchanges, voting materials, and implementation communications.

Confirm deadlines, duplicate treatment, email-chain treatment, and attachment requirements. Obtain an appropriate agreement or court direction before relying on categorical logging or exclusions. Federal discovery planning expressly addresses the timing and method of compliance with privilege-description obligations under Rule 26(f)(3)(D). (uscourts.gov)

Record: the protocol and deadline authority in the table’s accompanying instructions; request and batch links in Treatment/link. Assign disputed format questions before reviewers create inconsistent entries.

2. Map clients, capacities, and access questions

Separate the corporation, special committee, individual directors, controller, minority shareholders, and advisers. Verify representation rather than inferring it from an email domain, board position, or counsel’s attendance.

For a director employed by the controller, identify the capacity relevant to each communication. Record changes in committee membership and representation over time. Ask counsel to assess disputed access, disclosure, or privilege questions under the applicable law; do not resolve them merely by labeling someone an insider or outsider.

Record: supported client identity, participant capacities, source references, and time-dependent uncertainty in Client/purpose, People/capacities, and Issue/owner.

3. Evaluate purpose and distribution

Read the content, not just the subject line. Identify requested legal advice separately from pricing discussions, forecasts, scheduling, and negotiation updates. Check forwarding history and adviser participation against counsel’s applicable-law analysis.

For proposed work-product claims, capture the litigation-related circumstances and supporting evidence rather than using “privileged” as a catch-all. Keep responsiveness, confidentiality, and protection decisions distinct: federal discovery reaches nonprivileged matter subject to relevance and proportionality limits under Rule 26(b)(1). (uscourts.gov)

Record: the proposed basis, purpose evidence, distribution facts, and approval status. Assign any unresolved legal standard or factual gap to counsel before final treatment.

4. Review chains, attachments, and mixed records separately

Examine a banker’s spreadsheet independently of counsel’s covering email. Review earlier messages, board-pack appendices, embedded comments, and available hidden content. Do not substitute family-level coding for component-level analysis.

For mixed minutes, locate ordinary voting records separately from passages recording requested legal advice. Have counsel assess whether targeted redaction is supported by the applicable law and protocol. Preserve page or paragraph references so another reviewer can reproduce the decision.

Record: component rows, parent-child links, proposed redaction locations, and individual treatments. Identify missing attachments explicitly; do not describe or assess unseen content.

5. Draft descriptions that explain without revealing

Use verified facts: document type, participants and capacities, general subject, and the purpose supporting the asserted protection. An entry might describe an email requesting legal advice concerning disclosure obligations for a proposed controller acquisition without recounting the advice.

Avoid both “email regarding legal matters” and descriptions revealing counsel’s recommendation or litigation assessment. For work product, identify an appropriate factual connection to the asserted protection without exposing counsel’s analysis. Never invent context to strengthen an entry.

Record: proposed text in Safe description and verification in Source/pinpoint. Have a second reviewer assess descriptive sufficiency and disclosure risk.

6. Reconcile withholding, redactions, and production

Compare the table with the withheld population, redaction list, and production manifest. Trace duplicates and family relationships under the protocol. Investigate inconsistent treatment of copies, unaccounted-for attachments, and redactions without corresponding entries or authorized exclusions.

For federal party requests, Rule 34(b)(2)(C) requires objections to state whether responsive materials are withheld; partial objections must identify the disputed part and permit inspection of the rest. Reconcile responses with actual treatment, without importing that provision into subpoena practice. See Rule 34(b)(2)(C). (uscourts.gov)

Record: production IDs, withholding references, exceptions, and correction owners in Treatment/link and Issue/owner.

7. Approve and preserve the disclosure version

Prioritize overlapping representation, forwarded advice, adviser participation, and mixed board records. Give approving counsel the source material and precise question, not merely a protection label.

Create the disclosure version from approved metadata and descriptions. Remove internal legal reasoning and investigation notes, but retain factual information necessary to support the assertion. Compare the release copy with the approved working table and record subsequent corrections by version.

Record: approving reviewer, approval date, and release-version reference. Keep unresolved entries pending, or address their timing expressly under the protocol; do not present provisional assertions as completed determinations.

Worked example

Fictional scenario: Alder Vale Instruments, Inc. faces a minority-shareholder challenge to a proposed acquisition by controlling shareholder North Quay Holdings. All parties, documents, dates, and descriptions below are fictional.

Engagement record R-03 identifies Mira Sen as special-committee counsel. Committee chair L. Orr requests disclosure advice by email. The attached banker model has no identified legal annotation in the content reviewed so far. Separate committee minutes record legal advice and ordinary voting business; attendee J. Vale’s role remains unverified.

The family analysis changes the outcome: AVI-041 does not supply an independent reason to withhold AVI-042. If approved for production, the spreadsheet remains in the internal reconciliation record but ordinarily drops out of the disclosure log unless the protocol requires otherwise.

The minutes require passage-level review, not blanket withholding. Vale’s attendance does not establish affiliation or resolve the protection question. Missing role evidence remains an assigned issue; none of the proposed treatments is final.

Common mistakes

• Treating corporate participants as one client. Verify corporation, committee, director, and shareholder representation separately, including relevant dates.
• Withholding an entire board pack because counsel received it. Review financial exhibits, resolutions, and advice passages independently.
• Equating transaction sensitivity with protection. Separate confidentiality designations from the asserted legal basis.
• Revealing the advice in the description. State the general legal subject and supported purpose without disclosing conclusions.
• Reconciling only fully withheld records. Include partial redactions, attachment decisions, and protocol-authorized exclusions in the internal accounting.

Final quality check

• Each withholding or redaction maps to an approved entry or documented protocol treatment.
• Participant roles and representation match verified evidence for the relevant period.
• Each assertion identifies its basis and approving reviewer.
• Chains, attachments, and mixed records have documented component decisions.
• Descriptions permit assessment without exposing protected substance.
• IDs, pinpoints, and production links resolve to the correct versions.
• Open issues are resolved or expressly assigned with release treatment established.
• The disclosure copy excludes internal reasoning and satisfies requirements checked against primary sources and case-specific directions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation review capabilities, including document review, privilege and confidentiality analysis, redaction, and production, can support examination of committee communications and mixed board materials. Keep client identity, capacity analysis, asserted protection, and disclosure approval under lawyer supervision. To discuss this review workflow, book a demo.

Frequently asked questions

Does copying a lawyer justify a privilege entry?

Do not approve an assertion on that fact alone. Review purpose, participants, distribution, and counsel’s applicable-law analysis. Capture uncertainty where business discussion and requested legal advice overlap.

Should committee counsel and company counsel be identified separately?

Yes, in the internal record. Verify each representation and relevant period. Separate identification supports analysis; it does not itself establish entitlement to withhold a particular communication.

Can one entry cover an email and its valuation attachment?

Follow the governing protocol, but assess components independently first. Where grouping is permitted, preserve document-level internal decisions and make the grouped entry’s scope clear.

Can this log be reused for a shareholder inspection demand?

Reuse verified metadata, not procedural assumptions or final treatment. Reassess scope, descriptions, and assertions under the inspection proceeding’s requirements and directions before releasing a revised log.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34: federal discovery scope, assertion descriptions, compliance planning, and withholding statements.
• Delaware General Corporation Law, Section 220: Delaware stockholder inspection requirements and scope.

Scope: General professional workflow guidance as of October 13, 2026; substantive protection and access questions require matter-specific analysis.

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.