How to prepare a privilege review log for Bankruptcy Adversary Proceedings

Prepare a privilege review log by confirming the adversary proceeding’s discovery protocol, mapping participants and document families, and recording counsel’s protection decisions against identifiable source material. Convert approved decisions into descriptions that permit assessment without revealing protected substance, then reconcile the log with withheld documents and redacted productions. The deliverable is an approved served log supported by a separate internal decision record. Bankruptcy-specific review should address prepetition and postpetition roles, restructuring advisers, changes in management, and uncertainty about who may assert the protection.

When to use this workflow

Use this workflow when counsel for a debtor, trustee, creditor, committee, officer, or other adversary party must review responsive material before production. Typical triggers include requests for payment-authorization emails, restructuring communications, investigation files, and advice concerning transactions challenged in the complaint.

This guide addresses US federal bankruptcy adversary proceedings. Bankruptcy Rule 7026 applies Civil Rule 26 in those proceedings. In contested matters, Rule 9014 generally applies Rule 7026 but excludes specified disclosure and conference provisions unless the court orders otherwise. Check the proceeding classification, local rules, and discovery orders before setting the protocol. Bankruptcy Rules 7026 and 9014

This is a general workflow guide, not a determination of privilege in a particular matter. Counsel must separately resolve governing privilege law, client identity, and authority to assert protection.

What you need

Assemble a defined review set and the information needed to interpret it:

• The complaint, answer, discovery requests, responses, and orders or agreements governing logging, redaction, and production.
• Documents with stable IDs, original metadata, attachment relationships, and available custodian information.
• A participant directory identifying debtor personnel, outside and in-house counsel, financial advisers, committee representatives, lenders, and counterparties.
• Engagement records or other reliable evidence of each lawyer’s client and relevant representation period.
• A timeline identifying the petition, management or representative changes, and relevant communications, plus the production inventory.
• Written review instructions identifying decision authority, escalation criteria, description conventions, and counsel-verified delivery dates.

Do not infer the client from a firm’s name or assume an adviser served the same party throughout the restructuring. Missing role evidence belongs on the issue list, not in a guessed description.

Use the template

The Bankruptcy Adversary Proceedings — Privilege review log is an internal working template. Copy this table into your working document or spreadsheet. Derive the served log from approved entries; do not inadvertently serve internal analysis or reviewer instructions.

Use stable record and family IDs rather than filenames alone. Identify actual senders, recipients, and copied recipients, with their capacities; link lengthy role evidence to a separate directory. Role labels alone may be insufficient for the served log.

Source locator identifies the email, attachment, page, spreadsheet cell, or redacted passage. Protection / claimant records the asserted protection and the person or entity asserting it. Treatment distinguishes withholding, redaction, production, and pending review.

Basis / issue contains internal reasoning and missing evidence. Decision / status identifies reviewer, approver, issue owner, and next action. Keep production references here or in a linked inventory. Adjust the served fields to the agreed or ordered method; this table is not a prescribed court form.

Step by step

1. Confirm the proceeding’s logging requirements

Read discovery orders and agreements alongside the requests. Record scope, format, timing, treatment of duplicates and email chains, and permitted exclusions. Resolve unspecified points rather than importing another matter’s conventions. Distinguish party requests from subpoenas.

Rule 26(b)(5)(A) requires express claims and descriptions allowing assessment without disclosing protected information. Rule 26(f)(3)(D) makes compliance timing and method part of discovery planning; neither provides a universal log template. Civil Rules 26(b)(5)(A) and 26(f)(3)(D)

Record: Put protocol references and counsel-verified dates in the working document’s header. Identify affected rows and assign format questions. Separately evaluate whether to seek a nonwaiver order; do not treat an agreement’s existence as sufficient protection.

2. Map participants and claimants by date

Identify each participant’s capacity when the communication occurred. Debtor counsel, lender counsel, committee counsel, and a financial adviser are not interchangeable. Check whether the relevant role changed between the communication and review dates.

Use the petition date as an organizational marker, not an automatic privilege boundary. Flag former-management communications, multiple represented parties, and uncertain engagements. Ask separately who the client was and who may assert protection now; metadata cannot answer those questions alone.

Record: Enter participant identities, capacities, and proposed claimant. Link role evidence, including engagement-period information where available. Assign disputed claimant or authority questions to supervising counsel before approving the assertion.

3. Reconstruct families before deciding treatment

Review emails with attachments and relevant earlier messages while keeping every component identifiable. A legal discussion and its payment-ledger attachment may require different treatment. A forwarding message may introduce recipients absent from the original exchange.

Preserve copies that differ in recipients, annotations, or attachments. Check embedded messages and attachment references against collected files. If a component is missing, request it or document the gap; do not describe unavailable content as though reviewed.

Record: Populate IDs, dates, types, and exact locators. Identify missing family members and assign collection follow-up. Keep affected decisions pending when the missing component matters, without unnecessarily suspending independently reviewable items.

4. Assess protection against the actual content

Read the material rather than relying on lawyer names, subject lines, or confidentiality labels. Separate legal-advice questions from operational reporting, negotiations, and financial administration, while applying the governing law to mixed communications.

For proposed work product, document the facts concerning preparation and litigation context. For attorney-client privilege, identify the relationship and purpose supporting the claim. Examine third-party participation and circulation without assuming that every adviser is an agent or that every third-party disclosure has the same consequence.

Record: State protection, claimant, supporting facts, and counsel’s decision. Link the controlling legal analysis where needed. Escalate unresolved issues instead of converting a tentative review tag into an approved assertion.

5. Select treatment and draft an assessable description

