How to prepare a privilege review log for Breach-of-Contract Disputes

Prepare a privilege review log by separating potentially protected communications from ordinary contract-performance evidence, verifying participants and document families, and recording counsel’s decisions in descriptions that permit assessment without exposing protected content. Start with the governing privilege law and discovery protocol, then reconcile approved withholdings and redactions against the production set. The deliverable is a service-ready log supported by a separate internal record identifying source documents, asserted protections, review evidence, unresolved questions, and dispositions—not merely a list of documents mentioning lawyers.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must account for withheld or redacted material in a breach-of-contract dispute. Triggers include reviewing termination advice, cure-notice drafts, disputed acceptance communications, or damages analyses before production.

In federal district-court litigation, Rule 26(b)(5)(A) requires express protection claims and descriptions enabling assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. Neither prescribes a universal log template. Federal Rules of Civil Procedure, Rules 26(b)(5)(A) and 26(f)(3)(D)

Federal procedure does not necessarily mean federal privilege law. Under Evidence Rule 501, state law governs privilege regarding a civil claim or defense for which state law supplies the rule of decision. Identify the applicable law rather than assuming the contract’s governing-law clause resolves every privilege question. Federal Rules of Evidence, Rule 501

State litigation and arbitration require separate procedural checks. This is a general professional workflow, not a determination that particular material is protected.

What you need

Assemble these inputs before drafting entries:

• Logging instructions: applicable rules, orders, discovery agreements, requests, responses, and treatment of redactions, duplicates, and threads.
• Contract context: executed agreement, amendments, incorporated schedules, and notice, cure, acceptance, payment, and termination provisions.
• Review population: candidate documents, available native files, metadata, attachments, family relationships, and production identifiers.
• Participant directory: senders, recipients, copied recipients, organizational roles, counsel relationships, and unresolved identities.
• Decision materials: matter-specific privilege instructions, litigation-context evidence, reviewer assignments, production records, and existing decisions.

Keep the actual contract versions available. A draft cure notice and the notice delivered under the contract may share a title but have different circulation histories. Review each version in context rather than classifying it by filename.

Use the template

The Breach-of-Contract Disputes — Privilege review log is an internal working table. You can copy this table into your working document or spreadsheet. Create the external log from approved fields under the governing protocol; exclude internal reasoning and investigation notes.

Use stable entry and document IDs in Entry / source. Date / pinpoint distinguishes the communication date from file metadata and identifies the message, page, or spreadsheet cells at issue. Record unknown dates rather than substituting collection dates.

People / roles identifies relevant senders and recipients, including copied participants. Family / scope specifies the whole document, particular passages, or individual attachments. Protection names each asserted basis; “confidential” is not a substitute for that assessment.

Description holds proposed service-ready wording. Review / gap identifies the reviewer, supporting context, and missing facts. Disposition / owner records production, withholding, redaction, or pending review and the responsible lawyer. Expand combined fields when the external protocol requires separate columns. Keep produced and cleared items internally for reconciliation without automatically including them in the served log.

Step by step

1. Establish the protocol and approval authority

Read the governing discovery materials. Identify required fields, timing, permitted grouping, redaction treatment, and any logging exceptions. If the protocol is silent, seek counsel’s direction rather than inventing an exemption. Record the actual source of the deadline; do not infer one from a prior matter.

Assign an approving lawyer and maintain control notes identifying the governing privilege instructions and protocol version. Separate attorney-client privilege questions from work-product questions so reviewers do not use one label for both.

Record: protocol reference, deadline authority, approving lawyer, and unresolved format questions in control notes; identify the owner of affected rows.

2. Connect candidates to the contract dispute

Organize review around disputed formation, performance, acceptance, payment, notice, cure, termination, and loss. Include relevant drafts and attachments, not just messages containing counsel’s name. Identify ordinary invoices, delivery records, test reports, and counterparty correspondence for independent review.

Use the discovery requests and responses to bound the population. Federal Rule 26(b)(1) limits discovery to relevant, nonprivileged information proportional to the case’s needs. Federal Rules of Civil Procedure, Rule 26(b)(1)

A communication about an unpaid invoice may concern collection operations, legal advice, or both. Its connection to the dispute establishes review context, not protection.

Record: source IDs, contract issue, family links, and candidate scope. Treat this classification as triage rather than a final decision.

3. Verify identity, circulation, and dates

Confirm who created, sent, and received each communication and their roles at that time. Resolve aliases, shared accounts, outside consultants, and counsel performing business functions. Compare headers with available metadata and retain discrepancies.

Inspect forwarded chains and version history. Determine whether a termination draft remained internal, was forwarded outside the organization, or became the counterparty-facing notice. Do not infer a recipient’s role from an email domain or treat a document’s current location as its complete circulation history.

For damages spreadsheets, inspect visible cells, comments, and accessible revision information without altering the source.

Record: verified roles, date source, exact location, circulation evidence, and assigned identity questions.

4. Assess protection at the appropriate level

Read the content rather than relying on privilege headings. Identify the asserted protection, supporting facts, and applicable-law questions. For mixed legal and commercial discussions, identify the passages requiring counsel’s decision; do not assume that redaction is appropriate without that assessment.

Work-product review requires its own factual inquiry. Federal Rule 26(b)(3) addresses documents and tangible things prepared in anticipation of litigation or for trial, subject to qualifications and exceptions. Capture why and when the material was prepared rather than treating every post-dispute document as protected. Federal Rules of Civil Procedure, Rule 26(b)(3)

Assess attachments separately. A routine test report accompanying an advice request needs an independent disposition. Review outside circulation and possible disclosure issues with counsel instead of automatically treating them as preserving or defeating protection.

