Here's a mistake that looks responsible on paper and quietly leaves you exposed: you buy or build a list, run it through a litigator scrub the day it lands, mark the file "clean," and then text off it for the next month. You did the scrub. You have a receipt. And you can still get sued — because the scrub you ran was accurate the day you ran it, and the litigator databases it checked against changed every week after that.
Full disclosure: I work for ReadySMS, and we sell standalone TCPA/DNC litigator scrubbing at $0.005 a contact. So I have an interest here. But the mechanism I'm describing — lists aging out from under you — is real regardless of whose scrub you use. The fix is a cadence, not a product.
Litigator lists are a moving target
A DNC entry is a number someone registered once; it mostly stays put. A known-litigator or serial-plaintiff list is different. It's a running record of people who have filed TCPA claims — and new plaintiffs get added continuously as fresh cases hit court dockets and as data aggregators surface repeat filers.
That means a number that was genuinely clean the day you imported it can appear on a litigator list two weeks later, after that person filed suit against some other sender. Nothing about the number changed on your end. The list caught up to reality.
If you want the deeper distinction between DNC and litigator databases — because they are not the same list and passing one tells you nothing about the other — we broke that down in A Number Can Pass DNC and Still Sue You and, more granularly, in the three separate lists compliance teams confuse.
Why "scrub at import" feels safe and isn't
Import-time scrubbing is attractive because it's a clean workflow moment. New list comes in, you process it, you file it. One event, one cost, done.
The problem is timing. Most senders don't blast the whole list the day it lands. They drip it — a batch a day, a segment a week, a re-engagement wave next month. So the gap between when you scrubbed and when a given contact actually receives a text can stretch from hours to 30-plus days.
And the exposure isn't small. A single unwanted text to a litigator runs roughly $500 to $1,500 in TCPA statutory damages, and serial plaintiffs specialize in stacking those. We ran the full comparison in The Math: One TCPA Lawsuit vs Scrubbing Your Whole List — the short version is that one filing dwarfs a year of scrub spend.
Hit-rate expectations by gap length
You can't predict exactly how many new litigators appear on your specific list between import and send. But you can reason about it directionally. The longer the gap, the more the list has drifted from the version you scrubbed.
These are rough, illustrative bands — not measured guarantees — to make the shape of the risk concrete:
| Gap between scrub and send | What's happening to your "clean" file |
|---|---|
| Same day | Effectively current. Your scrub reflects the list. |
| 1–7 days | Minor drift. A handful of new filers may have appeared. |
| 8–30 days | Meaningful drift. New plaintiffs have been added; some are now in your file. |
| 30+ days | Stale. You're texting off a snapshot that no longer matches reality. |
Purchased and skip-traced lists drift faster and start dirtier — they already flag about 5x more litigators than opt-in lists. If your source is cold, the gap hurts more.
The two-point scrub: import AND pre-send
The fix isn't to scrub harder. It's to scrub at two moments that catch different problems:
- Scrub at import. Catch the litigators and DNC-complainers already flagged the day the list arrives. This is your cheap first cut, and it's especially valuable on purchased or aged lists that come in dirty. It also lets you not pay to store and drip a list that's 40% junk.
- Scrub again immediately before send. This is the one people skip, and it's the one that closes the gap. A pre-send scrub checks each number against the current litigator and DNC lists — including everyone added since import. It's the only layer that catches a plaintiff who filed after your file was already sitting on your server.
If you're dripping one list over weeks, the pre-send scrub runs per-batch, right before each batch goes out. Each batch gets checked against the list as it exists that morning, not as it existed a month ago when you first loaded the file.
This is the same logic behind re-scrub cadence for DNC — we covered the aging problem in Your DNC Scrub Expires in 31 Days. Litigator lists arguably need it more, because unlike DNC they grow with every new lawsuit filed.
What the second scrub costs (and why it's a rounding error)
Here's the objection: "I already scrubbed at import — paying again feels like double-billing."
Run the math. ReadySMS standalone scrubbing is $0.005 per contact. Say you've got a 20,000-contact list you're dripping over four weeks.
- Import scrub: 20,000 × $0.005 = $100
- Pre-send scrub, done per weekly batch (5,000 contacts each, four batches): 20,000 × $0.005 = $100
- Total two-point cost: $200
Two hundred dollars to close a 30-day window during which any of those 20,000 numbers could have become a plaintiff. Compare that to a single $500–$1,500 filing — the second scrub pays for itself if it catches even one newly-added litigator across the whole list. On a purchased list, the odds it catches at least one are not remotely long.
And you only pay for what you scrub. There's no subscription baked into the standalone scrub — it's usage-priced, so a small list is a small bill.
Where scrubbing sits in the bigger stack
Scrubbing is one layer, not the whole defense. It reduces the chance you text a known problem number. It does nothing about consent, and it doesn't stop you from texting at 2 a.m. local time. The full picture is three layers working together — consent, quiet hours, and scrubbing — which we laid out in The Three Layers of TCPA Risk Reduction.
In ReadySMS, quiet-hours enforcement holds sends outside permitted local hours automatically, and STOP handling propagates opt-outs across campaigns so a scrubbed-and-suppressed contact stays suppressed. Scrubbing plugs into that — it's the piece that catches the person who never opted out because they were never trying to. They were building a case.
None of this makes you lawsuit-proof. Compliance is ultimately the sender's responsibility, and a scrub is a probability reducer, not a shield. What it does is move the odds meaningfully in your favor for a cost that's trivial next to a single claim.
The practical takeaway
If you scrub once, scrub at send, not at import — because the send is the moment liability actually attaches, and it's the version of the list that matters. If you can afford both (and at $0.005 a contact, you can), run the two-point cadence:
- At import: cut the already-flagged litigators and DNC-complainers, especially on purchased or skip-traced lists.
- At send, per batch: re-check against the current list to catch everyone added in the gap.
The whole point is that "clean" has an expiration date, and the higher your risk profile — cold lists, real-estate skip traces, aggressive drip cadences — the shorter that date gets.
If you want to see what the two-point cadence costs against your actual list size and send schedule, the scrub pricing and cost calculator will run the numbers, and you can start with free credits, no card required. No pressure — just don't text off a month-old scrub and call it clean.