Data Freshness Scoring: How to Rate B2B Lead Data Quality by Recency and Source Reliability

Every outbound operator knows the sinking feeling: you sequence a batch of leads, hit send, and watch your delivery rates tumble while bounce notices pile up. The data looked fine on paper—complete records, decent titles, company names that matched your ICP. But the emails bounced, the phones rang disconnected, and the LinkedIn profiles had job changes from 18 months ago. Your SDRs just spent three days building sequences on a list that was already dead when it landed in your CRM.

Stale data is the silent killer of B2B outbound velocity. Industry benchmarks show that B2B email lists decay at roughly 30% per year for mid-market contacts, with senior roles rotting faster as executives change companies more frequently. For a team sending 2,000 emails per month, that decay rate means 600 contacts become unreachable within twelve months without any refresh. The cost is not just missed conversations—it's wasted SDR hours, damaged sender reputation, and sequence data that teaches your outreach algorithm the wrong lessons about timing and messaging.

Freshness scoring replaces gut-feel data quality checks with a consistent, repeatable rating system that scales across large lead lists and multiple data vendors. Instead of guessing whether a record is usable, you assign a numeric score based on three dimensions: how recently each field was verified, how reliable the source is, and how quickly the data is likely to expire. That score determines exactly what happens next—immediate sequence, light enrichment, full refresh, or archive.

This article gives you a concrete framework for building a freshness scoring system from scratch. You'll get a point-based rubric with tier definitions from Fresh to Stale, a source hierarchy that weights vendors by reliability, decay modeling tables by role seniority, and a step-by-step workflow for applying scores to raw lead lists before campaigns launch. The goal is to make every contact dollar count by routing the freshest data to your highest-converting sequences.

Outbound teams lose deals to stale data long before a conversation starts. A contact record that looks complete but contains an email address that bounced last month or a job title that changed three quarters ago is worse than no data at all—it creates false confidence, burns sequence capacity, and contaminates your deliverability metrics.

Consider the math on a typical outbound batch. A team purchases a list of 5,000 contacts at a vendor's standard price. Without a freshness scoring system, the team loads all 5,000 into their CRM and sequences them over 30 days. If the list was sourced six months ago and the provider does not re-verify regularly, the likely outcome is a 20-30% bounce rate on email, a 40% disconnect rate on phone numbers, and reply rates that land below 0.5% because the titles and companies no longer match the ICP. The SDR team spent 150 hours building and executing sequences that produced a fraction of the expected pipeline.

Freshness scoring prevents that waste. By evaluating each record before it enters a sequence, you can route only the highest-confidence contacts to your top-priority campaigns, send aging records to enrichment before outreach, and archive records that have decayed beyond usability. The result is better deliverability, higher reply rates, and SDR time spent on contacts that are actually reachable and relevant.

Salesforce's guide to B2B lead generation emphasizes that data quality directly impacts conversion rates—teams that systematically score and maintain lead data see measurable improvements in opportunity creation and pipeline velocity. Freshness scoring is the operational mechanism that makes that principle real at scale.

A single "last verified" timestamp is not enough to judge data freshness. Two records might both show a verification date of 45 days ago, but one came from a direct phone confirmation by a vendor's research team while the other was inferred from a job board posting that may never have been accurate. The first record is almost certainly reachable; the second is a gamble.

Freshness scoring evaluates three independent dimensions, each contributing a component to the final score:

• Recency—how recently each individual field (email, phone, job title, company, LinkedIn URL) was last verified by a reliable source. Recency is the most intuitive dimension, but it must be applied per field, not as a single record-level date.
• Source Reliability—where the data originated and what validation process it passed. A direct verification from a human researcher is worth more than a scrape from a public directory, even if both timestamps show the same date. Source reliability acts as a confidence multiplier on recency.
• Decay Risk—how quickly each data point is likely to expire based on the role's stability, the industry's turnover rate, and the company's growth stage. A VP of Sales at a Series A startup has a much higher decay risk than a Staff Engineer at a public enterprise, even if both records were verified on the same day.

Each dimension produces a sub-score. The combined freshness score is a weighted sum that maps to a 0-100 scale. The practical output is a tiered classification—Fresh, Active, Aging, or Stale—that determines exactly what action to take with each record before it touches an outreach sequence.

Recency scoring assigns point values to each contact field based on how many days have passed since the last verified check. Because email is the primary outreach channel in most B2B sequences, email recency carries the highest weight. Phone numbers, job titles, company affiliations, and LinkedIn profiles each carry lower weights based on their importance to initial contact.

