How to prepare a privilege review log for Partnership Disputes

Prepare a partnership-dispute privilege review log by identifying the client and applicable privilege law, mapping participants’ roles when each communication occurred, and separating legal advice from governance and financial records. Review forwarding history and attachments before choosing production, redaction, or withholding. Record decisions against stable document identifiers and draft descriptions that permit assessment without revealing protected substance. The resulting deliverable is a disclosure log reconciled with production, supported by a separate internal record of counsel’s reasoning, source evidence, approvals, and unresolved questions.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must account for responsive partnership documents withheld or redacted on privilege or trial-preparation grounds. Concrete triggers include contested withdrawals, capital calls, distributions, expulsions, and allegations that managing partners sought personal advice using partnership resources.

This guide uses federal district-court procedure. Confirm state-court rules, arbitral directions, local requirements, stipulations, and case-specific orders separately. Federal Rule of Civil Procedure 26(b)(5)(A) requires an express protection claim and a description enabling assessment without revealing protected information. It neither establishes privilege nor mandates universal log columns. (uscourts.gov)

Keep statutory partner-access demands distinct from litigation discovery. Delaware Section 15-403, for example, addresses partnership information rights and permits contractual expansion or restriction. Treat it as an illustrative Chapter 15 framework, not a nationwide rule or a substitute for limited-partnership or LLC legislation. Establish the entity type before using it. (delcode.delaware.gov)

What you need

Assemble these inputs before approving withholding decisions:

• Review authority: discovery requests, responses, log protocol, protective orders, disclosure-related orders, and the source of each applicable deadline.
• Client records: engagement letters, conflict records, and evidence distinguishing representation of the partnership, individual partners, or multiple clients.
• Partnership context: operative agreements and amendments, admission and withdrawal records, management delegations, disputed resolutions, and capital-call or distribution materials.
• Source documents: complete email families, attachments, message exports, minutes, financial records, and available metadata from business and personal accounts.
• Participant information: names, aliases, functions, partner-status dates, and documented counsel relationships.
• Production controls: stable document IDs, production identifiers, redaction references, duplicate relationships, and prior decisions.

Do not use only the latest signed agreement to establish historical roles. Delaware Chapter 15 recognizes written, oral, and implied partnership agreements, including amendments, and generally gives the agreement control over specified partnership relationships subject to statutory limits. These provisions supply context, not a privilege determination. See Sections 15-101(15) and 15-103. (delcode.delaware.gov)

Use the template

The Partnership Disputes — Privilege review log is an internal working table from which counsel prepares the disclosure version. Copy this table into your working document or spreadsheet.

Give each entry a stable number and document ID, with message, page, attachment, or redaction pinpoints. Identify authors and all recipients, including copied recipients, either directly or through a linked roster. Use roles at the communication date rather than current titles.

Keep client/purpose and evidence/gaps internal. Distinguish verified facts from inference and record the basis for escalation. Disclosure description contains proposed outward-facing language; owner/status identifies the decision-maker and release condition.

Do not serve this table unchanged. Prepare a separate disclosure version, removing internal analysis while retaining required descriptive information. Split combined fields into separate author, recipient, date, and document-type columns when the governing protocol requires them. An internal entry for a produced attachment may remain useful even though it does not belong on the served withholding log.

Step by step

1. Establish the procedural and privilege-law framework

Identify the forum, claims, governing orders, service date, and permitted logging method. Confirm any categorical treatment or exclusions; do not presume litigation counsel’s communications are exempt from logging.

Separate withholding procedure from applicable privilege law. Evidence Rule 501 directs that state law governs privilege concerning civil claims or defenses for which state law supplies the rule of decision. Identify the applicable law rather than assuming the partnership agreement’s governing-law clause resolves every privilege question. (uscourts.gov)

Record: link entries to a matter-level protocol note identifying authority, format, timing, and counsel responsible for unresolved legal questions.

2. Map clients and participants over time

Build a dated roster distinguishing partnership counsel, individual counsel, joint representation, managing partners, former partners, accountants, consultants, and administrative recipients. Verify relationships against engagement records and contemporaneous evidence, not email domains or signature blocks alone.

A withdrawal dispute may span changing relationships. A managing partner might request advice before withdrawing, then forward it afterward. Record both events and capacities. Where partnership-funded counsel advised an individual, investigate the representation rather than treating payment as the answer.

Record: identify the asserted client, participants’ historical roles, supporting references, and representation gaps. Link a detailed roster when names or capacities will not fit comfortably in the row.

3. Reconstruct each communication and its family

Open the actual source, not merely a search hit. Examine message sequence, recipients, forwarded content, attachments, and versions. Compare apparent duplicates for added commentary, changed recipients, or different attachments.

Review a ledger, valuation report, consent, or withdrawal notice independently of its covering email. Do not extend the email’s proposed treatment across the family without examining each component. Check whether a longer thread contains earlier material requiring separate treatment.

Record: identify the reviewed version, link attachment entries, and note missing family members or incomplete forwarding history. Preserve uncertainty about a missing attachment rather than describing unseen contents.

4. Evaluate the asserted protection against the document

Read the communication in its partnership context. Distinguish a request for legal advice about a disputed capital call from instructions to calculate balances, schedule a vote, or circulate tax materials. As a review practice, treat counsel’s presence and confidentiality labels as prompts for examination, not substitutes for a source-supported rationale.

Identify each proposed protection separately. For trial-preparation protection, record the anticipated dispute, preparation purpose, and factual basis for counsel’s analysis. Do not use the date litigation began as the sole explanation. Escalate mixed-purpose records and uncertain representation under the applicable law.

Record: enter the asserted protection, purpose, source-supported rationale, and specific unresolved issue. Mark tentative conclusions provisional; do not convert them into approved withholding through a bulk status change.

