How to prepare a privilege review log for Patent Infringement Matters

Prepare a privilege review log by identifying responsive material proposed for withholding or redaction, verifying participants and their roles, and recording a supported protection claim with a nonrevealing description. In patent litigation, distinguish legal communications from engineering, prosecution, licensing, and product-development records rather than treating counsel’s involvement as dispositive. The deliverable is a source-linked internal review table and an approved external log, with unresolved patent-agent, third-party, and advice-of-counsel questions assigned to counsel before release.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must explain privilege-based withholding from a patent-infringement production. Triggers include inventor email review, technical attachments to counsel communications, redacted licensing records, and reconciliation of production files with withholding decisions.

This guide addresses US federal district-court litigation. Rule 26(b)(5)(A) requires an express privilege or trial-preparation protection claim and a description permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning; neither prescribes a universal spreadsheet format. Check case orders and logging arrangements before setting fields or delivery dates. Federal Rules of Civil Procedure, Rules 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

State proceedings, arbitration, ITC investigations, and PTAB proceedings require separate procedural checks. This is a general workflow, not a substantive privilege opinion: counsel must identify the governing law and assess each assertion against the facts.

What you need

Assemble a bounded review set and the instructions governing it:

• Discovery scope: requests, responses, withholding statements, production specifications, scheduling orders, and logging protocols.
• Source records: native documents, readable versions, attachments, complete email headers, stable document IDs, and production numbers where available.
• Patent context: asserted patents, accused products and versions, prosecution matters, and relevant licensing or infringement-advice projects.
• Participant directory: names, aliases, employers, counsel relationships, and roles at the communication date—not merely current titles.
• Review instructions: candidate protections, escalation criteria, treatment of duplicates and threads, and responsible decision-makers.
• Issue background: proposed advice-of-counsel reliance and known patent-agent, consultant, joint-development, or external-recipient communications.

Keep factual role information separate from legal conclusions. An inventor’s title, law-firm domain, or “privileged” subject line is a review lead, not an approved determination. Identify the evidence supporting participant roles so another reviewer can reproduce the assessment.

Use the template

Use the Patent Infringement Matters — Privilege review log as your internal working table. You can copy this table into your working document or spreadsheet. Prepare the external version separately to avoid disclosing internal reasoning or unresolved questions.

Use stable IDs for withheld records without production numbers. Identify parent-child relationships in the first column; cite the document, page, message, or attachment in Source cite. Specify whether Date means message date or document creation date, and preserve uncertainty.

Record senders, recipients, copied participants, and relevant roles. In Protection / basis, distinguish the asserted protection from the internal justification. The basis may contain confidential analysis and should not automatically appear externally. Nonrevealing description holds proposed external text.

Treatment distinguishes withholding, redaction, production, and pending review. Identify exact redacted portions and the approved production version. Reviewer / open issue assigns a named owner and next decision; link a separate issue sheet when necessary. Add fields required by the governing protocol. Do not assume this eight-column internal table alone satisfies every external logging requirement.

Step by step

1. Fix the logging scope and governing instructions

Read requests, responses, orders, and agreed protocols together. Confirm the production population, deadline source, required fields, and authorized grouping or exclusions. Document any treatment of post-filing counsel communications rather than importing conventions from another case.

For Northern District of California utility-patent actions within the local rules’ scope, Patent L.R. 3-2 requires the infringement claimant to produce specified categories, including invention-development, prosecution, ownership, and licensing records. Use those categories to check review coverage where applicable, not to decide privilege or impose claimant obligations on the accused infringer. Northern District of California Patent Local Rules, Rules 1-2 and 3-2. (cand.uscourts.gov)

Record: link the population and governing instructions to the table; assign unresolved scope or timing questions in Reviewer / open issue.

2. Reconstruct families, threads, and technical context

Read communications with attachments and relevant thread context. Identify separately created schematics, test results, claim comparisons, prosecution drafts, and licensing analyses. Review each attachment instead of inheriting the parent email’s disposition.

Compare versions found elsewhere. A counsel-marked schematic and its clean engineering original need distinct records and potentially different decisions. For consolidated threads, examine changing recipients and forwarded content; the last message may not adequately describe earlier communications.

Record: enter family IDs, source locations, version distinctions, and missing attachments. Assign gaps rather than reconstructing absent content from filenames. Link duplicate decisions while preserving differences in circulation or annotations.

3. Verify participants and communication purposes

Identify who sent, received, copied, or forwarded the material and their roles then. Distinguish litigation counsel, prosecution counsel, patent agents, in-house lawyers, inventors, technical consultants, and business negotiators.

Examine purpose, not just subject matter. A product-release discussion involving an in-house lawyer differs factually from a request for infringement advice. Mixed technical, commercial, and legal discussion requires focused analysis. For outside recipients, obtain available engagement or role evidence without assuming either protection or its loss.

Record: enter verified roles and supporting references. Record apparent purpose and uncertainty in Protection / basis, clearly separating inference from verified facts. Assign missing role evidence to an owner.

4. Decide the proposed protection and treatment

Counsel should assess each assertion under the applicable substantive law and facts. Distinguish attorney-client privilege from work-product protection; if both are asserted, support each separately. For work-product candidates, identify the claimed litigation connection and supporting circumstances for counsel’s analysis.

Prioritize patent-agent communications, third-party circulation, and possible advice-of-counsel reliance. Distinguish confidentiality designations from the privilege or protection actually proposed. Where analysis remains incomplete, retain a pending status with a decision target—not an approved assertion.

Record: state the proposed protection, internal factual basis, disposition, and decision-maker. For redactions, cite the precise portions and examine the remaining text for disclosure of protected substance. Do not resolve the issue by withholding the entire technical record without analysis.

5. Draft a description that permits assessment

