The offer is signed on Tuesday, the client has told the runner-up the role is filled and the start date is in the planning. On Friday the candidate calls: his manager offered a raise and a new title, and he has decided to stay. Nobody on the desk knew he had not resigned yet, nobody had asked how his employer was likely to react, and the runner-up has already accepted something else. This article explains why every candidate at offer stage in your Applicant Tracking System needs a recorded counter-offer check: what the check is and what it is not, which fields to keep on the application, when to have the conversation, how it links to notice period, offer and start date, and how to measure counter-offer losses with your own data.
The risk looks different per segment. Recruitment agencies lose a fee and a client’s trust when an accepted offer falls through before the start. Staffing desks see it as a no-show on the first day, after the shift plan was built around that person. Secondment firms compete with an employer or end client who wants to keep a consultant on the current assignment. Executive search consultants work with senior candidates whose employers often fight hardest to keep them, across long notice periods. In-house recruitment teams plan onboarding, equipment and a hiring manager’s calendar around someone who may never arrive.
Why counter-offers catch desks off guard
- The candidate’s reason for moving was discussed once on the phone and never written down, so nobody can check whether the offer actually solves it
- The offer stage is treated as the finish line, while the candidate still has to resign and work through a notice period
- Nobody records whether the candidate has resigned, so “accepted” and “resigned” look the same on the board
- Contact stops after acceptance, exactly when the current employer starts talking to the candidate
- The runner-up is released the day the offer is accepted, so there is no fallback if the placement collapses
A counter-offer is not a surprise event; it is a predictable step in many moves. If the Applicant Tracking System only records that an offer was accepted, the desk sees the risk the day it becomes a loss.
What a counter-offer check is, and what it is not
A counter-offer check is a short, honest conversation with the candidate, recorded on the application, about what happens when they hand in their notice. It asks what made them start looking, whether this offer addresses that, how they expect their employer to respond and what they would do if the employer offered more money or a different role.
It is not a pressure tactic and not a loyalty score. Staying with a current employer is a legitimate choice. The point is that the candidate, the recruiter and the client all see the situation clearly before plans are built on it. A candidate who says “if they match the salary, I would probably stay” has given you useful information; the right response is to talk about it openly and keep the shortlist alive, not to push.
Where it lives: fields on the application at offer stage
Keep the check on the candidate’s application for this vacancy, not in a recruiter’s memory or a chat message. A few fields are enough:
- Reason for moving — in the candidate’s own words, recorded at the first qualifying call and dated, so it can be compared with the offer later
- Counter-offer conversation — the date it took place and a short factual note of what the candidate said, including any counter-offer they mention
- Resignation planned — the date the candidate intends to hand in their notice, shown as the next action date so somebody checks in that day
- Resignation confirmed — the date the candidate confirmed they resigned; until this is filled, the placement is not secure
- Outcome — resigned and starting, stayed after a counter-offer, or withdrew for another reason, linked to the recorded withdrawal reason when the move falls through
The fields sit next to the information that already belongs to this stage: the notice period, the salary expectation and the offer acceptance deadline. Together they show at a glance whether an accepted offer is likely to become a start.
When to have the conversation
- At the first qualifying call — ask why the candidate is looking and record the answer; this is the baseline for every later check
- Before the offer is made — confirm the reason for moving still holds and that the offer addresses it; if salary is the only reason, say so on the record
- Between acceptance and resignation — agree on the resignation date and call the candidate after the conversation with their manager
- During the notice period — keep regular contact until the start date, because counter-offers do not always come on the day of resignation
Each moment is a task with a date on the application. When the desk reviews its pipeline, accepted offers without a confirmed resignation are easy to spot.
How it connects to the rest of the pipeline
- Runner-ups — keep the second candidate informed and available until the resignation is confirmed, and use the runner-up talent pool when the first choice stays
- Start date — a confirmed start date before the vacancy closes is only realistic once the resignation is confirmed and the notice period is known
- Client communication — tell the hiring manager when the candidate plans to resign and when you expect confirmation, so the client does not close every other door early
- After the start — the reason for moving is a good topic for the check-ins during the guarantee period; a former employer sometimes tries again after a few weeks
Record facts, not guesses
Notes about a candidate’s motivation are personal data. Write down what the candidate told you, with a date, and leave out speculation about private circumstances, character or loyalty. A note such as “Candidate expects a salary counter-offer; would decline unless the role changes” is useful and fair. Keep in mind that the candidate can ask to see these notes, for example through a data access request, so write them as if the candidate will read them one day.
Common mistakes to avoid
- Treating acceptance as the end — an accepted offer without a confirmed resignation is still an open risk
- Asking only at the end — a first question about counter-offers on the day of the offer feels like pressure; a reason for moving recorded weeks earlier makes it a normal follow-up
- Releasing the runner-up too early — the fallback disappears the moment it is most likely to be needed
- Going quiet during the notice period — silence after acceptance leaves the conversation to the current employer
- Arguing the candidate out of a counter-offer — inform, do not pressure; a candidate who moves reluctantly is a guarantee risk
- Logging the loss as “other” — if the outcome is not recorded as a counter-offer, you cannot learn from it
Questions teams ask
- Is it awkward to ask about counter-offers? — Less than you think, if the reason for moving was discussed from the start; most candidates appreciate being asked before they resign rather than after
- Should we tell the client? — Share the planned resignation date and whether it has been confirmed; share the candidate’s personal reasons only when the candidate agrees
- Does this matter for staffing and secondment? — Yes; the conversation is shorter, but a no-show on day one or a consultant kept on the current assignment costs the same planning effort
- What if the candidate stays after all? — Record the outcome and the reason, thank the candidate, keep the relationship and revisit the record later; people who stayed after a counter-offer sometimes move after all
Measure it with your own data
Count from your own records: how many accepted offers ended without a start, how many of those were counter-offers, how many calendar days passed between acceptance and confirmed resignation, how many accepted offers had a recorded counter-offer conversation, and how often a runner-up was still available when the first choice stayed. Report the number of offers behind each figure, and look at segments separately. Do not compare yourself with industry averages; your own counts show where accepted offers turn into losses.
A practical start
- Add reason for moving, counter-offer conversation, resignation planned, resignation confirmed and outcome to the application at offer stage
- Make the reason for moving part of every first qualifying call
- Add counter-offer as a standard option in your withdrawal reasons
- Agree that the runner-up is released only after the resignation is confirmed
- Review every accepted offer without a confirmed resignation in your weekly pipeline review
An accepted offer is not yet a start
A counter-offer check turns a late surprise into an early, recorded conversation. Write down why the candidate wants to move, talk about the counter-offer before the resignation, track the resignation as a date and keep the runner-up warm until it is confirmed. Explore the product or book a demo — we show how applications, offer stages, next action dates and withdrawal reasons are set up in BoldATS for your segment.