The scoring scale follows a sliding window that rewards recent verification and penalizes records that have not been checked in months. A verification within the last 30 days earns maximum points for that field. Between 31 and 90 days, points fall to a partial level. Between 91 and 180 days, points drop to a reduced tier. Beyond 180 days, the field earns minimal points regardless of how accurate it may have been originally.

Below is the recency scoring table for each field, with maximum point values and decay thresholds:

For additional context, see HubSpot on sales prospecting.

The maximum recency score for a perfect record with all five fields verified within 30 days is 100 points. In practice, most records will have partial coverage—some fields may be missing entirely, and others may have verification dates that fall into different windows. The recency sub-score is the sum of points earned across all available fields, then normalized to a 0-100 scale for combination with other dimensions.

Example: A contact record has an email verified 45 days ago (30 points), a phone verified 20 days ago (20 points), a job title verified 90 days ago (10 points), a company verified 120 days ago (6 points), and no LinkedIn URL. Total raw points: 66 out of 100 possible. Normalized recency sub-score: 66.

Recency alone is misleading if the source of verification is unreliable. A record with an email "verified" 15 days ago by a vendor that only checks syntax, not deliverability, is less trustworthy than a record verified 60 days ago by a vendor that sent a confirmation ping to the mail server. Source reliability scoring adjusts the recency sub-score based on the trustworthiness of the data origin.

Define three reliability tiers for data sources:

• Tier 1 — Direct Verification. Data confirmed through direct action: email bounce-back check, phone call confirmation, manual LinkedIn profile review, or direct confirmation from the contact. These sources produce the highest confidence because they involve active validation rather than passive inference. No discount is applied.
• Tier 2 — Multi-Source Consensus. Data that appears consistently across two or more independent providers or public sources, none of which individually qualify as direct verification. For example, if three lead databases all show the same job title for a contact and the title is corroborated by a public LinkedIn scrape, the confidence is moderate. Apply a 20% discount to the recency sub-score.
• Tier 3 — Single-Source or Inferred. Data that comes from a single vendor scrape, a job change inferred from news without confirmation, or a public directory that has not been validated. These records carry the highest risk of inaccuracy. Apply a 40% discount to the recency sub-score.

Source tier assignment must be done at the field level, not the record level. A record might have a Tier 1 email (verified by bounce check) but a Tier 3 job title (scraped from a single source six months ago). The recency points for each field are multiplied by the source multiplier before summation.

Continuing the example from the previous section: the email (Tier 2) receives a 20% discount on its 30 recency points, yielding 24 points. The phone (Tier 1) receives no discount, keeping its 20 points. The job title (Tier 3) receives a 40% discount on 10 points, yielding 6 points. The company (Tier 2) receives a 20% discount on 6 points, yielding 4.8 points. The normalized recency-source sub-score becomes 54.8, down from 66 due to source reliability adjustments.

Source reliability scoring answers the question that recency alone cannot: is this data trustworthy even though the timestamp looks current?

The third dimension of freshness scoring looks forward rather than backward. Even a record with a recent verification and a reliable source may be at high risk of decay if the contact holds a role that churns quickly or works at a company with high turnover. Decay risk modeling assigns a penalty based on the expected shelf life of each field given the contact's seniority, industry, and company stage.

Different roles decay at different rates. Executive and VP-level titles change jobs more frequently than individual contributors or managers because senior hires are often targeted by recruiters and have shorter tenures at growth-stage companies. Company size also matters: startups under 50 employees have higher churn rates than enterprises with established HR infrastructure.

The reference table below shows average field shelf life by seniority band, based on aggregated tenure data across B2B sales and marketing roles:

Decay risk is expressed as a forward-looking penalty applied to the combined recency-source sub-score. If a contact's record is 6 months old and the average title shelf life for that seniority band is 12 months, the record is at 50% of its expected title lifespan—a moderate decay risk. Apply a small penalty (5-10 points). If the record is 10 months old on a 14-month shelf life, the risk is high, and the penalty increases (15-20 points).

Industry factors also matter. Technology, SaaS, and professional services tend to have higher turnover rates than manufacturing, government, and healthcare. For industries with above-average churn, apply an additional 5-point decay penalty across all fields.

Decay risk modeling is the dimension that transforms freshness scoring from a historical evaluation into a predictive tool. It answers the question: how likely is this data to still be accurate when the sequence reaches this contact in 2-4 weeks?

For additional context, see Salesforce guide to B2B lead generation.

