Build a copyright case chronology by separating each work’s creation, revision, publication, registration, alleged access, disputed use, licensing, and notice events. Tie every entry to an exact document version and pinpoint reference, distinguish documented dates from assertions or estimates, and retain contradictory evidence. The deliverable is a sortable, source-backed chronology that lets counsel test the sequence underlying ownership, copying, defenses, and remedies without turning factual inferences into findings. Each material unresolved event should carry a specific verification task and an accountable owner.
Use this workflow when an infringement demand, complaint, anticipated defense, or new production makes timing consequential. It serves outside counsel and in-house teams assessing which rights the claimant held, whether the accused party encountered the asserted version, what use occurred, and how permissions changed during that period.
Scope the chronology by asserted work, accused actor, and relevant period. Several revisions of one illustration should not become a single undifferentiated timeline. Repeated uses by different defendants likewise should not collapse into one “infringement” event.
This guide uses United States copyright law and federal evidentiary rules. State proceedings, arbitration, Copyright Claims Board matters, and foreign-law issues require separate checks. These are workflow recommendations, not prescribed legal requirements; controlling precedent, applicable contracts, local rules, and case-specific orders remain separate inputs.
Collect records establishing both the work’s history and the accused conduct:
Assign stable document IDs and work/version IDs before building rows. Retain untouched source files and record provenance. A screenshot’s capture date, the date displayed on the page, and the date of the underlying conduct may differ. Preserve the capture context, including the URL and available timestamp information, in the source record.
Define the immediate question—for example, whether a licensed preview preceded an allegedly unauthorized public release. That question determines the date range and collection priorities without excluding adverse evidence.
The companion template is Copyright Infringement Matters — Case chronology. You can copy this table into your working document or spreadsheet. Keep event IDs stable after sorting or inserting earlier events.
| Event ID | Date / basis | Work / version | Actor / event | Source / pinpoint | Status / conflict | Issue / significance | Next action / owner |
|---|---|---|---|---|---|---|---|
Date / basis records the event date and its foundation: native metadata, a contemporaneous message, later recollection, or an estimated range. State both event and document dates where necessary, preserving relevant time zones.
Source / pinpoint identifies a document ID or Bates number plus the page, paragraph, attachment, timestamp, frame, or file location supporting the entry. “Email chain” is insufficient when only one message supports the proposition. Cross-reference an attachment’s own document ID rather than treating it as part of the message without inspection.
Status / conflict distinguishes documented, corroborated, asserted, inferred, disputed, and unresolved propositions. A documented statement is not necessarily a verified event. Issue / significance explains relevance without deciding liability. Next action / owner assigns the missing check. Repeat work and actor identifiers so each row remains understandable when filtered.
Create an identifier for each asserted work and materially different version. Identify the alleged act and asserted exclusive right before reviewing chronology candidates. Sections 102(b) and 106 distinguish excluded ideas, systems, and similar subject matter from enumerated exclusive rights. Resemblance alone does not identify the protected material or right at issue; these provisions do not supply a universal substantial-similarity test. See 17 U.S.C. §§ 102 and 106.
Use neutral descriptions such as “uploaded image V3 to public product page,” not “infringed copyright.” Add a separate row when another actor, version, or act changes the proposition. Establish a version cross-reference using filenames and reliable file identifiers where available; similar filenames alone should not establish a match.
Record: work/version, actor/event, and issue being tested. Mark unidentified versions for resolution rather than assuming equivalence.
Review the complete source, including attachments and surrounding messages. Separate its date from the event described. A June email saying a file was delivered “last month” supports a reported May range, not a precise delivery date.
For native files, determine whether the available timestamp concerns creation, modification, export, upload, or collection. Do not select whichever timestamp best fits the theory. If sequencing depends on hours, reconcile time zones and document the conversion while retaining the original timestamp.
Where records conflict, cite both and explain whether they describe different events or genuinely inconsistent accounts. Do not resolve a discrepancy merely by choosing the earlier record.
Record: date or range, date basis, pinpoint, and status. Assign retrieval of the underlying log or a witness explanation when the distinction matters.
Place authorship, signature dates, stated effective dates, amendments, and permission changes on the timeline. Read work schedules and scope provisions alongside signatures. Payment or possession of a physical original should not substitute for copyright ownership evidence.
Section 201 addresses initial ownership, while §§ 202 and 204 distinguish physical-object ownership from copyright and generally require a signed writing for ownership transfers other than by operation of law. See 17 U.S.C. §§ 201–204. Work-made-for-hire status must satisfy § 101’s definition; commissioning or payment alone does not establish it. Section 101 also excludes nonexclusive licenses from its ownership-transfer definition, so do not extend § 204’s writing requirement to every permission. See 17 U.S.C. § 101.
Record: execution and effective-date events, covered versions, permission periods, and chain-of-title gaps. Assign questions about scope, retroactive wording, or termination effect to counsel; chronology entries do not resolve contract interpretation.
Build distinct entries for transmission, receipt, download, internal circulation, incorporation, and external release. A sent attachment does not necessarily establish opening; a public capture records observed content at capture time, not necessarily first appearance.
Link each accused-use entry to the compared version and exact location. Include evidence suggesting independent development or permitted use. If fair use is raised, collect dated evidence addressing purpose and character, the work’s nature, amount and substantiality used, and market effect. These are statutory factors, not a mechanical decision rule. See 17 U.S.C. § 107.
Record: separate access and use events, contrary sources, and the inference needed to connect them. For comparisons, cite specific pages, frames, timestamps, or file locations rather than recording only “similar.”
Keep application submission, registration decision, effective registration date, claimed publication, and alleged infringement commencement distinct. Do not relabel every public-looking distribution as legally established publication: § 101 expressly distinguishes public display alone from publication. See 17 U.S.C. § 101.
Section 411(a) generally conditions infringement actions concerning United States works on preregistration or registration, subject to exceptions and a refusal procedure. Section 412 separately restricts statutory damages and attorney fees by reference to registration, publication, and infringement commencement. Section 410(d) addresses effective registration dates. These dates have different functions; registration alone does not settle remedy eligibility. See 17 U.S.C. §§ 410–412.
Record: relevant dates and sources separately. Flag counsel’s statutory-pathway analysis and missing earlier-use evidence instead of marking remedies simply “available.”
Read the timeline chronologically, then filter by issue, work, actor, and source. Look for impossible sequences, unexplained version changes, missing intervals, and statements contradicted by contemporaneous records. Distinguish firsthand observations from accounts supplied by others.
For federal evidentiary planning, Rule 901(a) requires evidence sufficient to support that an item is what its proponent claims. Rule 602 generally requires a foundation for witness personal knowledge. Authentication alone does not resolve hearsay or every other admissibility question. See Federal Rules of Evidence 602 and 901.
Record: conflicting references and the specific foundation question. Assign a custodian inquiry, witness interview, or targeted document search—not merely “investigate.” Link witness accounts to statement paragraphs or transcript lines.
Have a second reviewer open sources for consequential events and verify wording, version, and date basis. Preserve unresolved contradictions instead of smoothing them into one narrative. Separate strategic comments from factual descriptions and review sensitivity and intended audience before sharing.
An internal chronology is not automatically a Rule 1006 evidentiary summary. That rule concerns voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced, and requires underlying originals or duplicates to be available to other parties. Illustrative aids are separately governed by Rule 107. See Federal Rules of Evidence 1006 and 107.
Record: completed checks and remaining actions with responsible reviewers. Retain a dated working version and correction history; use stable event IDs rather than spreadsheet row numbers for follow-up references.
Fictional scenario: Lumen Finch Studio alleges that Bracken Loop Goods used its “Harbor Pattern” illustration on an online product page beyond preview permission. All parties, documents, dates, and clause wording below are invented.
Counsel has a signed permission PDF, a delivery email and attachment, and a captured product page. The permission allows use “solely for internal packaging evaluation through March 31, 2025,” but its referenced work schedule is missing. The email identifies an attached preview; no opening record has been collected. The screenshot shows a pattern, but neither first upload nor a conclusive asset match is established.
| Event ID | Date / basis | Work / version | Actor / event | Source / pinpoint | Status / conflict | Issue / significance | Next action / owner |
|---|---|---|---|---|---|---|---|
| C-01 | Feb. 3, 2025; signatures | Harbor Pattern; version unresolved | Parties sign preview permission | F-01, pp. 1–2; § 2 | Referenced Schedule A absent | Stated limits identified; covered asset uncertain | Obtain executed schedule; ownership counsel |
| C-02 | Feb. 5, 2025; sent timestamp | HP-V2 preview | Studio emails Bracken design lead | F-02, message 1; attachment F-03 | Transmission documented; opening unverified | Potential access, not established viewing or copying | Seek receipt evidence; case associate |
| C-03 | Apr. 18, 2025; capture timestamp | Public image; version unresolved | Captured Bracken page displays pattern | F-04, capture p. 1 | Observed display; first upload unknown | Potential use beyond stated limits; match needed | Obtain release log and source asset; evidence lead |
The chronology changes the immediate decision. Counsel should not describe February 5 as proven viewing or April 18 as infringement commencement. April 18 follows the stated permission period, and public display differs from internal evaluation, but the missing schedule prevents a confident statement about the covered asset. The proposed requests therefore target the schedule, receipt evidence, and release history rather than assuming those facts.
Authorship, ownership, registration, and publication records remain collection gaps. None should be invented to complete the narrative. If later evidence establishes an earlier release, add that event and revise the related analysis without overwriting the capture entry.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, and chronology capabilities can support organizing copyright-specific events. Counsel should verify references, preserve version distinctions, and decide what each sequence establishes. The reviewed chronology can inform deposition and trial preparation. To discuss this workflow, book a demo.
Separate rows when actor, version, permission period, or timing matters. Group repetitive records only if the grouping preserves source traceability and does not conceal differences relevant to the analysis.
Use “date unresolved” or a supported range. Cite its basis and assign a verification task. Do not substitute collection dates for unknown event dates to simplify sorting.
One source may bear on both, but distinguish its propositions and limitations. Separate rows where different evidence or inferences support receipt, viewing, and incorporation; do not let chronological sequence substitute for proof.
Identify the instrument or communications, covered asset, dates, and competing readings. Flag missing attachments. Keep documented historical events separate from counsel’s authorization analysis, including questions requiring contract interpretation.
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.