Known-Litigator Scrub Lists: What They Do and Don’t Fix Under the TCPA

A known-litigator scrub removes phone numbers tied to people who have filed TCPA suits before, and no federal rule stops a business from using one. It’s a sensible filter, because repeat filers are a familiar feature of TCPA litigation and a number that never gets called can’t produce a claim. But the scrub is not part of the Do Not Call safe harbor and doesn’t fix a consent or opt-out problem. A company that relies on it instead of compliance has hidden its exposure, not removed it.

Is it legal to suppress known TCPA litigators?

Yes. Nothing in the TCPA or the FCC’s rules requires a business to market to anyone. Choosing not to call or text a number is always compliant with the statute. The TCPA regulates who a company may contact, not who it must contact.

The practical questions are about the data. Litigator lists are usually built from public court dockets, and a reputable vendor will say where its data comes from and how often it updates. A business should know what it’s buying. A list that pulls in names from dockets without matching them to phone numbers carefully will suppress the wrong people, which costs revenue but creates no TCPA exposure.

Why doesn’t a litigator scrub count toward the Do Not Call safe harbor?

Because the safe harbor lists what counts, and a litigator scrub isn’t on the list.

A company that makes telephone solicitations avoids liability for a call to a Registry number if “the violation is the result of error” and, as a routine practice, it meets five standards, according to 47 C.F.R. § 64.1200(c)(2)(i). It needs written procedures and trained personnel. It must keep a list of numbers it may not contact, and it must scrub against “a version of the national do-not-call registry obtained from the administrator of the registry no more than 31 days prior to the date any call is made.” It also has to buy Registry access properly. A litigator scrub can be one of a company’s written procedures, but none of the five standards depends on it.

The statute’s own defense works the same way. Section 227(c)(5) makes it “an affirmative defense” that the defendant “has established and implemented, with due care, reasonable practices and procedures to effectively prevent telephone solicitations in violation of the regulations prescribed under this subsection,” under 47 U.S.C. § 227(c)(5). Procedures that prevent calls to Registry numbers and opted-out numbers fit that description. Procedures that prevent calls only to people likely to sue don’t.

Can a litigator scrub hurt a company’s defense?

It can, if it’s the main control. Discovery in a Do Not Call case usually reaches the company’s compliance procedures. A program built mostly to avoid lawsuits, with weak Registry scrubbing and slow opt-out processing, looks worse on paper than a program with no litigator filter at all.

The willfulness question sharpens that risk. Damages under § 227(c)(5) are up to $500 per violation, and a court may increase the award to as much as three times that amount, up to $1,500, if “the defendant willfully or knowingly violated the regulations,” according to the statute. A plaintiff’s lawyer will try to frame heavy spending on litigator suppression, set beside light spending on Registry and opt-out compliance, as evidence that the company knew its calls were reaching people who didn’t want them.

There’s one more trap in how the scrub is bought. The safe harbor requires a process ensuring the company “does not sell, rent, lease, purchase or use the national do-not-call database, or any part thereof, for any purpose except compliance,” and a company must not “participate in any arrangement to share the cost of accessing the national database,” according to § 64.1200(c)(2)(i)(E). Some vendors bundle litigator scrubbing and Registry scrubbing into one service. A company using a bundle should confirm it holds its own Registry access and that the vendor runs the Registry scrub under the company’s account, not a shared one.

Where a litigator scrub helps, and where it doesn’t

Exposure Statute or rule Exposure per violation Does a litigator scrub answer it?
Calls or texts to Registry numbers § 227(c)(5); § 64.1200(c)(2) Up to $500; up to $1,500 if willful or knowing Reduces lawsuits, but isn’t a safe-harbor element
Calls after an opt-out § 227(c)(5); § 64.1200(d) Up to $500; up to $1,500 if willful or knowing No. Only the internal do-not-call list answers it
Prerecorded or autodialed calls without consent § 227(b)(3) Up to $500; up to $1,500 if willful or knowing No. Consent records answer it
Class actions Fed. R. Civ. P. 23 Multiplied across the class Partly. It removes some likely class representatives, not class members

