What is candidate rediscovery?
Candidate rediscovery is searching the CVs you already hold for a new role before you source new ones. Your database holds people you have read, interviewed or placed, so you know more about them than about a fresh applicant. Search it first, and source new CVs only for what it can't cover.
Rediscovery is one step of building a shortlist; the rest, from writing the criteria to ranking a fresh pile, is in the guide to shortlisting candidates from CVs.
An old record tells you more than a new CV does, but each part of it answers a different question.
| What's on file | What it tells you | What it can't tell you |
|---|---|---|
| The CV | The skills and work they claimed then | Whether it's still true, or anything since |
| An earlier interview on a skill the new role shares | How they answered when that skill was tested | Anything on a skill that wasn't tested |
| Your decision and the client's outcome | Who you put forward, and what the client did | Whether the reason still holds for this client |
| Whether they replied last time | How reachable they are | Whether they want to move now |
Source: this guide's reading, 18 Nov 2026
How do you search old CVs in your database?
Search old CVs with the new brief's criteria, not the old job title. Filter on the must-haves a CV can show, such as location, years or a named tool, then read the rest for evidence of each weighted criterion. A "Platform Engineer" and a "DevOps Lead" may have done the same work, and a title search finds only one of them.
Start from the brief, not the old shortlist
Write the new role's criteria and must-haves before you open the database. An old shortlist was built for a different client's weights, so the people at its top were ranked for a different job.
Filter wide, then read
Filters on a CV database match words. A skills filter that looks for "Salesforce" misses a CV that says "SFDC", and a location filter misses a candidate who is open to moving. Filter only on what truly rules someone out, add the synonyms yourself, and read what's left.
Why keyword search misses people
A CV lists what the person called their work; the brief lists what the role needs. Search for the work, not the word. For a B2B sales role, "discovery calls", "pipeline" and "quota" find more of the right people than the title "Business Development Executive". (An illustration, not a rule for every role.)
Questions to ask any tool that ranks your database
Take these to any ATS or matching tool you are weighing, Recagn included:
- What does it read: the whole CV, or fields parsed from it?
- Does it rank against your criteria and weights, or its own?
- Does it show the reason for each rank?
- Does it tell a thin CV in the right line of work from a CV in a different one?
- Does it decide anything on its own, or only order the list?
- What does each read cost, and is that price published?
How do you rank past candidates for a new role?
Rank past candidates by the CV against the new criteria first, then by what you learned about them on earlier roles that tested the same skills. An earlier interview, your decision and the client's outcome are evidence a fresh CV lacks, and older history counts for less. You decide who to approach again.
| History | Counts when | Counts less when |
|---|---|---|
| An earlier interview | The role tested a criterion the new one shares, even under another title | The title matched but the skills tested were different |
| Your decision | You recorded why you put them forward or held them back | The reason was specific to that client |
| The client's outcome | The client interviewed, passed on or hired them, and said why | No reason was given |
| Whether they replied | They answered your last invitation | They ignored the last two |
Source: this guide's reading, 18 Nov 2026
Let the history fade. An interview from two years ago says less than one from last month, so give recent history more weight. History on a different skill says nothing about this role.
Confirm what has changed
Some facts go stale fast. Before you put a past candidate forward again, confirm their notice period, current and expected CTC, location, and whether they want to move at all.
Then ask before you submit them. A candidate who agreed to be put forward for one role hasn't agreed to every role you work on.
How do you know your database has nobody for this role?
Your database has nobody for this role when the best match is weak: the top CVs sit in a nearby line of work, miss a must-have, or are too thin to judge against the criteria. Stop there and source fresh CVs. A ranked list always has a first place, so read the evidence, not the rank.
Signs the pile is empty for this brief
- The top few work in a nearby job, not this one.
- Every top CV fails a must-have or can't show it.
- The best evidence is a skills list with no work behind it.
- The people who fit are the ones who stopped replying.
What to do next
Source for the gap you found. If the brief needs B2B sales and your database holds education counsellors and developers, the new search is for B2B sellers. Keep the near misses for the interview stage if the client's must-haves allow them, and note why each one was close.
Rank one is where you start reading
Read the top CVs yourself before you call anyone. A rank orders the list; whether the person fits is something you check on the CV and then in the interview.
How Recagn does this
Recagn is our product. It assesses each CV in a role's Pool on the parsed CV against the brief's scorecard, which Recagn calls a rubric. Each candidate gets a match score from 0 to 100, a recommendation of Strong, Possible or Weak, a reading of whether they work in the role's line of work, and a one-line reason. You choose who to invite.
Each role picks one Pool: a named group in your candidate database, or General, which is the whole database. Recagn leaves out anyone already in the role's pipeline or not contactable, applies the role's filters when they are on, and reads each CV's parsed skills, years, education, projects and locations against the locked rubric. Every line on a CV is a claim to test in the interview, so a hard gate reads "unproven" or "failed" on the CV, never passed. Recagn reads a thin CV in the right line of work for what it shows, and keeps "unrelated" for a CV in a different line of work, which makes it Weak. How that reading fits into CV screening is on Recagn's resume screening page.
On the Candidates list you can also filter by skills, location, work authorisation, years and Pool before you start.
The whole pool, best match first. Under rank 1, each criterion's points add up to its score.
Business Development Executive (B2B SaaS) Sourcing · 14 in the pool
- 1Tanvi J.50/100PossibleAdjacent
The profile sits in an adjacent sales space with plausible inside-sales exposure but is too thin — no metrics, no deal context, and a Pune location vs. Bengaluru requirement — to confirm fit against the role's core criteria.
- Prospecting & Outreach20% · Unknowable · 12/20 pts
- Discovery & Qualification25% · Unknowable · 15/25 pts
- Pipeline & CRM Discipline15% · Unknowable · 9/15 pts
- Measurable Track Record25% · Gap · 5/25 pts
- Communication & Buyer Credibility15% · Unknowable · 9/15 pts
- Total50/100
Hard gates
- 2-5 years B2B sales/BDUnproven
- Bengaluru hybridUnproven
- Clear English communicationUnproven
- CRM working knowledgeUnproven
- Comfort with cold outreachUnproven
- 2Nisha P.44/100WeakAdjacent
The candidate shows genuine sales-process instincts and CRM capability, but the profile points to an education/consumer-enrolment context with no visible B2B, multi-stakeholder, or logistics-domain experience.
- 3Karan B.32/100WeakAdjacent
The candidate claims outbound calling skills that touch the right occupational family, but falls below the experience floor, has no CRM knowledge, no measurable track record, and no logistics or B2B SaaS context evident in the profile.
- 4–1411 more at 26 · Weak · Unrelated
Abhishek S., Arjun M., Debashish M., Farhan I., Priya N., Rohan D., Rohit M., Siddharth K., Sneha K., Ujjawal P., Vikram S.
We ran an existing brief through Recagn on 18 Nov 2026: a Business Development Executive for a B2B SaaS company in Bengaluru, hybrid, 2–5 years, against a Pool of 14 invented CVs. In this run, the order is the exported rule: highest score first, and a tie goes to the earlier candidate id.
The three highest are all in sales. Tanvi J. scored 50, Possible; Nisha P. 44, Weak; Karan B. 32, Weak. Recagn read each as adjacent: sales work near the role, in an education or consumer counselling setting for Tanvi, education or consumer services for Nisha, and a consumer or inside-sales context for Karan. Recagn read Karan's CV as failing two hard gates, "2–5 years B2B sales/BD" and "CRM working knowledge".
The other eleven are developers, marketers, DevOps engineers and a data-entry profile. Each scored 26, Weak, unrelated, with Recagn's reason on its row. Nobody came out Strong. The run put sales first and showed plainly that this Pool held no strong fit for this brief: the case for sourcing fresh.
Tanvi's 50 adds up criterion by criterion. Recagn found four of the five criteria unknowable from her parsed profile and Measurable Track Record a gap. It gives 5 points for a supported criterion, 3 for unknowable and 1 for a gap, weighted by the rubric and scaled to 100, so her 12 of 20, 15 of 25, 9 of 15, 5 of 25 and 9 of 15 points make 50. All five of her gates read unproven, including Bengaluru hybrid against her Pune location. Recagn's reason reads the profile as too thin to confirm fit, citing no metrics, no deal context and the location.
Rank one is where your reading starts. Her CV's summary says "3+ years", and the one role listed starts in Aug 2025, about 1 year 3 months before the run. That arithmetic is ours, on a CV written for Recagn's worked examples, and it is the first question to ask her.
Weak matches go into a counted Parked group under the list. From the list you approve and invite, or skip. Searching your candidate database and reading every CV comes off your plate. Who gets invited stays yours. Recagn recommends. Only you can reject a candidate.
Each CV Recagn reads uses one CV read from the plan's monthly allowance, or two on a role set to senior assessment; the price per read is in the FAQ below.
Questions people ask
If nobody in my database fits, will a ranking still put someone first?
Yes, a ranked list always has a first place. Read the score and the recommendation, not the position. In Recagn's worked example, run on 18 Nov 2026 against a pool of 14 invented CVs, the top CV scored 50 out of 100 with a Possible recommendation and nobody came out Strong: a sign to source fresh CVs for that brief.
Does Zoho Recruit match old candidates to a new job opening?
Yes, on its higher plans. Zoho Recruit's Candidate Matches gives each candidate a match score from skills, keywords, experience, education and industry, and shows up to 20, highest score first, on the Professional, Enterprise, People Plus and Zoho One plans (Zoho Recruit help, no date shown, read 18 Nov 2026). Check that its weighting suits the brief before you rely on the order.
How many old CVs can Recagn read against a new role in a month?
900 CV reads a month on Starter. Each CV Recagn reads against a role uses one read, or two if the role is set to senior assessment, so reading a database of 500 CVs for one role uses 500 reads, or 1,000 on a senior role. That works out to at most ₹3.33 a CV before GST (₹3.93 with GST), a ceiling, because the plan also covers interviews.
Do you need to ask a past candidate before putting them forward again?
Yes, ask first. Agreeing to be put forward for one role isn't agreeing to every role you work on, and their notice period, CTC or plans may have changed since you last spoke.