The combined freshness score is a weighted sum of the three dimensions: recency (adjusted for source reliability) minus the decay risk penalty. The formula is simple:

Freshness Score = (Recency-Source Sub-score) - (Decay Risk Penalty)

The result is a number between 0 and 100. That number maps to one of four confidence tiers, each with a distinct action threshold for routing records into your outreach workflow:

The four tiers create a clear decision framework that scales across lists of any size. A team processing 10,000 records can apply the scoring rubric, segment into tiers, and route each tier to the appropriate workflow in a single batch operation. The tier definitions also provide a common language between operations teams and SDRs—everyone knows what "Aging" means and what to do with it.

LinkedIn's lead scoring documentation emphasizes that recency signals and source attribution are critical inputs to any scoring model—the same logic applies at the data freshness level. A contact with a Fresh score is a contact you can confidently sequence today. A contact with a Stale score is a contact you should not touch until the data has been rebuilt.

Freshness scoring is not a theoretical exercise—it is an operational process executed on raw lead lists before they enter your CRM or sequence tools. Below is a step-by-step workflow that any B2B team can implement with spreadsheet functions or API calls:

1. Export the raw list with all available metadata, including field-level verification dates, source tags for each field, and any existing confidence scores from your data providers. Do not skip fields that seem unimportant—company verification dates and LinkedIn URLs contribute to the total score.
2. Tag each field with its last-seen date. If a field does not have a verification timestamp, assume it is older than 180 days and assign the minimum recency points. Maintain a strict policy: no timestamp means no recency credit.
3. Cross-reference source data for each contact. If you use multiple vendors, tag each field with its source tier (Tier 1, 2, or 3). If a field comes from a vendor you cannot classify, default to Tier 3 and apply the 40% discount.
4. Calculate the combined freshness score for each record using the recency table, source multipliers, and decay risk penalty. Use a spreadsheet with lookup functions or an API endpoint that accepts verification dates and source tags as inputs.
5. Segment into tiers based on the 0-100 score. Create separate lists or CRM lists for Fresh, Active, Aging, and Stale records.
6. Route each tier: Fresh records go to your highest-priority sequence immediately. Active records enter a standard sequence with a pre-send email verification step. Aging records are queued for enrichment before any touch. Stale records are archived or removed from the active list.

Automation makes this workflow scalable. If your data provider offers API access to field-level verification dates and source metadata, you can pull freshness scores on demand and update CRM fields programmatically. This approach ensures that every record entering your outbound pipeline has a score before it ever reaches an SDR's queue.

Enrichment costs credits, and archiving saves time. The freshness score gives you a data-driven rule for deciding which records deserve enrichment investment and which should be retired. The decision logic follows score thresholds tied to campaign priority and available budget:

• Score above 60 (Fresh + Active). No enrichment needed for standard outbound. These records are ready to sequence as-is. For high-priority accounts or enterprise deals, you may choose to enrich anyway for maximum confidence, but the cost is optional.
• Score 40-60 (Aging). Full record refresh recommended. Run email verification, title and company enrichment, and phone number re-verification before any outreach. The enrichment cost is justified because the account is likely still relevant—the data just needs updating.
• Score below 40 (Stale). Decision threshold. If the account is a high-priority target (named account, top ICP segment, recent intent signal), run deep-verification on all fields before deciding whether to retain. If the account is low-priority or bulk list filler, archive immediately and do not spend enrichment credits.

The decision framework prevents two common mistakes: wasting enrichment budget on records that are too far gone, and discarding valuable contacts that just need a light refresh. By tying the decision to a numeric threshold, you eliminate guesswork and ensure consistent treatment across your entire lead database.

For teams that operate enrichment pipelines, the freshness score acts as the trigger for when to pull new data. A record that scores 45 today should be sent to enrichment before it enters a sequence next week. A record that scores 25 today should be evaluated for archival unless it sits on a high-value account list. This logic integrates directly with data enrichment workflows that refresh contact data from multiple sources.

Freshness is not a stationary attribute—scores decay continuously as verification dates age. A record that scores 90 today will drop below 85 in two months if none of its fields are re-verified. Without ongoing monitoring, your entire lead database drifts toward the Stale tier without anyone noticing until bounce rates spike.

Set up a quarterly re-scoring cadence for all active lists. Run the freshness scoring algorithm on the first day of each quarter and compare the distribution of tiers from the previous quarter. If the percentage of Fresh and Active records drops below 60% of the active list, trigger a batch enrichment campaign to pull verification dates forward for all records above the Aging threshold.

