Key points
- Use the next campaign, material changes and observed failures to trigger review.
- Keep field observation, retrieval and validation dates separate.
- Refresh specific evidence without overwriting reviewed values or reviving exclusions.
Refresh a B2B lead record when the next use or a material observation calls its evidence into question. Check the field that matters rather than assuming every record expires on the same calendar.
Role, company, email, phone and account attributes can change independently. Keep their sources and observation dates separate so a new retrieval does not make the whole record appear freshly verified.
Define what changed or remains unknown
- Identity or employer: the person may belong to a different company or business unit.
- Responsibility: the title or remit may no longer match the campaign.
- Contact channel: an address or number may be missing, invalid or uncertain.
- Account context: ownership, activity, location or scale may affect eligibility.
- Campaign eligibility: preferences, suppression or ownership may have changed.
A typo or incorrect source value may have been wrong from the start rather than having decayed. Distinguish an initial error from a change over time when evaluating a provider or review process.
The data quality guide separates coverage, accuracy and validation. That distinction matters before choosing a refresh schedule.
Choose review timing from the next decision
Before a record is reused in a campaign
Review the evidence required for the proposed action, including account fit, relevant responsibility, contact fields and preferences. The age of the list is one input, not a substitute for those checks.
When a material change is observed
A company announcement, direct reply, account review or other suitable evidence can create a specific task. Confirm the relevant entity and field before overwriting a reviewed CRM value.
When delivery or contact outcomes reveal a problem
Classify the actual result. A confirmed invalid recipient, a temporary deferral and an authentication failure require different responses; not every bounce proves that the person's address changed.
When the evidence is missing or conflicting
Record the uncertainty and assign research. A missing observation date is not proof that a value is current or that it is exactly a particular age.
Build a policy the team can execute
For each cohort, define the intended use, essential fields, consequence of an error, available evidence and review owner. Use those inputs to choose a routine review interval where one is useful.
- Name the cohort. Keep active conversations, new campaign candidates and unused stored records distinguishable.
- Specify the evidence. Decide what must be known before the next action.
- Set event triggers. Identify observations that require review before the routine interval.
- Assign the task. Route the specific field or eligibility question to an owner.
- Record the outcome. Preserve source, method, date, uncertainty and the next action.
- Review the policy. Adjust it from observed problems, workload and the consequence of missed changes.
There is no supported universal annual decay percentage or role-seniority shelf life in this process. A founder, an executive and an individual contributor all need evidence relevant to their actual record and intended use.
The CEO and founder audiences may need different account research, but their labels do not determine a mandatory refresh interval.
Refresh without overwriting the evidence
- Retain original source values and the current reviewed CRM values.
- Distinguish retrieval date from field observation and validation dates.
- Specify whether a null leaves a field unchanged or deliberately clears it.
- Review identity before linking or merging records.
- Keep conflicting values and material gaps in a review queue.
- Reapply preferences, suppression and ownership before activation.
A contact becoming more senior does not automatically increase buying intent. A new source value should change the next action only when it supports the actual task.
The freshness evidence framework explains how to grade known, unknown and conflicting field evidence. The CRM hygiene workflow develops the destination controls.
Understand what another retrieval can establish
Dievio contact search returns available matching records. Repeating it is not a native job-change alert or proof that every field was newly verified.
A free count preview measures matching contact records, not freshness, unique companies or mailbox validity. Use it for coverage questions rather than a record-validation decision.
A custom API workflow can own schedules and review queues around supported operations. It must preserve successful source results and reconcile exceptions; downstream recovery should not automatically repeat a potentially billable lookup.
Search retrieval charges for returned leads, empty searches cost zero and repeating retrieval can charge again. Saved-list downloads add no search-credit charge. Keep API and workspace budgets separate when designing repeated work.
Check whether the refresh process is useful
Track material corrections, unresolved conflicts, recurring source errors and the effort required. Measure whether the process supplies the evidence needed for the next task, not merely how many fields were overwritten.
Use the pre-export checklist before release. Keep a corrected or newly retrieved record separate from automatic campaign reactivation; readiness still depends on the intended use and its requirements.



