The first time most floors hear the phrase, it arrives attached to a demand letter. Somebody dialled a number, the number belonged to a person who has done this before, and a compliance vendor is now explaining that this could have been avoided for a fraction of a cent per record.
That pitch is broadly true and worth understanding precisely, because litigator scrubbing is one of the few compliance products where what you are buying is genuinely not what the name suggests.
This page describes operational practice, not legal advice. Nothing here is a compliance opinion about your dialling programme, and a litigator scrub is not a defence to a claim. Put your specific setup in front of counsel and treat their answer as authoritative over anything on this page.
What it is, and what it is not
| It is | It is not |
|---|---|
| A commercial file of numbers and identities linked to repeat telephone-consumer claimants and serial complainants | A government registry. No agency publishes one, and no agency endorses any vendor’s version |
| A probability signal — this number has a history of producing claims | A determination that any individual is a bad actor, or that a claim against you would fail |
| A layer you add on top of do-not-call scrubbing and consent records | A substitute for either of those |
| Vendor-compiled, with a methodology that differs from vendor to vendor | A standardised dataset. Two vendors’ lists will not agree, and neither is canonical |
Where the names come from
There is no feed. Every litigator list is assembled, and the assembly is what determines whether it is any good. The raw material is public and semi-public:
- Court dockets. Federal and state filings naming plaintiffs in telephone-consumer matters, harvested and deduplicated across jurisdictions.
- Demand letters and pre-litigation correspondence. Contributed by subscribers, which is why several of these products operate as consortiums — you send in what you receive and get everyone else’s in return.
- Regulatory complaint records. Public complaint databases, which capture people who complain frequently without ever filing suit.
- Attorneys and known associates. Numbers connected to firms and practitioners active in this area.
Each of those sources gives you a name. Your dialer needs a number. Bridging the two is an identity-resolution step, run by the vendor, with exactly the same weaknesses as any other identity resolution — and it is the part of the product nobody markets. Skip tracing accuracy explains why a confident match and a correct match are different things; that entire problem applies here, with the added twist that the consequences of a false positive and a false negative are wildly asymmetric.
The two errors, and which one you should prefer
A false negative — a genuine repeat claimant your list missed — costs you the thing you bought the list to avoid. A false positive — a household flagged because they share a surname, an address or a recycled number with somebody in a docket — costs you one suppressed record you would probably never have sold anyway.
The asymmetry is severe enough that the correct posture is to accept false positives without complaint. A team that argues with its vendor about over-suppression has misunderstood the economics of the product. Suppress the flagged record, do not attempt to adjudicate it, and never act on a flag in any way other than not calling — a litigator flag is a dialling decision and nothing else.
How the scrub actually runs
There are three integration points, and floors typically end up with two of them for different reasons.
- Batch, before load. The whole file goes to the vendor and comes back flagged. Cheapest per record, and correct for lists that will be worked within a short window.
- Real time, at dial. An API call in the dialling path. More expensive per record and the only option that catches somebody who was added to the list after your batch ran.
- Appended flag, carried in the record. Convenient and quietly the most dangerous, because the flag ages inside your CRM while looking permanently authoritative. A litigator flag from eight months ago is not a current answer.
The ordering rule is the same one that governs every other scrub: it runs on the list you are about to dial, after the numbers exist, not on the address file you bought last month. DNC compliance for outbound solar works through why the append-then-scrub sequence matters, and the same sequence applies here.
Questions worth asking a vendor
- What is a hit matched on? Phone number alone, name plus number, or household. Number-only matching inherits every reassigned-number problem in the phone system.
- How often is the file updated, and how quickly does a new filing appear? The value of the product is almost entirely in its recency.
- Does anything ever come off? A file that only grows becomes progressively more false-positive-heavy. Ask what the removal policy is and whether there is one.
- What jurisdictions does the docket harvesting cover? Coverage of state courts is much more variable than coverage of federal ones.
- Will you give me a hit rate on my own file before I buy? A sample scrub is cheap for them to run and tells you more than any statistic in the deck.
The list you keep yourself matters more
Here is the part vendors do not lead with. The single most predictive signal that a household will cause you trouble is not a court docket — it is that this household has already complained to you. That information is free, you generate it every day, and it is the one list no vendor can sell you because only you have it.
A floor that logs complaints properly, pushes them into suppression the same day, and never lets a purchased list reintroduce them is doing more for its risk profile than any subscription. The litigator product is a useful supplement to that discipline and a poor replacement for it. Building a suppression list covers how to keep the vendor flag, your own complaints, prior contacts and customer records in one file that survives changing dialers.
Is it worth buying?
For a floor dialling at volume into households with no prior relationship, most compliance practitioners treat it as inexpensive insurance, and the arithmetic is not close: the per-record cost is fractional against the cost of responding to a single claim. For a small team dialling their own past customers and inbound enquiries, the exposure profile is different and the money is usually better spent on consent records and internal suppression first.
Either way, buy it as what it is — a probability filter with an unaudited methodology and an asymmetric error cost — rather than as protection. Nothing you purchase changes what you are responsible for. The underlying quality of the list is a compliance input too: a file matched to whoever is associated with an address rather than to the owner on title produces more wrong-party calls, and wrong-party calls are where complaints come from. List hygiene for call centers covers the routine that keeps that under control.
Disclosure: Scout Data is our product. We sell homeowner contact data, not litigator scrubbing, and we have no commercial interest in which vendor you pick. We do have an interest in the upstream half of the argument: our List Builder matches phones to the owner on title and scrubs against the federal do-not-call registry before delivery, which reduces the volume of wrong-party dialling that generates complaints in the first place.
Frequently asked questions
What is a litigator list?
A commercially compiled list of phone numbers and identities associated with people who have repeatedly brought or threatened telephone-consumer claims against callers. Floors scrub against it before dialling, on the theory that a small population of repeat claimants generates a disproportionate share of demand letters. It is a vendor product, not a government registry.
Is litigator scrubbing legally required?
No. Nothing requires you to buy one, and scrubbing against one is not a defence to anything. Federal and state do-not-call obligations, consent requirements and your internal do-not-call list are the actual legal duties. A litigator list is a commercial risk-reduction tool that sits on top of those, and it does not substitute for any of them.
How accurate are litigator lists?
Nobody publishes an audited answer, and you should be suspicious of a vendor who claims one. The compilation depends on matching names in court records and complaint databases to phone numbers, which is an identity-resolution problem with all the usual failure modes — common names, shared households, reassigned numbers. Ask what a hit is matched on before you ask how big the list is.