Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Prepare a trademark privilege review log by connecting each proposed withholding or redaction to its source, participants, asserted protection, and a description that permits assessment without exposing protected substance. Review clearance communications, brand-selection records, enforcement correspondence, and customer-confusion investigations component by component, preserving document-family context. The deliverable is an external log reconciled with production, supported by a separate internal decision record that identifies factual gaps, approval decisions, and responsibility for resolving open issues within the applicable discovery schedule.
When to use this workflow
Use this workflow when outside counsel, in-house counsel, and discovery teams must explain privilege-based withholding or redactions in a trademark infringement action. It is particularly useful when legal consultation overlaps with packaging approval, marketplace enforcement, licensing, or customer-service investigations.
The procedure assumes US federal district-court litigation. Rule 26(b)(5)(A) requires an express protection claim and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method. These provisions do not establish substantive attorney-client privilege or prescribe universal log columns. Verify controlling law, local rules, and case-specific orders. Federal Rules of Civil Procedure, Rule 26
Trademark subject matter identifies review targets, not privilege outcomes. Section 1125(a)(1)(A), for example, addresses specified uses creating likely confusion concerning affiliation, origin, sponsorship, or approval. Licensing discussions and customer contacts may therefore deserve focused review; that statutory relevance does not establish protection. 15 U.S.C. § 1125
For state litigation, TTAB proceedings, arbitration, or pre-suit investigations, verify the applicable procedure separately.
What you need
Assemble these inputs before drafting descriptions:
- Discovery framework: requests, responses, scheduling orders, logging agreements, production scope, and verified compliance dates.
- Source records: native files or reliable review copies, metadata, complete headers, attachments, thread relationships, custodian information, and stable document identifiers.
- Trademark materials: clearance searches, proposed names, packaging revisions, takedown instructions, enforcement correspondence, confusion reports, and licensee or distributor communications.
- Participant directory: names, organizations, roles at the communication date, counsel relationships, and unresolved identities, including outside designers and agencies.
- Decision instructions: counsel-approved privilege criteria, redaction conventions, duplicate and family treatment, escalation owners, and approval responsibilities.
Maintain an access-controlled internal record separately from the external log. Substantive advice, possible disclosure concerns, and detailed legal reasoning should not migrate into the served version simply because they helped reviewers reach a decision.
Use the template
The companion template is Trademark Infringement Matters — Privilege review log. Copy this table into your working document or spreadsheet. Use it as an internal master, then prepare an external version matching the governing protocol.
| Log ID | Document / family | Date / type | Participants / roles | Protection / treatment | Nonrevealing description | Source / verification | Decision / owner |
|---|---|---|---|---|---|---|---|
Assign a stable log ID independently of production numbering. Identify each message or file and its family relationship. For redactions, record a page, paragraph, or other reproducible location; do not cite only an entire document set.
Capture actual authors, senders, recipients, and copied recipients as relevant, with roles verified at the communication date. A linked participant directory can supply repeated role information if the protocol permits. Distinguish asserted protection from treatment: withholding, partial redaction, release, or pending review.
The description explains purpose without revealing advice. Source / verification records supporting locations and factual gaps; Decision / owner records approval, next action, and responsibility. Those internal fields may be unsuitable for service. Add separate date or recipient fields where required rather than compressing information beyond usability.
Step by step
1. Establish the logging protocol and review boundary
Read requests, responses, orders, and logging agreements together. Confirm covered custodians and productions, required fields, delivery dates, and treatment of redactions, duplicates, attachments, and email chains. Do not assume that categorical logging or exclusion of post-filing counsel communications is authorized.
Reconcile the log with discovery responses. Rule 34(b)(2) requires specific objections and disclosure of whether responsive materials are withheld on an objection; a privilege log does not replace those responses. Federal Rules of Civil Procedure, Rule 34
Record: link a protocol note to the master table, identifying the review population, compliance dates, and owner of each unresolved procedural question.
2. Organize trademark records into reviewable families
Group communications with attachments and relevant thread context. A clearance email may attach a search report, label mockup, and sales forecast. Inspect each component rather than assigning one result to the bundle.
Keep standalone versions identifiable. Distinguish a marketplace screenshot from counsel’s annotated copy, and trace the same asset across marketing and legal files. Missing attachments are collection gaps, not evidence of their presumed contents. Use family links to navigate related records without obscuring component-level decisions.
Record: document and family IDs, component types, missing items, and exact proposed redaction locations. Explain divergent treatment of apparently identical copies internally.
3. Verify participants and communication purpose
Check complete headers and available role records. Trademark files frequently involve designers, advertising agencies, distributors, licensees, and marketplace vendors. Identify each person’s organization and function at the time, not merely their current title.
Ask whether the communication concerns legal advice, commercial mark selection, routine enforcement administration, or mixed purposes. Where outside participants appear, gather engagement and distribution facts for counsel’s assessment under controlling law. Do not infer the outcome solely from a lawyer’s presence or an unfamiliar email domain.
Record: verified identities, roles, factual purpose, header or directory citations, and unresolved distribution questions with assigned owners.
4. Assess the protection against the actual content
Read the complete record before proposing attorney-client privilege or work-product protection. Keep confidentiality designations separate from the protection decision; flag sensitive launch plans and sales figures for their appropriate review rather than automatically labeling them privileged.
For proposed work product, document who prepared the material, why, and the litigation context. Rule 26(b)(3) addresses qualifying materials prepared in anticipation of litigation or for trial and includes conditions for discovery despite that protection. A creation date alone does not establish the required context. Federal Rules of Civil Procedure, Rule 26(b)(3)
For confusion investigations, inspect original customer messages separately from counsel’s questions and summaries.
Record: proposed basis, internal factual reasoning, component-level treatment, and approving counsel.
5. Draft descriptions that explain without disclosing
Describe document type, relevant participants, general subject, and supported legal purpose. “Email requesting legal advice concerning clearance of a proposed travel-bag mark” is more useful than “privileged email,” without stating the advice.
Do not reveal counsel’s confusion analysis, settlement recommendation, or investigative conclusions. Conversely, do not manufacture a legal purpose for routine packaging approval. Have a second reviewer compare the description with the source and proposed claim, using Rule 26(b)(5)(A)’s assessment requirement as the procedural benchmark. Federal Rules of Civil Procedure, Rule 26(b)(5)(A)
Record: the proposed external description, source location, verification decision, and necessary revisions. Keep substantive reasoning in the internal record.
6. Reconcile decisions with the production and external log
Compare approved entries against the actual production set. Confirm that redacted pages match logged locations, released attachments are not described as withheld, and duplicate or forwarded copies have consistent or explained treatment.
Keep pending decisions internal with named owners. An unresolved spreadsheet status is not a final protection claim. Counsel must address its effect on compliance timing. Before service, remove internal commentary and inspect the external file itself, including hidden columns, comments, and unintended content.
Record: final disposition, production or redaction references, discrepancy resolutions, approval status, and responsibility for any outstanding action.
Worked example
Fictional scenario: Aster Quay Goods sues Bracken Vale Supply over the fictional HARBORTHREAD mark for travel bags. All parties, people, documents, and communications below are invented. Defense counsel reviews naming files, packaging correspondence, and a customer-confusion investigation.
An email requests clearance advice and attaches an unannotated mockup intended for public packaging. A later packaging thread includes an outside designer whose engagement role is unclear. A counsel memorandum references customer messages missing from the collected family. These records require different decisions, not a single “legal file” classification.
| Log ID | Document / family | Date / type | Participants / roles | Protection / treatment | Nonrevealing description | Source / verification | Decision / owner |
|---|---|---|---|---|---|---|---|
| PL-001 | BV-014 / F-014; attachment BV-015 | Feb. 4, 2026 / email | Sender Mara Pell, brand director; recipient Owen Rusk, outside counsel | Attorney-client / email withheld after approval | Email requesting legal advice on clearance of proposed travel-bag mark | BV-014, p. 1; headers and roles verified; BV-015 separately inspected | Rusk approves email claim after content and distribution review; production lead releases unannotated mockup |
| PL-002 | BV-088 / F-088 | Mar. 12, 2026 / chain | Sender Pell; recipient Nia Venn, outside designer; counsel Rusk copied | Pending / no final assertion | Packaging-revision correspondence; purpose under review | BV-088, pp. 1–4; designer’s engagement role unresolved | Review lead obtains engagement and distribution facts; Rusk determines protection and treatment |
| PL-003 | BV-203 / F-203 | June 9, 2026 / memorandum | Author Rusk; recipient Ivo Marr, general counsel | Work product proposed / pending approval | Counsel memorandum concerning investigation of reported customer confusion for infringement defense | BV-203, pp. 1–3; referenced customer-message attachment missing; preparation context requires verification | Rusk verifies preparation purpose; collection lead locates messages for separate review |
PL-001 separates the consultation from the design asset. Its approval rests on the fictional content and distribution review, not merely the presence of outside counsel. PL-002 remains unresolved because neither the designer’s title nor copied counsel supplies the missing role facts. PL-003 distinguishes the memorandum from underlying messages that reviewers have not seen.
Only PL-001 is ready for the external log after formatting and production reconciliation. The other entries remain internal pending decisions; counsel must resolve or otherwise address them within the applicable schedule. The missing attachment does not justify describing its contents or claiming it was reviewed.
Common mistakes
- Withholding an entire clearance family. Inspect search materials, mockups, forecasts, and consultation separately; document each component’s treatment.
- Putting trademark-merits conclusions in descriptions. Describe the legal purpose without revealing advice about confusion, ownership, or defenses.
- Ignoring agency or licensee recipients. Verify roles, engagement facts, and distribution before counsel decides the protection claim.
- Treating confidentiality as the privilege rationale. Keep commercial sensitivity and protection analysis in separate fields and review paths.
- Serving internal uncertainty as a completed claim. Resolve pending entries or obtain counsel’s direction on appropriate procedural treatment; remove internal analysis from the external file.
Final quality check
- Every final assertion has counsel approval grounded in the actual source.
- Stable document and family IDs lead to reproducible locations.
- Dates, authors, recipients, and roles match verified records.
- Descriptions explain the claim without exposing protected substance.
- Attachments, duplicates, and redactions have reconciled treatment.
- The external log matches production, discovery responses, and the governing protocol.
- Missing evidence and open issues are resolved or expressly assigned, with counsel addressing compliance implications.
- The served file contains no internal reasoning, hidden review notes, or unintended content.
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 that support to examine trademark records while retaining counsel’s responsibility for protection decisions, descriptions, and protocol compliance. The template remains your work product. Explore litigation preparation or book a demo to discuss this review workflow.
Frequently asked questions
Should every trademark clearance document appear on the privilege log?
Use the document’s contents, actual withholding, and applicable protocol—not its folder name—to decide. Keep released materials in the internal reconciliation record where useful, without presenting them as withheld in the external log.
How should we handle a thread involving a design agency?
Preserve the thread and verify the agency’s role, engagement, and distribution. Counsel should assess those facts under controlling law. Record uncertainty internally rather than assuming that agency participation either establishes or defeats protection.
Can one entry cover an entire email chain?
Verify the permitted method under applicable requirements and agreements. Even where grouping is permitted, retain internal component-level detail sufficient to explain changed recipients, separate attachments, and different redaction decisions.
Should customer-confusion reports receive the same treatment as counsel’s summary?
Review them separately. Identify each record’s creator, purpose, distribution, and source location. A proposed claim for counsel’s summary does not decide treatment of underlying messages; absent messages remain collection gaps until obtained and reviewed.
Sources
- Federal Rules of Civil Procedure — Rules 26 and 34: privilege-claim descriptions, compliance planning, trial-preparation materials, and document-request responses.
- 15 U.S.C. § 1125(a)(1)(A): statutory context for confusion concerning affiliation, origin, sponsorship, and approval.
Scope: General professional workflow guidance using an October 13, 2026 research cutoff; protection decisions depend on applicable law and verified matter-specific facts.
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.
