Intraspexion intraspexion.com
Published 20 Nov 2026 11 min read

eDiscovery in fashion and apparel disputes: where the evidence lives

A practical framework for locating, preserving, and reviewing the visual, time-sensitive evidence that drives fashion, trade-dress, and counterfeit disputes.

eDiscovery in fashion and apparel disputes: where the evidence lives

Fashion disputes do not reduce neatly to document-heavy commercial litigation. The central evidence is visual: a silhouette, color combination, textile motif, packaging treatment, campaign image, or product arrangement. It is also time-sensitive. A design may move from a mood board to a sketch, then a tech pack, sample, approval, production order, product page, social post, and wholesale catalog before the allegedly competing product reaches the market.

Those transitions can expose both priority and copying. In a design-infringement or trade-dress dispute, the contest is often over who developed the relevant look first and how closely an accused version tracks the claimant’s design history. In a counterfeit dispute, the evidence may instead connect a seller or supplier to unauthorized production, distribution, listing, or marketing. Across both settings, dates, versions, approvals, and provenance carry substantial weight. Trends also move in weeks, so a collection containing only the final product images may omit the context needed to reconstruct when a design appeared and how it developed.

Where the electronically stored information actually sits#

A sound collection plan starts with the product’s digital lifecycle rather than a generic list of custodians. The useful questions are where each design artifact was created, which systems retained it, who changed it, and which records distinguish an original from a later iteration. Data from different sources may establish different parts of the same story. The following locations should be examined against the actual business process for the brand at issue.

Design files and tech packs#

Design teams commonly work with layered artwork, pattern files, colorways, specifications, comments, and revision histories. Those layers may separate the original ornament from later adjustments to color, placement, or scale. They may also identify the working file associated with a sample or production run. Tech packs add another dimension by tying visual design to materials, dimensions, construction details, and factory revisions.

Flattening a design to a PDF at collection can remove exactly the information a dispute needs. The resulting document may look like the design while discarding editable layers and relationships to source files. A flattened image also does not, by itself, establish when the underlying design was created or altered. Collection should therefore consider whether native files and their associated metadata can be exported and reviewed alongside any more portable image versions. Where a team used a design or pattern application, the inquiry also needs to address account data, shared workspaces, version history, and the relationship between cloud records and locally stored copies.

Product lifecycle and sourcing systems#

Sample requests, supplier messages, approvals, purchase orders, and factory communications frequently hold the clearest narrative of development. They can show when a concept was communicated outside the design team, which revisions were requested, and whether a third party had access to protected material. The records may sit in enterprise applications, email, messaging platforms, or shared manufacturing portals rather than in one easily searched system.

These records also introduce practical collection problems. Communications may cross time zones and languages, causing names, dates, and product identifiers to vary between systems. A supplier may identify a style by an internal number while a sales team uses the product name and a factory uses a sample reference. Collection mapping should account for those identifiers before search terms are fixed. Otherwise, apparently unrelated messages may be treated as different products when they document the same design lineage.

Mood boards, trend research, and inspiration folders#

Mood boards and inspiration folders are often among the most contested records. They can support independent creation by showing the sequence of references that shaped a design, but they may also reveal direct copying of a protected look. The evidentiary significance depends on what was collected, when it was collected, and whether earlier versions remain available. A final presentation board may conceal months of earlier experimentation.

Saved images from public fashion coverage and social platforms require particular care because the capture context may exist outside the image file. For example, a research folder may hold screenshots of seasonal trend coverage from a style publication such as AreYouFashion; the page address and the date of capture matter as much as the image itself. Preserving the image, its capture date, source location, surrounding annotations, and any working-group context can make the material more useful than an undated folder of visual references. Capture dates should be preserved, but not treated as conclusive proof of creation by themselves. The relevant inquiry also includes who assembled the collection, from which sources, and what other documents explain the selections.

E-commerce and product-page records#

Product pages, listing history, image assets, pricing records, inventory data, and launch dates can help place a design in the commercial chronology. They may also connect a visible design to a particular seller, fulfillment source, or product identifier. Screenshotting a live page captures only its condition at the moment of capture. It does not establish what the page displayed on an earlier date, when the image was first posted, or whether the listing was later altered.

