Check records with changed representation, conflicting contact instructions, missing sources or unknown review dates before you reuse them. Then review the older records that remain on this campaign's shortlist. Treat age as a reason to look again, rather than proof that an address has expired. A record checked yesterday still needs attention if the creator announces a new manager today.
Build the queue around the next campaign
Start with creators you intend to approach for this campaign. Refreshing every historical contact can consume the time needed to resolve the records you will use next.
Keep a separate hold list for records with a do-not-contact instruction or an unresolved permission question. Finding a newer public address must not automatically return those records to outreach. A contact refresh answers whether the recorded route is current. Your team still needs to decide whether the proposed message is permitted and welcomed for that purpose.
For that separate decision, use the public-contact review before a CRM import. Do not treat a public address as permission to market.
Use this queue as an operational recommendation. The priority labels below are your team's workflow, not platform rules.
| Priority | Signal in the record | Action before use |
|---|---|---|
| Hold | Contact restriction or unresolved permission question | Keep out of the campaign export; route to the responsible reviewer |
| First | Creator reports a new manager, agency or business route | Recheck representation and the scope of the new route |
| First | Current source conflicts with the saved address | Resolve the conflict; leave the record on hold meanwhile |
| First | No source URL, unknown creator match or no source-check date | Re-establish the source and identity before use |
| Next | Older source check with no known change | Reopen the source and compare its current instructions |
| Lower | Recent source check, clear purpose and no known conflict | Confirm that the campaign matches the recorded route |
Within each priority, review the records needed for the earliest outreach batch first. A large follower count should not let a conflicted address skip review.
Choose review dates without inventing an expiry rule
A contact's collection date tells you when someone saved it. It does not tell you whether anyone has checked the source since then. An import date may be newer still, even when the underlying research is old.
Use the last completed source check when sorting records by age. Keep records with no check date in their own group; treating a blank as today's date hides the uncertainty.
The UK's ICO accuracy guidance ties updating personal data to its intended use. It also says that new information suggesting a record is wrong should prompt reconsideration and correction. This supports a change-triggered review process where UK GDPR applies. It does not supply a universal expiry period for creator email addresses. The ICO page currently says it is under review following the Data (Use and Access) Act.
Set a review date based on your next planned use and the unresolved risks. You can choose an internal age threshold to organize workload, but label it as a team policy. Do not present that threshold as a guarantee that younger records are accurate.
Recheck the route and its purpose
Open the recorded source and ask whether it still connects this creator to this business contact. Follow current links from the creator's profile when the old destination has disappeared. Read the routing language as well as the address.
For a YouTube record, YouTube's Business Inquiry Emails help describes checking the channel's About section and selecting the email-viewing option. The address is available only when the channel owner has supplied one. If you cannot view a current address through the permitted route, record that limit. Do not guess a replacement or bypass an access check.
A representation change needs more than an address replacement. Determine whether the listed representative handles the campaign's territory and type of work. A press contact and a sponsorship contact may serve different purposes. Use the manager-routing guide when deciding whom to approach.
If sources disagree, preserve the disagreement in a short note and keep the record out of the send list. A newer timestamp on an imported file does not resolve conflicting instructions.
Modash's relationship-management article discusses maintaining relationships with talent managers and assigning a point of contact. Apply that organizational idea to the refresh process: give each disputed record one reviewer. Otherwise, two teammates may replace each other's contact decisions without resolving the underlying conflict.
Record what the review established
Use fields that distinguish a successful source check from an attempted visit.
| Field | What to record |
|---|---|
| Creator record | The stable internal record and current profile URL |
| Source URL | The page that currently supports the business route |
| Contact role and scope | Creator or representative; stated purpose or territory |
| Last source check | Date a reviewer read and confirmed the relevant source |
| Last review attempt | Date of the latest attempt, including blocked or unavailable pages |
| Review outcome | Confirmed, changed, conflicting or unresolved |
| Change reason | The fact that prompted review, such as new representation |
| Reviewer and next action | Who owns the record and what must happen before use |
| Next review trigger | Planned campaign use, a review date or a reported change |
For the underlying source log, follow how to record where each creator email came from. Keep the refresh note focused on what changed and what remains uncertain.
An unavailable page should update the attempt date, not the last confirmed source-check date. Likewise, opening the spreadsheet or moving a row to a new CRM does not count as reading the source.
Work through a hypothetical refresh batch
The following records and ages are hypothetical. They illustrate queue order, not recommended expiry limits.
| Record | Last source check | New evidence | Decision |
|---|---|---|---|
| Creator A | 8 days ago | Current profile names a different agency | Review first; exclude old route pending resolution |
| Creator B | Unknown | Imported address has no source | Review first; reconstruct traceable business source |
| Creator C | 140 days ago | No known change | Review next because the source check is older |
| Creator D | 3 days ago | Current source still matches this campaign's purpose | Lower priority; keep the completed review visible |
Creator A comes before Creator C despite the newer check. The new agency information creates a specific reason to doubt the saved route. Creator B's import date cannot repair the missing source.
If Creator C's page cannot be opened, the outcome stays unresolved. The campaign deadline does not turn an incomplete check into a confirmed contact.
Before handing off the batch, filter out every hold and unresolved row. Give the outreach owner the confirmed records, their source-check dates and any limits on the contact's scope. Start by assigning a reviewer to the first changed-representation or untraceable record in your next campaign.
