Product
Analyze
Review
Produce
Draft
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 infringement document collection checklist by translating disputed uses, claims, defenses, and discovery requests into specific records, custodians, systems, and collection tasks. Separate ownership and historical-use evidence from marketing context, customer communications, and commercial data. For each task, record its scope, source, period, collection status, evidence references, and unresolved gaps. The resulting checklist should show what counsel sought, what arrived, what was verified, and who must address each limitation before the scoped collection can be closed.
When to use this workflow
Use this workflow when litigation counsel and an in-house team are planning an initial collection, responding to document requests, or investigating gaps in a trademark production. Claimant counsel needs records supporting asserted rights and challenged conduct; defense counsel needs evidence testing those assertions and supporting pleaded defenses.
This guide addresses US federal trademark litigation and federal district-court discovery, with an October 13, 2026 authority cutoff. Verify controlling precedent, local rules, standing orders, and case-specific orders. State courts, TTAB proceedings, arbitration, and pre-suit investigations require separate procedural decisions. This is a collection-planning workflow, not a complete preservation or production protocol.
What you need
Start with the operative pleadings, disputed marks, relevant products or services, served requests, and discovery tracker. Add preservation instructions, discovery agreements, and applicable orders.
Obtain a preliminary inventory of:
- Registration and application records, assignments, licenses, and relevant corporate entities.
- Mark-selection files, design versions, launch plans, packaging, advertisements, and marketplace accounts.
- Sales systems, product identifiers, geographic fields, distribution channels, returns, and adjustments.
- Customer-service platforms, complaint records, social accounts, and employees handling reported confusion.
- Marketing, sales, design, records-administration, distributor, and licensee contacts, including retention and access information.
Identify who maintains each source. Marketing may approve packaging while an outside designer retains editable files and a fulfillment provider holds shipment images. Those require separate tasks. Include source categories relevant to pleaded defenses, rather than treating the claimant’s allegations as the entire collection scope.
Use the template
Use the Trademark Infringement Matters — Document collection checklist below. You can copy this table into your working document or spreadsheet. Create one row per source and collection task; split rows when custodians, systems, periods, or access conditions differ.
| Task ID | Issue / request | Records / scope | Custodian / system | Period / versions | Status / evidence | Gap / handling | Owner / next action |
|---|---|---|---|---|---|---|---|
“Records / scope” should identify actual objects: carton artwork for specified products, not merely “branding.” “Period / versions” captures historical coverage. “Status / evidence” records collection status, date, batch identifier, and stable document IDs with page, image, or spreadsheet-cell references.
Use “Gap / handling” for missing periods, uncertain provenance, access restrictions, or restricted-review routing—not privileged advice or a substitute privilege log. “Owner / next action” identifies an accountable person, action, and target date. Keep unresolved tasks open, or expressly classify them as documented exceptions rather than verified collections.
Step by step
1. Define the disputed uses and factual questions
Identify each mark variant, product or service, channel, geography, and alleged period. Distinguish registered-mark allegations from other theories. Section 1114(1)(a) addresses specified unauthorized commercial uses of registered marks likely to cause confusion, mistake, or deception; resemblance alone does not establish infringement. See 15 U.S.C. §1114. (govinfo.gov)
Section 1125(a)(1)(A) addresses specified uses causing likely confusion about affiliation, connection, association, origin, sponsorship, or approval without requiring federal registration in its text. The statute does not prescribe a universal confusion-factor test. See 15 U.S.C. §1125. (govinfo.gov)
Translate allegations and defenses into collection questions: Which packaging reached customers? Who controlled the listing? What records support an asserted earlier use? Use controlling precedent to refine issue priorities.
Record: issue codes, request references, challenged uses, and factual boundaries.
2. Map custodians to original sources
Interview people responsible for brand decisions, sales, customer communications, and records administration. Locate email, messaging, shared drives, design repositories, marketplace accounts, archives, and physical samples. Ask whether records sit with former employees or outside providers.
Separate company advertising from reseller listings and unrelated third-party references. Identify access arrangements for distributor and licensee records; a business relationship alone should not be treated as proof that records are retrievable. Refer uncertain access and control questions to counsel.
Ask about overwritten listings, account deletion, retention settings, and migrations. Escalate preservation concerns promptly; do not let this inventory delay preservation decisions or authorize uncontrolled changes to retention settings.
Record: custodian/system pairings, access contacts, source limitations, and preservation escalations.
3. Set periods and collection boundaries
Select periods around mark selection, claimed first use, launch, territorial expansion, notice, redesign, and discontinuation. An older ownership or assignment record may matter even when challenged sales fall within a shorter period.
Rule 26(b)(1) defines discovery by nonprivileged relevance and proportionality, without requiring admissibility. Use that framework to assess breadth and retrieval burden. Rule 34(b)(2) requires specific objections and identification of withholding based on objections; verify response and production timing against the rule and applicable orders or stipulations. See Federal Rules of Civil Procedure, Rules 26 and 34. (uscourts.gov)
Test proposed search terms against known documents, including supported mark variants, campaign names, and product codes. Record missed examples and adjust before relying on the search boundary.
Record: periods, versions, search-method references, exclusions, and counsel’s reasons for limitations; cross-reference the response tracker.
4. Collect disputed uses with their context
For online uses, retain contextual captures showing URL, capture time, seller identity, product identifier, surrounding text, and disclaimers. Record geography where known and relevant. Keep available source files and account history separately from screenshots.
For physical uses, identify packaging versions, sample provenance, print identifiers, and records connecting versions to distribution. Distinguish creation, revision, capture, and shipment dates. A newly collected image cannot, by itself, establish when its contents first reached customers.
Record collection methods and knowledgeable contacts. Evidence Rule 901 requires support for finding that an item is what its proponent claims; authentication does not resolve all admissibility questions. See Federal Rules of Evidence, Rule 901. (uscourts.gov)
Record: provenance, stable evidence references, version uncertainty, and foundation questions.
5. Collect customer and commercial records without overstating them
Collect complete service threads, tickets, available recordings, and attachments—not favorable excerpts alone. Separate customer statements from employee paraphrases and later summaries. Link duplicate reports and retain contrary evidence.
Ask which product, advertisement, or seller the customer encountered. A return-address inquiry may not establish the alleged confusion. Rules 602 and 801–802 address personal knowledge and hearsay; admissibility analysis depends on the proposed use of the statement. See Federal Rules of Evidence, Rules 602 and 801–802. (uscourts.gov)
For commercial data, obtain field definitions, product mappings, transaction periods, and explanations of returns and adjustments. Keep raw extracts distinguishable from business summaries. Do not label a sales total as recoverable damages.
Record: system identifiers, linked records, duplicate risks, data definitions, and questions for business contacts.
6. Route sensitive materials for legal review
Clearance and mark-selection files may combine legal communications with business discussions. Preserve document families and participants’ roles so reviewers can assess context. Treat confidentiality restrictions separately from privilege questions.
Rule 26(b)(5)(A) requires an express protection claim and descriptions allowing assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method; neither establishes substantive privilege or universal log columns. See Federal Rules of Civil Procedure, Rule 26. (uscourts.gov)
Record: restricted-review routing, responsible lawyer, and a nonrevealing handling note. Keep sensitive advice outside the broadly circulated checklist.
7. Reconcile the collection and assign gaps
Compare received batches with expected custodians, periods, products, and versions. Check attachments, export fields, and whether packaging files represent distributed designs or unused proposals. Reconcile extracts to available system totals, explaining discrepancies rather than silently adjusting them.
Use precise statuses: “requested,” “received,” “verified,” “unavailable,” and “counsel-limited.” Receipt is not verification. If an interview suggests an earlier listing existed but no source is located, preserve that distinction instead of inventing a launch date.
Record: batch references, reconciliation results, missing evidence, retrieval attempts, and next actions with owners and target dates. Close verified tasks separately from unresolved exceptions and downstream review or production work.
Worked example
Fictional scenario: Alder Finch Goods alleges that Harbor Vale Supply’s NORTHBRIAR kitchen-storage packaging infringes its NORTH BRIAR mark. Defense counsel is collecting records for a disputed January–June 2026 launch period and July 2026 notice. All parties, marks, documents, and facts are fictional.
Marketing supplies revision C artwork dated January 8, but no shipment record connects it to distributed cartons. Sales supplies an August company-storefront capture. Customer service supplies two July tickets: HV-021 contains a customer’s original message and third-party seller screenshot, HV-022; HV-023 is an internal escalation repeating that report.
| Task ID | Issue / request | Records / scope | Custodian / system | Period / versions | Status / evidence | Gap / handling | Owner / next action |
|---|---|---|---|---|---|---|---|
| TC-01 | Packaging / RFP-4 | Carton artwork; distribution records | Marketing / design drive | Jan–June; A–C | Received: HV-001 p. 1, revision C | A–B missing; artwork proves no shipment date | Marketing lead: seek printer and shipment records by Oct. 16 |
| TC-02 | Listings / RFP-7 | Company and reported seller listings | Sales / storefront | Jan–July | Partial: HV-014 August capture; HV-022 screenshot | Historical content and third-party control unverified | Sales lead: seek account history and seller identity by Oct. 19 |
| TC-03 | Confusion / RFP-9 | Tickets, attachments, linked orders | Service / ticket platform | July | Received: HV-021–023 | Escalation duplicates report; exposure unclear | Service manager: locate order and original contact details by Oct. 16 |
TC-01 directs counsel toward operational evidence rather than more artwork copies. TC-02 prevents an August capture from substituting for launch-period evidence and separates company use from third-party material. TC-03 identifies one reported incident, not two independent incidents, while leaving exposure unresolved. None establishes the launch date or the legal significance of the customer’s statement.
Common mistakes
- Collecting only certificates and logo images. Add ownership history, actual uses, products, channels, and records addressing pleaded defenses.
- Using current captures as historical proof. Label capture dates and seek historical account or distribution records.
- Searching only the exact mark. Test supported variants, product codes, and campaign names against known records.
- Equating ticket counts with incidents. Link originals, forwarded reports, and internal escalations before counting.
- Closing tasks on receipt. Verify coverage and attachments; document missing sources and limitations separately.
Final quality check
- Every task links to an issue, defense, or request.
- Marks, entities, products, and channels are identified consistently.
- Sources have custodians, periods, access contacts, and statuses.
- Evidence IDs resolve to correct files and pinpoints.
- Event, creation, capture, and collection dates remain distinct.
- Sensitive materials have appropriate review routing.
- Open issues have owners and dates; accepted limitations have recorded counsel decisions.
- Legal propositions and procedural assumptions match primary authorities and applicable orders.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, chronology, and evidence analysis capabilities can support examination of collected materials. Use chronology support to assist document-linked analysis; the checklist remains the team’s work product. Counsel retains responsibility for collection scope, verification, privilege decisions, and unresolved gaps. Book a demo to discuss this workflow.
Frequently asked questions
Should claimant and defense counsel use different checklists?
Use the same structure with different priorities. Claimant counsel may emphasize ownership and customer exposure; defense counsel may emphasize selection history, use context, and contrary evidence. Include supporting and adverse material within the defined scope.
How should unavailable historical listings be recorded?
Identify the account, expected period, retrieval attempts, and contacts consulted. Mark content unavailable or unresolved; do not substitute a current capture without explaining its limits.
Should clearance communications be excluded from collection?
Do not decide from the folder name alone. Route potentially protected material for counsel-directed handling while retaining context and family relationships. Collection, privilege assessment, and production are separate decisions.
When is the checklist complete?
A scoped collection closes when tasks are verified or expressly limited by counsel. A checklist may be handed over with assigned exceptions, but those tasks remain unresolved. Neither milestone establishes completion of review or production.
Sources
- 15 U.S.C. §1114 — Registered-mark infringement
- 15 U.S.C. §1125 — False designations of origin
- Federal Rules of Civil Procedure — Rules 26 and 34
- Federal Rules of Evidence — Rules 602, 801–802, and 901
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.
