Candidate Data Decay Report 2026: How Fast Your Talent Pool Goes Stale (and What It Costs)

Last updated: 2026-06-18

A talent pool is the most perishable list a recruiter keeps, because its entire premise is people who might move, and people who move break their own records. The candidate you sourced three months ago may already sit at a different company, with a different title and a dead work email. This report quantifies how fast a candidate pool goes stale, why candidate data decays faster than most, what it costs in reachability and time-to-fill, and the re-verification cadence that keeps a pool worth sourcing from.

The thesis is that a sourced list is a depreciating asset from the day you build it, and the better the candidate, the faster their data rots. Treating a talent pool as a durable database you can work for months is the quiet reason so much sourcing effort lands on people who have already moved on. The fix is to re-verify a candidate's contact data at the moment of outreach, not when the pool was assembled.

Why candidate data is the most perishable

All B2B contact data decays, but candidate data has a structural disadvantage: you are deliberately targeting people in motion. Sourcing seeks strong, in-demand professionals, and those are precisely the people who get recruited, promoted, and poached most often. The very signal that makes someone a good candidate, that they are desirable, is the signal that their current data has a short shelf life.

This inverts the usual intuition that a carefully built pool is a stable asset. A pool of mediocre, static contacts would age slowly; a pool of strong, mobile candidates ages fast, because mobility is correlated with quality. So the better your sourcing, the faster your pool decays, which means the reward for finding great candidates is a list that needs refreshing sooner, not a database you can sit on.

The practical consequence is that recruiters cannot treat the pool the way a static CRM is treated. The end-to-end sourcing motion has to assume the data is moving underneath it, and build re-verification in rather than bolt it on later. The full sourcing approach is in the recruitment sourcing plan guide.

There is a lag effect that makes the real decay worse than the mobility rate alone implies. People do not update their profile the instant they move, so a pool captured at any moment holds a hidden layer of candidates who have already changed roles but whose record still reads as current. The pool therefore overstates its own freshness on the day you build it, because the not-yet-updated movers look fine until you reach out and discover the move the hard way.

Mobility also varies by segment, which matters for who you sourced. Fast-moving functions and industries, sales, tech, and the senior roles most recruiters chase, churn well above the average, so a pool of exactly the candidates you most want decays faster than the headline rate suggests. The more attractive your target profile, the shorter the window in which your sourced data stays true.

How fast a talent pool goes stale

The driver is job mobility, and it is well documented. US labour statistics, including JOLTS turnover data, put median employee tenure under four years and falling, and workforce research from the LinkedIn Economic Graph tracks a steady stream of role changes captured through profile updates. Roughly 15 to 20 percent of professionals change roles in a given year, and each move can break a title, an employer, a work email, and a direct phone at once.

Decay is uneven by field, which matters for what to refresh. Current employer and job title are the most volatile, because a single move invalidates both, and they are exactly the fields a recruiter screens on. Work email and direct phone follow the general contact-data curve and break with the move. Personal attributes, name and general background, are stable. So a candidate record can be perfectly correct on the durable fields and wrong on the ones that decide whether you can reach and qualify the person.

Put together, this means a sourced pool degrades fastest on its most useful fields, the current role and the working contact, within months of being built. The pool does not fail all at once; it quietly loses reachable, accurately-described candidates every month until a campaign runs into the decayed portion and the response rate disappoints. This is the recruitment-specific case of the broader B2B data-decay benchmark.

A concrete way to size your own decay is to re-verify a sample. Take a slice of a pool you built a few months ago and check it today: the share that has changed employer, shifted title, or now bounces is your real decay rate for that segment, and for the in-demand profiles most recruiters source it is usually higher than expected. Run that once and the abstract percentages become your own numbers, which tends to settle any debate about whether a re-verify step is worth it.

The half-life of a sourced list

Combine the rates and a sourced list has a measurable half-life. With current employer and title turning over at 15 to 20 percent a year, and contact fields decaying alongside, a pool built and shelved for a couple of quarters is materially wrong on a meaningful share of its key fields by the time you work it. The candidates are not gone, but a chunk of them can no longer be reached at the address on file or described accurately by the title you saved.

This is why a large saved pool can be worth less than a smaller fresh one. Volume captured once and left to age is not coverage; it is a snapshot of who your candidates used to be. The recruiter who maintains a smaller pool re-verified at the point of contact out-reaches the one sitting on a big stale list, because only the verified record is certain to connect to a current person in a current role.

