Cost Per Hire vs. Headcount Planning: Cost Average and Staffing Scenario Compared

One metric reconciles cost; the other documents a scenario

Cost per hire divides included internal and external recruitment costs by included hires from the same defined period. The counted-hire event, cost classifications, currency, allocation rules, and exclusions must be documented before comparing teams or periods.

The headcount scenario adds approved growth roles and approved one-for-one backfills to show gross planned hires. End-state headcount increases only for growth roles. The advanced worksheet applies one entered average base salary, load percentage, horizon, common vacancy lag, and internal discussion scores.

The sequence depends on the documented question

If the question is how a known recruitment-cost pool averaged across a completed counted-hire cohort, start with cost per hire. If the question is how approved growth and approved backfill assumptions combine in a proposed plan, start with the headcount scenario.

Do not use cost per hire to decide how many roles are needed. Do not use the headcount scenario as a demand forecast, committed budget, recruiter-capacity model, or validated prioritization method.

Joining the outputs requires additional records

A recruiting budget scenario can multiply a scope-aligned cost-per-hire assumption by planned hires only when finance accepts the cost definition and its behavior at the proposed volume. HR Hub's cost-per-hire volume sensitivity deliberately holds total entered cost constant and is not such a forecast.

Role-level salary, employer load, timing, sourcing model, vacancy status, internal movement, contractor use, approval status, and recruiting capacity require separate records. Reconcile these before using either output in a budget or hiring decision.

Method, scope, and sources

Cost per hire = included internal plus external recruitment costs ÷ included hires from the same defined period. The compact view accepts aggregate internal and external totals. The advanced workspace itemizes user-classified cost categories and shows constant-total-cost volume sensitivities; those sensitivities are not forecasts or efficiency rankings.

Define the measurement period, counted-hire event, cohort, currency, source records, allocation rules, and exclusions. Internal/external classification is organization-defined. Exclude or separately govern post-hire, onboarding, ramp-up, vacancy, and unfilled-position costs. Zero included hires makes the metric unavailable, and comparisons require aligned definitions.

Method status: Supported.

Worked example

Hypothetical: documented internal recruitment costs are $18,000 and external costs are $12,000 for 10 included hires whose counted event falls in the same quarter. Cost per hire = $30,000 ÷ 10 = $3,000. A 20-hire sensitivity holding the same $30,000 total constant would show $1,500, but it is not a forecast that costs remain fixed.

Sources

• BSI Standards / ISO, via ANSI webstore — PD ISO/TS 30407:2017 — Human resource management — Cost-Per-Hire: Directly defines CPH as average total recruitment costs divided by number of hires; distinguishes CPH Internal and CPH Comparable; requires transparent data and formula disclosure; and excludes post-hire and unfilled-position costs.
• International Organization for Standardization — ISO/TS 30407:2017 Human resource management — Cost-Per-Hire: Confirms the specification remains current after 2024 review and supports representative data, transparent sources, error minimization, process audit, and transparent display.
• Chartered Institute of Personnel and Development — Resourcing and talent planning report 2024: Provides practical examples such as in-house resourcing time, advertising, and agency/search fees, and cautions that estimates differ when organizations include different costs.

Method, scope, and sources

Gross planned hires = planned growth roles + approved one-for-one backfills. Illustrative end-state headcount = current headcount + planned growth roles. The advanced workspace also applies one average base salary, user-entered salary-load percentage, quarter-based horizon, and common vacancy lag, plus a publisher-defined 1–5 internal discussion score.

This is an organization-defined planning scenario, not a demand forecast, committed budget, capacity diagnosis, approval decision, or validated prioritization method. Define the fiscal horizon, population, positions versus people/FTE, backfill approval, role timing, salary basis, and load inclusions. The common-lag amount and priority score require role-level review.

Method status: Publisher-defined.

Worked example

Hypothetical advanced scenario: current headcount is 48, with 12 approved growth roles and five approved one-for-one backfills. Gross planned hires = 17 and illustrative end-state headcount = 60. Any salary-and-load amount applies one entered average and timing assumption to all 17 hires; the result is not a committed budget.

Sources

• Chartered Institute of Personnel and Development — Workforce planning: Defines workforce planning as balancing labor supply/skills and demand/numbers, identifying gaps, and linking to strategy; explicitly says no single formula yields a correct workforce plan.
• U.S. Office of Personnel Management — Workforce Planning Guide: Supports analyzing future staffing requirements and comparing workforce supply after separations with future needs, rather than prescribing this calculator formula.
• U.S. Bureau of Labor Statistics — Employer Costs for Employee Compensation: Overview: Supports a narrow base-salary label because employer compensation also includes benefits and legally required costs.