Describe document type, relevant participant capacities, general subject, and legal purpose without revealing advice or conclusions. “Email regarding patent” usually conveys too little. A candidate description is: “Engineer email to litigation counsel requesting legal advice concerning accused controller design.” Use it only if the record supports those facts.

Avoid technical detail that reveals the advice sought, and do not describe counsel’s infringement or validity conclusion. Tailor descriptions to prosecution, licensing, and infringement communications rather than applying one generic sentence. The procedural objective is assessment without protected disclosure. Federal Rules of Civil Procedure, Rule 26(b)(5)(A). (uscourts.gov)

Record: enter proposed external wording and preserve supporting citations internally. Return unsupported descriptions to the assigned reviewer.

6. Reconcile decisions with the production

Compare the table with the actual production population. Confirm withheld records are excluded, approved redactions appear in the correct versions, and producible attachments have not remained excluded through family coding. Check visible text, metadata, and native-file treatment against production instructions.

Reconcile entries with request responses and withholding statements. Rule 34(b)(2) requires specific objections and disclosure of whether responsive materials are withheld on an objection; that response obligation is distinct from preparing the log. Federal Rules of Civil Procedure, Rule 34(b)(2). (uscourts.gov)

Record: update dispositions, production references, redaction locations, and discrepancies. Retain internal rows for released candidates so reviewers can explain their omission from the external log.

7. Approve the external log and retain the decision trail

Have responsible counsel review difficult assertions and a risk-based selection of other entries against their sources. Independently inspect the external version for internal reasoning, revealing descriptions, unexplained abbreviations, missing participants, and inconsistent protection labels.

Assign remaining questions an owner and resolution target tied to the actual schedule. Decide whether unresolved material prevents release or requires another authorized approach; “pending” is not permission to miss obligations.

Record: capture approval, version, covered population, and issue dispositions. Retain the released log and production reconciliation together so later corrections can be traced to the original decision.

Worked example

The parties, records, dates, and descriptions below are entirely fictional.

Aster Quay Devices sues Brindle Circuit Works over an allegedly infringing controller. Brindle’s counsel reviews engineer Lena Moss’s mailbox. One family contains a request to outside litigation counsel Daniel Voss for design-related legal advice and an earlier bench-test spreadsheet. Another record contains a forwarded exchange involving patent agent Mira Pell and external development consultant Owen Reed.

In this fictional scenario, counsel approves withholding the first email after substantive review and approves producing the clean spreadsheet. The forwarded exchange remains unresolved: its headers identify recipients, but available records do not establish the consultant’s engagement or the patent agent’s function.

Family review changes the decision: the spreadsheet is not withheld simply because it accompanied the email. Its earlier date and clean technical contents support separate review; counsel’s disposition is specific to these fictional facts, not a categorical attachment rule.

The third row is an internal issue entry, not a final external assertion. Do not invent an engagement relationship to complete it. Obtain evidence or assess the consequences of its absence, then revise the basis, description, and disposition. Only the first row currently supports an approved external withholding entry.

Common mistakes

• Treating prosecution records as one category. Separate filed materials, drafts, counsel instructions, and technical inputs; assess each record’s purpose.
• Inheriting a parent email’s treatment. Review clean drawings, test data, and claim-comparison attachments independently while preserving context.
• Using titles as conclusions. Verify what the lawyer, agent, or consultant was doing in the communication.
• Describing the legal conclusion. State the advice-seeking subject without exposing infringement, validity, or exposure assessments.
• Deferring advice-of-counsel questions. Identify potentially affected records early and assign reliance implications to counsel before approval.
• Serving the worksheet unchanged. Remove internal analysis and unresolved notes while preserving sufficient supported external detail.

Final quality check

• Every in-scope withholding and redaction is accounted for under the approved logging approach.
• IDs, dates, participants, and citations match underlying records.
• Attachments, versions, duplicates, and consolidated threads received deliberate treatment.
• Each assertion has counsel-approved support, not merely a keyword match.
• Descriptions permit assessment without exposing protected substance.
• Production versions, redactions, responses, and dispositions reconcile.
• Open issues are resolved or assigned with a documented release decision.
• The external log excludes internal analysis and matches approved instructions and population.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation workflow includes document review, privilege and confidentiality analysis, redaction, and production. Use these capabilities to support source review and counsel’s examination of withholding decisions. The template remains your team’s work product; lawyers retain responsibility for assertions, descriptions, and release. To discuss this workflow, book a demo. (decover.ai)

Frequently asked questions

Must every email in a patent-related thread have its own entry?

Check the order and logging protocol. If grouping is authorized, ensure the entry accurately covers dates, participants, and asserted protection. Preserve message-level references internally, particularly where recipients change or technical attachments differ.

How should patent-agent communications be handled?

Escalate them for individualized analysis. Verify the agent’s function, communication purpose, participants, and matter context. Record missing evidence explicitly. The participant label alone does not complete counsel’s substantive assessment.

Should a redacted engineering document appear in the log?

Follow the governing instructions. Internally, identify the record, exact portions, asserted protection, and approved production version. Do not confuse sensitive engineering information with a supported protection claim; examine the technical remainder separately.

What if the team may rely on advice of counsel?

Identify potentially affected advice, communications, attachments, and circulation early. Assign counsel to assess proposed reliance and its implications before approving affected entries. Record the decision and scope; do not silently assume existing withholding remains appropriate.

Sources

• Federal Rules of Civil Procedure, December 1, 2025 edition: Rules 26(b)(5)(A), 26(f)(3)(D), and 34(b)(2), addressing claims, descriptions, planning, and response requirements.
• Northern District of California Patent Local Rules: Rules 1-2 and 3-2, addressing district-specific scope and the infringement claimant’s accompanying production obligations.

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.