---
title: "Offer decline recovery for agencies"
description: "When a candidate declines the client's offer, agency recruiters need a plan. Diagnose the real reason, confirm the brief, then choose the next move."
url: "https://www.leonar.app/blog/offer-decline-recovery/"
lang: "en"
image: "https://www.leonar.app/og/blog/offer-decline-recovery-en.png"
tokens: 4962
---

1.  [Home](https://www.leonar.app/)
2.  [Blog](https://www.leonar.app/blog/)
3.  [Staffing](https://www.leonar.app/blog/category/staffing/)
4.  When a candidate declines the offer: agency recovery

Staffing October 1, 2026 9 min read

# When a candidate declines the offer: agency recovery

When a candidate declines the client's offer, agency recruiters need a plan. Diagnose the real reason, confirm the brief, then choose the next move.

[![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 October 1, 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

![Offer decline recovery worksheet with fields for the package declined, candidate’s stated reason, unknowns, next action, owner and due date](https://www.leonar.app/_astro/offer-decline-recovery.DFWYmSwQ_Z1sedL5.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

-   [First, separate what you know from what you assume](#first-separate-what-you-know-from-what-you-assume)
-   [The real reasons candidates walk away, with the data](#the-real-reasons-candidates-walk-away-with-the-data)
-   [Write one decline record before you do anything else](#write-one-decline-record-before-you-do-anything-else)
-   [Confirm the client’s constraints before you touch the brief](#confirm-the-clients-constraints-before-you-touch-the-brief)
-   [Your four moves after a candidate declines](#your-four-moves-after-a-candidate-declines)
-   [Why reopening research too early costs you the search](#why-reopening-research-too-early-costs-you-the-search)
-   [The reserve candidate you already assessed](#the-reserve-candidate-you-already-assessed)
-   [Keep the recovery on the record, not in your head](#keep-the-recovery-on-the-record-not-in-your-head)
-   [Which move fits your declined search?](#which-move-fits-your-declined-search)

A candidate declining the client’s offer feels like the floor dropping out of a search. It is not. It is a decision point, and the recruiters who recover fastest treat it as one.

Before you reopen sourcing or fire off apologies, you do three things. You write down exactly what was declined and why. You confirm with the client what, if anything, has changed. Then you choose one of four moves: clarify the decline, revise the brief, approach a candidate you already assessed, or reopen the search. This guide gives you a short record to capture the decision and a simple way to pick the right next step.

## First, separate what you know from what you assume

The reason a candidate gives in the first five minutes is rarely the whole story. Someone who says the money was not right may have taken a counteroffer. Someone who blames the commute may have doubts about the manager they met. Your job is not to guess the hidden reason. It is to record the stated one cleanly, then mark your own hunch as a separate line.

Write the candidate’s reason in their words. Then, underneath, write your assumption and label it as yours. Keeping these two apart matters more than it sounds. If you fold your guess into the record as fact, every later decision inherits a mistake. The client hears your theory as the candidate’s truth, and you may revise a brief that never needed changing.

Hold the unknowns too. Often you will not know whether the offer was beaten on pay, on title, or on gut feeling. That is fine. An honest “we do not yet know why” is worth more than a confident wrong answer, because it tells you the very next task is to find out.

## The real reasons candidates walk away, with the data

It helps to know the common patterns, as long as you treat them as prompts rather than conclusions. [Top Echelon, citing its 2018 State of the Industry Report](https://topechelon.com/blog/candidate-declines-job-offer-what-to-do/), reported salary as the top reason a candidate turned down an offer at 28.8%, followed by a better competing offer at 23.0% and a client who took too long to decide at 22.4%.

For post-acceptance declines, [Robert Half’s 2019 survey](https://press.roberthalf.com/2019-05-15-Cold-Feet-Survey-Shows-28-Of-Professionals-Renege-On-Job-Offer-After-Accepting) covered more than 2,800 adult office workers in 28 major US cities. Among respondents who had backed out after accepting, 44% cited a better offer, 27% a counteroffer, and 19% negative information about the company. These historical figures are not a current benchmark for agency or executive-search candidates.

Read these as a checklist of what to rule out, not a diagnosis. Your candidate declined for one real reason, and it may not be on any list. The data earns its place by pointing your questions, so you ask about pay, competing offers, and timing early instead of circling for days.

## Write one decline record before you do anything else

A decision you do not write down gets remade badly a week later, usually at the worst moment. The fix is a short record, one per declined offer, that captures what was turned down, why, what you still do not know, who owns the next move, and what that move is.

```
OFFER DECLINE RECORD

Client / company: [name]
Role: [title]
Candidate: [name]
Recruiter owner: [name]
Decision date: [date]

WHAT WAS DECLINED
  Package: [base, bonus, equity, benefits]
  Start date offered: [date]
  Stage reached: [verbal / written offer / post-acceptance]

WHY (keep these separate)
  Candidate's stated reason: [their words]
  Your assumption, labelled as yours: [your read]
  Still unknown: [what you cannot confirm yet]

NEXT ACTION
  Owner: [name]
  Due: [date]
  Move: [clarify / revise brief / approach reserve / reopen]
  Client decision needed first? [yes / no]
```

You can run this on paper. It works better on the record itself, where it stays live and searchable, and where the whole team can see who owns the next step. In Leonar you keep this on the project and the candidate’s contact record: the stated reason and your assumption as separate notes or custom fields, the outcome as a pipeline stage, and the next action as a task with an owner and a date.

Be clear about what the tool does here. It stores the decision and reminds the owner when the next action is due. It does not analyse the decline for you, predict who will accept next, or rank your reserve candidates. That judgement stays with the recruiter, which is exactly where it belongs.

## Confirm the client’s constraints before you touch the brief

Here is the step almost everyone skips. A decline is often a message about the client, not the candidate. The budget sat below market. The process dragged until a competitor moved faster. The seniority the client wanted never matched the money they offered. If any of that is true, no new shortlist will fix it.

So before you rewrite the brief, go back to the client with the decline record and a plain question: what can move? Pay, timeline, title, working pattern, or nothing. Their answer decides everything downstream. If the client can lift the offer, you may not need a new candidate at all. If nothing can move, you need to reset expectations before you spend another hour sourcing.

This is also where the original brief earns its keep. If you ran a proper [intake meeting that turned a rough request into an agreed spec](https://www.leonar.app/blog/recruiter-intake-meeting/), you have a baseline to compare against. The decline tells you which part of that agreement no longer holds, and the client tells you whether it can be fixed.

## Your four moves after a candidate declines

Once you know the real reason and the client’s room to move, you have four clean options. Most declines resolve into one of them.

| Move | What it means | When to choose it |
| --- | --- | --- |
| Clarify | Get the full reason first | The stated reason is thin or you suspect a hidden cause |
| Revise brief | Change the spec or the offer | The client confirms a constraint can move |
| Approach reserve | Go to an assessed second choice | A candidate you already vetted still fits the confirmed brief |
| Reopen search | Start sourcing again | The brief is sound but your shortlist is genuinely exhausted |

The order matters. Clarify and confirm come before revise and reopen, because the last two cost the most time and are the easiest to get wrong. Your engagement model shapes the urgency here too. A retained search buys you room to diagnose properly, while a contingency desk feels pressure to move fast. If you work across both, it is worth being clear on [how retained and contingency models change the recovery](https://www.leonar.app/blog/retained-vs-contingency-recruitment/) before you pick a move under pressure.

## Why reopening research too early costs you the search

The most expensive mistake is reopening sourcing before the client has decided what changed. Consider a fictional example to see how it plays out.

A search partner places a shortlisted finance director with a mid-market client. The candidate declines the written offer, saying the base was lower than expected. The partner assumes the market has moved, reopens research that afternoon, and spends a week building a fresh longlist at a higher salary band.

Then the client reveals the budget cannot move at all, and the real issue was a vague reporting line the candidate did not trust. The new longlist is useless. It was built on a changed brief the client never agreed to, against a problem that was never about pay.

Had the partner confirmed the client’s constraints first, the week would have gone to fixing the reporting structure and re-approaching the original shortlist. Reopening research is sometimes the right move. It is almost never the first one. The deeper causes behind this pattern are worth understanding, and they overlap with [the reasons executive searches fail in the first place](https://www.leonar.app/blog/why-executive-searches-fail/).

## The reserve candidate you already assessed

Before you start over, look at who you already have. A strong second choice from your original shortlist is faster and safer than a cold restart, provided the brief the client confirmed has not materially changed.

The key word is assessed. A reserve candidate is only real if you can see your own evidence on them. If you built a proper [submission pack with your assessment and evidence at the shortlist stage](https://www.leonar.app/blog/candidate-submission-template/), that work is sitting on their record, ready to reuse. You are not scrambling to remember why they ranked second. You are reading a note you wrote when the detail was fresh.

Make the call yourself. Your reserve is a human you evaluated, weighed against a brief you now know better than you did a month ago. No tool should rank that person for you or tell you they will accept. It can surface your past notes and keep the shortlist tidy. The decision to re-approach is yours.

## Keep the recovery on the record, not in your head

A decline that lives only in your inbox and your memory gets handled twice as slowly and half as well. The recovery moves through stages, the candidate reason, the client decision, the next action, and each of those belongs on a record the whole desk can see.

That is the quiet case for running recovery inside your CRM rather than your head. The declined offer becomes a pipeline stage. The reason and your assumption become notes. The next move becomes a task with an owner and a due date. Nothing here is automated magic. It is honest recordkeeping, so a colleague covering your desk can pick up a declined search and know exactly where it stands.

If you want one place to run this across a team, [Leonar for executive search](https://www.leonar.app/for-executive-search/) keeps your clients, candidates, and decisions on one set of records, with projects, pipeline stages, notes, and tasks that any owner can follow.

## Which move fits your declined search?

Start with what you can prove. If you cannot yet state the real reason in the candidate’s own words, your next move is to clarify, not to source. If you have the reason but have not spoken to the client about their constraints, that call comes before any change to the brief.

If the client has confirmed what can move and a candidate you already assessed still fits, go to your reserve. Only when the brief is sound and your shortlist is truly spent do you reopen research.

A declined offer is not the end of a search. It is the moment it either gets handled with a clear head or spirals into a scramble. The record you keep decides which. When you want to weigh up running your searches on one set of shared records, you can [compare Leonar’s plans](https://www.leonar.app/pricing/).

## Frequently asked questions

### What should an agency recruiter do first when a candidate declines the offer?

Write down what was actually declined and the exact reason the candidate gave, before you react. Capture the role, the package, and the start date they turned down, then record their stated reason word for word. Do not restart sourcing the same hour. A decline is a decision point, not an emergency. The recruiters who recover fastest slow down for ten minutes first, because the next move depends entirely on why the offer fell through. Once the facts are on the record, you can decide whether to clarify the decline, go back to the client, approach a reserve candidate, or reopen the search.

### Why do candidates decline job offers after accepting them?

In Robert Half's 2019 survey of more than 2,800 adult office workers in 28 major US cities, a better competing offer was the top reason among those who had backed out after accepting. In that group, 44% cited a better offer, 27% a counteroffer, and 19% negative information about the company. These historical findings do not establish today's ranking for agency or executive-search candidates. The only reason that matters for your recovery is the real one for this candidate, which is why you confirm it rather than assume it.

### Should you revise the client brief after a candidate declines?

Only after you confirm what actually changed with the client. A decline is often a client signal rather than a candidate problem. The budget may be below market, the timeline may have dragged, or the seniority bar may not match the offer. Before you rewrite a single line of the brief, get the client to confirm which of their constraints can move. If you revise the spec on your own assumption and resume sourcing, you risk presenting a fresh shortlist against the same wall that caused the first decline.

### When should you go back to a reserve candidate instead of reopening the search?

Go back to a reserve candidate when someone you already assessed still fits the brief the client has confirmed. If your earlier shortlist included a strong second choice, and the role has not materially changed, that person is a faster and safer bet than starting over. Review your own notes and assessment from the submission stage so the decision rests on real evidence, not a rushed scramble. The recruiter makes this call. No tool should rank your reserve candidates for you or promise that one of them will accept.

### Can you approach a candidate who previously declined an offer?

Yes, for future roles, as long as you kept the relationship warm and the record clean. A no to one opportunity is not a no to you. Thank them, ask whether they would like to hear about other roles, and note what they are looking for next. Many strong placements come from candidates who declined once and fit a later role perfectly. Keep their reason and their preferences on their contact record so that when the right mandate lands, you can reach out with something genuinely relevant instead of starting cold.

### How do you stop the same decline from happening on the next candidate?

Fix the cause you diagnosed before you re-present anyone. If the offer was below market, the client needs to move on pay or you need to reset expectations. If the process lost the candidate through delays, tighten the timeline. If the role itself does not compete for the talent you want, that is a conversation about the spec, not the shortlist. Repeated declines are a signal, not bad luck. Treating each decline as a one-off guarantees you meet the same wall with the next candidate you submit.

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/)

staffing executive-search crm 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

-   ![Job order decision record showing five factors and the accept, clarify, park or decline outcome for an agency mandate](https://www.leonar.app/_astro/job-order-prioritization.DSuCjU2k_ZJeXEm.webp)

    Staffing

    ### [Job order prioritization for recruitment agencies](https://www.leonar.app/blog/job-order-prioritization/)

-   ![Staffing redeployment handoff worksheet with end date, availability, client need, and next action columns](https://www.leonar.app/_astro/staffing-redeployment-workflow.kL495uvs_Z63B4R.webp)

    Staffing

    ### [Staffing redeployment: an assignment-end worksheet](https://www.leonar.app/blog/staffing-redeployment-workflow/)

-   ![Agency interview scorecard template with evidence, anchored rating, confidence, and open-questions columns](https://www.leonar.app/_astro/interview-scorecard-template.BrzT4z80_GVh31.webp)

    Staffing

    ### [Interview Scorecard Template for Recruiters](https://www.leonar.app/blog/interview-scorecard-template/)


## 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