Endearist
DE EN Get Endearist
Personal CRM

Recruiter candidate relationships: place the same person twice

Silver-medalist candidates, the no with a timeline, and notes that stay confidential — how recruiters build relationships that outlast a single search.

By Endearist Team 8 min read

Recruiting measures itself in placements, but the durable business is made of something slower: the same person, placed twice in a career — and everything they route to you in between. Granovetter’s Getting a Job (1974) found that most positions travel through personal contacts. The recruiter who is a personal contact, rather than a vendor, wins that traffic.

An ATS is built around the requisition: candidates enter, one exits as “placed,” the rest exit as “rejected” or “withdrawn,” and the file closes. Useful for the agency’s reporting. Structurally wrong for your career — because the people in that file do not close. They keep moving.

The developer you placed in 2023 becomes a team lead in 2026, and suddenly he is the one with five open roles and a budget. The candidate who withdrew becomes a VP somewhere that hires forty engineers a year. The hiring manager who briefed you moves companies and becomes a candidate herself. None of these arcs fit a pipeline stage, and all of them are where the next decade of fees comes from.

Working the long arc takes three beats after every placement: week one (how does the reality compare to the pitch?), day ninety (past the honeymoon — any surprises?), then twice a year, forever. Modest effort, compounding return. The Endearist page for recruiters describes the destination: when that 2023 placement needs a recruiter he trusts, the shortlist is exactly one name long.

The same long arc applies on the client side. The hiring manager who briefs you well is rare — and she is also mobile: in three years she is running a bigger org somewhere else, and the quality of your relationship, not your agency’s logo, decides whether the briefings follow her. Log her preferences the way you log a candidate’s: how she likes shortlists presented, what she actually weighs, the hire she still talks about. Recruiting is a two-sided network, and both sides change jobs.

Silver medalists: the list nobody keeps

Every completed search produces one placement and one or two silver medalists — candidates who survived the full process and lost on circumstance, not quality. The client picked the one with migration experience; the timing collided with a vesting cliff; the budget got cut to one hire. The ATS files them all under “rejected” and forgets.

That filing is the single most expensive data loss in recruiting. A silver medalist is pre-vetted by a real process, demonstrably open to moving, and usually still open — just not placed. For the next adjacent search, they are a half-finished candidate: weeks of screening already done.

What to log while the search is still warm: why they came second (in the client’s words, not a euphemism), what they were genuinely looking for, their stated timeline, and a check-in date about five months out. Then the cadence does the rest. When a matching role opens, you are not sourcing — you are calling someone who already trusts your judgment about what suits them. Our piece on how often to follow up with professional contacts covers the general rhythm; for silver medalists, every four to six months with something specific is the proven groove.

The no with a timeline

Recruiters deliver more rejections than almost any profession, which means rejection handling is the brand. Candidates forget the roles they did not get; they remember precisely who told them, how fast, and whether the reason was real.

  1. Deliver the no fast, with the real reason

    Within a day of knowing, with substance: they chose the candidate who had run this exact migration; on skills it was even. Three minutes of honesty, rare enough in this industry to be memorable for years.

  2. Ask about their horizon

    The decline direction matters too. When a candidate turns down an offer, ask what would need to be different — and listen for the timeline hiding in the answer. The commute, the school year, the vesting cliff: each is a reason with a date attached.

  3. Log the why and the when

    Four lines: the real reason, what would change it, the date it might change, and how they want to be contacted. The ATS marks her offer declined; your notes mark her revisit mid-2027, wants hybrid, do not call during Q4.

  4. Set the check-in, keep the door explicit

    End the conversation with the future in it: I want to work with you when the timing is right — mind if I check in around then? Almost everyone says yes. Now the no has a shape, and the shape has a date.

The candidate who declined because her daughter had just started school is not a dead lead — she is a person with a reason and a timeline. Respect the timeline and the next call goes to you.

One habit that costs nothing: when the timing a candidate named actually arrives, reference it. “You said mid-2027 — it is mid-2027, and I have something worth a look” is the entire message. It works because it proves the earlier conversation was a conversation, not a pipeline stage. Two guardrails for silver medalists specifically: tell them they were close — most never find out, and knowing changes how they answer your next call — and never park them in a generic talent-pool newsletter. A person who came second deserves a person, not a drip campaign.

Confidentiality: what the shared database should never know

Candidates tell a trusted recruiter things they would never put on LinkedIn: why they are really leaving, the manager they cannot work for another year, the salary number they whispered, the health situation shaping their dates. They tell you — not your agency’s database and its twenty other users.

Two disciplines follow. First, separation: that layer of confidence does not belong in the shared ATS, where it is visible to colleagues today and discoverable in an audit or acquisition tomorrow. Keep it in a system of your own, on your own device. Second, restraint: even in private notes, write what serves the person. Under the GDPR, health data and similar categories carry special protection — and the practical rule is older than the regulation: note the timeline, not the diagnosis. “Revisit mid-2027” serves her; the medical detail serves nobody.

Cadence at scale, and a network that survives the agency change