Define alert thresholds that flag issues before they affect campaign performance:

For additional context, see LinkedIn Sales Solutions on lead scoring.

• List average score below 60. The list is no longer fresh enough for reliable outreach. Pause active sequences on that list and prioritize a full refresh before resuming.
• More than 30% of records in Stale tier. Review the sourcing strategy for that list. A high proportion of stale records suggests the original data was purchased from a low-tier source or has not been refreshed since acquisition.
• Single-field decay spike. If phone numbers show a sudden drop in recency across the database while emails remain current, investigate whether a specific vendor stopped re-verifying phone fields.

Log freshness scores as custom fields in your CRM—one field for the composite score and one field for the last-scored date. This creates a historical record that lets you track score trends over time and correlate freshness changes with campaign performance. If reply rates drop by 20% in a quarter, you can check whether the average freshness score of the sequenced records also declined.

An auditing approach that reviews data stack health periodically—including freshness scores as a KPI—keeps the feedback loop tight between data operations and outbound results.

Freshness scoring is only effective if implemented correctly. The following mistakes undermine the system and produce misleading tier assignments that waste time or miss opportunities.

Treating all sources as equal. A vendor that verifies email deliverability daily is not the same as a vendor that scraped a directory two years ago and has never re-checked. Without source tiering, recency scores overstate the confidence of low-quality data. A record with a 10-day-old email from an unreliable source might score 85 and enter a Fresh sequence, only to bounce on the first send.

Ignoring decay risk. Two records with identical recency and source scores may have very different future reliability because one belongs to a VP at a startup and the other to an engineer at a public company. Decay risk is the dimension that distinguishes them. Failing to include it means your scoring system treats high-churn and low-churn roles the same, and you will over-invest in outreach to contacts who are likely to have moved before you reach them.

Scoring only email without evaluating title and company. A valid email address is useless if the contact has changed roles and no longer fits your ICP. Sending a personalized sequence to a "VP of Sales" who is now a "Director of Marketing" wastes the sequence and confuses your targeting metrics. Freshness scoring must cover at least the four primary fields—email, phone, title, and company—to produce a usable tier assignment.

Setting score thresholds too high. Some teams push the Fresh threshold to 95 or higher, expecting perfection from every record. The result is that 80% of their list lands in Aging or Stale, creating a bottleneck in the enrichment queue while SDRs wait for refreshed data. Realistic thresholds recognize that a score of 85 indicates a contact that is very likely reachable, even if one field is slightly outdated. Calibrate thresholds against your actual bounce and reply rates, not against an ideal of perfect data.

Not re-scoring after enrichment. Enrichment updates verification dates and may improve source tiering, but the freshness score does not automatically recalculate unless you re-run the scoring algorithm. Teams that enrich aging records and then immediately sequence them without re-scoring miss the opportunity to confirm that the refresh was successful. Build a re-scoring step into your enrichment workflow so that every record has a current score before it enters a sequence.

HubSpot's sales prospecting framework emphasizes that data quality is a continuous discipline, not a one-time check. Freshness scoring is the operational tool that makes that discipline practical—but only when the scoring system itself is maintained and calibrated against real-world outcomes.

Stale data is a tax on outbound velocity that compounds with every week it goes unaddressed. A team that sequences 2,000 contacts per month without freshness scoring is wasting roughly one out of every three sends on records that will never convert—either because the contact has moved, the email bounces, or the title no longer matches the ICP. The cumulative cost over a quarter is measured in lost SDR hours, degraded sender reputation, and pipeline that never materializes.

Freshness scoring replaces that waste with a systematic process. You evaluate recency per field, weight by source reliability, adjust for decay risk, and assign a numeric tier that tells you exactly what to do with each record. Fresh records go to the front of the line. Aging records get enriched before they reach an SDR. Stale records get archived unless they sit on a high-priority account.

The framework in this article gives you the scoring rubric, the tier definitions, and the workflow logic to implement freshness scoring today. The next step is applying it to your live lead lists—and that requires a data source that provides the field-level verification dates and source metadata your scoring algorithm needs.

Search fresh B2B leads on Dievio to access verified contact data with recency metadata built in, so your freshness scoring system always starts from a reliable baseline.

Related workflow: B2B Data Coverage, Accuracy, and Validation: What to Check Before You Buy.

Related workflow: How Often to Refresh B2B Lead Data Before It Decays.

Build Your First Outbound List to validate the segment before you commit to full outreach.