Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Prepare a privilege review log by linking each proposed withholding or redaction to its source, participants, asserted protection, purpose, and an assessable description. In shareholder derivative matters, distinguish corporate advice, individual representation, board deliberations, and committee investigations instead of treating every lawyer-involved record alike. The resulting deliverables are a source-linked internal review table, a checked disclosure version, and an exception list assigning unresolved representation, purpose, access, and redaction questions to counsel. Keep internal legal reasoning separate from descriptions intended for disclosure.
When to use this workflow
Use this workflow when company, committee, or individual-defense counsel must explain withholding in board materials, litigation-demand responses, director communications, or investigation records. Requesting counsel can adapt it to assess an opposing log, recording challenges rather than purporting to approve another party’s claims.
In federal proceedings, Rule 26(b)(5)(A) requires express claims and descriptions enabling assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. Neither supplies substantive attorney-client privilege law. Confirm the governing privilege law, local rules, scheduling orders, and logging agreements; do not apply federal procedure automatically in state court or arbitration. Federal Rules of Civil Procedure, Rule 26
For Delaware corporations, distinguish stockholder inspection from plenary discovery. Section 220 imposes conditions concerning purpose, particularity, and relatedness, among other requirements; it is not the litigation discovery framework. 8 Del. C. § 220
What you need
Assemble inputs that permit reviewers to test each claim:
- Operative requests or inspection demands, responses, orders, and logging agreements, including the source of each deadline.
- Stable document IDs, metadata, email families, attachments, board-portal versions, and proposed production references.
- A dated participant directory distinguishing corporate, committee, and individual counsel from directors, employees, and other advisers.
- Engagement records, committee authorizations, and available evidence of representation and distribution.
- The litigation demand, board response, investigation mandate, and challenged transaction materials needed to understand purpose.
- Originals, proposed redacted copies, prior disclosure information, and an exception list identifying missing evidence.
Keep inspection demands and litigation demands separately identified. A reference to “the demand” does not establish which process generated the communication. Collect only the context needed for this review; the log need not become a complete merits chronology.
Use the template
Use the Shareholder Derivative Matters — Privilege review log as an internal working table. You can copy this table into your working document or spreadsheet. Prepare a disclosure version only after checking applicable requirements and excluding internal analysis.
| Entry / source | Date / type | Participants / roles | Matter context | Protection / purpose | Proposed description | Treatment / location | Rationale / gap | Owner / status |
|---|---|---|---|---|---|---|---|---|
Connect each entry to document and family IDs. For produced redactions, add the Bates reference and exact page or passage. Preserve the original reference if pagination changes. Use the actual document date; label estimates and unknown dates explicitly.
Identify authors, senders, recipients, copied recipients, and relevant capacities, using a linked directory where necessary. Separate transaction approval, inspection response, litigation-demand response, and committee investigation in “Matter context.”
“Protection / purpose” records the proposed claim, not merely “confidential.” “Rationale / gap” holds supporting facts, contrary indicators, and unresolved questions. That internal column should not migrate into the served log. Expand the disclosure fields when the governing protocol requires additional detail.
Step by step
1. Define the population and governing method
Identify whether the assignment concerns inspection, plenary discovery, supplemental production, or an opposing log. Establish the document cutoff, required detail, authorized grouping, exclusions, and deadline sources. Do not import an agreement from another action.
In federal discovery, Rule 34(b)(2)(C) requires an objection to state whether responsive materials are withheld on its basis. Reconcile those statements with the log and production record. Federal Rules of Civil Procedure, Rule 34
Record: Add a governing-method note above the table. Put request references in “Matter context” and assign unresolved protocol questions in “Owner / status.”
2. Establish identity and family relationships
Connect each original to attachments, duplicates, and proposed produced versions. A board-portal export may combine a commercial presentation and legal memorandum without justifying identical treatment.
Review email chains for changed recipients and added content. Examine attachments independently rather than inheriting the parent email’s proposed treatment. Before consolidating duplicates, confirm that content and distribution differences do not matter and that grouping is permitted.
Record: Enter source and family IDs, dates, types, and page references. Flag unavailable attachments, incomplete chains, and unverified versions in “Rationale / gap.”
3. Verify participants and representation
Use engagement records, committee resolutions, signatures, and reliable contemporaneous evidence to establish roles. A lawyer representing the company may not be acting for an individual director; do not infer the client from attendance or an email address. Treat ambiguous relationships as questions for counsel, not settled metadata.
For outside recipients, investigate their function, attendance purpose, and distribution history. Identify shareholder-access or director-access disputes separately for governing-law analysis rather than assuming the recipient’s status answers them.
Record: Add verified capacities and source references. Identify the proposed privilege holder internally, and assign uncertain representation or access questions to a named lawyer.
4. Assess purpose and each asserted protection
Read the communication in context. Distinguish legal-advice requests from valuation recommendations, investor messaging, scheduling, and transaction implementation. For mixed communications, identify the passages requiring analysis instead of applying a blanket label.
Assess attorney-client and work-product assertions separately. For federal work-product analysis, document what supports preparation in anticipation of litigation or for trial; an investigation label alone does not establish that basis. Rule 26(b)(3) governs federal trial-preparation protection and its qualifications. Federal Rules of Civil Procedure, Rule 26(b)(3)
Record: State the proposed protection, purpose, supporting evidence, and contrary indicators. Mark unresolved claims “pending counsel decision,” with the missing factual or legal determination identified.
5. Draft descriptions and select treatment
Write a description identifying the document’s nature, participants, and general legal subject without disclosing advice. Prefer a supported description such as “request for legal advice concerning the board’s response to the litigation demand” over “email about board matters.” Do not add a legal purpose absent from the source.
Propose full withholding, partial redaction, or release. For mixed minutes, mark exact paragraphs and inspect the remaining text for intelligibility and unintended disclosure. The federal description must permit assessment without exposing protected information; there is no universal wording formula. Federal Rules of Civil Procedure, Rule 26(b)(5)(A)
Record: Enter the external description and treatment separately from internal reasoning. Keep released records in the internal decision history, not automatically in the disclosure log.
6. Test consistency and resolve exceptions
Compare related records across directors, committees, and custodians. Investigate inconsistent proposed treatment: changed recipients, annotations, or content may explain it, but clerical errors may not.
Review prior production and disclosure information before approval. Route representation, access, mixed-purpose, and investigation questions to counsel with source materials attached. Do not treat an unresolved status as approval or as permission to postpone compliance indefinitely.
Record: Document the reviewer, decision, supporting references, and any revised boundaries. Give each remaining exception an owner, decision date, and counsel-approved handling instruction consistent with the governing schedule.
7. Reconcile the disclosure version with production
Prepare the disclosure log from approved entries, omitting internal rationale and drafting comments. Match references against actual withheld records and redacted copies. Account for each withholding requiring explanation under the governing method, including permitted grouped entries.
Inspect descriptions for adequacy and accidental substantive disclosure. Retain controlled versions so corrections remain traceable. If production changes after approval, recheck the affected entry rather than assuming its earlier description remains accurate.
Record: Identify the approved log version, production set, reviewer, and outstanding exceptions. Preserve a crosswalk between internal source IDs and external references.
Worked example
Fictional scenario: A derivative action challenges Alder Quay Systems, Inc.’s acquisition of a business owned by a director’s sibling. All parties, records, dates, and descriptions below are fictional. Company counsel reviews board and demand-response materials; a separately advised committee later investigates the litigation demand.
The review includes mixed minutes, a commercial email with a model, and interview notes. Committee authorization is available, but it does not establish every participant’s role or the notes’ distribution. These are internal proposals, not approved disclosure entries.
| Entry / source | Date / type | Participants / roles | Matter context | Protection / purpose | Proposed description | Treatment / location | Rationale / gap | Owner / status |
|---|---|---|---|---|---|---|---|---|
| PL-01 / AQ-014 | May 6, 2025 / minutes | Board; company counsel; attendance verified | Acquisition approval | Attorney-client proposed; advice segment | Minutes recording legal advice about acquisition conflict procedures | Proposed redaction, p. 3 ¶¶ 2–3 | Text identifies legal guidance; valuation discussion assessed separately; distribution check open | Company counsel / boundary review |
| PL-02 / AQ-031; attachment AQ-032 | May 8, 2025 / email and model | CFO; directors; copied lawyer, capacity unknown | Valuation analysis | No supported claim yet; commercial purpose apparent | No withholding description approved | Email decision pending; assess model separately | Copying lawyer supplies no demonstrated legal purpose; engagement evidence missing | Review lead / verify role |
| PL-03 / AQ-078 | August 19, 2025 / notes | Committee counsel; employee; unidentified observer | Litigation-demand investigation | Attorney-client and work product proposed | Counsel’s interview notes concerning litigation-demand investigation | Full withholding proposed, not approved | Authorization supplied; observer role, distribution, and litigation-preparation basis need verification | Committee counsel / investigate |
PL-01 narrows the inquiry from withholding entire minutes to testing specific redactions. PL-02 prevents a copied lawyer from substituting for evidence of purpose; absent further support, counsel should reassess the proposed hold rather than invent a claim. PL-03 separates two proposed protections and identifies the evidence needed for each. The existence of a draft description does not resolve those gaps.
Common mistakes
- Using one “company lawyer” label. Verify corporate, committee, and individual capacities through dated sources.
- Treating the board packet as one protected record. Review presentations, resolutions, memoranda, and attachments separately.
- Confusing inspection and litigation demands. Identify which demand generated the record and which disclosure framework applies.
- Giving every investigation record identical treatment. Assess notes, administrative messages, exhibits, and reports on their own facts.
- Serving internal reasoning or leaving indefinite holds. Separate disclosure fields, assign exceptions, and obtain timely handling instructions.
Final quality check
- Every entry resolves to the correct original, version, and family.
- Participant capacities have source support or an assigned verification issue.
- Each asserted protection has a factual basis and counsel’s recorded decision.
- Descriptions permit assessment without exposing protected substance.
- Redaction boundaries match the actual produced copies and pagination.
- Entries reconcile with withholding statements and applicable grouping rules.
- Open issues have owners and compliant handling instructions; internal notes are excluded.
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 review of board and investigation records while retaining representation, protection, and disclosure decisions with counsel. The log and participant directory remain your work products. To discuss this workflow, book a demo.
Frequently asked questions
Can one entry cover an entire email chain?
Check the governing protocol first. Review changed recipients, added content, and attachments before grouping. Preserve source links and explain differing treatment internally even when a grouped disclosure entry is permitted.
Should ordinary board minutes appear on the log?
Apply the logging requirements to what is actually withheld or redacted, not to the board-minutes label. Review specific passages and record the proposed basis. Do not use counsel’s attendance as a substitute for analysis.
What if an investigation participant is unidentified?
Assign verification of identity, role, attendance purpose, and distribution. Do not invent a consultant relationship. Escalate the gap early enough for counsel to determine treatment within the applicable schedule.
Can an inspection log be reused in the derivative action?
Use it as an input, not an automatic replacement. Reconcile populations, requests, requirements, representation facts, and subsequent disclosures. Delaware inspection has statutory conditions distinct from plenary discovery, so an earlier description may need revision. 8 Del. C. § 220
Sources
- Federal Rules of Civil Procedure, Rules 26 and 34: federal protection claims, discovery planning, trial-preparation materials, and withholding statements.
- 8 Del. C. § 220: Delaware stockholder inspection conditions.
This is a general workflow guide, not advice for a particular matter. Confirm applicable rule and statutory versions, transition provisions, governing privilege law, and case-specific orders before use.
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.
