Employee Retention Guide
Employee retention starts at the hiring decision, not at the exit interview. Most avoidable first-year attrition traces back to three things: expectations set wrongly during hiring, a job designed badly before anybody was hired into it, and a manager the person did not thrive under. Onboarding, career pathing and pay reviews decide most of what happens afterwards.
Last updated
Why is retention a hiring problem before it is an HR problem?
Because a large share of avoidable first-year departures were decided during hiring rather than during employment. Three causes recur. The role was oversold, so the person arrived expecting something the job does not contain. The job itself was designed badly before anybody was hired into it, with incoherent scope, no authority to match the responsibility, or a workload two people previously shared. And the profile hired was wrong for the actual work, usually because the scorecard described an idealised version of the role rather than the real one. None of those are fixable by engagement programmes afterwards. They are fixable at intake, in the job description, and in what gets promised at offer stage. The economics are straightforward too: with average cost per hire at $5,475 according to the SHRM 2025 Benchmarking Report, somebody leaving in month seven means paying that again, plus the vacancy and the ramp. Model your own figure with an employee turnover calculator using your own inputs rather than a borrowed multiplier. Start with any role that has turned over twice, because a repeat departure from one seat is a design problem.
How do expectations set during hiring show up as attrition?
As a resignation somewhere between month three and month nine, usually explained as a better opportunity elsewhere. What actually happened is a gap between what was described and what arrived. The defence is a realistic preview given deliberately: say the hard parts out loud during interviews, describe the least enjoyable part of a normal week, and let the candidate speak to somebody doing the job today without their manager in the room. Anyone who withdraws after that conversation was going to leave anyway, and losing them before an offer costs a fraction of losing them after a relocation. Then write down what was promised. Scope, title path, remote policy, on-call, travel, review cycle, and anything said about progression. Hand that document to the manager on day one, because most broken promises are not dishonesty; they are a conversation the manager never heard about. The role-specific hiring guides are a useful check on whether the role you are describing matches how that job is normally structured elsewhere. Then check the promise against reality at ninety days, while there is still time to close the gap or explain it.
What does onboarding do to first-year attrition?
It decides how quickly somebody becomes useful and whether they build the relationships that make leaving feel costly. The mechanics are unglamorous and they compound. Access, equipment and accounts working on day one, arranged the week before rather than the morning of. A named buddy who is not the manager. A manager one-to-one inside the first three days. A written 30, 60 and 90 day plan with one real deliverable in the first month, because early contribution is what turns a new hire from a guest into a member of the team. Introductions arranged rather than left to chance, which matters most for remote joiners with no corridor to bump into anyone in. Then two honest check-ins, at 30 and 90 days, asking what differs from what they expected. Most first-week failures start with a poor handover from the applicant tracking system to whoever runs onboarding, so make that handover a defined step with an owner rather than an email. Measure completion of the plan rather than attendance at an orientation session, since the plan is the part that produces a contributing colleague.
Want this evaluated against your actual hiring process?
Free forever for 1 user Β· no credit card
What is the difference between a stay interview and an exit interview?
Timing, and therefore usefulness. A stay interview happens while the person is still there and something can still change. An exit interview happens after the decision, filtered by politeness, a reference they may need later, and a wish to leave cleanly. Exit interviews are still worth running, but read them in aggregate for patterns rather than treating any single one as the truth. Stay interviews are the higher-value practice and hardly anyone runs them. Twice a year, thirty minutes, ideally with somebody other than the direct manager where trust is the issue. The rule that makes them work: act visibly on at least one thing raised, within a month. A stay interview that produces no change teaches people that speaking up is pointless, which leaves you worse off than never asking. Keep notes out of the performance record so the conversation stays safe to have honestly. Run them at a consistent point in the year rather than in response to a resignation, because a stay interview scheduled the week after somebody quits reads as damage control to the whole team.
- What would make you seriously consider leaving?
- What part of the role would you change tomorrow if you could?
- What do you want to be doing in two years, and is it possible here?
- Has anything promised when you joined not materialised?
- What is the best thing about this job that I should protect?
How much does manager quality decide whether people stay?
A great deal, because the manager controls nearly everything experienced daily: workload, feedback, which projects land where, whether credit is distributed fairly, and whether growth conversations happen at all. Rather than argue about the size of the effect in general, measure it inside your own company. Look at voluntary attrition by manager across two years, adjusting for team size and function, and look at internal transfer requests out of each team. Patterns appear quickly and are rarely a surprise to anyone working there. The most common root cause is structural: promoting the strongest individual contributor into management with no training and no support, then evaluating them on output rather than on team health. Fix it in three places. Make management a deliberate choice with a genuine alternative track. Train the specific behaviours, which are one-to-ones, feedback, workload distribution and career conversations. And be willing to move somebody out of management without framing it as a demotion, which is the part most companies avoid. Give new managers a peer group as well as training, since most management questions are too small to escalate and too specific to look up.
How does internal mobility keep people who would otherwise leave?
Because most people who leave for a new challenge would have taken that challenge internally if it had been visible and reachable. Three mechanics make it work. Post roles internally before or alongside external advertising, and mean it rather than running a formality after the decision is made. Set a transfer policy that stops a manager blocking a move indefinitely, with a maximum handover notice, because talent hoarding is the single most common reason these programmes fail. And keep a record of skills and interests, so a recruiter filling a role thinks of internal people first. Career pathing supports all of it: two tracks, individual contributor and management, with the expectations at each level written down, and lateral moves treated as normal rather than as a step sideways. Internal hires arrive with context, relationships and trust already in place. Note that this data usually lives in the HR system rather than the recruiting one, so read the ATS versus HRIS distinction before assuming a single tool covers both. Count internal fills as a hiring outcome in the reporting, because whatever is not counted stops being anybody's priority.
When should you review compensation, and what happens if you do not?
On a fixed calendar, at least annually, using market data you actually purchase rather than whatever a candidate claims in a negotiation. The failure mode is compression: pay for new hires drifts up with the market while existing people stay on their joining number, until somebody internal discovers what a new colleague earns. That discovery produces resignations that look sudden and were not. Review bands, check for compression explicitly, and correct it during the review rather than when a resignation forces it. Counter-offers deserve a plain position: they usually fail as a retention strategy, because money is rarely the only reason, and paying somebody who resigned teaches everybody else the mechanism for a raise. Some companies still make them for critical roles, and if you do, set the policy in advance rather than deciding in the moment. Pay transparency and pay equity obligations vary by jurisdiction and change often, so confirm what applies to you with qualified employment counsel. Explain the outcome of the review even when nothing changes for a given person, since silence after a stated review cycle gets read as a decision anyway.
How do you measure retention so the number means something?
One turnover percentage tells leadership almost nothing. Split it four ways. Voluntary versus involuntary, because those have different causes and different fixes. Regretted versus non-regretted, decided by asking the manager a single question before the person leaves: would you rehire them. By tenure cohort, since first-year attrition is a hiring and onboarding signal while fifth-year attrition is a growth and pay signal. And by manager, team, source and role, which is where the actionable patterns live. Then price it. Turnover cost is replacement cost plus the cost of the vacancy plus the ramp before a replacement is fully productive, so model it with a cost of vacancy calculator using your own salary and revenue inputs. Resist grading yourself against a published benchmark; healthy turnover varies enormously by industry, seniority and region. Compare against your own trend and your own cohorts, and report retention beside your other recruitment metrics rather than in isolation. Report it alongside a short note on what changed, because leadership seeing attrition numbers with no action attached stops asking within two quarters. Keep the definitions fixed so the trend stays comparable.
How to put this into practice
- Split attrition into regretted and non-regretted Ask every manager one question before a departure completes: would you rehire this person. Record the answer against the leaver. Within two quarters you will have a number leadership can act on instead of a single blended percentage.
- Find the cohorts that leave Break attrition down by tenure band, manager, team, hiring source and role. Look for concentrations rather than site-wide averages. Most companies find that a small number of teams or one hiring source accounts for a disproportionate share.
- Audit the job design of roles that churn For any role that has turned over twice, examine the job itself before blaming the hires: scope, authority, workload, reporting line and whether it was previously two positions. Rewrite the role before opening the requisition a third time.
- Fix the handover from offer to manager Write down everything promised during hiring, including scope, progression, remote policy and on-call, and give it to the manager before day one. Most broken promises are simply a conversation the manager never heard about.
- Start stay interviews on a fixed cadence Twice a year, thirty minutes, with a consistent set of questions and notes kept out of the performance record. Commit in advance to acting visibly on at least one item raised, otherwise the exercise teaches people that speaking up changes nothing.
- Make an internal move easier than an external one Post roles internally first, cap how long a manager may delay a transfer, and keep a usable record of skills and interests. Then check how many roles were filled internally last quarter, and treat a low number as a process problem.
- Put compensation review on the calendar Set an annual review against purchased market data, check explicitly for compression against recent hires, and correct it during the review rather than at resignation. Model the cost of losing somebody so the correction can be compared against it.
Mistakes worth avoiding
Read next
More guides
Recruiting terms explained
Related roles to hire
Recruitment & staffing services
Choosing your recruiting stack
Free tools for this
Employee Retention Guide β FAQs
What is a good employee retention rate?
What is regretted attrition?
How do you calculate the cost of employee turnover?
What is a stay interview?
Are exit interviews worth doing?
Does onboarding really affect retention?
Should you make a counter-offer to keep somebody?
How does internal mobility affect retention?
Run the process in this guide end to end
Pitch N Hire is an applicant tracking system. The workflow described here β requisition to offer β runs in one pipeline instead of across spreadsheets, inboxes, and calendars.
Free for 1 user Β· No credit card Β· Talk to a real hiring expert
Put this into a process that runs itself
See how Pitch N Hire handles the parts of this that eat a recruiter's week β posting, screening, scheduling and keeping every decision in one place.
Prefer to talk? Book a demo Talk to sales View pricing
Free 1-user plan Β· No credit card Β· Talk to a real hiring expert