The takedown is the easy part of enforcement. Removal requests scale with tooling; a brand can clear hundreds of listings without anyone reading a complaint. The harder question is what happens to the sellers behind those listings. A growing number of brands answer it with a Schedule A lawsuit: one complaint naming dozens or hundreds of anonymous storefronts as defendants, paired with an ex parte temporary restraining order that freezes their marketplace accounts before they can move money or rename a shop.
That structure is efficient, and it is also where most enforcement programs discover that the evidence collected for takedowns is not the evidence a court requires. A Schedule A lawsuit is usually decided long before any hearing, in the case file sitting behind the complaint.
What a Schedule A Lawsuit Requires Now
The mechanics are simple enough. The plaintiff sues defendants identified only by their storefront aliases, lists those aliases on a schedule that is often filed under seal, and seeks an ex parte TRO. Marketplaces are served with the order, listings come down, and funds in the defendants' accounts are frozen. For most defendants, that order is the first notice that a case exists.
The Northern District of Illinois became the center of this practice. A trademark docket search cited by Taft's step-by-step guide to Schedule A litigation found roughly 4,200 Schedule A cases filed there between January 2013 and February 2025, which led one judge to write that the district had become "the Northern District of Illinois vs. the Internet."
The docket has since tightened. Several judges there publish standing orders governing Schedule A counterfeit cases, and their requirements reach directly into the case file. Every motion for expedited discovery, a TRO, or a preliminary injunction must show that the court likely has personal jurisdiction. Counsel must be prepared to show cause why joining many defendants satisfies Rule 20(a)(2) and the standard applied in Bailie v. Defendants Identified on Schedule A. Citing product images next to the plaintiff's mark is explicitly insufficient: the briefing has to walk through each claim, the law that applies to each element, and a case-specific argument for why the accused product infringes.
None of that is a legal theory problem. It is an evidence architecture problem, and it is why two brands with identical claims can end up with very different results.
Where Schedule A Case Files Break Down
A removal request needs one thing: proof that a listing infringes. A Schedule A lawsuit needs a fact pattern for every defendant — who they are, what they sold, when, at what price, and how their conduct connects to the other defendants in the case.
Joinder is the first wall. Courts have refused to treat similar-looking storefronts as one series of transactions, and recent decisions have pushed back on the reasoning that once made large joinders easy to justify. A spreadsheet of 120 URLs is not a joinder argument. Facts about each defendant are.
Personal jurisdiction is the second, especially for overseas sellers. The record has to show that the defendant's own conduct was aimed at the forum, and courts commonly look to evidence that the accused product was actually purchased from that defendant — a purchase tied to one storefront, not a generic sample.
The infringement analysis is the third. Element by element means exactly that: the mark, the goods, the likelihood-of-confusion facts, and the evidence supporting each step. Screenshots rarely carry it on their own, and judges have said so directly.
Then come the formalities. Foreign-language exhibits need admissible translations, and machine translation does not qualify. Serving a defendant by email under Rule 4(f)(3) requires a showing of reasonable diligence in finding a physical address, usually after discovery from a marketplace, so requests made at the TRO stage without that trail get rejected.
Timing works against the plaintiff too. Listings vanish, storefronts rename, prices change, and the record that felt complete in month one is gone by month six. Assembling the file afterward produces gaps, and gaps invite severance, denied relief, and in the worst case a fee award: in Opulent Treasures, a plaintiff that joined defendants it had not properly investigated was ordered to pay $98,276.20 to one of them.
The arithmetic explains why so many cases get built on a sample. At a brisk twenty minutes per defendant, a 120-defendant file is forty hours of assembly before a single argument is drafted, and the work is repetitive enough that errors go unnoticed. Volume feels like leverage. Without structure, it is exposure.
How AI Builds a Defensible Schedule A Case File
Automation changes the outcome when it is pointed at the case file rather than at the removal count. CourtifyAI's Auto Pilot runs monitoring, evidence capture, cease-and-desist, and claim preparation as one pipeline, so nothing has to be reconstructed later.
The record starts at detection. When a suspect listing is found, the system captures the page state, price, listing text, images, and seller identifiers with timestamps in a structured, tamper-evident form. Because monitoring repeats, the record becomes a time series rather than a snapshot. That matters at the TRO stage: duration and price movement are facts about the conduct, and they exist only if someone was watching while the listing was live.
Identity correlation is where a listing pile becomes a defendant list. Shared images, copied descriptions, overlapping contact details, and repeated storefront patterns let the workflow group listings across marketplaces and link them to a single seller. That is what a joinder argument needs — documented connections rather than a claim that the pages look alike. It also surfaces sellers who return under new names, which is the point at which a removal program turns into a case.
Each defendant then gets its own exhibit set: the listings attributed to it, the capture metadata behind every artifact, a comparison of the accused product against the genuine one at the element level, and the seller details from the storefront. This is the unit that a joinder memorandum, a jurisdiction showing, and a TRO package all consume, and the unit manual workflows never have time to produce at scale.
Test purchases plug into the same structure. The workflow tracks the order, payment, shipment, and item received, then stores photographs and hashes so the physical evidence stays tied to the listing that produced it. That exhibit supports both infringement and the jurisdiction showing.
Formalities stop being a scramble: foreign-language text is extracted for translation as part of the packet, and identification attempts made before filing stay on record to support a later request to serve by email.
The drafting layer then works from the record rather than from memory. CourtifyAI's AI legal assistant drafts the complaint, the schedule, the TRO memorandum, and the joinder section from the same evidence file, so the facts in the brief match the exhibits behind it. For the element-by-element side, How to Prove Trademark Infringement Online sets out the proof structure.
The stakes per defendant make this worth doing properly. Under 15 U.S.C. § 1117(c), statutory damages for counterfeiting run from $1,000 to $200,000 per counterfeit mark per type of goods, and up to $2,000,000 per mark per type of goods where the use was willful. Every defendant carries its own exposure, and the evidence attached to each one is what moves a claim inside that range.
What Changes When the Record Exists Before the Complaint
The first change is that relief comes faster. A TRO filed with a complete, per-defendant record does not need a second pass to answer questions about jurisdiction or joinder, and accounts are frozen while the listings are still live rather than after the defendants have moved on.
The second is that diligence stops being a risk. Fee awards tend to follow sloppy joinders, and a defendant that should never have been named is easier to catch when the file shows what was verified.
The third is repeatability. Once the pipeline exists, a second case is largely a rerun: new defendants flow through the same capture, grouping, and exhibit generation. That changes who can afford to litigate, because cost stops scaling linearly with the number of defendants.
The fourth is the internal argument. Programs that report removal counts compete for budget against programs that report claim-ready defendants and recoveries. How to Manage Trademark Infringement Cases at Scale covers the docket side of running those cases without losing the thread.
Schedule A litigation is not a volume play, even though it looks like one. It is an evidence play. The brands that win these cases are not the ones that found the most listings. They are the ones whose case file was already assembled, defendant by defendant, when the complaint was ready to file.
Frequently Asked Questions
What is a Schedule A lawsuit?
A Schedule A lawsuit is a single trademark or copyright case filed against many anonymous online sellers, identified in the complaint by their storefront aliases and listed on a schedule that is often filed under seal. Plaintiffs typically seek an ex parte TRO so that marketplace accounts and funds are frozen before the defendants learn about the case.
How many defendants can be joined in a Schedule A case?
There is no fixed cap, and complaints have named hundreds of defendants. Joinder still has to satisfy Rule 20(a)(2), which requires a common question and relief arising from the same transaction, occurrence, or series of transactions. Courts apply that test case by case, so the number matters less than the documented connections between defendants.
Can you file a Schedule A lawsuit without a test purchase?
Yes, but the record gets thinner. Courts often look to a purchase from a specific defendant to establish that the seller directed its conduct at the forum, and a purchase also produces physical evidence that the product is counterfeit. Without one, the jurisdiction showing and the infringement argument rest on listing evidence alone.