5. Choose treatment and draft the disclosure description

Choose production, redaction, withholding, or a temporary hold tied to a defined question. For redactions, identify the exact passage and examine the remainder. Record treatment at the appropriate message or attachment level.

Draft a description identifying document type, relevant participant capacities, general subject, and asserted protected purpose without revealing advice. “Confidential partnership business” gives little useful information. “Email from managing partner to partnership counsel requesting legal advice concerning a proposed withdrawal notice” is more informative when the source supports it.

Record: keep proposed treatment and outward-facing language separate from internal reasoning. Include redaction pinpoints and protocol-required fields. A hold is an internal review status, not a completed protection claim.

6. Resolve partnership-specific access and disclosure questions

Escalate joint-representation, former-partner access, third-party participation, disputed-client identity, and possible disclosure effects. Frame each question precisely: who was represented, when, in what capacity, and on what evidence? Do not substitute ownership status for that analysis.

For suspected inadvertent production, preserve the disclosure history and seek instructions under the applicable rules and orders. Evidence Rule 502(d) permits a federal court to order protection against waiver through disclosure connected with pending litigation, including its effect in other federal or state proceedings. Check the actual order and its terms. (uscourts.gov)

Record: assign an owner, supporting references, required follow-up, and disposition. Prevent release of affected documents until the blocking question is resolved.

7. Reconcile the log with production and responses

Compare the approved disclosure log with the final production population and redaction set. Confirm that withheld sources have entries or documented protocol exclusions, produced copies reflect approved treatment, and duplicate decisions are explainable.

For federal party document requests, Rule 34(b)(2) requires specific objections and a statement whether responsive material is withheld on an objection. Reconcile those statements with the review results. (uscourts.gov)

Record: final identifiers, approval, reconciliation results, and the served log version. Preserve superseded internal decisions and reasons. Remove produced items from the disclosure log without deleting their useful review history.

Worked example

Fictional scenario: Alder Quay Partners, a fictional general partnership, disputes a $460,000 capital call and managing partner Mira Chen’s proposed withdrawal. An engagement letter identifies the partnership as counsel Ellis’s client. Chen sent Ellis an advice request with a finance spreadsheet. A later collected email shows partner Owen Hale forwarding that request to personal adviser Rowan. The reviewed records do not explain how Hale obtained the original or establish Rowan’s role in any representation.

All parties, documents, amounts, and dates below are fictional. The entries illustrate provisional review, not final privilege conclusions.

The family review separates the spreadsheet from the advice request: attachment status does not justify carrying forward the email’s proposed withholding. The later forwarding also changes the original email’s review status. Counsel must assess its effect on the proposed claim, not merely decide how to treat AQ-028.

The draft description for L03 remains incomplete because no protected purpose is established. Obtain evidence about receipt and participation before approving a claim. The missing evidence is a gap, not proof of either confidentiality or waiver. Counsel can approve the spreadsheet independently if its review is complete; the linked legal communications remain on hold.

Common mistakes

• Treating every partner as the client. Verify the engagement and representation history; distinguish partnership representation from individual or joint representation.
• Using counsel’s attendance as the explanation. Examine purpose, especially in capital calculations, distribution discussions, and governance logistics.
• Withholding an entire financial-document family. Review each attachment and version, then record distinct treatment where warranted.
• Assessing forwarding only against the later copy. Link the original and forwarded records so counsel considers any effect on the underlying claim.
• Serving internal notes or unresolved holds. Prepare a disclosure version with approved claims and adequate descriptions; retain sensitive reasoning separately.

Final quality check

• Each entry resolves to the actual reviewed source and a stable identifier.
• Dates, authors, all recipients, document types, and pinpoints match source evidence.
• Client identities and historical roles have supporting references or assigned questions.
• Each asserted protection has an approved internal rationale under the applicable law.
• Attachments, threads, forwarding, duplicates, and redactions received distinct consideration.
• Descriptions support assessment without disclosing advice or internal strategy.
• Production, redaction sets, response withholding statements, and the served log reconcile.
• Rules and orders are verified; release-blocking issues are resolved and remaining follow-up is expressly assigned.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation document review, privilege and confidentiality analysis, redaction, and production capabilities can support review of partnership communications; tabular review supports work across multiple documents. Counsel remains responsible for verifying sources, deciding protection, and approving descriptions and treatment. Discuss the collection and review requirements when you book a demo.

Frequently asked questions

Must every withheld item have a separate row?

Follow the governing rule, order, or agreed protocol. Rule 26(b)(5)(A) requires an assessable description, not universal columns. Confirm the basis for categorical logging or exclusions before using them. Internally, retain source-level links sufficient to reconcile every affected document. (uscourts.gov)

Can a former partner obtain partnership counsel’s emails?

Do not decide from former-partner status alone. Establish the client, representation history, dates, asserted access basis, agreement, and applicable privilege law. Assign the legal question before approving affected entries; a role roster organizes the evidence but does not resolve entitlement.

Should capital-account records appear on the privilege log?

Include them only when their approved treatment and the applicable protocol require logging. Review ordinary financial records separately from legal annotations and covering messages. If a spreadsheet is produced, remove any obsolete withholding entry while preserving its internal review record.

What if forwarding history is incomplete?

Record what the source establishes and what remains unknown. Identify missing messages, recipients, or attachments and assign targeted follow-up. Do not invent a participation relationship or infer a final disclosure effect from an incomplete chain. Keep affected release decisions provisional.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34
• Federal Rules of Evidence, Rules 501 and 502
• Delaware Code, Title 6, Chapter 15, Subchapter I
• Delaware Code, Title 6, Chapter 15, Subchapter IV

Scope: general professional workflow guidance; particular decisions depend on applicable law, orders, facts, and agreement terms.

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.