Texts carry one open question. The Seventh Circuit held in July 2026, in Steidinger v. Blackstone Medical Services, that a text isn’t a call for a private Do Not Call suit under § 227(c)(5). That decision binds only federal courts within the Seventh Circuit, so a texting program elsewhere shouldn’t count on it.

Companies tend to miss the class-action row. A class action needs one named plaintiff, and suppressing repeat filers removes the most likely candidates. But the class includes everyone who got the same calls. If the program has a real Registry or opt-out failure, a first-time plaintiff can bring the same class claim, and the litigator scrub did nothing for the thousands of other recipients.

How should a litigator scrub fit into a compliance program?

Last, not first. The order that holds up in litigation is the Registry scrub on a current download, then the internal do-not-call and opt-out list, then any state registries, then consent verification for prerecorded and autodialed campaigns. A litigator filter on top of those is a reasonable business choice. Under them, it’s a substitute that won’t survive discovery.

Two details make the scrub easier to defend. First, document it in the written procedures as a business filter, separate from the compliance controls, so it doesn’t read as the company’s main answer to the Do Not Call rules. Second, keep the suppression records with the same version dates and logs as the Registry scrub. If a known litigator receives a call anyway, the company will want to show exactly which list version was in use and why the number got through.

The serial TCPA plaintiffs post covers how businesses defend the suits that repeat filers bring once they’ve been called.

If a repeat filer sends a demand anyway

  1. Put the call and text logs for the number under a litigation hold, along with the consent record, if any, and the campaign that produced each contact.
  2. Pull the internal do-not-call list entries and opt-out history for the number, with dates.
  3. Retrieve the Registry scrub logs showing the download date used for each call, plus the litigator-scrub version and the reason the number wasn’t suppressed.
  4. Gather the vendor contracts for the dialer, the scrub services, and any lead sources, along with call scripts and recordings.
  5. Have counsel review the demand before anyone answers it, calls the claimant, or discusses a payment.

The firm’s TCPA litigation defense page explains how Do Not Call claims are defended.

Questions businesses ask about litigator scrubbing

Does the FCC allow businesses to block known TCPA plaintiffs?

Nothing in the TCPA or the FCC’s rules requires a company to call or text anyone, so declining to contact numbers on a litigator list is permitted. The limits come from the data itself and from how the list is bought. If a vendor bundles Registry data into the service, the company still needs its own Registry access, because the safe harbor bars sharing the cost of that access.

Will a litigator scrub stop TCPA class actions?

It reduces them, but it won’t stop a class action built on a real compliance failure. The scrub removes repeat filers who are likely to serve as named plaintiffs. Anyone else who received the same calls can bring the class claim. A class action is about what the company did to everyone, not just the person who sued.

Does using a litigator list prove a company knew it was violating the TCPA?

No, not by itself. Suppressing likely litigants is a normal business choice. The risk comes from imbalance. If discovery shows strong litigator filtering beside weak Registry or opt-out compliance, a plaintiff will argue that the company knew its calls reached people who didn’t want them. That argument is aimed at willfulness, which can raise damages to as much as three times the base amount.

Should a litigator scrub replace the Do Not Call Registry scrub?

Never. The Do Not Call safe harbor requires scrubbing against a Registry download no more than 31 days old, along with written procedures and trained staff. It also requires an internal do-not-call list. A litigator scrub satisfies none of those requirements. It’s a business filter that sits on top of the Registry scrub and the internal list, not a replacement for either.

When the call reached a repeat filer anyway

If your company has been sued by a repeat TCPA filer, the Registry scrub logs and the litigator-list version in use on the call date usually decide how the case goes. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving calls to numbers on the Do Not Call Registry. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.

Sources

The private right of action and its affirmative defense are in 47 U.S.C. § 227(c)(5). The Do Not Call safe harbor and the internal do-not-call list rules are in 47 C.F.R. § 64.1200(c)(2) and (d).

This post is general information about the Telephone Consumer Protection Act and related laws as of September 4, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.

← Back to Blog

Let’s Talk.