Published November 8, 2026.
An accepted offer feels like the end of the recruiting process, but the period between acceptance and the first day is where a hire can still disappear. This review sets out a bounded protocol for measuring how often candidates drop out after accepting an offer and what the record can honestly show. It separates a candidate withdrawal from an employer rescission and a failed condition. The distinction matters because each one calls for a different response.
Question and scope
This review asks how often candidates drop out after accepting an offer and before the agreed start date. The unit is one accepted offer for one candidate and one role. The study measures the share that did not start, the reason, and the time between acceptance and the dropout. It does not judge whether the candidate made the right choice or whether the offer was competitive.
Set the scope to one employer, one role family, and one offer process. Record the definition of acceptance, the conditions attached to the offer, and the start-date policy. If the process changes during the window, keep the earlier definition for offers already accepted and analyze the later cohort separately. A new background-check rule can look like a dropout increase when it is only a different condition.
Define the population as every offer accepted during the window, including offers later rescinded, withdrawn by the candidate, or still pending a start date. The unit is the offer, not the candidate, because one candidate can accept one offer and later accept another elsewhere. A rehired candidate is a separate unit with a link to the earlier record. Test the definition on two recent offers.
Data sources and methodology
Draw the accepted offers from the applicant tracking system and the onboarding record. Record the export date, the filters, the row count, and the selection rule. Match the acceptance date, the start date, the first day attended, and any withdrawal or rescission record. A missing start date should be marked missing, not assumed.
Use the recorded acceptance date as the start of the observation window and the agreed start date as the end. A candidate who never signs the contract has not accepted, even if they said yes on a call. A candidate who signs and then withdraws is in the sample. State the evidence used for acceptance. Collect the role family, the seniority, the location, the source, and the recruiter. These strata matter because a senior role with a long notice period and a frontline role with a quick start have different exposure. Report the result by role family and by the length of the gap between acceptance and start.
Why the post-offer period matters
The post-offer period is when a candidate compares the new role with the current one, hears a counteroffer, or loses confidence in the move. A delay in paperwork, equipment, or a start date gives the candidate more time to reconsider. The dropout rate is therefore partly a measure of the onboarding speed, not only the offer. A candidate who withdraws may still have had a good experience. The reason matters: a counteroffer, a family move, a failed condition, or a better fit elsewhere each imply a different response. The protocol should record the reason without turning the candidate into a metric. A low dropout rate is not automatically good if the business rescinds offers or pressures candidates to start before they are ready. Read the rate beside the rescission count and the candidate feedback. The quality of the hire matters as much as the volume.
Defining a dropout
Define a dropout as an accepted offer where the candidate does not start on the agreed date and does not start a later agreed date within the observation window. A candidate who starts late because of a visa or a notice period is not a dropout if the delay was agreed and recorded. A candidate who withdraws before the start date is a dropout even if the reason is a failed condition. Separate a candidate withdrawal from an employer rescission. The two have different causes and different fixes. A rescission may follow a failed background check or a budget change. Report the two categories separately and do not pool them into one headline.
Do not count a candidate who never signed the contract. A verbal yes is not an acceptance for this measure. Do not count a candidate who started and left on the first day as a post-offer dropout; that is an early exit and belongs in a separate measure. Each definition needs a positive and a boundary example.
Sampling and data quality
Include every accepted offer in the window. If the volume is large, take a random sample within each role family and report the sampling rule. Do not sample only the offers that resulted in a start, because that biases the result. Record the missing start dates and the number of records excluded.
Check the acceptance date against the signed contract or the onboarding system. A recruiter may mark an offer accepted before the candidate signs. Use the signed date if the business has it, and state which date was used. The two dates can differ by days and change the exposure window. Note the collection date separately from the offer window. An offer accepted near the observation date may still be waiting for a start date and should be censored. Report the censored count beside the completed outcomes.
Analysis and reporting
Report the number of accepted offers, the number of dropouts, and the share by category. Show the counts by role family, source, and the length of the acceptance-to-start gap. Present the median days from acceptance to withdrawal. Use the same denominator for every rate.
Inspect the withdrawals and group the reasons without naming the candidate. A cluster after a long gap may point to a slow onboarding process. A cluster from one source may point to a channel that attracts candidates who are not ready to move. Compare the result with the offer acceptance rate and the time to start.
A useful additional view is the share of candidates who asked for a later start date and then withdrew. That pattern may indicate a competing offer or a hesitation that a conversation could have surfaced. Record the request and the follow-up. The finding can improve the check-in between acceptance and start.
Limitations and sources of error
The record cannot show whether the candidate would have stayed if the start date had been earlier or the offer higher. It can show only that the candidate did not start and what reason was recorded. A dropout is not proof of a bad offer, and a start is not proof of a good hire. The protocol also cannot capture a candidate who accepted and continued to interview elsewhere. Applicant tracking systems can mark an offer as accepted when only a verbal yes was given, or leave a withdrawal unrecorded when the recruiter moved on. Record those cases and their treatment. If the candidate and the employer disagree about the start date, note the version in the record and use the written offer for the measure.
A small sample makes a rate unstable. Report the count and describe the cases rather than ranking recruiters. A single withdrawal in a small cohort can look like a large percentage. The report should say so.
Review cadence and next action
Review the result with the recruiting lead and the onboarding owner. Ask them to choose one observable change: a check-in call after acceptance, a faster paperwork path, a realistic start date, or a clearer pre-hire conversation about the role. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions for the next cohort. If the dropout rate fell but the early-exit rate rose, the change may have moved the problem to the first month. If the rate is stable but the reasons changed, the offer conversation may be improving in one area and failing in another. Close the review when the owner accepts the finding and the next cohort is scheduled.
Data Sources and Methodology
The review uses public employment guidance to bound the definitions and to keep the recommended record fields within common legal and administrative practice. The sources below are used as context, not as a claim that any one employer follows them in the same way. Each measure in this protocol is defined from the employer's own records, then compared with these public references where the reference is relevant. The citations are listed with the specific topic they support so a reader can check the boundary without searching the whole site.
- U.S. Bureau of Labor Statistics, HR specialists occupational outlook
- U.S. Bureau of Labor Statistics, employer costs for employee compensation
- U.S. Department of Labor, hour and leave standards
- U.S. Equal Employment Opportunity Commission, laws and guidance
- U.S. Small Business Administration, manage your business
- National Institute of Standards and Technology, Cybersecurity Framework
- U.S. Department of Health and Human Services, HIPAA Privacy Rule
- Internal Revenue Service, understanding employment taxes
- U.S. Census Bureau, business help site
- Gallup, workplace research
The method is deliberately descriptive. It does not pool employers or estimate a national rate. A reader who repeats the protocol should use the same definitions, the same observation window, and the same sampling rule, then report the counts beside the shares. Keep that report with the study record so a later reviewer can repeat the comparison.
Sources
- Society for Human Resource Management, candidate experience - accessed November 8, 2026.
- U.S. Bureau of Labor Statistics, job openings and labor turnover - accessed November 8, 2026.
- U.S. Department of Labor, hiring guidance - accessed November 8, 2026.
- U.S. Equal Employment Opportunity Commission, recordkeeping - accessed November 8, 2026.