How to Calculate Employee Turnover Rate

A 12% annual turnover rate in a 10-person team sounds manageable. But if both departures came from the same manager’s team, in the same 6-month window, two years in a row? That is not a statistical blip. That is a retention crisis hiding behind an average. 

Company-level turnover rates smooth out everything that matters: 

• The same manager losing people every cycle 

• Senior technicians leaving at three times the rate of junior staff 

• A specific tenure band, say employees at the 9-to-15-month mark, quietly walking out the door 

In MSP and IT service environments, losing one experienced technician costs you 3 to 6 months of recovery time, client relationship continuity, and institutional knowledge that no job description replaces. 75% of voluntary departures are preventable. But you cannot prevent what the headline number is actively hiding from you.

“Employee turnover rate is the percentage of employees who left an organisation during a defined period relative to average headcount. It measures the volume of departures, not their cause, concentration, or preventability.“ 

It tells you how many people left. That is, it. It does not tell you why they left, whether departures were preventable, which manager the problem is concentrated in, or what role or tenure band is most at risk. 

Most managers treat it as a verdict. It is a starting point. 

One distinction that gets overlooked: voluntary and involuntary turnover are not the same number. Resignations and terminations require completely different responses. Mixing them into one rate distorts the picture. Similarly, track turnover monthly rather than just annually. A spike in Q2 that recovers by Q4 looks fine in the annual figure, but the service disruption it caused was very real.

The Standard Employee Turnover Rate Formula 

Turnover Rate = (Departures ÷ Average Headcount) × 100 

Average Headcount = (Opening Headcount + Closing Headcount) ÷ 2 

The most common error: using end-of-period headcount instead of average headcount. If your team grew or shrank during the period, that single number will skew your result. 

Worked Example for a Service Team

Voluntary Turnover Rate Formula 

Voluntary Turnover = (Voluntary Departures ÷ Average Headcount) × 100

Terminations are a performance management issue. Resignations are a retention issue. Tracking them separately is the only way to know which problem you are solving. 

Use monthly rolling figures for operational monitoring and annual calculation for benchmarking. Once you have your rate, track your team’s retention rate alongside turnover to get the full picture of what is happening with your headcount. 

Generic HR benchmarks are not useful for MSP and IT service businesses. Here are the thresholds that matter in your industry: 

The IT and managed services sector typically runs 13 to 17% annual voluntary turnover. Whether your number is improving or worsening matters more than where it sits today. 

One counterintuitive point: low turnover is not automatically good. A team at 2% for three years with zero voluntary departures might be quietly disengaged. People who stopped caring enough to leave is a different kind of problem, and the turnover rate will not flag it.

The Cost Calculation Every Service Manager Should Run

Replacing one technician costs 33 to 50% of their annual salary when you factor in recruitment, ramp-up time, lost productivity, and CSAT impact. At a $65K salary, that is $21,000 to $32,500 per departure. Multiply that by your annual departures. That number tends to sharpen focus quickly.

The headline rate is a starting point. The real work happens when you break it apart across three dimensions. 

• By manager: Run the formula separately for each manager’s team. Any manager with voluntary turnover more than 5% above the company average for two or more consecutive periods is showing a pattern, not noise. 

• By role: Calculate departures by role divided by average headcount in that role. If your most experienced technician tier is turning over at 3x the rate of tier-1 staff, the problem is the career path or workload distribution, not general morale. 

• By tenure band: Group departures by length of service. Departures clustering in the 6-to-18-month band point to an onboarding or progression problem. Departures in the 2-plus year band point to culture or compensation. 

• The 3-Segment Rule: If all three dimensions point to the same intersection, that is your problem. Stop averaging. Act on the overlap.

Turnover rate is a retrospective metric. It updates after someone leaves, not before they decide to. Most resignations are decided 4 to 8 weeks before they are announced. In that window, the decision is often already made, but the behavioral signals are visible to anyone tracking them: 

• Declining engagement in 1:1s 

• Stalled goal progress 

• Reduced participation in team recognition 

• Subtle drop in CSAT ownership 

The turnover rate cannot catch any of these. By the time it moves, the departure has already happened or is in motion. One retained resignation costs a conversation and possibly a compensation adjustment. One executed resignation cost $21,000 to $32,500 and months of disruption. The math on catching it early is straightforward. 

To identify the behavioral signals that predict turnover before it happens, the data you need is not in the turnover rate. It is in how your team performs day to day, before the resignation is written. 

Calculating your employee turnover rate correctly matters. But the real skill is knowing what to do with the number once you have it: segmenting by manager, role, and tenure, reading it against the right benchmarks, and understanding what it structurally cannot tell you. 

The managers who retain their best people are not the ones who monitor the rate. They are the ones who track what drives it before it moves. 

Team GPS gives service team managers real-time visibility into the performance and engagement signals that precede turnover, so the conversation happens at week four, not after the resignation letter. Start with the formula. Segment the data. Then look at what is happening upstream of the number.

Q: Should I include contractors in my turnover rate calculation? 

A: Include them only if they fill core service delivery roles on an ongoing basis, as their departure carries the same operational impact as a permanent employee. Project-based contractors should be tracked separately. 

Q: What is a good turnover rate for an MSP or IT service business?  

A: Below 10% is strong, 13 to 17% is the industry norm, and above 20% signals a systemic problem. Your own trend over time is more useful than any single industry benchmark. 

Q: How do I calculate turnover rate if my team size changed significantly during the year?  

A: Use average headcount calculated from monthly figures, then divide by 12. This removes the distortion caused by rapid growth or reduction during the period. 

Q: What is the difference between turnover rate and attrition rate?  

A: Turnover includes all departures, voluntary and involuntary. Attrition typically refers to voluntary departures where the role is not backfilled. Voluntary turnover rate is the number service team managers should focus on most. 

Q: How often should I calculate my turnover rate?  

A: Monthly using a rolling 3-month voluntary figure for operational monitoring, and annually for benchmarking. Monthly cadence catches concentration patterns before they compound into something harder to fix. 

Q: My turnover rate is low, but I keep losing the same type of person. What does that mean?  

A: Your headline rate is masking a role-specific or career path problem. Segment by role and tenure band. If the same profile keeps leaving, the issue is structural, and a low overall rate makes it easier to miss.