Set verification cadence by when you will use a record and how you will use it. Even carefully verified email lists can become risky within weeks.1 Treat each check as a dated decision, triggered by the next send, the record's age, or its channel. Use recurring review for active accounts, a pre-campaign gate for older records, and a separate check for phone numbers. Before outreach, decide whether the record is ready, due for another check, or on hold.
The cadence
Use a trigger stack. Run the earliest applicable check and record the result so the next person can see why the record was cleared, held, or reviewed.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Account refresh | Whether active account records remain current and target-account data is ready for significant outreach. Check active-account contact data at least quarterly and target-account data before significant outreach.2 | Has this account been checked in the current review cycle? |
| Campaign gate | Whether the record is fresh enough for the campaign about to launch. For systems with periodic re-verification, run a pass immediately before launch, especially when contacts have been in the CRM more than 30 days.3 | Has this record been checked since it entered the campaign? |
| Second pass | Whether the original result still deserves confidence. Run a second verification through a dedicated service when contacts are more than 30 days old, even if the original tool included verification.4 | Would a separate check change this result? |
| Stale contact review | Whether a contact that has gone quiet needs another check before outreach. Revalidate contacts that have not engaged in six to twelve months before further outreach.5 | Has this contact engaged since the last review? |
| Phone pre-call check | Whether the number is suitable for the call you are about to make. | May this number have been reassigned? |
Apply the trigger
Store cadence as conditions instead of using one date for every record. Bring campaign records into review immediately before launch. A record with no current outreach need can stay in its scheduled cycle.
Use the earliest trigger when several conditions apply. If a target account is old and a campaign is imminent, run the campaign check and attach the result to that specific outreach plan. If the record fails the check, keep it out of the send until someone decides what happens next.
Keep the record history small and usable. Capture the last checked date, channel, result, reason for the check, and disposition. That lets the next person distinguish a current result from an old status without rerunning the same work blindly.
Email checks
Email verification should produce a disposition that controls sending. Decide in advance what a clear, unresolved, or failed result allows you to do.
Use a recent result for the current campaign and route uncertain outcomes for review. Keep the result beside the contact record so a later user can tell whether the address was cleared for this campaign or inherited from an earlier check.
An eight-week experiment found that 5.5% of verified emails degraded, with 2.3% becoming invalid and 3.2% becoming accept-all.6 The pre-send gate remains useful when the original verification was done carefully. Set the decision before launch so an unresolved result does not quietly enter the batch.
Phone checks
Phone records need their own gate because a valid number can later belong to someone else. Run the check close to the call, keep the result with the number, and remove uncertain numbers from the active call queue until someone resolves them.
The Reassigned Numbers Database is designed to prevent consumers from receiving unwanted calls intended for a previous holder of their number.7 Before calling, use it to determine whether a number may have been reassigned and avoid calling consumers who do not want the calls.8 Callers can check the database before making a call.9 Doing so can reduce potential Telephone Consumer Protection Act liability by helping avoid inadvertent calls to consumers who have not given consent.10
When the database indicates possible reassignment, hold the number and investigate the contact through an appropriate channel. Do not let a previous successful connection override a current reassignment result.
Adjust the policy
Start with the trigger rules and tune them from the results. A cohort that produces more holds or failed results as it ages needs an earlier review point. A cohort that remains stable can keep its current trigger while you continue recording outcomes.
Separate the policy by channel and use case. Email records need a send gate, phone records need a reassignment check, and older or inactive contacts need a stronger freshness test. Store those rules where the person preparing outreach can see them without relying on memory.
Review the outcomes after each campaign cycle. Count how many records were cleared, held, or sent for review. Use those patterns to change the trigger that created the most avoidable risk, and give every exception a clear reason.
What not to do
Avoid these mistakes in the operating policy:
- Email verification is not permanent because email data decays quickly as people change jobs and domains change settings.11
- Keep invalid email addresses out of campaigns. They cause hard bounces that directly damage sender reputation.12
- Do not clear accept-all addresses automatically. They increase risk and uncertainty even when they do not bounce immediately.13
- Do not let database size set the cadence. Data decay in the technology industry can reach 35% annually, and verification cadence matters more than database size.14
Set the next check from the earliest trigger, record the outcome, and show the reason for sending, reverifying, or pausing beside the record.