The honest framing is that pool size is a vanity metric and contactable freshness is the real one. The number that predicts sourcing results is not how many candidates you have saved but how many you can actually reach today, in the role you think they hold, which is a freshness question answered at the moment of outreach rather than at list-build.

It is worth distinguishing the two ways a candidate record fails, because they need different responses. A record can be stale, accurate once and now outdated as the person moved, or it can be incomplete, never carrying a working contact in the first place. Re-verification fixes the first; enrichment fixes the second; and a pool usually suffers from both at once, which is why a single on-demand step that both refreshes and completes the record is worth more than either alone.

What candidate decay costs

The cost shows up directly in reachability and time-to-fill. Outreach to a candidate who has moved bounces or reaches the wrong context, the message references an employer they left, which both wastes the attempt and damages the impression with a passive candidate you wanted to court. Re-sourcing a candidate you already found, because the saved contact no longer works, is pure rework, and it stretches the days between opening a role and filling it.

The organizations handling this data mostly know it is shaky and mostly do not fix it. Deloitte's human-capital research has found that a large majority of leaders doubt the reliability of their workforce and candidate data, while only a small fraction report real progress on it. That gap, aware the pool is decaying, not acting on it, is where sourcing efficiency leaks quarter after quarter, and it compounds with every campaign run on an aging list.

There is a candidate-experience cost layered on top. A passive, in-demand professional judges an approach in seconds, and a message sent to a stale address that bounces, or one that misreads their current role because the data is old, reads as carelessness from the employer brand they were supposed to be impressed by. Fresh, verified data is not only more efficient; it protects the first impression where it matters most.

The capacity angle makes this a leadership issue, not just a recruiter annoyance. Time spent re-sourcing decayed candidates and chasing dead contacts is non-recruiting time, the same drain that shows up across sales when reps work stale data, and it directly stretches time-to-fill. Reclaiming it does not just tidy the workflow; it adds sourcing capacity without adding headcount, which is exactly the trade a talent leader under pressure wants.

The re-verify cadence for a talent pool

The answer is to refresh the volatile fields at the point of use, not on a calendar. Re-verify a candidate's current employer, title, and working contact details just before you reach out, because everything between sourcing and outreach is unseen decay, and the highest-value, most mobile candidates are the ones most likely to have moved in that gap. Treat the pool as a starting list to confirm, not a finished database to trust, and measure your contactable rate, the share you can actually reach, as a standing metric.

This is the layer Derrick provides. Once you have a shortlist or a pool, Derrick re-verifies and enriches a candidate on demand directly inside Google Sheets, refreshing the current company and title, finding and verifying a work or personal email and a phone, so the outreach lands on a current, reachable person rather than a snapshot from when you sourced them. The pool becomes a live list, which mechanically answers the decay this report documents, without pretending any sourced list stays true on its own. Re-verify your candidate data on demand with Derrick, free for 100 credits per month, directly in Google Sheets.

The broader sourcing picture, time-to-fill, the reachability wall, and response rates, is in the companion talent sourcing report; this report is the decay-specific deep dive that explains why a pool you trust quietly stops working.

This white space is worth naming: plenty of talent reports benchmark time-to-fill and cost-per-hire, but few quantify how fast the candidate pool itself rots, even though that decay is what quietly turns a good pool into a list of people you can no longer reach. For a function judged on speed, the perishability of its core asset, the pool, is among the most consequential and least measured variables in the whole sourcing motion.

Methodology and sources

This report draws on non-vendor, primary sources: US labour statistics and JOLTS turnover data for employee tenure and job mobility; the LinkedIn Economic Graph for how role changes surface through profile updates; Deloitte's Global Human Capital research for the reliability of workforce and candidate data; and SHRM for talent-acquisition context. Per-field decay is presented using job-mobility data and the structural logic of role-tied records; where a candidate-decay figure could only be traced to a sourcing or enrichment vendor's marketing, we did not cite it, and LinkedIn is treated as a macro workforce reference rather than a tool to compare against.

A closing thought. The instinct in sourcing is to build a bigger pool, as if scale were safety. Decay says the opposite: the bigger and better the pool, the faster it ages, because quality and mobility move together. The recruiters who fill roles faster are not the ones with the largest saved lists but the ones who re-verify a candidate at the moment they reach out, so the strong passive candidate they worked hard to find is still reachable, still in the role they think, and still worth the message. Build the pool, but trust the verification, not the list, and the strong candidate you sourced is still a candidate you can actually reach when it counts, in the role you think they hold, on a channel that still actually works on the day you reach out.