A dormant record is a candidate or contact with no meaningful activity in 12 months. No outreach. No reply. No call. No submission. No status change.<\/p>\n
Run that filter tonight. The number will be worse than you think. A firm with 100,000 candidate records typically finds 50,000 to 70,000 of them untouched.<\/p>\n
Here’s the part that matters: dormant is not dead.<\/p>\n
Some of the most valuable records in your CRM went quiet for a boring reason. Nobody had a live role that fit. That’s it.<\/p>\n
Think about a candidate you shortlisted eighteen months ago. Their record has interview feedback. Salary expectations. Notice period. A recruiter’s note about why they turned the last offer down. Someone on your team spent hours building that.<\/p>\n
Or a hiring manager who signed off on three placements and then went quiet. That contact has something no prospect has. A history of paying your invoices.<\/p>\n
Your competitor has none of this. They’re starting from a name and a LinkedIn profile.<\/p>\n
So the cost isn’t that these records exist. The cost is what happens while they sit there.<\/p>\n
<\/span>It’s a Revenue Problem, Not a Data Problem<\/span><\/h2>\nRecruiting is a conversion business. The benchmark data says so plainly.<\/p>\n
71% of placements come from candidates who were already in the CRM before the role opened<\/strong> (Source: The Economics of Recruiting<\/a>)<\/em>, from Recruiterflow’s study of 2,100+ recruiting firms.<\/p>\nNow put a second number from that dataset next to it. It takes roughly 213 sourced candidates to produce one hire<\/strong>.<\/p>\nSit with those two for a second.<\/p>\n
Most of your placements come from people you already have. Most of your recruiters’ hours go to finding people you don’t.<\/p>\n
The same study found something that surprises most owners. Top-quartile firms add fewer<\/em> candidates per recruiter than everyone else. 800 versus 930. And they place 5.21 per recruiter against 1.38.<\/p>\nThey’re not winning by sourcing harder. They’re winning by converting better. And the raw material for conversion is the database.<\/p>\n
Which reframes the whole problem. When a database goes dormant, you don’t lose data. You lose the channel that produces 71% of your revenue, one record at a time. Then you spend money on job ads to replace it.<\/p>\n
That’s a big part of the $168,000 annual revenue gap per recruiter<\/strong> between the top 25% of firms and everybody else (Source: The Economics of Recruiting<\/a>)<\/em>.<\/p>\n![\"Economics](\"https:\/\/recruiterflow.com\/blog\/wp-content\/uploads\/2026\/05\/5-1024x342.png\")
<\/a><\/p>\n<\/span>The Model: Five Inputs, One Afternoon<\/span><\/h2>\nYou can run this today. It gives you an annual cost figure, not a forecast. The goal is to find out whether the number is big enough to deserve recruiter time.<\/p>\n
Input 1: Warm dormant records (W).<\/strong> Not your whole database. Only records with commercial history. Previously submitted, interviewed, shortlisted, placed. Plus clients who have paid you before.<\/p>\nInput 2: Reactivation-to-placement rate (R).<\/strong> Use 2% to 3%. Everyone’s first instinct is to use 10%. Don’t. A conservative number is one you can defend to your leadership team without a fight.<\/p>\nInput 3: Average placement fee (F).<\/strong> Your trailing twelve months. Not your best quarter.<\/p>\nInput 4: Recovery window (T).<\/strong> How many years of dormant records you’d genuinely work. One to two years is honest. Five is a spreadsheet fantasy.<\/p>\nInput 5: Current recovery rate (C).<\/strong> What share of that warm pool your team actually touches in a year. Without a system, it’s usually under 5%.<\/p>\nThen:<\/p>\n
Recoverable revenue = W \u00d7 R \u00d7 F<\/p>\n
Annual cost of dormancy = Recoverable revenue \u00d7 (1 ? C)<\/p><\/blockquote>\n
Here’s a worked example. A 12-recruiter firm:<\/strong><\/p>\n\n- 4,000 warm dormant records<\/li>\n
- 2.5% reactivation-to-placement rate, so 100 placements<\/li>\n
- $22,000 average fee, so $2.2M recoverable<\/strong><\/li>\n
- Currently touching 5% of the pool<\/li>\n
- Annual cost of dormancy: around $2.09M<\/strong><\/li>\n<\/ul>\n
To be clear, that’s not money you’re going to collect. It’s the size of a channel your firm owns outright and isn’t operating.<\/p>\n
Two decisions come out of it. Does the pool justify dedicated recruiter time? And does it justify a system that surfaces the pool so nobody has to remember to look?<\/p>\n
Getting input W right is the hard part. The six-step recruiting database audit<\/a> walks through how to find which dormant records still carry value.<\/p>\n<\/span>Four Costs the Model Misses<\/span><\/h2>\nThe calculation above measures revenue you didn’t earn. These four hit the P&L directly.<\/p>\n
1. You pay for the same person twice<\/h3>\n
A candidate goes dormant. Six months later they apply through a job board, or a recruiter finds them on LinkedIn, or they click an ad you paid for.<\/p>\n
You just bought them again.<\/p>\n
The first acquisition is already sunk. The sourcing hours, the screening call, the interview debrief. The second one lands on this year’s marketing spend.<\/p>\n
Almost nobody reconciles the two, because the CRM sits in one report and the job board budget sits in another.<\/p>\n
2. Speed, which decides contingent work<\/h3>\n
A dormant record starts every search from cold. Someone has to verify the email, check the title, find out if they even want to move.<\/p>\n
Firms running automated job-change monitoring cut time to first submittal by 34% and see 12% higher placements<\/strong> (Source: AI & Recruitment Automation Playbook<\/a>)<\/em>.<\/p>\nOn a contingent brief with three firms working it, that gap decides who invoices.<\/p>\n
3. The client side, which usually costs more<\/h3>\n
Dormant candidates cost you placements. Dormant clients cost you accounts.<\/p>\n
Picture a hiring manager who placed two roles with you, then moved to a new company. Your CRM calls them a stale contact. They’re actually a warm business development opportunity with budget authority, sitting in a field nobody queries.<\/p>\n
For most firms, the lapsed client is the more expensive loss. The database resurrection playbook<\/a> covers both sides.<\/p>\n4. Decay, which compounds while you decide<\/h3>\n
HubSpot’s database decay simulation<\/a>, built on MarketingSherpa research, puts B2B contact decay at 2.1% per month.<\/p>\nTitles change. Emails bounce. Direct lines get reassigned.<\/p>\n
A record you could have called for free in January costs you an enrichment credit and an hour of research by December. And the relationship context, the part that made the record worth having, fades faster than the phone number.<\/p>\n
The good news is that compounding runs both ways. A 10% lift in submissions per recruiter produces a 4.6% lift in revenue per recruiter<\/strong> (Source: The Economics of Recruiting<\/a>)<\/em>. Warm dormant records are the cheapest submissions available to you, because the screening is already done.<\/p>\n<\/span>What Recovery Actually Looks Like<\/span><\/h2>\nPlenty of firms run this calculation, wince, and carry on exactly as before. Two things separate the ones that don’t.<\/p>\n
They work a ranked queue, not a database.<\/strong><\/p>\nReactivation dies the moment it becomes a cleanup project. Nobody finishes a cleanup project.<\/p>\n
It works when it produces something small and specific. Forty people worth calling this week, ranked by how close each one came to producing revenue last time.<\/p>\n
Prioritisation is the entire discipline. For surfacing past candidates against live roles specifically, talent rediscovery<\/a> has the workflow.<\/p>\nThey stop relying on recruiters to notice.<\/strong><\/p>\nNo consultant is checking 4,000 profiles for job changes. Let’s be realistic about that.<\/p>\n
Either a system watches for movement or nobody does. Recruiterflow’s AIRA Job Change Alert Agent<\/a> tracks candidates and contacts for role changes and updates the record. A dormant profile becomes a reason to pick up the phone.<\/p>\nAIRA Matchmaker works the other direction. It matches a live brief against candidates already in your database by meaning rather than keyword, so your first shortlist draws on people your firm has already met.<\/p>\n
One caveat worth stating. The more valuable the relationship, the more human the re-engagement should be. If a partner placed an executive five years ago and that person just became a CEO, that call comes from the partner. Not a sequence.<\/p>\n
The system’s job is to surface the moment. The consultant’s job is to work it.<\/p>\n
And prevention beats the cure every time. If records update as a by-product of normal recruiting work, from calls, notes, status changes and detected job moves, your database never accumulates a decade of dormancy in the first place.<\/p>\n
![\"\"](\"https:\/\/recruiterflow.com\/blog\/wp-content\/uploads\/2026\/08\/banner2aira-1024x280.png\")
<\/a><\/h2>\n<\/span>FAQs<\/span><\/h2>\nHow long before a candidate record goes stale?<\/strong><\/h3>\nContact fields decay at roughly 2.1% per month, according to HubSpot’s decay simulation<\/a>. Relationship context goes faster. What a candidate told you about compensation eighteen months ago is probably wrong today, even if their email still works.<\/p>\nIs it cheaper to reactivate a dormant candidate than source a new one?<\/strong><\/h3>\nAlmost always. The sourcing and screening cost is already sunk, and the record carries interview history a new candidate doesn’t have. It’s why top-quartile firms add fewer candidates per recruiter and still place nearly four times as many (Source: The Economics of Recruiting<\/a>)<\/em>.<\/p>\nShould I delete dormant records or keep them?<\/strong><\/h3>\nDormancy on its own is a weak reason to delete. Base the decision on commercial value, reachability, and your lawful basis for holding the data. Requirements vary by jurisdiction, so follow your firm’s legal guidance rather than a blanket rule.<\/p>\n
Do dormant records create compliance risk?<\/strong><\/h3>\nThey can. Most data-protection regimes tie retention to a stated purpose and a defined period, and a record nobody has touched in three years is harder to justify. Handle retention policy inside the audit, not as a separate project.<\/p>\n
How often should a firm audit its database?<\/strong><\/h3>\nA full audit once a year, with lighter quarterly reviews of your best candidate and client segments. Firms with continuous job-change detection need much less manual auditing, because freshness is maintained instead of restored.<\/p>\n
Which is worth more, a dormant candidate or a dormant client?<\/strong><\/h3>\nUsually the client. A dormant candidate is one potential placement. A lapsed client who used to send you multiple roles is a revenue stream. And a client contact who moved companies is a second one.<\/p>\n
Can AI reactivate a dormant database without generic outreach?<\/strong><\/h3>\nThe useful role for AI is surfacing and preparing, not sending. AIRA agents detect job changes, refresh records, and match existing candidates to live briefs. The message that actually lands still comes from a recruiter who knows the history.<\/p>\n","protected":false},"excerpt":{"rendered":"
Now put a second number from that dataset next to it. It takes roughly 213 sourced candidates to produce one hire<\/strong>.<\/p>\n Sit with those two for a second.<\/p>\n Most of your placements come from people you already have. Most of your recruiters’ hours go to finding people you don’t.<\/p>\n The same study found something that surprises most owners. Top-quartile firms add fewer<\/em> candidates per recruiter than everyone else. 800 versus 930. And they place 5.21 per recruiter against 1.38.<\/p>\n They’re not winning by sourcing harder. They’re winning by converting better. And the raw material for conversion is the database.<\/p>\n Which reframes the whole problem. When a database goes dormant, you don’t lose data. You lose the channel that produces 71% of your revenue, one record at a time. Then you spend money on job ads to replace it.<\/p>\n That’s a big part of the $168,000 annual revenue gap per recruiter<\/strong> between the top 25% of firms and everybody else (Source: The Economics of Recruiting<\/a>)<\/em>.<\/p>\n You can run this today. It gives you an annual cost figure, not a forecast. The goal is to find out whether the number is big enough to deserve recruiter time.<\/p>\n Input 1: Warm dormant records (W).<\/strong> Not your whole database. Only records with commercial history. Previously submitted, interviewed, shortlisted, placed. Plus clients who have paid you before.<\/p>\n Input 2: Reactivation-to-placement rate (R).<\/strong> Use 2% to 3%. Everyone’s first instinct is to use 10%. Don’t. A conservative number is one you can defend to your leadership team without a fight.<\/p>\n Input 3: Average placement fee (F).<\/strong> Your trailing twelve months. Not your best quarter.<\/p>\n Input 4: Recovery window (T).<\/strong> How many years of dormant records you’d genuinely work. One to two years is honest. Five is a spreadsheet fantasy.<\/p>\n Input 5: Current recovery rate (C).<\/strong> What share of that warm pool your team actually touches in a year. Without a system, it’s usually under 5%.<\/p>\n Then:<\/p>\n Recoverable revenue = W \u00d7 R \u00d7 F<\/p>\n Annual cost of dormancy = Recoverable revenue \u00d7 (1 ? C)<\/p><\/blockquote>\n Here’s a worked example. A 12-recruiter firm:<\/strong><\/p>\n To be clear, that’s not money you’re going to collect. It’s the size of a channel your firm owns outright and isn’t operating.<\/p>\n Two decisions come out of it. Does the pool justify dedicated recruiter time? And does it justify a system that surfaces the pool so nobody has to remember to look?<\/p>\n Getting input W right is the hard part. The six-step recruiting database audit<\/a> walks through how to find which dormant records still carry value.<\/p>\n The calculation above measures revenue you didn’t earn. These four hit the P&L directly.<\/p>\n A candidate goes dormant. Six months later they apply through a job board, or a recruiter finds them on LinkedIn, or they click an ad you paid for.<\/p>\n You just bought them again.<\/p>\n The first acquisition is already sunk. The sourcing hours, the screening call, the interview debrief. The second one lands on this year’s marketing spend.<\/p>\n Almost nobody reconciles the two, because the CRM sits in one report and the job board budget sits in another.<\/p>\n A dormant record starts every search from cold. Someone has to verify the email, check the title, find out if they even want to move.<\/p>\n Firms running automated job-change monitoring cut time to first submittal by 34% and see 12% higher placements<\/strong> (Source: AI & Recruitment Automation Playbook<\/a>)<\/em>.<\/p>\n On a contingent brief with three firms working it, that gap decides who invoices.<\/p>\n Dormant candidates cost you placements. Dormant clients cost you accounts.<\/p>\n Picture a hiring manager who placed two roles with you, then moved to a new company. Your CRM calls them a stale contact. They’re actually a warm business development opportunity with budget authority, sitting in a field nobody queries.<\/p>\n For most firms, the lapsed client is the more expensive loss. The database resurrection playbook<\/a> covers both sides.<\/p>\n HubSpot’s database decay simulation<\/a>, built on MarketingSherpa research, puts B2B contact decay at 2.1% per month.<\/p>\n Titles change. Emails bounce. Direct lines get reassigned.<\/p>\n A record you could have called for free in January costs you an enrichment credit and an hour of research by December. And the relationship context, the part that made the record worth having, fades faster than the phone number.<\/p>\n The good news is that compounding runs both ways. A 10% lift in submissions per recruiter produces a 4.6% lift in revenue per recruiter<\/strong> (Source: The Economics of Recruiting<\/a>)<\/em>. Warm dormant records are the cheapest submissions available to you, because the screening is already done.<\/p>\n Plenty of firms run this calculation, wince, and carry on exactly as before. Two things separate the ones that don’t.<\/p>\n They work a ranked queue, not a database.<\/strong><\/p>\n Reactivation dies the moment it becomes a cleanup project. Nobody finishes a cleanup project.<\/p>\n It works when it produces something small and specific. Forty people worth calling this week, ranked by how close each one came to producing revenue last time.<\/p>\n Prioritisation is the entire discipline. For surfacing past candidates against live roles specifically, talent rediscovery<\/a> has the workflow.<\/p>\n They stop relying on recruiters to notice.<\/strong><\/p>\n No consultant is checking 4,000 profiles for job changes. Let’s be realistic about that.<\/p>\n Either a system watches for movement or nobody does. Recruiterflow’s AIRA Job Change Alert Agent<\/a> tracks candidates and contacts for role changes and updates the record. A dormant profile becomes a reason to pick up the phone.<\/p>\n AIRA Matchmaker works the other direction. It matches a live brief against candidates already in your database by meaning rather than keyword, so your first shortlist draws on people your firm has already met.<\/p>\n One caveat worth stating. The more valuable the relationship, the more human the re-engagement should be. If a partner placed an executive five years ago and that person just became a CEO, that call comes from the partner. Not a sequence.<\/p>\n The system’s job is to surface the moment. The consultant’s job is to work it.<\/p>\n And prevention beats the cure every time. If records update as a by-product of normal recruiting work, from calls, notes, status changes and detected job moves, your database never accumulates a decade of dormancy in the first place.<\/p>\n Contact fields decay at roughly 2.1% per month, according to HubSpot’s decay simulation<\/a>. Relationship context goes faster. What a candidate told you about compensation eighteen months ago is probably wrong today, even if their email still works.<\/p>\n Almost always. The sourcing and screening cost is already sunk, and the record carries interview history a new candidate doesn’t have. It’s why top-quartile firms add fewer candidates per recruiter and still place nearly four times as many (Source: The Economics of Recruiting<\/a>)<\/em>.<\/p>\n Dormancy on its own is a weak reason to delete. Base the decision on commercial value, reachability, and your lawful basis for holding the data. Requirements vary by jurisdiction, so follow your firm’s legal guidance rather than a blanket rule.<\/p>\n They can. Most data-protection regimes tie retention to a stated purpose and a defined period, and a record nobody has touched in three years is harder to justify. Handle retention policy inside the audit, not as a separate project.<\/p>\n A full audit once a year, with lighter quarterly reviews of your best candidate and client segments. Firms with continuous job-change detection need much less manual auditing, because freshness is maintained instead of restored.<\/p>\n Usually the client. A dormant candidate is one potential placement. A lapsed client who used to send you multiple roles is a revenue stream. And a client contact who moved companies is a second one.<\/p>\n The useful role for AI is surfacing and preparing, not sending. AIRA agents detect job changes, refresh records, and match existing candidates to live briefs. The message that actually lands still comes from a recruiter who knows the history.<\/p>\n","protected":false},"excerpt":{"rendered":"<\/a><\/p>\n<\/span>The Model: Five Inputs, One Afternoon<\/span><\/h2>\n
\n
<\/span>Four Costs the Model Misses<\/span><\/h2>\n
1. You pay for the same person twice<\/h3>\n
2. Speed, which decides contingent work<\/h3>\n
3. The client side, which usually costs more<\/h3>\n
4. Decay, which compounds while you decide<\/h3>\n
<\/span>What Recovery Actually Looks Like<\/span><\/h2>\n
<\/a><\/h2>\n<\/span>FAQs<\/span><\/h2>\n
How long before a candidate record goes stale?<\/strong><\/h3>\n
Is it cheaper to reactivate a dormant candidate than source a new one?<\/strong><\/h3>\n
Should I delete dormant records or keep them?<\/strong><\/h3>\n
Do dormant records create compliance risk?<\/strong><\/h3>\n
How often should a firm audit its database?<\/strong><\/h3>\n
Which is worth more, a dormant candidate or a dormant client?<\/strong><\/h3>\n
Can AI reactivate a dormant database without generic outreach?<\/strong><\/h3>\n