---
title: "Candidate Database Reactivation: 30-Day Sprint"
description: "Run a 30-day candidate database reactivation sprint: segment, score and re-engage dormant ATS records, then measure results and purge safely."
url: "https://www.leonar.app/blog/candidate-database-reactivation/"
lang: "en"
image: "https://www.leonar.app/og/blog/candidate-database-reactivation-en.png"
tokens: 5746
---

1.  [Home](https://www.leonar.app/)
2.  [Blog](https://www.leonar.app/blog/)
3.  [CRM & ATS](https://www.leonar.app/blog/category/crm-ats/)
4.  The 30-day candidate database reactivation sprint

CRM & ATS August 20, 2026 14 min read

# The 30-day candidate database reactivation sprint

Run a 30-day candidate database reactivation sprint: segment, score and re-engage dormant ATS records, then measure results and purge safely.

[![Pierre-Alexis Ardon](https://www.leonar.app/_astro/pierre-alexis-ardon.ByBiMn-t_1eJ10c.webp)](https://www.leonar.app/authors/pierre-alexis-ardon/)

[Pierre-Alexis Ardon](https://www.leonar.app/authors/pierre-alexis-ardon/) Co-founder

Updated August 20, 2026

![Adrien Tedjirian](https://www.leonar.app/_astro/adrien-tedjirian.BbnmZr4f_18wWaF.webp) ![Dolihane Feddag](https://www.leonar.app/_astro/dolihane-feddag.DkmcuiI8_uRaLP.webp) ![Louis de Froment](https://www.leonar.app/_astro/louis-de-froment.Y5ImtxTq_28zrXp.webp)

Trusted by 400+ recruiting agencies

4.9 Rated on G2

![Candidate database reactivation sprint with a 30-day agency workflow](https://www.leonar.app/_astro/candidate-database-reactivation.Cp_Lu__F_1kupyf.webp)

Ready to take action?

Discover Leonar in a few minutes.

[See pricing](https://www.leonar.app/pricing/)

-   7-day free trial
-   Full feature access
-   Cancel anytime

Summarize with AI

Choose an AI

[ChatGPT](https://chat.openai.com/?q=Summarize%20this%20article%20about%20recruiting%20from%20Leonar%3A%20) [Perplexity](https://www.perplexity.ai/search/new?q=Summarize%20this%20article%20about%20recruiting%20from%20Leonar%3A%20) [Claude](https://claude.ai/new?q=Summarize%20this%20article%20about%20recruiting%20from%20Leonar%3A%20) [Mistral](https://chat.mistral.ai/chat?q=Summarize%20this%20article%20about%20recruiting%20from%20Leonar%3A%20)

Table of contents

-   [What candidate database reactivation actually is, and what it is not](#what-candidate-database-reactivation-actually-is-and-what-it-is-not)
-   [Why your candidate database decays faster than you think](#why-your-candidate-database-decays-faster-than-you-think)
-   [Week 1: segment the database by last-touch and stage reached](#week-1-segment-the-database-by-last-touch-and-stage-reached)
-   [Build a re-contactability score from fields you already have](#build-a-re-contactability-score-from-fields-you-already-have)
-   [Week 2: decide re-engage, park or purge for each segment](#week-2-decide-re-engage-park-or-purge-for-each-segment)
-   [Week 3: run a short re-introduction sequence you control](#week-3-run-a-short-re-introduction-sequence-you-control)
-   [What to delete instead of re-contacting](#what-to-delete-instead-of-re-contacting)
-   [Week 4: measure the sprint on three honest numbers](#week-4-measure-the-sprint-on-three-honest-numbers)
-   [Rank the revived shortlist and hand it over well](#rank-the-revived-shortlist-and-hand-it-over-well)
-   [Turn the one-off sprint into a standing habit](#turn-the-one-off-sprint-into-a-standing-habit)

One of your lowest-cost sources of placements may not be a new job board or a bigger sourcing budget. It may be the database you already own. Many agencies have candidates who were spoken to once and never called again. That is pipeline they already paid to build, quietly going stale.

This guide turns that idea into a plan you can start on Monday. The 30-day sprint produces five useful tools. You will build a segmentation matrix, a contact score, a decision rule, an outreach sequence, and a scorecard. You will also decide what to delete instead of contacting again. Keeping the wrong record can create needless risk.

## What candidate database reactivation actually is, and what it is not

Candidate database reactivation means working through the people already in your ATS or CRM. The aim is to bring the right ones back to life. You segment them and decide who is worth a fresh approach. Then you run a short re-introduction before spending on net-new sourcing. Many recruiters call it talent rediscovery. The words matter less than the habit.

It helps to draw a clear line around three related jobs. Teams often confuse them.

Reactivation is not the same as data hygiene. Hygiene fixes duplicates, blank fields, and wrong titles. If your database is a mess, clean it first. Our guide on [how to clean a recruiting CRM](https://www.leonar.app/blog/how-to-clean-recruiting-crm/) explains that work. Reactivation starts with a usable record. It asks if this person is worth contacting again, and how.

Reactivation is also not tool selection. You may still be choosing where your candidates should live. If so, our roundup of [candidate relationship management tools](https://www.leonar.app/blog/candidate-relationship-management-tools/) can help. This guide is about working the database you already have, whatever it runs on.

Reactivation here is about candidates, not clients. Winning repeat work from companies needs its own rhythm. Our [recruitment agency client retention](https://www.leonar.app/blog/recruitment-agency-client-retention/) playbook covers that work. The two jobs connect, but the moves are different. Here we stay on the candidate side.

## Why your candidate database decays faster than you think

A database does not go stale because you built it badly. It goes stale because people change while the record sits still. Someone switches jobs, changes their number, moves city, or wants something new. The record does not update itself. Its useful share can shrink over time.

Dormancy is normal, not neglect. A role closes and attention moves to the next brief. A strong candidate is never logged for future work. Repeat that across a busy desk for a few years. You get a graveyard of good people nobody talks to.

Picture a typical tech desk. A strong backend engineer reaches the final interview, but the role is frozen. You move on to the next brief. Eighteen months later, that engineer is open again. Nobody on your team recalls the name, so the record sits untouched. Another agency finds them cold and bills the fee. You already had the relationship. You just never reached back.

The database can still have a cost edge. You already spent time and money finding these candidates and earning a first talk. Re-engaging them avoids some of the work needed to start a cold relationship. Even a small recovery across a large database can lead to placements. Much of the first contact cost is already paid. That is why your CRM is an asset, not a filing cabinet.

## Week 1: segment the database by last-touch and stage reached

The first tool is a segmentation matrix. You cannot reactivate a database as one blob. Split it by two facts you may already record. Note when you last spoke and how far the candidate got in a process.

Last-touch date shows how cold the relationship is. Furthest stage shows how much you know and how warm it once was. A finalist from eight months ago differs from an applicant you never called. Cross those two points in a simple grid. It shows where to focus first.

| Segment | Who it is | First move |
| --- | --- | --- |
| Warm near-miss | Reached interview or final stage in the last 12 months | Contact first, highest yield |
| Silver medalist | Lost out to another hire, strong feedback on file | Re-introduce for similar roles |
| Placed and settled | You placed them, guarantee long passed | Nurture as a source of referrals |
| Early applicant | Applied once, never progressed or called | Re-qualify before investing time |
| Cold and thin | Old record, little data, no recent contact | Score, then park or purge |

Build this in whatever you use. Filters, tags, and custom fields in a [recruiting CRM](https://www.leonar.app/features/recruiting-crm/) make it quick. A spreadsheet export works too. Stop treating every record the same. Start with the segment most likely to place.

## Build a re-contactability score from fields you already have

The second tool is a contact score. It ranks people within a segment so you contact the best first. Keep it simple and add the points. Use data you already hold. You do not need a data scientist or a complex model.

Give each candidate points across a few plain signals. The example weights are in brackets. Pick your own and use them the same way each time:

-   **Recency (0 to 3).** More points the more recently you last spoke.
-   **Stage reached (0 to 3).** More points for finalists and interviewees than for untouched applicants.
-   **Reachable channel (0 to 2).** Points for a working, permitted route such as email, phone, or a LinkedIn profile.
-   **Role match (0 to 2).** Points if their skills fit a role you are likely to work again.
-   **Lawful basis and purpose (pass or fail).** Document the applicable lawful basis and purpose for holding and contacting the record. If you cannot, handle it under your retention policy instead of contacting the person.

Here is how that works. Say you score on a scale of ten. A recent finalist with a verified route and useful skills might score nine. An old applicant with no notes or usable contact route might score two. You do not need perfect precision. You need a fast way to put your best bets first.

Add them up and sort. High scores go to the front of the queue. Low scores go to a review pile for the purge step. The score is a guide, not a verdict. Trust your judgment when a name jumps out. Keep the weights simple enough for any recruiter to use. Otherwise, the scores stop being useful.

## Week 2: decide re-engage, park or purge for each segment

The third tool is a decision rule for each segment. Segments and scores are useless until they lead to action. Write one plain rule for every record: re-engage, park, or purge.

Re-engage warm near-misses, silver medalists, and other high scorers with a live, permitted channel. Confirm that you have a documented applicable lawful basis and purpose. These people may be more likely to reply and place. Start here, since early wins can support the rest of the sprint.

Park the maybes. A mid-scoring candidate gets a tag and a review date. The same goes for someone whose data is thin but not dead. You are not contacting or deleting them yet. You are setting a reason to look again in three months. A parked record is a decision on hold, not one avoided. The review date stops the pile from growing forever. If no reason to keep the record appears by then, handle it under your retention policy.

Purge the records you cannot use or cannot justify. That is the honest part, and it gets its own section below. For now, mark them so the next step is clean.

## Week 3: run a short re-introduction sequence you control

The fourth tool is the re-introduction sequence. It is a short, human set of touches. You prepare, review, and send them from your own accounts. It is not a blast or automation aimed at a third-party network. It restarts a real talk with people who once knew your name.

Keep it to three or four touches over a couple of weeks, and lead with value rather than a pitch:

-   **Touch one.** A brief, personal note that references your last conversation and gives a concrete reason to reconnect now. Something like: “Hi Sam, we spoke last spring about the platform lead role at a fintech. You reached the final stage and the feedback was strong. A similar mandate has just opened and you came straight to mind. Open to a quick catch-up?”
-   **Touch two.** A relevant role or market insight a few days later, only if it genuinely fits them.
-   **Touch three.** A light, no-pressure close that makes it easy to say “not now” and stay in touch.

Personalise each message with what you know. Mention the role they nearly landed, their field, or their goals at the time. On the Professional plan and up, Leonar’s [multichannel outreach](https://www.leonar.app/features/multichannel-outreach/) supports sequences across email and LinkedIn. Write and review each message before you enrol a candidate. Messages then go from your connected accounts. The tool paces the work, but you own every word.

## What to delete instead of re-contacting

Some reactivation guides give little space to deletion. Yet the sprint is not only about who to contact. It is also about who to remove. Re-engaging a record you cannot justify holding creates risk. It is not a placement waiting to happen.

Work through the purge pile with a clear rule. First, check every permitted contact route you use, including email, phone, or LinkedIn. A record with no usable route may belong in the purge pile under your policy. If consent was the lawful basis you relied on, missing or expired consent also calls for deletion unless another valid basis applies. Merge duplicates into one clean record, keep the useful notes, and delete the copies.

Retention has legal duties, and this guide is not legal advice. Keep a record only while its purpose, lawful basis, and your retention policy support doing so. Act on valid erasure requests under the rules that apply to your organisation. The details depend on where you work and how you collect data, so confirm them with your counsel. CRM controls can help you delete, anonymise, or archive records in line with your policy. Those controls carry out your decision. They do not make you compliant by themselves, and no tool can promise that.

Deleting can feel like losing pipeline. A smaller database of current, reachable, defensible records may serve you better than a huge graveyard. It is easier to work and creates less worry. For a deeper look at the two databases an agency runs, read our guide to [candidate CRM versus client CRM](https://www.leonar.app/blog/candidate-crm-vs-client-crm/).

## Week 4: measure the sprint on three honest numbers

The fifth tool is a scorecard. A sprint you cannot measure is hard to repeat. You do not need a dashboard. Track three numbers and compare them with your own baseline, not someone else’s benchmark.

| Metric | How to read it |
| --- | --- |
| Reply rate | Replies divided by candidates contacted. Tells you if your re-introduction lands. |
| Qualified-submission rate | Revived candidates you sent to a client divided by those contacted. Tells you if the pipeline is real. |
| Cost per revived candidate | Your time and spend on the sprint divided by qualified submissions. Tells you if it beats sourcing. |

Compare these figures with your usual cost for net-new sourcing. If a revived candidate costs less to submit, you have found lower-cost pipeline. Run the sprint again next quarter. If it costs more, tighten your segments and score before you blame the idea.

## Rank the revived shortlist and hand it over well

Once replies come in, you have a warm shortlist. Do not let it sit. Rank the candidates and get the best in front of a client. This route may move faster than a new cold search.

Sort the repliers by fit for the live role. Present the strongest first with the context you hold. Share past feedback, why they nearly landed before, and what changed. That context is your edge. The client sees a vetted person with a story, not just a name from a job board.

Speed matters here as much as quality. A revived candidate who replies today may reach a client this week. A cold search could still be building a longlist. Lead your submission with the person’s history. Note their past stage, the panel feedback, and why the fit is stronger now. A fresh sourcing result will not hold that context. It can help turn a new talk into a placement.

For a large shortlist, Leonar’s [AI talent sourcing](https://www.leonar.app/features/ai-talent-sourcing/) can score candidates against a role. This is available on the Professional plan and up. The best fits rise to the top. The ranking saves a manual sort, while you decide who goes to the client.

## Turn the one-off sprint into a standing habit

A single sprint recovers a lot of value at once. The bigger win is never letting the database go fully cold again. So bank the sprint as a habit, not a one-time rescue.

Keep it light. A short quarterly pass may suit your best segments. Each pass should have a real reason to reach out. Let a relevant role or market update trigger the touch. Do not rely on a calendar reminder alone. Log each result so your segments and score improve over time.

The habit also protects the work you just did. Revived records will cool again if nobody logs the next talk. The same happens when no one updates a changed number. A light rhythm keeps useful records current. Your next sprint then starts from a warmer base and may take less effort.

Run this well and your database stops being a graveyard. It becomes a pipeline you can work and improve. That is the difference between a CRM you fill and one you use. To see how Leonar fits your desk, [compare Leonar plans](https://www.leonar.app/pricing/) and choose the right match for your agency.

## Frequently asked questions

### What is candidate database reactivation?

Candidate database reactivation is the practice of re-engaging people already in your ATS or CRM so they become live pipeline again. Many were spoken to once, then never called back when the role closed. You segment records by last touch and stage reached, decide who is worth contacting, and run a short re-introduction before sourcing net-new. It is often called talent rediscovery. You already paid to build these relationships, so your own database can often be a lower-cost source of pipeline.

### How is reactivation different from talent rediscovery?

In practice the two terms describe the same idea, so do not get stuck on the label. Talent rediscovery usually stresses the search step: finding the good candidates hidden in your ATS for a role that is open right now. Reactivation stresses the full loop: segment, score, re-engage, then measure the result and decide what to keep. Some teams use rediscovery for candidates and reactivation for both candidates and lapsed clients. Pick one word for your agency and move on. What matters is that you run a repeatable procedure, not that you win a vocabulary debate.

### How often should an agency re-engage dormant candidates?

Run one focused reactivation sprint, then keep a light standing rhythm so the database never goes fully cold again. A quarterly pass over the segments that matter most is enough for many small agencies. Contract and interim desks may want it monthly, because availability changes fast. The trap is contacting the same people too often with nothing new to say, which trains them to ignore you. Let a real reason drive the touch: a relevant role, a market update, or a genuine change on their side. Frequency should follow value, not a calendar for its own sake.

### Is re-engaging old candidates GDPR compliant?

It can be, but that depends on your documented lawful basis, purpose, and retention policy, not on any tool. Consent is one possible lawful basis, not the only one. If consent was the basis you relied on, missing or expired consent calls for deletion unless another valid basis applies. Follow your retention policy and act on valid erasure requests. Data-retention features can help you delete, anonymise, or archive records after you make those decisions. They do not make you compliant on their own. This article is not legal advice, so confirm your duties with your counsel.

### Does database reactivation work for a small agency?

Yes, and small agencies often see the clearest gain because the work is manual and the database is a known size. You do not need a large team or a big budget. You need a last-touch date, a note on how far each candidate got, and a few hours a week for a month. The sprint in this guide is built for an owner-led desk with three to thirty recruiters. Start with your best segment, the recent near-misses, and prove the process on a small batch before you scale it. A tight database you actually work beats a huge one you never open.

### What should I delete from a candidate database?

Delete records your retention policy no longer permits you to hold. If consent was the lawful basis you relied on, delete records with missing or expired consent unless another valid basis applies. Records with no usable, permitted contact route may also belong in the purge pile. Check email, phone, LinkedIn, and any other channel your organisation permits before deciding. Merge duplicates after saving the useful notes. Park uncertain records with a review date, then handle them under your policy when that date arrives. This is not legal advice, so check your duties with your own counsel.

Not sure which plan fits your team?

Answer 3 quick questions and we will recommend the best option for your hiring workflow.

How large is your recruiting team?

What is your main challenge?

Are you an agency or an in-house team?

Your recommended plan

[See pricing details](https://www.leonar.app/pricing/)

crm database guides

![Pierre-Alexis Ardon](https://www.leonar.app/_astro/pierre-alexis-ardon.ByBiMn-t_2wY0oT.webp)

Author

[Pierre-Alexis Ardon](https://www.leonar.app/authors/pierre-alexis-ardon/)

Co-founder

Pierre-Alexis Ardon is co-founder of Leonar, where he focuses on building AI-powered recruiting systems, assisted sourcing, and search optimization. With a background in engineering and over 7 years working at the intersection of artificial intelligence and talent acquisition, he designs the algorithms that power Leonar's candidate matching and workflow assistance. Pierre-Alexis advises recruitment agencies on their digital transformation and regularly publishes analyses on how AI agents are reshaping HR workflows. He is passionate about making advanced technology accessible to recruiters who are not engineers.

AI recruiting systems Sourcing automation Recruiting analytics AI agents for HR

[LinkedIn](https://www.linkedin.com/in/ardonpa/)

## Related articles

-   ![Candidate CRM vs client CRM comparison for recruiting agencies](https://www.leonar.app/_astro/candidate-crm-vs-client-crm.LMtrZnaK_yNMgO.webp)

    CRM & ATS

    ### [Candidate CRM vs client CRM: what recruiters need to know](https://www.leonar.app/blog/candidate-crm-vs-client-crm/)

-   ![Clean recruiting CRM with deduplicated candidate records and tidy pipeline](https://www.leonar.app/_astro/how-to-clean-recruiting-crm.BEWGh7OL_Z15Nrmm.webp)

    CRM & ATS

    ### [How to Clean Your Recruiting CRM](https://www.leonar.app/blog/how-to-clean-recruiting-crm/)

-   ![ATS migration checklist control pack with field map and validation steps for recruiting agencies](https://www.leonar.app/_astro/ats-migration-checklist.DUaQNK43_2DpUi.webp)

    CRM & ATS

    ### [ATS migration checklist: the agency control pack](https://www.leonar.app/blog/ats-migration-checklist/)


## Streamline your recruitment with AI & automation

Join 400+ recruiting teams already using Leonar to source, engage and hire faster.

7-day free trial with full access

7-day free trial Full feature access Cancel anytime