Sign in

Blog · Territory, capacity and quota planning

Attrition forecasting for workforce planning

Attrition forecasting estimates aggregate workforce departures from historical exposure and departure rates. Build department and tenure assumptions from roster history, apply them to planned staffing, and reconcile the headcount outlook.

The short answerAttrition forecasting estimates how many employees are likely to leave across a department or workforce during a planning period. Define which departures count, calculate historical rates against employee exposure, and apply those rates to planned exposure by department and tenure. Compare the assumptions with actual departures and reconcile opening headcount, hires, exits and closing headcount.

Attrition forecasting estimates aggregate workforce departures so HR, finance and operations can review hiring and staffing assumptions. Calculate departure rates from consistent roster history, apply them to planned employee exposure, and compare the result with actual exits. The forecast supports group staffing decisions; it does not identify individual employees who will leave.

Define what counts as a departure

Decide whether you are forecasting voluntary resignations or all exits from the company. Keep the definition with the workbook. An employee moving between departments reduces one department's staffing but is not a company departure.

The Office of Personnel Management's data guide distinguishes monthly workforce snapshots from personnel actions; federal separations include retirements, resignations, terminations and deaths. Check your own reporting scope before calculating company rates.

For this example, departures mean exits from company employment, excluding internal transfers. Planned restructuring and specifically known exits would sit in separate assumption lines, with adjustments to prevent double counting. HR owns the classification; finance owns how the assumption feeds the headcount plan.

Build exposure from roster history

Export employee identifier, department, employment start date, effective exit date and departure category. Use an identifier to reconcile records without adding names to the planning summary. Retain historical department assignments rather than applying today's organization chart backward.

Create one monthly exposure measure per department and tenure band. An employee-month means one employee employed for a full month; partial months contribute the fraction employed. Assign that exposure to the tenure band applicable at the time. Assign departures to the employee's band at exit.

Monthly departure rate = Historical departures / Historical employee-months

Expected departures = Monthly departure rate × Planned employee-months

These are exposure-based planning rates. They are not quarterly probabilities applied repeatedly to the same opening roster. Planned exposure must reflect anticipated hires, exits and movement between tenure bands.

Work the department and tenure assumptions

A fictional US distribution company summarizes six months of roster history. Its planning team uses two tenure bands: under one year and one year or longer. Every historical departure and employee-month belongs to exactly one row.

Place the table in A:D on a summary sheet, with department in A, tenure in B, historical employee-months in C and departures in D. Calculate the monthly rate in E.

Department Tenure Historical employee-months Historical departures Monthly departure rate
Customer service Under one year 600 30 5.00%
Customer service One year or longer 900 18 2.00%
Warehouse Under one year 360 18 5.00%
Warehouse One year or longer 540 9 1.67%
Total 2,400 75 3.13%

In Microsoft Excel, enter the rate in E2 and fill down:

=D2/C2

To prepare the summary from monthly records, suppose History has department in B, tenure band in C, employee-month exposure in D and departures in E. For the chosen history window, the summary exposure in C2 is:

=SUMIFS(History!$D$2:$D$10000,History!$B$2:$B$10000,A2,History!$C$2:$C$10000,B2)

Replace the summed range with History!$E$2:$E$10000 for departures. Microsoft's SUMIFS documentation confirms that it sums matching rows using multiple criteria. Keep all ranges the same size. Covirage is not affiliated with Microsoft.

The company rate is 75 / 2,400 = 3.125% per employee-month, displayed as 3.13%. It is a ratio of totals, not the simple average of the displayed group rates. Preserve full precision in every calculation.

Apply the rates to planned exposure

The staffing plan supplies the following average headcounts for the next three months. Multiply each by three to obtain planned employee-months.

Department and tenure Planned average headcount Planned employee-months Rate used Expected departures
Customer service, under one year 110 330 5.00% 16.5
Customer service, one year or longer 160 480 2.00% 9.6
Warehouse, under one year 70 210 5.00% 10.5
Warehouse, one year or longer 90 270 1.67% 4.5
Total 430 1,290 41.1

Put planned average headcount in F and planned exposure in G. Expected departures belong in H. For row 2, enter these formulas in G2 and H2 respectively, then fill down:

=F2*3
=G2*E2

The expected total is =SUM(H2:H5), or 41.1 departures. Applying the pooled historical rate instead gives 1,290 × 3.125% = 40.3 departures, rounded to one decimal. The segmented result differs because the planned workforce mix differs from historical exposure.

Reconcile the staffing outlook and test a change

The company begins the quarter with 430 employees and plans 35 hires. Its headcount bridge is:

Headcount movement Expected employees
Opening workforce 430.0
Hires 35.0
Departures -41.1
Closing workforce 423.9

The identity is 430 + 35 - 41.1 = 423.9. Internal transfers must cancel in the company total. Revisit planned monthly exposure if this bridge changes hiring timing or the tenure mix. Use headcount variance to compare the resulting outlook with the approved staffing plan.

For a sensitivity, raise only the early-tenure warehouse rate from 5.00% to 6.00%. Its 210 employee-months now produce 12.6 expected departures, an increase of 2.1. Total departures become 43.2. That is a scenario, not evidence that the rate will rise.

Review misses monthly by group and compare the forecast saved before the period with actual departures. This article covers company departure assumptions; ramp and attrition in the capacity plan separately covers productive sales-representative capacity.

Where it goes wrong

  • Using closing headcount as historical exposure. Growth or contraction changes the denominator during the period.
  • Freezing tenure at today's date. Employees cross tenure boundaries, changing the group's exposure.
  • Double counting known departures. A specific exit added to an unadjusted baseline can appear twice.
  • Treating small groups as stable. Sparse history produces uncertain assumptions; combine groups or show scenarios.
  • Reading a group rate as a personal score. Aggregate planning does not establish an individual's likelihood of departure.

Review workforce assumptions in Covirage

Bring a sample of your own roster history, aggregate departure summary and staffing assumptions. Covirage maps the columns, and its tools compute and check exposure, group rates and planning comparisons; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account in about a minute, then set up your business and bring your file.

See Covirage for capacity planning for the planning context.

Questions people ask

Is attrition forecasting the same as employee flight-risk scoring?

No. An aggregate departure forecast estimates staffing losses across groups for budgeting and capacity decisions. It does not identify which individual will leave. Department and tenure assumptions can support workforce planning without assigning personal risk scores or treating a group average as an individual prediction.

Should attrition include retirements and layoffs?

Define the scope before calculating the rate. A total staffing-loss forecast may include resignations, retirements and other exits, while a voluntary-turnover review has a narrower numerator. Keep planned reductions and known retirements separate when they would otherwise be counted again through historical assumptions.

Why can expected departures contain a decimal?

Expected departures are planning quantities, so a department can have a forecast of part of a person even though actual departures are whole people. Keep decimals through the calculations, then choose an explicit rounding approach for requisitions or coverage decisions.