How to prepare a document collection checklist for Copyright Infringement Matters

Prepare a copyright infringement document collection checklist by linking each asserted work and disputed use to records concerning creation, ownership, permission, copying, distribution, and remedies. Specify versions, custodians, repositories, date ranges, and collection methods, then assign responsibility for missing evidence and preservation concerns. The resulting deliverable is a source-linked table distinguishing requested, received, verified, and unresolved material. It should show counsel what has been collected, where it came from, what remains unavailable, and why each outstanding task matters.

When to use this workflow

Use this workflow when litigation counsel or an in-house team receives an infringement demand, investigates suspected copying, prepares discovery collections, or identifies gaps in existing evidence. Claimants need records supporting their rights and the accused use; responding parties also need independent-creation, permission, and use-context evidence.

The scope is collection planning and reconciliation, not an infringement determination or a complete discovery-response process. This general professional guide addresses US copyright law and federal district-court litigation. State proceedings, arbitration, Copyright Claims Board matters, foreign issues, controlling precedent, and governing orders require separate checks.

What you need

Start with an allegation or issue summary and assemble:

• Work inventory: titles, internal IDs, contributors, formats, versions, and registration references.
• Disputed-use inventory: accused actors, URLs, products, platforms, approximate dates, and available examples.
• Rights file: employment and commissioning records, assignments, licenses, amendments, schedules, and permission communications.
• Source map: creators, marketing staff, licensing personnel, finance staff, IT contacts, repositories, devices, and outside vendors.
• Collection constraints: requests and orders, existing collections, access restrictions, retention settings, and preservation concerns.

Identify available native creative files, version histories, registration deposits, publication records, distribution data, and financial records. Distinguish sources the client can access from opposing-party or third-party sources requiring another collection route. Missing inputs should become assigned tasks, not assumptions.

Use the template

Use the Copyright Infringement Matters — Document collection checklist below. You can copy this table into your working document or spreadsheet. Create one row per task with a distinct source, scope, and completion criterion.

Work / issue connects the task to an identified work, accused use, and investigative question. Records / scope specifies categories, versions, and periods rather than “all copyright documents.” Custodian / source distinguishes the person from the repository and identifies who controls access.

Use Evidence / locator for received document IDs and pinpoint references: a license clause, deposit page, video timestamp, code location, or collection-manifest entry. Before receipt, enter “not collected.” Status / gap distinguishes requested, received, verified, missing, and disputed material. “Verified” means checked against the collection task, not legally sufficient.

Record access, confidentiality, privilege, and deletion concerns under Risk / handling. Assign a responsible person or role and concrete next action. If useful, include an internal target date there; procedural deadlines must retain their separate authoritative source.

Step by step

1. Define the work and disputed-use units

Give each asserted work a stable ID. Distinguish drafts, published versions, adaptations, and accused versions. For software, identify the release or repository snapshot; for audiovisual material, the cut and timestamps; for photographs, the original and edited deliveries.

Identify the asserted exclusive right and material at issue. Sections 102(b) and 106 distinguish excluded ideas, systems, and similar subject matter from enumerated rights. Resemblance alone does not resolve infringement, and these provisions do not supply a universal similarity test. See 17 U.S.C. §§ 102 and 106.

Record: work and accused-use IDs, relevant versions, asserted rights, and the question each task addresses.

2. Map sources and flag preservation concerns

Interview people who created, approved, licensed, published, or distributed the work. Locate working files, delivery packages, platform histories, and correspondence. Separate a custodian’s knowledge from their ability or authorization to retrieve records.

Identify expiring links, overwritten histories, changing webpages, closed accounts, and departed employees’ repositories. Refer these facts promptly to counsel for preservation assessment. For vendor-held or inaccessible material, identify the contact and obstacle rather than marking the source empty. Do not direct staff to enter accounts without authorization.

Record: custodian–repository pairs, access limitations, retention information, collection route, and an owner for each preservation concern.

3. Specify creative, access, and publication records

Request native creative files, associated histories, and linked assets where relevant. Include drafts, source materials, collaboration records, delivery messages, and evidence of access or dissemination. Separate creation from later revision, transmission, and public availability.

For online uses, capture available content with its URL, capture date, account context, and collection method. A current screenshot does not establish first historical use. Seek historical captures, platform records, or delivery logs where appropriate, without assuming they exist.

Keep public display and statutory publication distinct: public display alone does not constitute publication under 17 U.S.C. § 101. Maintain untouched collected originals and identified working copies, with a collection log linking files to their sources.

Record: formats, version identifiers, capture details, access evidence, and unresolved publication or use dates.

4. Collect ownership, permission, and registration evidence

Organize rights records by contributor and transaction. Obtain executed instruments, incorporated schedules, employment or commissioning records, amendments, and permission communications. Commissioning or payment alone does not establish work-made-for-hire status; that status must satisfy § 101. Section 204 generally requires signed writings for ownership transfers, subject to its terms, but nonexclusive licenses are excluded from the statutory transfer definition. See 17 U.S.C. § 101 and §§ 201–204.

Collect certificates, applications, correspondence, deposits, and publication evidence separately. Section 411(a) generally conditions infringement actions concerning United States works on registration or preregistration, with exceptions and a refusal procedure. Section 412 separately restricts statutory damages and attorney fees through timing requirements and exceptions. See 17 U.S.C. §§ 411–412.

