How to prepare a privilege review log for Post-Acquisition Disputes

Prepare a post-acquisition privilege review log by establishing disclosure requirements, mapping counsel relationships before and after closing, and reviewing communications with their attachments and forwarding history. Record the evidence supporting each protection claim without exposing the advice itself. Separate authority to assert privilege from whether a communication is protected, and distinguish legal consultation from transaction execution or accounting work. The deliverable is a source-linked internal decision log, an approved disclosure version, and an assigned list of unresolved ownership, recipient, and protection questions.

When to use this workflow

Use this workflow when buyer, seller, or target-company counsel reviews acquisition records for production in an indemnity, fraud, purchase-price adjustment, or other post-closing dispute. Triggers include requests covering diligence communications, collection of historical target legal files, or discovery that integrated mailboxes contain pre-closing transaction correspondence.

The workflow addresses privilege decisions and their documentation, not the entire discovery process. In US federal district-court litigation, Rule 26(b)(5)(A) requires an express claim when otherwise discoverable information is withheld on privilege or trial-preparation grounds, with descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. Neither specifies a universal spreadsheet format. Check local rules, orders, and the agreed protocol. Federal Rule of Civil Procedure 26.

For state litigation, arbitration, or contractual accountant proceedings, establish requirements separately. Federal discovery rules do not automatically govern those proceedings. The steps below are workflow recommendations; protection, control, and waiver determinations require applicable law and transaction-specific facts.

What you need

Assemble these materials before substantive review:

• Procedural instructions: requests, responses, local requirements, scheduling orders, log agreements, and any nonwaiver order.
• Transaction documents: executed acquisition agreement, amendments, schedules, and provisions concerning counsel, privilege allocation, records access, or dispute procedures.
• Relationship evidence: engagement letters, client identities, representation periods, adviser roles, and evidence explaining third-party participation.
• Review materials: native emails, attachments, messages, diligence questions, data-room records, accounting workbooks, indemnity notices, and accountant submissions.
• Provenance and responsibility: stable IDs, family relationships, custodians, repository migration history, reviewers, and escalation contacts.

Obtain complete communications where possible. An isolated email or rendered spreadsheet may omit recipients, comments, attachments, or context. Record missing material as a gap rather than inferring its contents. Identify which dispute and request bring the document into review; privilege analysis should not replace responsiveness review.

Use the template

Use the Post-Acquisition Disputes — Privilege review log as an internal decision record. You can copy this table into your working document or spreadsheet. Prepare the disclosure version separately to meet the governing requirements.

“Date / phase” distinguishes diligence, signing-to-closing, and post-closing communications. Record complete dates, not merely transaction phases. “Protection / claimant” identifies both the asserted basis and the person or entity on whose behalf counsel proposes to assert it; neither substitutes for the other.

“Source pinpoint” identifies the message, page, attachment, or workbook tab and cells reviewed. Reference supporting engagement or contract documents through stable IDs. Keep detailed internal reasoning in linked notes rather than the disclosure description.

Use distinct statuses for proposed withholding, partial redaction, production, and pending review. The final field should identify an accountable reviewer, concrete action, and any required completion date. Link final production identifiers and approval records through the document ID when they exceed the table’s space.

Step by step

1. Establish disclosure requirements and decision authority

Read the protocol and orders for required fields, email-chain treatment, duplicates, permitted exclusions, and submission timing. Do not presume that categorical descriptions or one entry per family are acceptable. Maintain a short requirements note linked to the worksheet.

Identify the lawyer approving claims and resolving client-identity or control questions. Rule 501 provides that state law governs privilege regarding civil claims or defenses for which state law supplies the rule of decision. It does not determine control of the target’s pre-closing privilege. Assign that analysis, including mixed-claim issues where relevant, rather than assuming the acquisition transferred every privilege right. Federal Rule of Evidence 501.

Record: protocol reference, responsible reviewer, governing-law research assignment, and unresolved authority to assert protection.

2. Map representation across the transaction

Identify seller, buyer, target, their lawyers, and financial advisers. Distinguish entity representation from representation of owners or executives. Mark changes at signing, closing, and subsequent engagements; distinguish ordinary target advice from advice concerning negotiation of the sale.

Read contractual privilege allocations alongside engagement evidence. Flag scope and enforceability questions for legal resolution. Possession of a mailbox and the existence of an allocation clause are inputs, not completed conclusions. The same lawyer may have represented different clients on different subjects.

Record: author and recipient roles, proposed claimant, transaction phase, and supporting engagement or agreement pinpoints in internal notes.

3. Reconstruct document families and context

Review emails, earlier messages, and attachments together while preserving distinct IDs. Compare repository copies when forwarding or migration has changed headers or context. Mark missing attachments and incomplete recipient lists explicitly.

In an adjustment dispute, inspect whether a workbook contains ordinary accounting records, legal-consultation material, or both. Do not extend a parent email’s proposed protection to every attachment. Equally, the status of a business attachment does not decide the accompanying request for advice. Examine native comments, hidden tabs, and the particular version collected.

Record: family links, reviewed version, attachment-level dispositions, and missing material requiring retrieval.

4. Test protection against the actual communication

Read beyond sender names and subject lines. Identify purpose, participants, confidentiality evidence, and the facts supporting the proposed claim. Counsel copied on an operational exchange is a review signal, not a sufficient decision record.

Evaluate attorney-client privilege and work product separately. For federal work-product analysis, Rule 26(b)(3) addresses materials prepared in anticipation of litigation or for trial and permits discovery in specified circumstances; a dispute-related label does not establish protection. Document why and when the particular material was created and assign applicable-law questions to counsel. Federal Rule of Civil Procedure 26(b)(3).

