High turnover in a company is a pattern of departures that disrupts staffing within a defined team and period. Diagnose the team and tenure pattern, estimate replacement costs, and assign retention actions to the problems that your records support.
Decide whether turnover needs action by comparing a defined employee group over consistent periods. Review the departures alongside staffing interruptions, vacancies, and workload rather than applying one percentage to every team.
Start with a clear measurement rule. Use one period, such as a quarter or year, and define whether the population includes all employees, one location, one function, or a specific tenure group.
For voluntary turnover, SHRM’s workforce reporting article checked November 1, 2026, uses departures divided by average employment for the same period. Its voluntary measure excludes terminations and layoffs; report those separately.
Voluntary turnover rate = voluntary departures during the period ÷ average headcount during the period × 100
For a hypothetical quarter with six voluntary departures and average headcount of 30, the result is 20%. This is a worked example, not an industry benchmark.
BLS’s JOLTS definitions, checked November 1, 2026, separate quits, layoffs and discharges, and other departures. Keep those categories visible when comparing employee groups:
| Review group | Evidence to compare | Question to investigate | Proposed action owner |
|---|---|---|---|
| One team, first 90 days | Onboarding records and recorded exit reasons | Did the role match the expectations given at hiring? | Hiring manager and onboarding owner |
| Established staff in one team | Workload records and development discussions | Which recurring issue appears across several accounts? | Function leader |
| Several teams, same location | Local working practices and feedback | Does the pattern follow the site or one manager? | Site and people leads |
| Comparable groups across periods | Consistent denominators and exit categories | Does the concentration persist? | People analytics owner |
This is a proposed diagnostic worksheet, not employee data or a finding about a particular employer. A high company-wide rate can hide a concentrated problem. A stable overall rate can also hide a serious issue in one team, job family, or employee cohort.
Employees leave for different reasons, so a retention plan should begin with diagnosis rather than a universal reward. Start by separating role design, manager behavior, development, recognition, and culture.
Use these diagnostic prompts to organize interviews and workforce records. They are questions for your own investigation, not a ranked list of proven causes:
CIPD’s 2026 turnover and retention factsheet recommends examining why people leave. Its public introduction identifies flexibility, fair treatment, and wellbeing as retention practices.
Do not label every resignation a culture problem. Ask the same core questions across interviews, surveys, manager reviews, and workforce data, then look for patterns by team and tenure.
A useful diagnostic prompt is: “What changed between the employee’s expectations when they joined and their experience before leaving?” Record the answer as evidence, not as a confirmed cause until the pattern appears repeatedly.
Keep recognition activity visible while you investigate employee departures.
Read Reporting Guide →Build an internal turnover cost estimate from recruitment spending and documented disruption. Record vacancy coverage, training time, and handover work separately so finance can check each estimate.
The following worksheet is a suggested accounting approach. Keep observed operational effects separate from costs that finance can substantiate:
| Cost area | Evidence to collect | Accountable owner | Practical response |
|---|---|---|---|
| Recruiting budget | Advertising, agency, interview, and assessment spend | Recruiting or finance | Compare spend by role and hiring channel |
| Lost productivity | Vacancy days, ramp time, delayed work, and overtime | Function leader | Identify work that stopped, slowed, or moved to another team |
| Institutional knowledge | Handoffs, undocumented processes, customer context, and specialist skills | Manager or operations lead | Capture critical procedures before departures where possible |
| Team morale | Pulse responses, workload changes, absence patterns, and internal transfers | People leader | Review workload and communication after an exit |
| Management capacity | Interviewing, onboarding, coaching, and repeated performance support | Direct manager | Track time spent on replacement and stabilization work |
For a hypothetical example, a team that loses two experienced analysts in one quarter should record recruiting spend, open-work backlog, overtime, training time, and undocumented process knowledge. That internal estimate is more useful than applying an outside dollar figure without matching its assumptions.
Avoid counting every disruption as a financial loss. Mark each item as measured, estimated, or still unknown so decision-makers can see where the evidence is strong.
Assign a manager to each documented problem and choose an action that addresses it. The table below is a suggested action plan; it does not promise a reduction in departures.
| Diagnosed issue | Manager action | Evidence to review |
|---|---|---|
| Goals change without explanation | Set written priorities, decision owners, and review dates | Goal clarity responses and missed-priority examples |
| Employees lack development visibility | Discuss skill goals, possible assignments, and learning access | Development-plan completion and internal movement |
| Feedback is infrequent or inconsistent | Schedule regular one-to-one conversations with documented follow-up | Conversation completion and employee feedback |
| Contributions go unnoticed | Recognize specific work and explain its value to the team or customer | Recognition coverage and employee comments |
| Workload remains unsustainable | Review capacity, deadlines, staffing, and work that can stop | Overtime, absence, backlog, and workload responses |
| Employees do not feel heard | Create a feedback route, publish themes, and explain decisions | Participation, response themes, and follow-through |
Do not treat a bonus, gift, or recognition message as proof that retention improved. Recognition can support a broader management practice, but the result needs to be tested against exit behavior, employee feedback, and cohort trends.
For a hypothetical 30-day pilot, a manager can document team priorities, hold one structured development conversation with each direct report, recognize specific contributions, and review workload risks. State the test before starting so the team knows what will change and what will be measured.
Track retention actions with the same definitions before and after the intervention. Review voluntary and involuntary exits, stated reasons, tenure, team, manager, location, role, and cohort trends.
Use a simple monthly or quarterly review:
If recognition is one action in your plan, keep its activity records separate from employee exit data. Our employee recognition report guide explains the reporting structure. For specific appreciation messages, see our recognition letter examples.
A useful dashboard separates leading signals from outcomes. One-to-one completion, development conversations, workload reviews, and recognition coverage are activity measures. Voluntary exits, stated reasons, regretted losses, and cohort movement are outcome measures. Neither group proves causation alone.
If your plan includes employee rewards, Giftronaut’s order history reports guide, checked October 31, 2026, describes exporting full, filtered, or individual-order records. Keep the CSV with your recognition-program records. Review departure counts and employee feedback separately in the HR process.
High turnover becomes actionable when leaders stop treating it as one company-wide number. Define the population, locate the concentrated patterns, connect each pattern to evidence, and assign a response owner.
Retention work then becomes a repeatable review rather than a one-time campaign. Keep the actions specific, the comparisons consistent, and the conclusions proportionate to the evidence.
See how reward delivery fits your employee recognition process.
Explore Employee Rewards →The BLS JOLTS FAQ, checked November 1, 2026, records retirements under other separations, not quits. Keep retirement distinct from voluntary resignations when comparing departure categories.
A transfer can be an exit from a location while the employee remains with the company. The BLS JOLTS FAQ, checked November 1, 2026, records transfers to another location as other separations and excludes transfers within the same location. Define whether your own report measures the company or a specific site before comparing results.
Monthly departure counts can be added to obtain a yearly total when the scope stays consistent. Percentages need their own denominator calculation; adding monthly rates is not the same operation. The BLS JOLTS FAQ, checked November 1, 2026, distinguishes period counts from point-in-time measures.
For a hypothetical group, nine of ten starting employees stay: retention is 90%. If one employee left and average headcount was 15, that turnover calculation is 6.67%. The calculations use different denominators, so these percentages are not complements.
Use published JOLTS aggregates for context and your own payroll records for company analysis. The BLS JOLTS FAQ, checked November 1, 2026, explains that respondents’ data receive confidentiality protections. Do not use aggregate industry results as if they were a particular company’s departure records.