peopleanalyst

Tools · People analytics

Turnover Cost

Enter a role and a few numbers — get a fully-loaded, cited cost of turnover and the retention business case.

The method

Fully-loaded turnover costing (Cascio's separation-cost framework)

When someone resigns, no invoice arrives. The recruiter's time, the empty seat, the six months the replacement spends getting up to speed — none of it lands on a ledger line, so the retention proposal walks into the budget meeting with a feeling while every competing request walks in with a number. A director can lose four engineers in a year and be unable to say what that cost.

Cascio and Boudreau's Investing in People devotes two full chapters to what they call the high cost of employee separations, and their central claim is an accounting one: turnover has a computable, fully-loaded cost — separation processing, replacement acquisition, and the long tail of lost productivity while the new hire ramps — and that cost is a multiple of anything visible in the ledger. They insist on the distinctions that make the number defensible rather than dramatic: voluntary versus involuntary separations, cost per event versus cost annualized over a segment, and absenteeism as the recurring cousin of turnover that deserves its own line. Their larger point is postural — treat these as investment analyses that inform decisions, not scary numbers that decorate slides.

Mike West's People Analytics For Dummies places the same arithmetic inside the Attraction–Activation–Attrition arc and pushes on the second half of the problem: the cost tells you the stakes, but managing attrition means finding the real reasons people leave — through segmentation and regression on your own data, not exit-interview folklore. Diez, Bussin, and Lee's Fundamentals of HR Analytics supplies the discipline that gets the number heard: make the business outcome the dependent variable, and walk into Finance with turnover expressed as a P&L consequence rather than an HR statistic. The method's honest limit is its assumptions — recruiting cost as a percent of salary, ramp-time productivity loss, knowledge-loss estimates (the softest component) — which is why the serious version of this analysis shows its defaults and its sensitivity, not just its total.

The books hand you the cost model and a blank spreadsheet; here the arithmetic runs deterministically in code — every default rate visible and overridable, missing inputs reported rather than invented — and the write-up flags which assumptions move the total most before you take it to Finance.

The books behind this tool

How it works

The number is code's, the defense is the corpus's: a deterministic layer computes the fully-loaded cost per separation (recruiting + onboarding + ramp-productivity + vacancy coverage + knowledge loss) with canon-typical, overridable default rates, annualizes it over the segment, and adds recurring absenteeism — then the model justifies each default against the people-analytics corpus, flags the highest-leverage assumptions, and frames the retention-investment business case. Distinct from talent-value (what an employee is WORTH) — this is what losing one COSTS; it consumes comp/headcount inputs, never duplicates them. Missing inputs are reported, never invented.

You bring

{ segment, annualSalary?, headcount?, annualSeparations?|turnoverRatePct?, recruitingPctOfSalary?, onboardingPctOfSalary?, rampMonths?, rampProductivityLossPct?, vacancyDays?, knowledgeLossPctOfSalary?, absenceDaysPerYear? }

You get

{ segment_summary, components[] (formula · assumption · per_separation), per_separation_total, separations, segment_annual_total, absenteeism_annual, grand_total, sensitivity_drivers[], interpretations[], business_case, grounded_in, provenance }

Use it for

See it work

example output

Segment: 30 Customer Success Managers at a mid-market SaaS company — $95K average salary, 22% annual turnover, a 9-month ramp override, and 6 unplanned absence days per employee per year.

Turnover Cost — Customer Success Managers (mid-market SaaS)

Segment: 30 CSMs, $95K average salary, 22% annual turnover (≈ 6.6 separations/yr). Every dollar below is computed from your inputs; default rates are canon-typical and overridable.

Cost per separation

DriverAssumptionFormulaPer separation
Recruiting & sourcing20% of salarysalary × rate$19,000
Onboarding & training10% of salarysalary × rate$9,500
Lost productivity during ramp50% loss over 9 months (override)salary × loss × (months ÷ 12)$35,625
Vacancy coverage45 vacant days(salary ÷ 260) × days$16,442
Knowledge & relationship loss10% of salarysalary × rate$9,500
Fully-loaded cost per separation$90,067

Annualized for the segment

  • Separations/year: 6.6 (30 × 22%)
  • Segment turnover cost: $90,067 × 6.6 = $594,442/yr
  • Absenteeism (6 days × $365/day × 30): $65,769/yr
  • Grand total: $660,211/yr

Where the number is most sensitive

The two largest drivers — lost ramp productivity ($35,625) and recruiting ($19,000) — carry the most risk. CSM ramp is genuinely long (the 9-month override is defensible: a manager isn't trusted with at-risk renewals on day one), so if anything that figure is conservative. A 3-month ramp improvement alone saves ~$11,900 per separation.

Interpretation

  • Ramp loss is the lever, not the recruiter invoice. For a relationship-carrying role, the real cost is the renewals a half-productive CSM doesn't save. (People-analytics canon: replacement cost rises with the role's tenure-to-productivity.)
  • 22% sits above the SaaS CSM healthy band (~12–15%). Roughly $190K/yr of this total is the gap above a normal-attrition baseline — that's the addressable prize.

Retention business case

At $660K/yr, cutting CSM turnover from 22% to 15% frees ~$190K annually — funding a retention program (career pathing, comp review, manager coaching) several times over. Frame "our CSMs keep leaving" to the board as a recurring $660K P&L line, not an HR complaint.

Grounded in: people-analytics cluster — fully-loaded replacement cost, ramp-to-productivity, absenteeism costing.

Run it now

Calculate the cost of turnover

Put a defensible dollar figure on attrition for a role or segment — recruiting, onboarding, ramp, vacancy, and knowledge-loss components computed in code and framed for a business case.

Prefer code? Call it over the API or hand it to your AI agent via MCP — POST /api/bicycle/turnover-cost · calculate_turnover_cost. API & agent access →

← All tools