How to prepare a privilege review log for Copyright Infringement Matters

Prepare a privilege review log by connecting each withheld or redacted item to its source, participants, asserted protection, and a description that permits assessment without exposing protected content. In copyright matters, examine creative attachments, clearance discussions, ownership advice, and infringement analyses separately rather than treating every lawyer-linked document alike. Use an internal table to resolve uncertainties, then create the disclosure version required by the governing procedure and orders. The deliverable is a source-verified log reconciled with production decisions, with open questions assigned to counsel.

When to use this workflow

Use this workflow when litigation counsel or an in-house team reviews responsive copyright-related material for withholding or redaction. Typical triggers include producing a creator’s mailbox, reviewing licensing records, or separating legal advice from release-planning discussions.

The task is privilege logging, not deciding infringement. A single email family may contain a creative draft, an executed permission, commercial discussion, and legal assessment. Each component needs an identifiable decision.

This guide assumes US federal district-court litigation. Rule 26(b)(5)(A) requires express claims and descriptions sufficient to assess them without revealing protected information. Rule 26(f)(3)(D) requires discovery-plan proposals addressing compliance timing and method. Neither prescribes a universal spreadsheet. Check controlling privilege law, local rules, and orders; assess state proceedings, arbitration, and Copyright Claims Board matters separately. See Federal Rule of Civil Procedure 26.

What you need

Assemble these inputs before drafting descriptions:

• Review population: responsive emails, chats, clearance memoranda, draft licenses, ownership analyses, and infringement assessments, with stable IDs.
• Creative-file context: native artwork, manuscripts, audiovisual files, source code, version histories, and associated attachments.
• Participant information: names, organizations, legal and business capacities, distribution-list membership, and unresolved identities.
• Matter references: asserted works and versions, disputed uses, discovery requests, and relevant production batches.
• Decision framework: governing orders, logging agreements, counsel’s instructions, and evidence supporting proposed protections.
• Production records: family relationships, proposed redactions, assigned Bates references, and withholding decisions.

Keep sources unchanged and separate from working descriptions. Reviewers must be able to reopen the exact message, attachment, or creative-file version—not merely locate a similarly named file.

Use the template

The Copyright Infringement Matters — Privilege review log is an internal working template. You can copy this table into your working document or spreadsheet. Create a separate disclosure version; do not deliver internal questions or strategic assessments with it.

Entry / source contains a stable log ID and document ID. Date / type distinguishes a message’s sent date from an attachment’s date; flag inferred or unavailable dates. Participants / roles identifies senders, recipients, copied participants, and relevant capacities, using a controlled participant list where helpful.

Work / family links the asserted work and version to the parent message and attachments. Treatment / location records withholding, redaction, production, or pending review, with page, paragraph, frame, or code-line references. Add Bates ranges when available. Protection identifies each asserted basis rather than saying only “confidential.”

Nonrevealing description explains function and subject without stating advice or conclusions. Verification / owner records the internal evidence check, uncertainty, responsible lawyer, and next action. Keep detailed legal analysis in restricted notes linked by entry ID. Expand fields when the governing disclosure format requires additional information.

Step by step

1. Establish the logging requirements and review boundary

Read the discovery order, scheduling order, protocol, and counsel instructions. Identify required fields, delivery timing, treatment of redactions and email chains, permitted grouping, and any agreed exclusions. Do not import another case’s exclusions or assume that litigation-counsel communications need no logging.

Define the population by request, custodian, repository, and production batch. Specify whether review includes attachments, embedded comments, revision layers, and chat-linked creative files. Record the governing references and schedule source in the working document’s header; record row-specific exceptions and their owners in Verification / owner.

2. Map participants, works, and document families

Verify participants before assigning roles. Distinguish litigation counsel, in-house counsel, creative directors, rights managers, freelance authors, agencies, insurers, and external vendors. Investigate distribution lists and forwarded messages; do not replace an unidentified address with “legal team.”

Map each item to the correct work and version. A message discussing a revised illustration may attach an earlier commercial draft. Preserve both identifiers and the parent-child relationship. Inspect attachments and embedded comments independently of the covering message.

Complete Participants / roles and Work / family. Assign uncertain identities or version matches to a named reviewer rather than treating missing metadata as resolved.

3. Identify the claimed protection and supporting context

Read the content and surrounding communications. Identify the legal service requested or provided, the participants’ capacities, and the facts counsel needs to assess the claim. Separate attorney-client privilege analysis from work-product analysis; record both only where each has support.

Rule 26(b)(3) addresses materials prepared in anticipation of litigation or for trial by or for a party or its representative, subject to its conditions and exceptions. See Federal Rule of Civil Procedure 26(b)(3). For a proposed work-product claim, record the preparation purpose and supporting context, not simply “after demand letter.”

Clearance threads may mix permission pricing, release dates, creative edits, and legal assessment. Send counsel a precise question about the passage and proposed treatment. Record the proposed basis in Protection and supporting locations in restricted notes referenced under Verification / owner.

4. Separate copyright evidence from communications about it

Review ownership instruments, permissions, and creative records independently from communications discussing them. Section 204(a) generally requires a signed writing for copyright ownership transfers other than transfers by operation of law; section 202 distinguishes copyright ownership from ownership of the material object. These provisions help identify relevant records, not determine privilege. See Copyright Act, sections 202 and 204.

Do not treat an executed agreement as protected merely because counsel received it. Likewise, distinguish an existing comparison image from a version containing counsel’s annotations. Inspect comments, hidden layers, and revision history before approving treatment; verify that the production version implements the decision without altering the preserved source.