Record: covered works, rights, territory, term, instrument citations, missing schedules, registration references, and supported dates. Leave legal sufficiency for counsel’s analysis.

5. Include use context, defenses, and financial records

Collect evidence that qualifies or contradicts the initial account. Responding parties may have independent drafts, stock-asset permissions, agency instructions, or use restrictions. Claimants may hold authorized-use records or licensing discussions that affect scope.

For potential fair use, organize collection around purpose and character, the work’s nature, amount and substantiality used, and potential market effect. These are statutory factors, not automatic exemptions or a mechanical scoring exercise. See 17 U.S.C. § 107.

Request relevant distribution, sales, licensing, and cost records with data definitions and period boundaries. Distinguish transaction-level records from summaries; company-wide revenue should not substitute without explanation for work-specific information.

Record: issue served, period, business unit, favorable and adverse categories, and financial-data limitations.

6. Set collection boundaries and review handling

For federal discovery, assess relevance, privilege, and proportionality under Rule 26(b)(1). Tailor sources and periods to the issues and governing orders. If volume is uncertain, a bounded sample can inform scope; it should not silently become the completed collection.

Separate “not collected,” “collected pending review,” and “withheld from production.” Rule 34 requires specific objections and disclosure of whether responsive material is withheld on an objection. Rule 26(b)(5)(A) requires express protection claims and descriptions permitting assessment without revealing protected information. The checklist is not automatically a sufficient privilege record. See Rules 26 and 34.

Record: approved boundaries, exclusions and reasons, review restrictions, and references to separate response or privilege records.

7. Reconcile receipt and assign every gap

Check received material against scope. Flattened images do not complete a native-file request; an unsigned draft does not establish receipt of an executed agreement. Check attachments, linked assets, date coverage, readability, versions, and incomplete extracts.

Resolve discrepancies with custodians and retain their explanations. If records cannot be located, document repositories checked and remaining options. Counsel should decide whether further collection is warranted; a task owner should not infer that an unavailable record never existed.

Record: received document IDs, verified coverage, deficiencies, follow-up owners, and approved closure reasons. Keep unresolved questions visible at handoff.

Worked example

Fictional scenario: Harbor Lantern Studio alleges that Alder Vale Outfitters copied three illustrations into an online campaign. All parties, documents, and references below are fictional. Claimant’s counsel receives flattened images, one registration certificate, an unsigned assignment draft, and current campaign screenshots. These establish collection leads, not ownership or infringement.

The illustrator reports that layered originals remain in a former collaboration account. A studio project manager recalls a signed assignment but cannot locate it. The studio’s marketing employee captured the accused campaign and recalls earlier, different content. Counsel does not yet possess Alder Vale’s internal campaign records.

The gaps change collection priority. Account access receives early attention because retrieval may become harder. Ownership remains unresolved despite the draft. Current screenshots support only the captured content, not a historical use period. The certificate receives a separate task to verify covered works, deposits, and dates; it does not cure these deficiencies.

Common mistakes

• Collecting only similar excerpts. Obtain complete relevant works and surrounding use context, with exact comparison locations.
• Treating invoices as the rights file. Seek authorship, employment, assignment, and permission records; preserve unresolved questions.
• Collapsing dates. Separate creation, revision, publication, registration, capture, and alleged-use dates, each with source support.
• Closing tasks on receipt. Verify formats, attachments, versions, and date coverage against the request.
• Ignoring adverse evidence. Include permissions, independent drafts, differences, and contradictory communications.
• Confusing collection with production. Keep receipt, review, withholding, and production decisions distinct.

Final quality check

Before handoff, confirm:

• Every work and disputed use has a stable ID and version description.
• Each task identifies its custodian, repository, scope, and owner.
• Evidence references resolve to accessible files and accurate pinpoints.
• Native files and histories are collected or their absence explained.
• Rights instruments, schedules, registration materials, and dates are checked against sources.
• Relevant adverse evidence and defense categories are included.
• Preservation, privilege, confidentiality, and access concerns have assigned reviewers.
• Open issues have concrete next actions or express closure decisions accepting the documented gap.

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 review of collected copyright records. Use the Chronology Viewer to examine documented events and trial preparation capabilities to support evidentiary preparation. The checklist remains the team’s work product; counsel controls scope, missing-evidence decisions, and legal conclusions. To assess this collection-review workflow, book a demo.

Frequently asked questions

Should each copyrighted work have its own checklist?

Not necessarily. One table can cover related works if stable IDs preserve distinctions. Split tasks when contributors, licenses, versions, repositories, or uses differ materially; otherwise one completed row can conceal an uncollected work.

What if native files no longer exist?

Record who checked which sources and what remains available. Collect alternative versions and transmission or publication records. Do not relabel substitutes as originals or assume they resolve every creation and comparison question.

Should fair-use material wait until a defense is formally raised?

Consider it during planning when the known use makes it relevant. Collect surrounding commentary, full presentations, and distribution context before those sources disappear. Preserving facts does not decide the defense.

When is the collection checklist complete?

When scoped tasks are verified or expressly closed with reasons, and unresolved gaps have owners. Completion is relative to approved scope. New works, sources, allegations, or discovery requirements may require reopening particular tasks.

Sources

• Copyright Act, Chapter 1: §§ 101, 102, 106–107.
• Copyright Act, Chapter 2: §§ 201–204.
• Copyright Act, Chapter 4: §§ 411–412.
• Federal Rules of Civil Procedure: Rules 26 and 34.

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.