Decide whether protection concerns the entire item or identifiable portions. For partial production, mark exact redaction locations and inspect headers, comments, adjacent text, and spreadsheet cells for repeated protected substance. Verify the rendered production copy, not just the review annotation.

Describe the communication’s nature, participants’ relevant roles, and general purpose without recounting advice. “Officer’s request to debtor counsel for legal advice concerning disputed payment obligations” is useful only if the source supports it. Avoid both empty descriptions and summaries revealing recommendations or strategy.

Record: Enter proposed served text, treatment, and redaction locators. Keep detailed reasoning separate. Use consistent terms without forcing materially different communications into identical descriptions.

6. Reconcile the log with responses and production

Compare approved entries with the withheld set, redacted versions, and production inventory. Investigate gaps, duplicate entries, and attachments treated inconsistently across copies. Wholly withheld items still need stable internal identifiers even when they have no production Bates number.

For party production requests, Rule 34(b)(2)(C) requires objections to state whether responsive materials are withheld and to identify the disputed portion of a partially objected-to request while permitting inspection of the rest. Bankruptcy Rule 7034 applies Rule 34 in adversary proceedings. Civil Rule 34(b)(2)(C); Bankruptcy Rule 7034.

Record: Add production references and reconciliation exceptions. Assign discrepancies and correct the response, log, or treatment as appropriate. Analyze nonparty subpoenas separately rather than applying Rule 34 indiscriminately.

7. Approve and preserve the served version

Have supervising counsel review descriptions, substantive exceptions, and consistency across comparable communications. Focus on disputed client identity, role changes, adviser circulation, and redactions affecting transaction evidence central to the claims.

Create the served version from approved disclosure fields. Inspect it independently for hidden columns, comments, linked notes, and descriptions exposing internal analysis. Preserve the served version and its relationship to the decision record so corrections remain traceable.

Record: Enter approver, version, final treatment, and status. Document any protocol-based exclusion rather than silently omitting an item. Resolve an issue or record an expressly approved disposition; assigning an owner alone does not make an assertion ready for service.

Worked example

Fictional scenario: In Harbor Lantern Components v. Cedar Vale Distribution, Harbor Lantern, a Chapter 11 debtor in possession, seeks recovery of a $420,000 payment. It filed its petition on March 2, 2026. Discovery seeks payment-authorization and restructuring communications. All parties, dates, records, amounts, and descriptions here are fictional; the treatments illustrate review decisions, not legal conclusions.

The review set contains a prepetition CFO email to debtor counsel, its ledger attachment, and a postpetition forwarding message copied to an unidentified consultant. Reviewers initially marked both families privileged. The available engagement record identifies counsel’s client, but the review file lacks sufficient evidence to resolve present assertion authority. No engagement evidence identifies the consultant’s role.

HL-042 remains in the internal record but would not ordinarily become a served privilege assertion. Separate review permits transaction evidence to proceed through production checks without treating its attachment to counsel’s email as dispositive.

HL-077 cannot be finalized by calling Rook an agent: the source record does not establish that relationship. HL-041 remains unapproved despite evidence of a legal-advice purpose. The example replaces blanket family withholding with document-specific reasoning and identifies precisely which missing evidence prevents approval.

Common mistakes

• Calling every lawyer “debtor counsel.” Verify represented parties and engagement periods, especially where committee and creditor lawyers share restructuring threads.
• Treating the petition as a privilege boundary. Organize by date, then assess the actual relationship, content, and assertion authority.
• Withholding an attachment because counsel received it. Inspect it separately and record any independent protection basis.
• Describing counsel’s advice instead of the communication. State general purpose and roles without exposing recommendations or strategy.
• Serving the internal matrix unchanged. Remove analysis and pending notes; create an approved, traceable served version.

Final quality check

• Every approved assertion maps to an inspected source and correct family.
• Participant identities, capacities, and claimants have supporting evidence.
• Descriptions do not imply inspection of missing material.
• Redaction locations match the rendered production files.
• Responses, withholding records, and served entries reconcile.
• Counsel has checked cited rules, governing privilege law, and applicable orders.
• Open issues have owners and approved dispositions before affected entries are served.
• The served version excludes internal reasoning, comments, and unintended confidential fields.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and redaction capabilities can support examination of bankruptcy communications and production decisions. Use that analysis alongside source inspection and your working log; counsel retains responsibility for assertions, descriptions, and approval. Explore litigation preparation capabilities or book a demo focused on your adversary proceeding’s review requirements.

Frequently asked questions

Must every email in a chain receive a separate entry?

Follow the agreed or ordered method. Keep messages traceable internally even where grouping is permitted. Different recipients, attachments, or content may require different decisions; grouping should not conceal those differences.

Should the served log include documents cleared for production?

Retain cleared decisions internally when useful for reconciliation, particularly attachments associated with withheld emails. The served log should follow the applicable requirements rather than reproduce every working row. Link redacted productions to approved assertions as the protocol requires.

What if a copied financial adviser’s role is unknown?

Seek engagement or other role evidence and investigate the circulation purpose. Do not invent an agency relationship or omit the recipient. Keep the decision pending for counsel’s assessment, and address approaching delivery dates under the governing protocol.

Can the template be reused for a contested matter?

Yes, as an organizational tool, not as a procedural shortcut. Rule 9014 generally incorporates Rule 7026 but excludes specified disclosures and the Rule 26(f) conference unless ordered otherwise. Recheck orders, timing, and logging requirements. Bankruptcy Rule 9014

Sources

• Federal Rules of Bankruptcy Procedure, Rules 7026, 7034, and 9014: incorporated discovery rules and contested-matter exceptions.
• Federal Rules of Civil Procedure, Rules 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2)(C): protection claims, discovery planning, and withholding statements.

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.