For mixed content, identify potential redaction boundaries for legal assessment rather than withholding everything by default.

Record: protection basis, supporting facts, proposed disposition, and uncertainty, without putting advice into the disclosure description.

5. Investigate recipients and post-closing access

Resolve unfamiliar addresses, consultants, shared inboxes, and forwarding chains. Establish each participant’s role, client relationship, and participation period. Do not classify every acquisition adviser as part of the legal team.

Separate access facts from waiver and control conclusions. Integrated buyer access to a target mailbox requires investigation, not an automatic answer. Assess appropriate nonwaiver protection: Rule 502(d) permits a federal court order preventing waiver through disclosure connected with the pending litigation, with effect in other federal or state proceedings. It does not itself establish privilege or resolve pre-closing control. Federal Rule of Evidence 502(d).

Record: access history, unresolved roles, relevant protection order, and the specific question assigned to counsel.

6. Draft descriptions that permit assessment

State the general legal purpose and acquisition subject without reproducing advice. “Target officer requests legal advice concerning acquisition disclosure obligations” is more useful than “Privileged email,” provided the source supports that description.

Do not recast routine diligence coordination as legal consultation. Check wording against the complete communication and proposed redactions. Where a consolidated entry is permitted, ensure its description accurately covers the included messages rather than obscuring participant or subject changes.

Record: source-verified description, claimant, protection basis, and reviewer approval or required revision. Keep investigative notes and substantive reasoning separate.

7. Reconcile decisions before release

Compare approved entries with withheld documents and redacted versions. Confirm attachment, duplicate, and forwarding decisions are consistent or have documented reasons for differences. Reconcile IDs with production records and relevant requests.

For federal party document requests, Rule 34(b)(2) requires responses addressing each item or category, specific objections, and a statement whether responsive material is withheld on an objection. A privilege log does not substitute for those responses. Federal Rule of Civil Procedure 34.

Keep pending rows visibly separate from approved entries, but do not treat internal uncertainty as extending a disclosure deadline. Obtain counsel’s timely disposition or an authorized procedural arrangement.

Record: final treatment, production identifier, approval, and explicit release instructions for unresolved items.

Worked example

Fictional scenario: Cedar Quay Holdings acquires all shares of Harborlight Components on March 20, 2026. After closing, Cedar Quay alleges inaccurate inventory representations and challenges the inventory adjustment. Counsel reviews target mailboxes migrated into Cedar Quay’s system.

Section 12.8 of the fictional agreement addresses control of specified transaction communications, but counsel has not resolved its application to the collected email. The collection contains a pre-closing advice request, its inventory-workbook attachment, and a post-closing request sent by the buyer’s CFO to its general counsel with a seller-side finance consultant copied. No reviewed evidence explains that consultant’s role.

All parties, documents, dates, and descriptions below are fictional. These are internal entries, not a disclosure-ready log.

Family review prevents blanket withholding of the workbook, but does not authorize its release before native inspection and counsel approval. The advice request supports further privilege assessment without establishing the client relationship or post-closing control. The consultant’s inclusion prompts a targeted investigation, not a predetermined waiver conclusion. Missing engagement and role evidence remain explicit gaps rather than invented support.

Common mistakes

• Equating mailbox possession with privilege control. Record custody separately from client identity and authority to assert protection.
• Treating closing as the sole dividing line. Assess subject matter, representation, and contractual allocation, not date alone.
• Withholding accounting families wholesale. Review schedules, native workbooks, and legal commentary individually while retaining family links.
• Revealing advice through descriptions. Replace conclusions about seller fraud with accurate, nonrevealing descriptions of the consultation’s subject.
• Serving internal reasoning or leaving pending rows unmanaged. Prepare a separate disclosure version and obtain timely decisions or authorized procedural arrangements.

Final quality check

• Each approved row identifies the exact reviewed document and version.
• Authors, recipients, and roles are verified; material unresolved roles block unsupported approval.
• Claimant authority and protection basis have separate documented assessments.
• Attachments, forwards, and partial redactions have reviewed dispositions.
• Descriptions match source content without disclosing protected advice.
• Entries reconcile with production records and request responses.
• Primary sources, local requirements, orders, and protocol provisions are verified; open issues have owners and explicit release instructions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, redaction, and tabular review capabilities can support lawyer review across acquisition records. Keep the log and relationship map as counsel-controlled work products. Explore litigation preparation or book a demo to discuss this workflow. Counsel retains responsibility for protection claims, control analysis, and disclosure decisions.

Frequently asked questions

Can the buyer assert privilege over every target email received at closing?

Do not assume so. Determine the client, representation scope, communication, applicable allocation language, and governing law. Record access and custody independently of authority to assert protection.

Should ordinary adjustment spreadsheets appear on the log?

Include them when counsel withholds or redacts material on a protection claim and the applicable requirements call for logging it. Association with legal correspondence warrants review, not automatic withholding. Internal rows can also document production decisions.

Can one entry cover an entire diligence email chain?

Follow the governing protocol. A permitted consolidated format still requires review of changing participants, subjects, dates, and attachments. Preserve document-level links so counsel can explain the entry’s coverage.

What if a consultant’s role remains unknown near the deadline?

Escalate with the missing evidence and available facts. Obtain counsel’s decision or an authorized procedural arrangement. Do not invent a role, finalize an unsupported claim, or presume that further time is available.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34: privilege-claim descriptions, discovery planning, trial-preparation protection, and document-request responses.
• Federal Rules of Evidence, Rules 501 and 502: applicable privilege law and federal nonwaiver orders.

Scope: General US professional workflow guidance as of October 13, 2026; matter-specific legal determinations remain with counsel.

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.