vcity logo

Lead Lists Have Two Dates: How Source and Verification Dates Age Your Data

SmartLeads
SmartLeads

nov 13 2026 · 4 min read

0

A lead list is a snapshot, not a live feed

When a lead list lands in your inbox, it feels finished. The file opens, the columns line up, and every row looks equally ready to contact. In practice, each row carries its own age, and the differences between rows are where most surprises come from.

Two dates do most of that work: the source date (when the list was compiled) and the last-verified date (when a record was last checked). They are rarely the same, and the gap between them tells you what to trust and what to re-check.

What each date actually tells you

Source or compile date. When the records were gathered and matched against the criteria you asked for — industry, company size, geography, role. It tells you whether the file still reflects the market you described.

Last-verified date. When someone last checked a record. On a well-built file this is per record, not one date for the whole list, because records are checked in batches over time.

Neither date says "this person will reply". Verification reduces the risk of a bad address or a stale field. It does not measure interest, timing, budget or permission. A verified email is a starting point, not a promise.

What ages fast, and what barely ages

Some fields decay quickly:

  • Job titles and roles, especially in fast-growing companies
  • Work email addresses, which change with roles and rebrands
  • Company names after mergers or repositioning
  • Headcount bands, when a company crosses a threshold
  • Contact preferences and opt-outs, which change without warning

Other fields stay useful for much longer:

  • Industry classification
  • Country and region
  • Broad company-size band
  • Whether the company still exists and operates in your market

This is why an older file is not uniformly stale. Parts of it need a fresh check; other parts are still perfectly usable as a research base.

A three-tier re-check routine

Sort the file by last-verified date and split it into tiers before you write a single message.

  • Tier A — newest records. Use these first, in small batches, so you can watch replies and bounces before committing volume.
  • Tier B — middle-aged records. Spot-check the title and the email domain before writing, since role changes are the most common break.
  • Tier C — oldest records. Treat these as a research list. Confirm the role and the company before any outreach, and expect a smaller usable share than in Tier A.

Those thresholds are rules of thumb, not formulas. A market where people change jobs often decays faster than a stable, specialist industry.

A clearly fictional example

The following numbers are invented to show the method, not a benchmark.

Imagine a 500-record list compiled in March and verified in April, opened in November. Split by last-verified date: 120 records from the last 60 days, 260 from three to nine months ago, and 120 older than nine months. Rather than loading all 500 into the CRM at once, the team works Tier A first, spot-checks Tier B, and re-researches Tier C. The point is not a specific yield. It is that one file can contain three different levels of confidence, and the date column is what shows you which is which.

How this shapes the package you choose

  • A one-time pack is a fixed snapshot. It is a good fit for a short, defined campaign where you know how many conversations you can handle — and where you accept that the file ages from the moment it is delivered.
  • A monthly subscription is built for teams that contact leads continuously. Check what the listing says about delivery and volume, and ask how dates are recorded in your files; do not assume a refresh policy that has not been published.
  • A custom-list quote is where you can be most specific. When you request the quote, state the criteria and ask which dates will appear in the delivered file.

You can see the current options on our store: https://vcity.io/orgs/smartleads

Three questions to ask before you buy

  1. Will the file show a compile date and a per-record last-verified date?
  2. Which fields were verified, and which were only matched to my criteria?
  3. What should my team re-check ourselves, and how often?

Put the dates to work in your CRM

Keep both dates as fields, not as a note in an email thread. Add a source field, a last-verified field, and a simple rule for how old a record can be before it needs a fresh check. Then segment your sends by tier so your best records get your best attention.

If you are still preparing the file for import, our checklist on mapping, deduplication and source dates walks through the field-by-field routine: https://vcity.io/orgs/smartleads/blog/before-you-import-that-lead-list-a-csvexcel-checklist-for-your-crm

Dates will not tell you who wants to buy. They will tell you where to spend your first hour, and that is usually enough to make the next list a better decision than the last one.

SmartLeads

Written by

SmartLeads

@smartleads

Comments

Please login to interact