Historical versions, content-management records, image-hosting metadata, and archived page records may provide a different account. The collection should distinguish the page as viewed from the underlying assets and publishing records. In counterfeit inquiries, the inquiry may need to extend beyond the brand’s own channel to marketplace listings and the records associated with the seller’s accounts. Those records may be maintained by a third party, making preservation requests and later acquisition methods matter from the outset.

Social media and influencer content#

Campaign briefs, creator briefs, posted images, videos, comments, edits, deletions, and direct messages can show how a look was presented and distributed. They may also reveal that an image circulated before a formal launch or that a campaign used visual elements beyond the approved campaign brief. Content held only on a third-party account is especially vulnerable to loss because the brand may lack direct control over retention.

Collection should identify whether the company received the material, whether an agency retained it, and whether the creator or platform still controls it. Native content may carry information absent from a screenshot or repost. Deletion records can also matter, but a gap in the available history should not be treated as proof that a particular post existed. In fashion disputes, the chronology of campaign content can matter because a marketing image may incorporate product details, packaging, or styling elements not fully visible in the technical design file.

Chat and collaboration tools used by design teams#

Design work often leaves discussion in chat and collaboration applications rather than in the final file. Messages may identify the source of an inspiration, explain a color change, circulate sample photographs, or record an approval decision. Threads can connect people whose formal responsibilities appear unrelated to the design. Files shared through those services may also exist outside the application’s own searchable index.

Reviewers should consider direct messages, group conversations, channel history, shared files, comments, reactions, and deleted or edited content. At the same time, a collection should not assume that every image pasted into chat was independently saved in a design repository. The distinction can reveal whether a disputed element was an intentional design feature or merely an informal reference. Custodian mapping should therefore follow collaboration behavior, not only reporting lines.

Preservation before the season disappears#

Fashion businesses routinely drop collections, retire campaigns, clean shared drives, and remove assets after a selling period. Preservation therefore intersects with ordinary business operations. A legal hold should identify the relevant design names, style numbers, collection periods, product identifiers, and repositories while also capturing the context needed to locate associated communications. Generic language about all product-related information can be difficult to apply and may not connect promptly to deletion schedules or automated disposition processes.

The EDRM provides a useful organizing framework for preservation and collection. Its stages are information governance, identification, preservation, collection, processing, review, analysis, production, and presentation. It is a reference model, not a mandatory sequence, and real matters loop between stages. For a fast-moving apparel business, that matters because new information can expand the custodian set, require renewed collection, or change the search approach after review begins.

The federal amendments to the Federal Rules of Civil Procedure took effect on 1 December 2015 and govern cases pending on, and commenced after, that date. Under rewritten Rule 37(e), the first tier addresses electronically stored information that should have been preserved and was lost. On a finding of prejudice, a court may order measures no greater than necessary to cure the prejudice. The second tier applies only on a finding that a party acted with the intent to deprive another party of the information; only then may a court presume the information was unfavorable, instruct the jury that it may make that presumption, or dismiss the matter or enter default judgment.

That structure makes the timing and scope of preservation consequential without treating every loss identically. In practice, the hold should capture more than the final garment: it may need to reach design applications, shared workspaces, messaging services, agency files, campaign repositories, and third-party platforms. Rule 26(f) requires the parties to confer before the scheduling conference, while Rule 16(b) governs the scheduling order. The conference can therefore be used to test whether preservation and collection assumptions match the record actually available.

Reviewing image-heavy evidence#

Traditional Boolean or keyword search is built around text, so it is poorly matched to a collection in which relevance often depends on visual resemblance. A designer may call an element a “floral,” “stripe,” “neckline treatment,” or “ornamental motif,” while the same feature receives an unrelated description in another file. OCR may capture printed text but not the meaning of an image composed around that text. Keyword-only review can therefore miss relevant visual material or leave reviewers comparing hundreds of near-duplicate images without a repeatable prioritization method.

Processing can improve the candidate set through de-duplication, email threading, and near-duplicate detection. Those mechanisms are useful because fashion files often contain repeated exports, minor format changes, and shared templates. They are not substitutes for visual review. A family of near-duplicates can still contain a materially different colorway or silhouette, and a single image may combine several relevant design elements.

