You bought a list eight months ago. You scrubbed it against a litigator database the day it landed — clean, or close to it. Since then you've been texting off that same file, maybe with a fresh import stitched in here and there. In your head it's still the clean list you paid for.
It isn't. The list didn't change, but the world around it did. The specific numbers on your file quietly became higher-risk while you weren't looking, and the one-time scrub you ran on day one stopped meaning anything the moment you closed the tab.
Full disclosure: I work for Ready, and we sell standalone litigator scrubbing at $0.005 per contact. So I have a horse in this race. But the mechanism I'm about to walk through is real whether you scrub with us or anyone else — and the math is the point, not the vendor.
Litigators aren't a fixed population — they're a growing one
The mistake baked into "I scrubbed it at import" is treating the litigator list as a snapshot of a stable population. It isn't. Two things happen continuously:
- New people become litigators. Someone who got a cold text in March, felt annoyed, and filed a complaint or a suit in June gets added to the litigator databases sometime after that. On day one of your list, that number was invisible. Now it's flagged.
- Numbers on your list get reassigned to people who are already litigators. Carriers recycle disconnected numbers. A 12-month-old list is roughly 30% reassigned or disconnected — a number you thought belonged to a friendly prospect now belongs to someone else entirely, and that someone else might be a serial filer.
Both curves point the same direction: up. The database grows, and your list's overlap with it grows. The overlap on day one is the floor, not the ceiling.
There's a real distinction here between DNC and litigator lists — a number can pass a DNC scrub and still be a known filer. If that's fuzzy for you, the difference between DNC lists and known-litigator databases is worth ten minutes before you read on.
A rough hit-rate-over-time model
Let me put approximate numbers on this. These are illustrative, framed as directional — not published stats — but they match the shape people who scrub regularly describe.
Say a freshly purchased list flags at a 0.5% litigator hit rate at import (purchased lists run far higher than opt-in — often 5x higher, because the population that ends up on resold files skews toward people who never consented and are more litigious).
| List age | Approx. flagged rate | Why it moved |
|---|---|---|
| Day 1 (fresh scrub) | ~0.5% | Baseline for a purchased file |
| Month 3 | ~0.9% | New filers added; a few reassignments |
| Month 6 | ~1.3% | Reassignment accelerates; database grew |
| Month 8 | ~1.5% | ~3x the day-one rate |
| Month 12 | ~1.8–2.0% | Compounding decay + database growth |
So the headline holds: by month eight, a purchased list can carry roughly three times the flagged numbers it had on day one — and every one of those is a number your import-day scrub swore was clean.
Opt-in lists you grew yourself decay much more slowly, because the population is friendlier and you're not inheriting anyone else's recycled numbers. That's the whole reason scrub frequency should track list source, not a fixed calendar.
Why one text to a stale flag is the whole problem
TCPA exposure runs roughly $500 to $1,500 per text — and known litigators are, by definition, the people most likely to turn a single message into that invoice. That's the entire business model of a professional filer: collect texts they never consented to, document them, and sue.
Here's the part that stings. Your day-one scrub was fine. You did the responsible thing. But the violation isn't measured against when you scrubbed — it's measured against when you sent. One text to a number that became a litigator flag in month five is the same violation as if you'd never scrubbed at all. The clean-on-import receipt doesn't help you.
This is why scrubbing before import isn't enough on its own, and why scrubbing after import is already too late if the send goes out on a stale file.
The scrub-cadence math (and why it's absurdly cheap)
Now the part that makes this an easy decision. Standalone litigator scrubbing runs $0.005 per contact — you pay only for what you scrub, and matches get auto-suppressed before send.
Take a 20,000-contact purchased list.
- One re-scrub: 20,000 × $0.005 = $100.
- At month eight, that list carries roughly 1.5% flagged — ~300 numbers you'd otherwise have texted.
- If even one of those 300 turns into a claim: $500–$1,500.
- If five do — not unusual, since litigators cluster and often file in volume: $2,500–$7,500.
You're spending $100 to remove a set of numbers whose expected cost, if you send to them, dwarfs the scrub by one to two orders of magnitude. And you're doing it repeatedly, because the flagged set keeps regrowing. I've laid the full version of this out in the math of one TCPA lawsuit vs scrubbing your whole list — it doesn't get closer with scale, it gets more lopsided.
A cadence tied to source, not the calendar
A blanket "scrub every 30 days" wastes money on friendly lists and under-protects risky ones. Tie the interval to where the list came from:
- Purchased / skip-traced / third-party lists: re-scrub before every send, or at minimum every 30 days if you send more often than that. This is your highest-decay, highest-baseline population. At $0.005/contact, per-send scrubbing on a 20K file is $100 — treat it as a line item, not a debate.
- Cold-outreach lists you compiled yourself: every 30–45 days. Still no consent relationship, so decay is real, but you're not inheriting someone else's recycled numbers.
- Opt-in lists you grew: every 90 days, or before a big blast. Lower baseline, slower decay. The main risk here is reassignment, not new filers.
- Any list about to receive a large one-time blast: scrub immediately before, regardless of when you last did it.
If you want the source-based schedule in full — including how DNC re-scrub windows layer on top of litigator scrubs — the source-based scrub schedule post breaks the cadence down further.
Where scrubbing fits (and where it doesn't)
I'll be honest about the ceiling: scrubbing is one layer, not a shield. It removes the numbers most likely to sue, but it doesn't manufacture consent you never had, and it won't save you from texting a legitimate non-consenting person at 6 a.m. their time.
The three layers that actually reduce exposure work together:
- Consent — the foundation. Scrubbing a list you had no right to text still leaves you liable to everyone you didn't happen to scrub off.
- Quiet-hours enforcement — holding sends outside permitted local hours so you're not stacking a timing violation on top of everything else.
- Litigator + DNC scrubbing — removing the people who will most aggressively act on any of the above.
Ready enforces quiet hours automatically and records opt-in attestation on bulk and API sends, so the scrub isn't operating alone. The three layers of TCPA risk reduction covers how they reinforce each other — scrubbing a stale list is necessary, but on its own it's the middle piece, not the whole picture.
The practical takeaway
Your day-one scrub expired the day you ran it. The litigator database keeps growing, your numbers keep getting reassigned, and a purchased list eight months on can carry roughly three times the flagged numbers it started with. The violation is dated to the send, not the scrub — so the receipt from import doesn't cover you.
Fix it with a cadence, not a one-time cleanse: re-scrub purchased lists before every send (or monthly), self-compiled cold lists every 30–45 days, and opt-in lists quarterly. At $0.005 a contact, a full re-scrub of a 20K list is $100 against a per-text exposure of $500–$1,500 — the cheapest insurance in your stack, and the only kind that stays current.
If you want to run a scrub against a list you already have — no SMS sending required — you can start with 2,500 free credits, no card and see your list's current hit rate before your next blast goes out. The number will surprise you if it's been sitting a while.