Build a trademark infringement chronology by separating events from document creation and capture dates, preserving each mark’s commercial context, and linking every substantive entry to identifiable evidence. Organize the record around adoption, documented use, territorial and channel expansion, customer contacts, notice, and changes to challenged presentations. Preserve competing accounts rather than selecting an unsupported date. The resulting deliverable is a source-linked chronology that helps counsel test factual positions, identify missing proof, and prepare witness questions without turning allegations or metadata into established facts.
Use this workflow when litigation counsel or an in-house team investigates a demand, evaluates competing use histories, or prepares testimony about a challenged mark. It is particularly useful when packaging, websites, marketplace listings, and sales records show different presentations over time.
The scope is US federal trademark disputes, with federal district-court procedure where discussed. State litigation, TTAB proceedings, and arbitration require separate procedural checks. Counsel should verify controlling precedent, local rules, and case-specific orders. This guide addresses factual organization, not a particular matter’s merits.
Section 1114(1)(a) addresses specified unauthorized uses in commerce of registered marks likely to cause confusion, mistake, or deception—not resemblance alone. Capture the goods, activity, and surrounding presentation, not merely side-by-side logos. See 15 U.S.C. §1114(1)(a).
Assemble sources that establish the sequence and materials that challenge it:
Include both sides’ use histories. Separate planned launches from completed publication or transactions. Seek native records or document families when an isolated screenshot or attachment lacks context. Identify who controlled each disputed presentation: a party, distributor, reseller, or unrelated third party.
The companion template is Trademark Infringement Matters — Case chronology. You can copy this table into your working document or spreadsheet. Maintain one row per discrete event, with linked event IDs for related developments.
| Event ID | Event date / basis | Record / capture dates | Event / use context | Source / pinpoint | Issue / position | Status / conflict | Foundation / limits | Action / owner |
|---|---|---|---|---|---|---|---|---|
“Event date / basis” records the date and why it is assigned. Label estimates and bounded ranges; never convert an approximate month into an invented day. In “Record / capture dates,” distinguish creation from collection, labeling each when both are available.
“Event / use context” identifies the mark version, goods, channel, territory, and actor. “Source / pinpoint” contains a retrievable identifier and page, image, or transcript reference. “Issue / position” explains the proposition supported or challenged. Use “Status / conflict” to distinguish documented events, reported accounts, inferences, and disputes—not to declare a legal conclusion.
Reserve “Foundation / limits” for provenance, knowledge, and evidentiary questions. Each unresolved point needs an action and responsible person or role. Keep any sort key separate from the supported date so spreadsheet ordering does not manufacture precision.
Identify which sequences matter: mark selection, each party’s documented use, product and territorial expansion, customer exposure, notice, and subsequent changes. Include ownership transitions or licensing events when relevant to the asserted history.
Distinguish registered-mark allegations from other pleaded theories. Section 1125(a)(1)(A) addresses likely confusion concerning affiliation, connection, association, origin, sponsorship, or approval without making federal registration a textual condition. It does not prescribe a universal multifactor test. See 15 U.S.C. §1125(a)(1)(A).
Record: Give each entry an issue and identify the position it supports or challenges. Keep circuit-specific legal analysis outside the factual description. Do not label an early document as establishing legal priority without separate analysis.
Assign stable identifiers before extracting events. Preserve email headers and attachments, transcript page and line references, and complete webpage captures rather than cropped logos. Record who collected online material, when, and from which URL; note location or account-dependent presentation where known.
Identify missing marketplace history, packaging versions, and distributor records. Absence from the reviewed collection does not establish that an event never occurred.
Federal Rule 26(b)(1) limits discovery to relevant, proportional, nonprivileged material; discoverability does not require admissibility. Use gaps to formulate focused requests rather than an unlimited search. See Federal Rule of Civil Procedure 26(b)(1).
Record: Enter source IDs, pinpoints, provenance limitations, and an owner for obtaining missing context. Identify the reviewed collection’s boundaries alongside the table.
Read each source for its actual temporal proposition. An April email recalling a February launch is an April account of February, not contemporaneous February documentation. A packaging file’s creation may precede manufacturing, shipment, and consumer exposure.
Retain conflicting accounts in linked rows. State whether dates are explicit, inferred, approximate, or disputed, and explain material inferences. Preserve time zones when sequence within a day matters.
A single document may support several events; give each its own row rather than compressing planning, publication, and sales into one “launch” entry.
Record: Populate both date fields and explain conflicts. Describe an earliest located transaction as the earliest found in the reviewed records, not necessarily the first transaction ever.
Trace material changes in wording, logos, packaging, goods, channels, territory, and seller control. Separate an online advertisement from an order and from the packaging actually delivered. Include surrounding disclaimers and other branding rather than extracting the challenged mark alone.
Likewise, separate a redesign approval from evidence of implementation. For notice, distinguish dispatch, receipt, and response when the records support different dates. Record a removal instruction separately from proof that a listing disappeared.
Record: Create version-specific entries identifying the actor and commercial context. Flag intervals with unknown presentation. Assign a targeted check, such as locating fulfillment records or a distributor’s archived catalog.
Assign each incident an identifier. Capture the speaker, date, product, channel, apparent exposure, and whether the record describes an origin, affiliation, or sponsorship concern—or simply an inquiry. Link forwarded reports to the original incident rather than counting them repeatedly.
Separate customer messages from employee recollections and counsel summaries. Rules 602 and 801–802 require attention to personal knowledge and purpose-specific hearsay analysis; reported incidents are not categorically admissible or excluded. See Federal Rules of Evidence 602 and 801–802.
Record: Describe the contact neutrally, identify the knowledge chain, and assign missing-original or witness follow-up. Preserve clarifying responses and contrary evidence with the incident.
Review by issue as well as date. Compare launch plans with transactions, expansion claims with distributor records, and cessation assertions with later captures. Preserve adverse evidence with the same specificity as favorable material.
Ask narrow questions: Who published this listing? Which packaging accompanied this order? What supports the asserted launch date? Rule 901 requires evidence sufficient to support a finding that an item is what its proponent claims; authentication alone does not resolve other admissibility questions. See Federal Evidence Rule 901.
Record: Identify a potential knowledgeable witness, the unresolved foundation, and the next document or interview request. Keep counsel’s assessment separate from the source-backed event.
Open every cited source and verify the pinpoint, date proposition, and context. Reconcile duplicate incidents and retain competing accounts. Record version date, inclusion criteria, and collection boundaries so additions do not silently alter “earliest documented” assertions.
Specify intended use. Rule 1006 governs qualifying summaries of voluminous admissible materials and requires access to underlying originals or duplicates; Rule 107 separately governs illustrative aids, which are not evidence. An internal chronology does not qualify merely because it is formatted as a chart. See Federal Evidence Rules 1006 and 107.
Record: Resolve each open item or assign an owner and next step. Check audience restrictions before circulating a version containing protected material or counsel’s analysis.
Fictional scenario: Alder Finch Goods challenges Brindle Orchard Supply’s use of MOSS HARBOR on insulated bottles, alleging conflict with Alder Finch’s MOSS HARBOUR branding. All parties, marks, documents, and events in this example are fictional; all dates below are in 2025.
Brindle Orchard’s April 2 response asserts a February 3 storefront launch. A January planning email proposes that date. Counsel also locates a February 19 order and a March 8 storefront capture, each recorded separately in the full chronology. Neither establishes the asserted February 3 publication. A customer ticket and a later reseller-removal instruction raise additional questions. These are three representative entries, not the complete chronology.
| Event ID | Event date / basis | Record / capture dates | Event / use context | Source / pinpoint | Issue / position | Status / conflict | Foundation / limits | Action / owner |
|---|---|---|---|---|---|---|---|---|
| TM-001 | February 3, asserted launch | Response: April 2; planning email: January 22 | Alleged MOSS HARBOR bottle storefront launch; territory unspecified | BO-140 p. 2; BO-014 p. 1 | Tests launch assertion | Response asserts completion; email shows planning only | No publication history; later order and capture do not establish this date | Seek storefront publication history / associate |
| TM-002 | March 12 ticket entry; call date unconfirmed | Ticket: March 12 | Agent reports caller asking whether sellers are related | BO-121 p. 1 | Possible affiliation concern | One reported inquiry; original wording unverified | No recording located; exposure source unknown | Interview agent; seek recording and customer contact / investigator |
| TM-003 | April 4, instruction date | Email: April 4 | Brindle Orchard directs reseller to remove bottle listing | BO-173 p. 1 | Tests cessation account | Instruction documented; implementation unknown | Reseller controls page; no later capture supplied | Seek response and listing history / associate |
The evidence changes preparation priorities. Counsel should not present February 3 as a proven launch or April 4 as proven cessation. The ticket warrants investigation without becoming established confusion. Missing publication history, exposure evidence, and reseller confirmation remain explicit gaps, not facts supplied by inference.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, chronology, evidence analysis, privilege and confidentiality analysis, and deposition preparation. Use its chronology capabilities to support factual organization and trial preparation capabilities for related witness work. Counsel retains responsibility for source verification, competing accounts, and evidentiary judgments. To discuss this workflow, book a demo.
Use the supported event date or labeled range. Preserve the asserted launch date and its source as a competing account. Never invent precision for sorting convenience.
Include relevant listings, identifying reseller control and uncertainty about authorization or timing. Do not silently attribute their exact presentation to the opposing party.
State what the record says, identify speakers and intermediaries, and link originals where available. Record exposure gaps and contrary evidence; assess evidentiary use separately.
Potentially, after a separate assessment of purpose, underlying materials, and applicable rules. An internal table is not automatically a Rule 1006 summary, and an illustrative aid is not evidence.
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.