The math of a recruiter’s network is unforgiving: people change jobs, cities, sometimes surnames, and a contact list left alone decays in a couple of years. The counter-move is a deliberately small working set, touched genuinely. A hundred to 150 people — placements, silver medalists, the hiring managers who used to be candidates — on a twice-yearly individual cadence is about five real messages a week. Rank them with a priority pass twice a year; the columns you need (who, why it was a no, when to revisit, who introduced whom) are exactly the spine of the investor pipeline tracker template — built for founders tracking passes, but a pass with a revisit date is a silver medalist. Rename two headers and it fits.

And keep the whole thing on your own device from day one. When you move agencies or go independent, the ATS stays behind — non-solicitation clauses exist for a reason, and the clean separation protects you legally as much as it protects the relationships. The person-by-person trust you built is your professional capital; Endearist exists so that a new letterhead never again means rebuilding the network from zero.

Place the person, keep the thread, and in three years the person places with you. That is the whole long game.

FAQ

How do recruiters keep in touch with candidates between searches?

With **individual, low-frequency, high-context touches** — not newsletter blasts. The working rhythm: a check-in around **90 days** after a placement, then twice a year; for silver medalists and warm prospects, every **4–6 months** with something specific to them — the promotion you saw, an article matching their stated ambition. Ten genuine messages a week beats one mail-merge per quarter, because candidates can tell the difference instantly — and reply rates prove it.

What is a silver-medalist candidate?

The candidate who reached the **final round and lost on circumstance, not quality** — the runner-up. They are the fastest future placement in recruiting: already vetted by a real process, already interested in moving, just mistimed or edged out by one competitor. Most agencies let them evaporate into the ATS as 'rejected'. A recruiter who logs _why_ they came second and checks in twice a year converts silver medalists at rates cold sourcing never approaches.

How do I reject a candidate without burning the relationship?

Deliver the no **fast, with the real reason, and with a timeline**. 'They went with someone who had run a migration like theirs — on skills you were even' costs you three minutes and is rare enough to be memorable. Then make the future explicit: 'I want to put you forward again — how does your timing look over the next year?' A no with a reason and a horizon keeps the relationship alive; a ghosted no ends it and gets discussed with friends.

How often should I check in with candidates I placed?

Three beats: **week one** (how is the reality versus the pitch?), **day 90** (past the honeymoon — any surprises?), then **twice a year** indefinitely. The placement is not the end of the relationship; it is the start of the most valuable phase. Placed candidates refer their colleagues while happy, warn you early if the role sours — and in two or three years, some of them have headcount and a budget of their own.

Why do placed candidates matter years after the placement?

Because **today's candidate is tomorrow's hiring manager**. The developer placed in 2023 becomes the team lead with five open roles in 2026 — and when he needs a recruiter he trusts, the shortlist is one name long if you stayed in touch, and zero names long if you vanished after the invoice cleared. The relationship journal that holds the whole arc — first screening call, offer negotiation, promotion congratulations — is what makes that shortlist yours.

What candidate notes are okay to keep, and which are not?

Keep what serves the candidate and the relationship: stated ambitions, timing constraints, the **real reason** behind a decline, salary expectations they shared willingly. Be deliberately restrained with sensitive context — under the **GDPR**, health data and similar categories enjoy special protection, and the honest rule is: note the _timeline_, not the diagnosis. 'Wants to revisit in mid-2027' serves the person; medical detail in a database serves nobody and creates risk. See our glossary entry on [GDPR and contact data](/en/glossary/gdpr-and-contact-data) for the basics.

Should I track candidate relationships outside the ATS?

The search record belongs in the ATS — that is what your agency pays for. The **relationship layer** is different: what candidates confide, they confide in _you_, not in a database twenty colleagues can search. And when you change agencies, the ATS stays behind, as the non-solicitation clause makes very clear. A personal, local system for the human layer — kept cleanly separate from your employer's data — protects both the candidate's trust and your professional capital.

Is it strange to contact a candidate I last spoke to two years ago?

No — dormant ties reactivate far better than people expect. **Levin, Walter & Murnighan (2011)** found that reconnecting after years of silence was often _more_ useful than working active contacts: the old trust persists, and the time apart means real news on both sides. With candidates, open with their trajectory, not your vacancy: 'Saw you shipped the platform rewrite — curious how the lead role is treating you.' The vacancy can come up in the second message.

How many candidate relationships can one recruiter genuinely maintain?

Far fewer than the ATS holds, and that is fine. A working set of **100–150 people** — placements, silver medalists, hiring managers, key connectors — on a twice-yearly individual cadence is roughly five real touches a week. The skill is choosing the right 150: rank by future value and warmth, not by recency of the last search. A [structured priority pass](/en/tools/contact-priorities) over your network twice a year keeps the working set honest.

When does a candidate's no become a yes?

When the **stated blocker changes** — and candidates usually tell you the blocker if you ask. The commute that did not work, the daughter who just started school, the vesting cliff eighteen months out: each is a reason with a date attached. Log the reason and the date, and the no becomes a scheduled future conversation. Timing changes; the next call goes to the recruiter who respected the last answer instead of arguing with it.