Record: asserted basis, withholding scope, internal supporting facts, and escalated questions. Leave essential factual gaps pending.

5. Draft assessable, nonrevealing descriptions

Describe the material’s general character, participants’ relevant capacities, and purpose. An entry might identify a request to counsel for legal advice concerning contractual cure obligations without revealing the advice or the client’s assessment of breach.

Avoid “email re contract,” which gives little basis for assessment. Conversely, do not reproduce conclusions, admissions, or negotiating positions to make the description specific. For work-product claims, develop wording that explains the asserted litigation purpose without exposing protected analysis.

Compare each description with the source. Ensure it does not describe advice that the document never contains or conceal material uncertainty behind a confident label.

Record: proposed external wording, reviewer, and approval status. Retain detailed reasoning only in the internal record.

6. Reconcile withholding decisions with production

Compare the table with the actual production population. Verify that proposed withholdings and redactions have approved dispositions or assigned exception questions. Confirm version-specific identifiers and check that attachments have not disappeared with a withheld parent.

For partial redactions, inspect the rendered production copy as well as the source. Verify the identified pages, cells, or passages and check that comments or other content do not undermine the intended treatment.

Federal Rule 34(b)(2)(B)–(C) requires specific objections and disclosure of whether responsive materials are withheld on those objections. Reconcile the log with response language; the log does not replace the response. Federal Rules of Civil Procedure, Rule 34(b)(2)

Record: production references, final scope, reconciliation results, and mismatch owners.

7. Approve and preserve the release version

Have counsel approve contested classifications, third-party issues, descriptions, and logging exceptions. Generate a separate external version containing only required, approved information. Inspect hidden columns, comments, revision marks, and document properties for internal notes.

Preserve the approved version and change history. If supplemental review changes a disposition, update the source-linked row and reconcile the relevant production and log versions. Escalate unresolved questions in time to meet applicable obligations or obtain appropriate direction; a pending row does not itself authorize delayed compliance.

Record: approver, approval date, release version, and the action assigned to each remaining issue. Never convert “pending” into “approved” merely to close a batch.

Worked example

Fictional scenario: Harborline Components sues Aster Vale Robotics over an invented $840,000 equipment purchase. The dispute concerns acceptance testing, unpaid invoices, and whether Aster Vale provided the cure opportunity described in fictional agreement § 8.2. All parties, documents, dates, amounts, and terms are invented.

Counsel reviews an internal advice request, its test-report attachment, and a termination draft forwarded to an unidentified outside address. For this example, counsel verified that the first communication sought confidential legal advice from retained counsel and approved its privilege claim under the matter’s instructions. Counsel separately cleared the routine report. The third item lacks recipient-role evidence.

Independent attachment review changes the production decision: AV002 is produced despite accompanying AV001. Its testing evidence remains available for the performance dispute. The email entry explains the legal purpose without disclosing advice.

AV019’s forwarded copy establishes an outside address, not the recipient’s function. Chen must obtain circulation context and assess its legal significance. The row supplies neither a fictional engagement relationship nor a premature waiver conclusion. L02 stays in the internal record but would not appear as a withheld item in the external log.

Common mistakes

• Treating lawyer-copied messages as protected. Verify purpose, roles, circulation, and the asserted basis before deciding.
• Withholding entire document families. Assess test reports, invoices, and schedules independently and reconcile their production.
• Conflating served notices with internal drafts. Use version-specific IDs and review actual recipients.
• Using confidentiality as the protection claim. Identify the legal basis separately from commercial sensitivity or confidentiality designations.
• Disclosing the disputed legal conclusion. Describe advice concerning notice or cure without revealing counsel’s interpretation.
• Treating pending review as permission to miss deadlines. Assign investigation promptly and obtain counsel’s direction under the actual protocol.

Final quality check

• Every source ID opens the correct document and version.
• Dates, participants, and roles are verified or expressly assigned for resolution.
• Attachments and forwarded messages have appropriate independent assessments.
• Each protection claim and external description has counsel’s approval.
• Pinpoints match the actual withheld or redacted scope.
• Production records, response language, and logging exceptions reconcile.
• Governing sources and protocol versions are verified; open issues have owners and timely resolution paths.
• The external version excludes internal analysis, hidden notes, and unapproved entries.

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. Use these capabilities to support source review while maintaining your own log and approval process. Counsel retains legal judgment over protection claims and descriptions. Explore litigation preparation capabilities or book a demo to discuss this workflow.

Frequently asked questions

Should every contract draft appear on the privilege log?

No document-type shortcut resolves that question. Review circulation, asserted protection, withholding scope, and the governing protocol. Keep cleared drafts in the internal reconciliation record without automatically adding them to the external log.

Can an email thread receive one entry?

Check the protocol before grouping. Identify changes in participants, purpose, attachments, and withholding scope. Preserve message-level internal detail so counsel can support the chosen treatment or separate entries when necessary.

How should counsel handle a redacted damages spreadsheet?

Identify precise cells or passages and inspect formulas, comments, and the rendered copy. Assess the asserted basis and record what is produced. Counsel’s receipt of the spreadsheet is not a sufficient review criterion.

What if a recipient’s role remains unknown?

Keep the uncertainty explicit, assign investigation, and escalate before approval. Record what the source establishes and what remains missing. Address the applicable deadline through counsel rather than leaving the item indefinitely pending.

Sources

• Federal Rules of Civil Procedure: Rules 26(b)(1), 26(b)(3), 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2).
• Federal Rules of Evidence: Rule 501, governing the applicable privilege-law inquiry.

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.