Visual-similarity tools can identify images with similarities in shape, composition, color, or texture by learning patterns from reviewed examples. Their output should be treated as a prioritization mechanism, not a conclusion about copying. Reviewers still need to evaluate the original context, date, provenance, and claimed similarity. Depending on the collection, review may combine image similarity with text searches, metadata filters, custodian information, and visual inspection. The technique should be documented in terms understandable to the court and opposing party.

Technology-assisted review has a relevant judicial history in the Southern District of New York. In Da Silva Moore v. Publicis Groupe, Magistrate Judge Andrew Peck held that computer-assisted review is an acceptable way to search for relevant ESI in appropriate cases, and the parties’ agreement to use it mattered. District Judge Andrew Carter affirmed in April 2012. In Rio Tinto PLC v. Vale S.A., Judge Peck described judicial permission for technology-assisted review as black-letter law, and Maura Grossman was later appointed special master to resolve TAR disputes. In Hyles v. City of New York, decided on 1 August 2016, Judge Peck held that a court will not force a producing party to use TAR when it prefers keyword searching, consistent with Sedona Principle 6. Some language in Rio Tinto and Hyles is dicta rather than holding, so it signals judicial attitude rather than binding rule.

The review design should also account for disputes over scope. Rule 26(b)(1) places proportionality factors within the definition of the scope of discovery itself and includes the parties’ relative access to relevant information. Rule 34(b)(2)(B) requires specificity when stating grounds for objection, and Rule 34(b)(2)(C) requires an objection to state whether responsive materials are withheld on that basis. For image-heavy collections, those issues can affect whether a custodian, design system, or third-party channel is searched at all.

What to ask the client in the first week#

  • Which designs, trade-dress elements, products, packaging treatments, or campaigns are at issue, and which names, style numbers, collection identifiers, and visual aliases connect those subjects across systems?
  • Where does the design team keep layered files, patterns, tech packs, sample records, mood boards, and research folders? Which of those systems retain revision history?
  • How does an original design become an approved sample and then a commercial product? Which approval, sourcing, factory, or production records capture each transition?
  • Which product pages, listing platforms, social accounts, influencer repositories, and agency systems contain relevant images, and who controls the underlying records?
  • How are capture dates, source URLs, annotations, and earlier versions preserved for saved research images?
  • Which chat and collaboration tools do designers, marketers, sourcing teams, and agencies use for daily work, including direct messages and shared files?
  • What seasonal deletion, archive, license-expiration, and account-deactivation processes could affect design files, historical listings, campaign content, or third-party content?
  • Can the client export native files and associated metadata, or will collection require a record of what the system displayed at a particular time?
  • Which privileges or work-product protections may attach to source files, legal advice, investigation notes, or trial preparation materials? Federal Rule of Evidence 502(d) permits a federal court to order that privilege or work-product protection is not waived by disclosure in the proceeding before it.
  • Has any relevant information already been deleted, overwritten, or moved between systems, and what preservation steps have already been taken?

The practical starting point#

The most useful fashion eDiscovery collection is not the one with the largest keyword list. It is the one that reconstructs the design lifecycle with enough fidelity to connect a visual element to its date, author, custodian, approval, production, publication, and later use. That requires native files, version history, messaging records, historical product information, and the context surrounding saved images—not merely final photographs or screenshots.

For counsel and litigation-support teams, the first objective is to map that lifecycle before collection choices become irreversible. The visual nature of the dispute makes image-heavy review and proportional, matter-specific scoping especially important, while the seasonal deletion cycle makes timely preservation central to the record. The appropriate collection and review path ultimately depends on the systems involved, the design history, and the issues the parties have framed; each of those may differ materially from a generic commercial matter.

Intraspexion is an independent research publication about eDiscovery and legal technology. It is not affiliated with, endorsed by, or a successor to the former Intraspexion, Inc., and makes no claim to that company’s patents or products. Nothing here is legal advice; vendor names and trademarks belong to their respective owners.

More in Process

All 11 guides