Candidate Drop-Off Rate

How to measure it stage by stage

A single overall drop-off number is too blunt to act on. Measure it between each pair of stages: applied to screened, screened to interviewed, interviewed to offer, offer to start. The fix for losing people before a phone screen (speed, scheduling) is completely different from the fix for losing them after an offer (pay, start date, a competing offer).

You need disposition codes that separate "candidate withdrew" and "no response" from "employer rejected." Many ATS setups lump them together under "not selected," which makes the metric impossible to calculate. Set a rule for silence too, such as no reply after three contact attempts over five business days, so recruiters close out stale candidates the same way.

The pipeline conversion rate tells you how many move forward. Drop-off tells you how many you lost who might still have been hireable. Look at both.

Typical ranges in high-volume hiring

These vary widely by role and labor market, but a common pattern for hourly hiring in the US looks like this:

• Application started to submitted: often 40% to 70% abandon on long forms. This is tracked separately as application completion rate.
• Submitted to first screen: 30% to 50% drop off when the first contact comes after 48 hours or more; under 15% when contact happens within an hour.
• Scheduled interview to attended: 20% to 40% no-show is common for entry-level roles.
• Offer to day one: 10% to 25% do not start, higher when the start date is more than two weeks out.

Professional and salaried roles usually leak less at the front and more at the offer stage.

Why candidates drop off

When teams survey or call back candidates who left, the same reasons come up again and again:

• Slow response. Hourly candidates often apply to five to ten jobs in an evening. The first employer to call usually wins.
• Too many steps. Every extra handoff between apply and offer costs people.
• Scheduling friction. Back-and-forth emails to find a time, or interviews only offered during the candidate's current shift.
• Surprises. Pay, schedule or location details revealed late that should have been in the job ad.
• Silence. Long gaps after an interview read as a rejection, and the candidate moves on.

A lot of what gets called candidate ghosting is really the employer going quiet first.

Drop-off rate vs rejection rate

Rejection is your decision. Drop-off is the candidate's. Mixing them hides problems: a stage with 60% attrition might be a strict but healthy screen, or a broken scheduling step that loses half of your best applicants. If a stage has high drop-off and low rejection, the process is the problem. If it has high rejection, look at the sourcing and the job ad instead.

How to reduce candidate drop-off

1. Make first contact within minutes for hourly roles, not days. Automated text outreach and self-scheduling do most of the work here.
2. Collapse steps. Combining the phone screen and the first interview into a single 20-minute conversation often cuts a full stage of leakage.
3. Offer self-scheduling with evening and weekend slots.
4. Put pay range, shift and location in the job ad and repeat them in the first message.
5. Send reminders 24 hours and 2 hours before every interview.
6. Shorten the offer-to-start gap, and keep in touch during it with a simple preboarding sequence.

Retest the stage rates after each change rather than changing everything at once.

Common mistakes

• Counting rejected candidates as drop-off, which inflates the number and points recruiters at the wrong fix.
• Reporting only an overall rate with no stage breakdown.
• Comparing drop-off across sources without adjusting for intent. Referrals and rehires leak far less than aggregator traffic.
• Treating drop-off as a candidate quality problem. Most of it is speed and friction, which the employer controls.