Few things waste more time in recruitment than a candidate who goes through two interviews and then turns out to want far more than the role pays. The client feels misled, the candidate feels their time was wasted and the recruiter has to start again. In most cases the salary expectation was discussed at some point, by phone or in a first call, but it never made it onto the candidate record. This article explains why every candidate in your Applicant Tracking System needs a recorded salary or rate expectation before they are presented to a client or hiring manager, what exactly to record and how to keep it current without turning it into extra admin.
The details differ per segment. Recruitment agencies compare the expectation with the budget the client gave in the brief. Staffing desks work with hourly wages and need to know the minimum a candidate accepts before offering shifts. Secondment teams record the rate a professional expects for an assignment, separate from what is charged to the client. In executive search the package is often complex, with variable pay, a car or shares, and discretion matters. In-house recruitment teams check the expectation against the salary scale or band agreed with the hiring manager.
What goes wrong without a recorded expectation
- The expectation lives in one recruiter’s head or notebook, so a colleague presents the candidate without knowing it
- Different recruiters record it differently, gross or net, monthly or yearly, with or without bonus, so the numbers cannot be compared
- The figure was noted months ago and nobody checked whether it still applies
- The mismatch only appears at the offer stage, after the client has invested several interviews
- Offers are declined for pay reasons, but because the expectation was never recorded, nobody can see the pattern
What to record on the candidate record
- The basis — gross yearly salary, gross monthly salary or hourly rate, always stated the same way within your team
- Minimum and preferred — a range says more than a single figure: what the candidate would accept and what they hope for
- What is included — holiday pay, a thirteenth month, variable pay, a car or other benefits, so two figures are not compared on a different basis
- The date it was confirmed — an expectation from last spring is a starting point, not a fact
- Flexibility and context — for example a lower figure in exchange for working from home, or a higher figure because of travel time
Use fixed fields rather than free text, so the Applicant Tracking System can filter and compare. A note such as “wants a bit more than now” helps nobody a month later.
Compare it with the vacancy budget before submission
The other half is the budget on the vacancy. Record the salary range or rate agreed with the client or hiring manager in the structured brief, using the same basis as the candidate fields. Then make the comparison part of the written entry criteria for the submission stage: a candidate only moves to “presented to client” when the expectation is recorded and either falls within the budget or the gap has been discussed with the client beforehand. That does not mean rejecting everyone above the range. It means the client decides with the full picture, before the first interview instead of after the last one.
Keep it current through the process
Expectations move. A candidate who receives another offer, or who learns more about the role, may adjust. Confirm the expectation again at two moments: just before the client submission and just before the offer, together with the notice period. Each confirmation updates the date on the record. If the figure changes, the change is recorded with who entered it and when, so nobody has to guess which number is the latest.
Staffing and secondment: two different numbers
In staffing and secondment, the amount the candidate receives and the rate charged to the client are two separate things. Record them in separate fields with separate access. The candidate’s expectation belongs on the candidate record; the client rate and the margin belong with the assignment and are visible only to the people who need them. Mixing the two in one note is how a margin ends up in an email to the wrong person.
Sensitive data, handled with care
A salary expectation is personal information. Limit who can see it, explain to the candidate why you record it and share it with a client only with the candidate’s agreement, just as with the consent before every submission. In executive search in particular, many candidates prefer that the figure is discussed verbally with the client first. The retention date on the candidate record applies to these fields as well; they are not kept longer than the rest of the record.
Measure it with your own data
The Applicant Tracking System can show how many candidates were presented to clients without a recorded expectation, how many of those were later rejected or withdrew, and how often a withdrawal or a rejection has pay as the recorded reason. Report these as real counts from your own records, with the number of records behind each figure and the same filters every time. Do not rely on general salary benchmarks you cannot verify; your own declined offers say more about your market.
Where artificial intelligence may help — and where it must not
Artificial intelligence may point out that a candidate’s recorded expectation is older than a set period, or that it falls outside the budget on the vacancy, so the recruiter can check it in the next conversation. It may also draft a short note summarising what the candidate said about pay, which the recruiter reads and corrects. It stays a helper. Artificial intelligence does not replace recruiters, does not decide which candidates are presented and does not negotiate pay with candidates or clients. That conversation is held by people; the Applicant Tracking System makes sure it starts from the right figures.
A practical start
- Agree as a team on one basis for recording pay: yearly or monthly, gross, and what is included
- Add fixed fields for minimum, preferred, basis and confirmation date to the candidate record
- Add the budget range to every vacancy brief, using the same basis
- Make a recorded expectation an entry criterion for the submission stage
- Review once a month how many offers were declined for pay reasons, and what the records showed beforehand
Know the number before the client does
A recorded salary expectation is a small field with a large effect: fewer wasted interviews, fewer surprises at the offer stage and clients who trust that the candidates they see are realistic. Explore the product or book a demo — we show how candidate fields, vacancy briefs and stage criteria work together in BoldATS for your segment.