Voluntary Exits
Count of employees who resigned during the period (initiated by employee, not the company). The numerator of the `hr.voluntary_turnover_rate` calculation and the headline "are we losing people" number boards anchor on. Common pitfall: ambiguous "mutually agreed" exits — companies sometimes log managed-out exits as voluntary to keep the visible number low. Define the test: if the employee initiated the conversation and there was no formal performance trigger, it is voluntary; otherwise log as termination. — HR KPI, I'mBoard-authored (editorial tier).
I'mBoard-authored (editorial tier)
No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.
Rogue ID: hr.voluntary_exits
Type: Number
Domain: HR
Definition
Count of employees who resigned during the period (initiated by employee, not the company). The numerator of the hr.voluntary_turnover_rate calculation and the headline "are we losing people" number boards anchor on. Common pitfall: ambiguous "mutually agreed" exits — companies sometimes log managed-out exits as voluntary to keep the visible number low. Define the test: if the employee initiated the conversation and there was no formal performance trigger, it is voluntary; otherwise log as termination.
Formula
Count of employees with employee-initiated separations (resignations, retirements) during the period. Excludes terminations (those go in `hr.terminations`), exclusions for cause, and contractor-end events.Why it matters
The leading indicator the board reads for retention health and culture risk. Concentration in a single team, level, or tenure cohort is more informative than the absolute number — investigate the pattern, not just the headline.
How to interpret
Convert to hr.voluntary_turnover_rate (annualized %) for cross-period comparison and benchmarking. Spike triggers: 3+ voluntary exits from one team in a quarter, or any C-1 (executive direct-report) departure — both warrant board narrative in hr.talent_challenges.
Calculation policy
How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.
Inclusion rules
- Count of EMPLOYEE-INITIATED separations — resignations and retirements — whose effective last day falls WITHIN the reporting period (period-flow, same period boundary as the rest of the report).
- Classification test: the employee initiated the conversation AND there was no formal performance trigger ⇒ voluntary. Apply the test consistently so the visible number is not gamed.
Exclusion rules
- Company-initiated separations — performance terminations, layoffs/RIFs, for-cause exits — those are
hr.terminations. - "Mutually agreed" / managed-out exits where the company drove the conversation or a performance process was underway — log these as terminations, not voluntary, even when paperwork reads "resignation".
- Contractor-end events — not employees, not in this count.
- Exits dated outside the reporting period.
Required inputs
- Separation records with initiator (employee vs company), reason code, and last-day date.
- Performance-process flags to disambiguate managed-out exits from genuine resignations.
- Team / level / tenure attribution for the concentration read.
Data-source priority
- HRIS offboarding records with reason codes.
- Manager / HR exit-interview notes to confirm the voluntary classification on ambiguous cases.
Edge cases
- Resignation tendered in one period with a last day in the next: count in the period of the effective last day, matching the headcount snapshot.
- Retirement: voluntary by definition (employee-initiated) unless it is a packaged exit tied to a RIF.
- "Quiet" managed-out: if a manager steered the exit, classify as termination regardless of how the paperwork reads — otherwise voluntary turnover is understated and involuntary is hidden.
Validation checks
- Voluntary + involuntary exits should reconcile against the period headcount drop alongside
hr.new_hires. - Converts to
hr.voluntary_turnover_rate(annualized % of average headcount) for benchmarking — the raw count and the rate must use the same exit set. - Concentration (3+ from one team in a quarter, or any executive direct-report) is more diagnostic than the absolute number — surface the pattern.
Common miscomputations
- Logging managed-out / "mutually agreed" exits as voluntary to keep the headline retention number low — the single biggest integrity trap on this KPI.
- Mixing contractor-end events into employee voluntary exits.
- Counting by resignation-notice date instead of effective last day, desynchronizing exits from the headcount snapshot.
Related KPIs
hr.voluntary_turnover_ratehr.at_risk_counthr.retention_initiativeshr.talent_challengeshr.total_headcount
Source
I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Stage relevance
| Company stage | Priority |
|---|---|
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- HR
Machine-readable
- This KPI as JSON:
/api/ontology/hr/voluntary_exits.json - All HR KPIs:
/api/ontology/hr.json - Full catalog:
/api/ontology/index.json
Total Headcount
Total number of employees (W-2 / direct-employment equivalents) across all departments at period end. The base denominator for nearly every other HR ratio — turnover rate, revenue per FTE, payroll as % of burn — so getting the snapshot date and the FTE-vs-headcount convention right matters. CANONICAL HEADCOUNT (#2056): this single KPI carries BOTH the plan and the reported figure via the scenario axis (#2019) — scenario=`budget` is the board-approved headcount plan (formerly the separate, now-deprecated `hr.approved_headcount_budget`), and scenario=`actual` is the reported end-of-period count. Budget-vs-actual variance is read off the two scenarios of this one definition. Common pitfall: mixing headcount (people) with FTE (capacity) — they diverge whenever part-time, contractor, or shared-services arrangements exist. Document the convention (typically "FTE-equivalent, employees only, end-of-period") at the board level once and apply consistently. — HR KPI, I'mBoard-authored (editorial tier).
Voluntary Turnover Rate
Voluntary exits over a trailing period, expressed as an annualized percentage of average headcount — the headline attrition number on the HR scorecard. Anchored to the Mercer US Turnover Survey methodology (Mercer reports voluntary vs involuntary turnover annually). Common pitfall: comparing a single quarter's annualized rate against an annual benchmark — short-window annualization is noisy. Best practice is trailing-12-months for benchmark comparison and trailing-3 or trailing-6 for trend reads. Per #1426: stage-specific industry norms here are folk-wisdom unless tied to a specific Mercer or comparable published cut. — HR KPI anchored to Mercer US Turnover Survey 2025.