Record separate treatment and pinpoint locations for components requiring different decisions. Retain produced-item rows internally when needed to reconcile the family.

5. Draft descriptions that explain without revealing

Draft from verified metadata and context. Identify the communication type, relevant participant capacities, general legal subject, and claimed protection. A possible description is: “Email from rights manager to counsel requesting legal advice concerning clearance rights for Work HA-03.” Use it only if supported by the source and applicable requirements.

Avoid “privileged email,” but also avoid disclosing counsel’s conclusions about ownership defects, copying, fair use, or exposure. Do not reproduce sensitive subject lines automatically. Distinguish a request for advice from a communication providing advice when the record supports that distinction.

Have a second reviewer compare the description with the source. Record the approved description and reviewer in the template; investigate unsupported descriptions rather than merely polishing them.

6. Reconcile the log with production decisions

Compare the working table against the withheld population and final redacted production set. Match source IDs, redaction locations, family members, and Bates references. Confirm that a produced attachment is not described as withheld and that approved redactions appear in the delivered version.

Rule 34(b)(2) requires specific objections and disclosure of whether responsive material is withheld on an objection. See Federal Rule of Civil Procedure 34. Reconcile the log with discovery responses; the log does not replace them.

Record final treatment, production reference, and reconciliation result. If review reveals a possible inadvertent disclosure, escalate under the applicable procedure and orders rather than treating a changed log entry as the complete response.

7. Approve the disclosure version and assign open issues

Prepare a disclosure version containing the required fields without internal research questions or legal deliberations. Counsel should approve the descriptions, asserted protections, and treatment of procedural exceptions before delivery.

Do not silently convert “pending” into “withheld.” Give each open issue an owner and resolution target tied to the actual schedule. Counsel must decide how any remaining issue will be handled under the governing requirements.

Preserve a versioned record linking the delivered log, corresponding production batch, and approved working decisions. Record later corrections against the same stable entry IDs so the team can explain what changed.

Worked example

Fictional scenario: Larkspur Learning sues Rivet Harbor Media over illustrations in the fictional Harbor Atlas series. Counsel reviews Rivet’s rights manager’s mailbox. One family contains a request for legal advice and an executed illustrator agreement. A separate release-planning thread includes an external clearance consultant whose role is unverified.

All parties, documents, dates, IDs, and described contents below are fictional. These are internal review entries, not jurisdiction-specific privilege conclusions.

Separate attachment review changes the family’s treatment: RH-0143 proceeds to production rather than disappearing into the parent’s proposed withholding. Its row remains an internal reconciliation record, not automatically an entry in the delivered log. RH-0142 still requires counsel’s assessment; identifying an advice request does not complete that assessment.

RH-0210 cannot be finalized from the available evidence. The consultant’s title establishes neither the relevant relationship nor the effect of participation. The assigned inquiry targets missing engagement evidence without inventing it or assuming either protection or waiver. Counsel must resolve the flagged passage and operational discussion before approving production treatment.

Common mistakes

• Treating every clearance discussion as legal advice. Separate commercial negotiations, release planning, and legal assessment; identify the function of the passage proposed for withholding.
• Extending the parent’s treatment to every attachment. Inspect licenses, creative drafts, comparison files, and annotations independently, then reconcile the family.
• Using “copyright strategy” as the description. State the verified legal function and general subject without revealing conclusions about copying or ownership.
• Assuming an external participant’s effect. Verify the creator’s, agency’s, or consultant’s role and route the legal assessment to counsel.
• Checking redactions against an obsolete review copy. Reconcile the approved entry with the final production version and assigned references.

Final quality check

Before delivery, confirm that:

• Every entry opens the correct source and version.
• Dates, participants, and capacities match verified information.
• Attachments and embedded comments have separate treatment where needed.
• Each claimed protection has a documented assessment, not just a keyword flag.
• Descriptions explain the claim without revealing protected substance.
• Withholding and redaction decisions match final production files and responses.
• Procedural sources and orders are verified; open issues are resolved or expressly assigned for counsel’s scheduled decision.

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 review while counsel determines protection and approves disclosures. Connect the work with trial preparation where appropriate. The table remains your working document, not a dedicated product module. To discuss this copyright-review workflow, book a demo.

Frequently asked questions

Should every email copying counsel appear on the log?

Counsel’s presence is a review signal, not the decision rule. Assess content, participants, context, and governing requirements. Keep rejected candidates internally when useful for reconciliation; do not automatically include them in the disclosure log.

How should we handle creative-file attachments?

Assign stable IDs and inspect exact versions, including comments and revision layers. Decide treatment separately from the covering communication. Record the family relationship and verify the approved production version.

Can we group a long clearance email chain?

Check the protocol and orders before grouping. Preserve message-level information internally to identify changes in recipients, purpose, attachments, and claimed protection, even if the permitted disclosure format is shorter.

What if we cannot identify an outside consultant’s role?

Seek engagement records or reliable context rather than inferring a relationship from a signature block. Assign counsel to assess the missing evidence and decide handling under the actual schedule. Do not finalize the claim by assumption.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34: privilege-claim descriptions, discovery planning, work-product provisions, and withholding disclosures.
• Copyright Act, Chapter 2, sections 202 and 204: copyright ownership, material objects, and transfer instruments.

Scope: general professional workflow guidance, not advice or a privilege determination for a particular matter.

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.