
Photo by Towfiqu barbhuiya on Unsplash
How Often Should You Re-Scrub a Call List? A Practical Answer
"Scrub before every campaign" is correct advice, but it's not a schedule. Here's how to turn that principle into an actual cadence you can build a process around.
The minimum: before every campaign, no exceptions
If a list is about to be dialed, it gets scrubbed first — full stop, regardless of when it was last checked. This is the non-negotiable floor. Everything below is about what to do between campaigns for a list that stays active over a longer period.
For lists in continuous use
If you're dialing from the same list across an extended campaign — not a single batch, but ongoing contact over weeks — re-scrub on a fixed interval rather than waiting for the campaign to formally "restart." A common practical cadence is weekly for active high-volume lists, since DNC registrations and honeypot/litigator data both update continuously, not on any campaign schedule of yours.
For lists you pause and resume
A list that goes idle for any meaningful stretch — a few weeks, a season, longer — should be treated as untrusted when you pick it back up. Time elapsed since the last scrub is the only variable that matters here, not how "clean" the list seemed the last time it was used.
After any list modification
Adding numbers from a new source, merging in a purchased list, or importing new leads all mean part of the list has never been checked. Re-scrub after any merge or import — the previously-clean portion doesn't need re-verification for this specific trigger, but the new numbers absolutely do.
A simple rule of thumb
Rather than tracking dates manually, tie the scrub to an event rather than a calendar:
- New campaign starts → scrub.
- List has been idle more than ~2 weeks → scrub before resuming.
- List modified (merge, import, manual additions) → scrub.
- Active list in continuous use → scrub on a fixed weekly interval regardless of the above.
This mirrors the workflow we lay out in our compliant calling workflow guide — scrubbing as a triggered step in the pipeline, not a one-time task.
Making re-scrubbing cheap enough to actually do
The reason teams skip re-scrubbing usually isn't that they don't know they should — it's that it feels like friction. A fast, low-cost re-scrub removes that excuse. Try Carrier Fence free — uploading and re-checking a list takes minutes, not hours.