Skip to content
CynestiaCynestia
06Primary offering

Candidate Database Reactivation

An operated recruitment workflow that turns the candidate records you have already accumulated into shortlists for the requisitions you are working now. We run every stage upstream of your recruiter's decision — you keep the ATS, the candidates, and the calls.

Six operated stagesBullhorn · Ceipal · JobAdderNo software to learnRecruiters keep every decision
Fig. 01 — the lifecycle at a glanceOperated end to end
CONNECTCLEANMATCHRE-ENGAGECONFIRMDELIVER
01The lifecycle

Six stages, from your ATS to a shortlist your recruiter can submit from.

Every stage has defined inputs, defined outputs, and a record your team can inspect. Follow it top to bottom — or use the index to jump to the part you want to interrogate.

01Stage 1 of 6

Connect

Read-scoped access to Bullhorn, Ceipal, or JobAdder — or scheduled exports if you would rather hand us files.

We connect to the ATS you already run. Where the platform supports scoped access, that is what we use; where it does not, we work from scheduled exports. Access is granted by you, limited to what the workflow needs, and withdrawn the moment you say so.

What we work from
  • ATS credentials or an export schedule
  • Your open requisitions
  • Agreed shortlist criteria
What you get
  • Confirmed connection
  • Scope of access agreed in writing
02Stage 2 of 6

Clean & organize

Years of accumulated records deduplicated, normalized, and structured so they can actually be searched.

Databases grow messy: duplicate profiles, job titles recorded four different ways, skills stored as free text, contact details from a system you retired. We deduplicate, normalize titles and skills, resolve the same person appearing more than once, and structure the history into something a matching workflow can read.

What we work from
  • Raw historical records
What you get
  • Deduplicated, normalized candidate records
  • Structured skills and work history
03Stage 3 of 6

Match

Every open req scored against the database on skills, experience, and trajectory — not keyword overlap.

For each requisition we work from what the role actually requires rather than a keyword string: core technologies, seniority, domain exposure, contract or permanent shape, location and work authorization, and the direction a career has been moving. Every match comes back with the reason it surfaced.

What we work from
  • Open requisitions
  • The cleaned database
  • Agreed shortlist criteria
What you get
  • Ranked candidates per requisition
  • A recorded reason for every match
04Stage 4 of 6

Re-engage

Relevant, individual outreach through the channels each candidate already used — under your agency’s identity.

Dormant candidates are contacted with context: the role, why they surfaced, and something specific to their history with you. Messaging follows your agency’s templates, identity, and recorded preferences, and is agreed before it goes out. No generic blasts, no purchased lists, no contact that ignores what the record already says.

What we work from
  • Shortlisted matches
  • Approved messaging
  • Your agency identity
What you get
  • Logged outreach and complete response threads
05Stage 5 of 6

Confirm

Availability, interest, rate expectations, and role-relevant qualifications — confirmed in conversation.

A matching record is not a submittable candidate. The workflow works through the conversation: are they available, are they interested, do the numbers line up, does the experience hold against the requisition. Answers come back structured, with the underlying conversation attached.

What we work from
  • Candidate responses
What you get
  • Availability, interest, and rate confirmed
  • Qualification evidence per candidate
06Stage 6 of 6

Deliver

A recruiter-ready shortlist with the evidence behind every candidate.

Your recruiter receives what they need to submit: who the candidate is, why they surfaced, what was confirmed, and what was actually said. There is no black-box ranking — the reasoning travels with the shortlist. Your team reviews, decides, and submits.

What we work from
  • Confirmed candidates
What you get
  • A recruiter-ready shortlist
  • Match reasons and the conversation log
02Inside the workflow

Cleaning is not housekeeping. It is what makes matching possible.

Stage 02 looks unglamorous until you see what a matcher has to work with. This is a representative slice of a ten-year-old staffing database — before and after the workflow has been through it.

The same person, three times

Duplicate profiles accumulate every time a candidate is re-added by a different recruiter or import. A matcher that reads each record separately will rank one person three times — or miss them entirely.

One skill, three strings

“react dev”, “react.js”, “reactjs”. Free-text skill fields are how databases actually look after a decade, and no keyword match reconciles them.

History nobody can search

Placements, submissions and conversations sit in notes and activity logs. The signal is there; no workflow can read it until it is structured.

Raw records
After the workflow
  • Mercer, Jonathan — Sr. React Engineer
  • Mercer J. — React Dev
duplicate profile
  • Jonathan Mercer · Senior React Engineer
2 records merged
  • “react dev”
  • “react.js”
  • “reactjs”
three skill strings
  • Skill graph normalized
ReactNodeTypeScript
  • last contact 2019
  • role history: none recorded
unindexed history
  • History reconstructed from activity logs
Placed 2023Submitted 4×Contract book

Two people who are one person. Three skill strings that are one skill. Nothing here is exotic — it is simply what happens when a database is grown rather than curated.

Fig. 02 — representative record slice · illustrative
The standard
A matching record is not a submittable candidate. The gap between the two is where placements are lost.
That gap is the entire job: confirm the person, confirm the numbers, confirm the fit — and put the evidence in front of a recruiter.
01Inputs and outputs definedEvery stage states what it consumes and what it produces, before it runs.
02Nothing hidden in a dashboardThe reasoning and the conversation travel with the deliverable.
03Advances only on proofNo stage moves until the one before it has delivered what it promised.
03The commercial case

What changes on your desk — and what we do not promise.

Both halves matter. The first is why firms engage us; the second is why the conversation stays honest after they do.

What changes

Operating outcomes
  • Requisitions start from a matched poolYour recruiter opens the req with existing, known candidates in front of them instead of an empty sourcing tab.
  • Recruiter hours move from searching to submittingReviewing and deciding is the skilled part. The hours spent digging through history for people who already match stop being necessary.
  • Your own history absorbs sourcing spendWhere a past placement or prior submission already fits the role, there is nothing to source cold and nothing to pay a board for.
  • Relationships get worked instead of lapsingContractors between assignments, past placements, and old applicants re-enter circulation while they are still reachable.

What we do not promise

Stated before you sign
  • No guaranteed placementsWe deliver candidates who are matched, re-engaged, and confirmed, with the evidence attached. Your recruiters review them and make the placements.
  • No fixed candidate counts or timelinesWhat a database yields depends on its size, age, and condition, and on your market. We agree what we will measure before the work starts, then report against it.
  • No autonomous decisionsNothing is rejected, advanced, or shortlisted without a recruiter seeing the evidence. The workflow searches and confirms; your team decides.
  • No replacement of your ATSWe work inside Bullhorn, Ceipal, or JobAdder and write nothing back to it without agreement. Your system of record stays your system of record.
The measure

The measure we agree on before the work starts is the measure we report against — not a number chosen afterwards to look good.

Next step

See what your database would surface.

Send us your agency, your ATS, and the requisitions on your desk right now. We will come back with a straight view on whether there is recoverable value — and what running this workflow against it would involve.

Assessment first · scope and measures agreed before the first candidate is contacted