Offer Acceptance Rate: What Is Good and How to Improve It

Offer acceptance rate is offers accepted divided by offers made, shown as a percentage. There is no single good figure, since it depends on role, level and market, but a falling rate is a warning. Track it by role and source, record why people decline, and fix causes such as slow decisions or unclear offers.

How to calculate it

Divide accepted offers by offers made in the same period, then multiply by 100. As an example only: if you made 20 offers last quarter and 16 were accepted, the rate is 16 divided by 20, which is 80 percent. Decide your rules and keep them steady. Count each offer once, even if it was revised. Decide how to treat offers that were withdrawn by you, offers still open at the end of the period, and verbal offers that never reached writing. Most teams count written offers that received a clear yes or no. Whatever you choose, write it down so that a colleague or a later quarter is measured the same way. A rate based on five offers moves a lot with one decision, so look at a longer period before drawing conclusions.

What counts as a good rate

Beware of headline benchmarks. Published figures vary by industry, country, seniority and how each source counts, and they are not a promise for your market. A better benchmark is your own history: your rate for this role last year, compared with now, and your rate across teams or sources. A very high rate can also hide a problem, such as offers pitched too low to compete only on candidates with no other choices, or too few offers made. A lower rate for senior or in-demand roles is normal, since those candidates hold several options. Use the number to ask questions, not to score yourself. If the rate drops and you cannot say why, you need better data on why candidates decline.

Why candidates decline

Common reasons include pay or benefits lower than expected or lower than a competing offer, a slow process during which they took another job, a counteroffer from their current employer, concerns about the manager or team that came up late, unclear role scope or progression, location or flexibility mismatch, and a poor experience of the process itself. Sometimes the reason is personal and has nothing to do with you. You will not know which applies without asking. A short, friendly call after a decline, and a record of what you hear, turns each lost offer into information. People are more honest when you make clear you are not trying to change their mind. Compare the reasons by stage and source. Candidates from referrals may decline for different reasons than those from job boards, and senior candidates may decline for reasons that entry-level ones never raise. Separate declines at the offer stage from withdrawals earlier in the process, because the fixes differ. A decline after a long wait points to speed, a decline after a late salary discussion points to early pay conversations, and a decline after meeting the team points to the role or the manager. Share anonymised reasons with hiring managers, and avoid blaming any single person for patterns that belong to the process.

Fix the offer before it is made

Most declines can be prevented earlier. During interviews, ask what matters to the candidate, and what a competing offer would need to beat. Share the pay range early, so that the offer is not a shock. Agree the package and limits with the hiring manager and finance before you call. Make sure the offer reflects what was discussed: the title, location, flexibility and start date. Check pay against comparable internal roles for fairness. If you cannot meet a candidate's number, find out what else would help, such as a review date, leave, flexible hours or a start date, within your approved limits.

Speed and communication

Delay costs offers. Strong candidates have other options and decide on momentum. Make the decision quickly after the final interview, say when they will hear, and keep the date. Call before you send the written offer, so that you can share enthusiasm and hear concerns. Send the written offer soon after. Answer questions the same day where you can. Stay in contact during the decision period without pressuring, and avoid unrealistic deadlines that feel like a pressure tactic. Give a reasonable time to decide, usually a few days, and be flexible where there is a good reason. Introduce the candidate to the future manager or team again if they ask.

Sell the whole package and the role

Pay is only part of the decision. Remind candidates, truthfully, of what they told you they wanted: the work itself, the team, growth, flexibility and stability. Describe benefits, leave, learning budget and progression in plain terms. Be honest about the downsides, since a surprise after joining leads to early exits and damages your reputation. Explain how you reached the figure, in terms of the range for the role and the person's experience. Candidates who understand the reasoning are less likely to feel lowballed, even if the figure is not their top ask.

Rules differ by country

Rules on asking about current pay, on pay transparency, on what an offer must contain, and on notice periods differ by country, state and city. Check local requirements before you change how you make or document offers.

A short action plan

1. Calculate your rate for the last two to four quarters, by role and source. 2. Record the reason for each decline in one consistent list. 3. Review the three most common reasons with the hiring managers. 4. Fix the earliest cause: pay range, speed, or role clarity. 5. Make offers by call first, then in writing. 6. Recheck the rate after another quarter. Treat the first results as a starting point, not a verdict. Small samples can mislead, so avoid big changes based on two or three offers. One useful practice is a decline interview. Within a week of a no, ask the candidate for ten minutes, say that you are not trying to change their mind, and ask three questions: What was the deciding factor? What could we have done differently? Would you consider us again in future? Record the answers under a fixed list of reasons so that you can count them later. Another practice is an offer review before you send: check that the title, pay, location, flexibility and start date match what the candidate has been told, and that the person who will approve the offer has seen it. Add a simple tracker with the date of the final interview, the date of the offer and the date of the decision, so that you can see whether long gaps lead to more declines in your own data. Share the quarterly figures and the top decline reasons with hiring managers, and agree one change to try. Keep changes small and measure them over enough offers to learn something.

In Rezumz

In Rezumz, offers are drafted on the candidate record, approved by the account owner or someone on your team before sending, and accepted online with a typed name. The approval and acceptance are recorded, and recording a reason on a rejection or withdrawal helps you see later where candidates drop out. Notifications tell your team when an offer's status changes. Rezumz does not set pay, predict who will accept or promise a particular rate, so the improvement comes from your process.