HR Headcount Planning: Making the Case for Another Hire

Why “We’re Stretched” Doesn’t Get Approved
Every team is stretched. When a CFO hears that HR is busy, the natural follow-up is “busy with what, and what happens if we don’t fix it?” If you can’t answer both in concrete terms, the request gets parked.
A strong case answers four questions:
What work is the team doing today, and how much of it?
What will demand look like in 12 months?
What important work isn’t happening, and what’s the cost?
Why is a hire the right fix, rather than a tool, a vendor, or a process change?
The rest of this page builds those answers.
Step 1: Quantify Today’s Load
Run a two-week time log across the People team. Use five tags: admin, policy questions, coaching-shaped questions (feedback, conflict, career), strategic projects, and employee relations cases. A detailed walkthrough is in the HR workload analysis template.
Then summarize it in one table:
Category | Hours per week | Share of team time |
|---|---|---|
Admin | ||
Policy questions | ||
Coaching-shaped questions | ||
Strategic projects | ||
Employee relations |
Leadership will look at the strategic row first. If it’s small, you’ve already shown the problem.
Step 2: Forecast Next Year’s Demand
HR demand scales with a few drivers you can pull from the business plan:
Hiring volume: every hire means sourcing, interviews, offers, onboarding.
New managers: each one generates questions, especially in their first six months.
New locations or countries: compliance, payroll, and policy work multiplies.
Planned programs: a new performance cycle, a comp review, an engagement survey.
Write the drivers down with numbers from the plan, then estimate the hours each one adds. You don’t need precision. You need a defensible direction.
Step 3: Decide What Needs a Person
This is the step most headcount requests skip, and it’s the one that wins credibility. Go back through the time log and sort each category:
Remove: low-value tasks nobody would miss.
Automate: rule-based admin your HRIS or a workflow tool can handle.
Self-serve: policy questions a good knowledge base can answer.
Support at scale: coaching-shaped questions employees and managers can work through with the right support.
Needs a person: strategic work, employee relations, and anything requiring judgment, trust, and context only your team has.
Only the last bucket justifies headcount. If you’ve cleaned up the first four, the number left over is the real gap, and it’s hard to argue with.
The HR Headcount Justification Template
Copy this and fill in the blanks:
Role requested: [title, level, start date]
The gap: Today the People team spends [X] hours/week on strategic and employee relations work, against [Y] hours of demand. Over the next 12 months, [hiring plan / new managers / expansion] will add an estimated [Z] hours/week.
What we’ve already done: We removed [tasks], automated [workflows], moved [questions] to self-serve, and gave employees [support] for coaching-shaped needs. This freed [N] hours/week.
What’s not getting done: [e.g., manager training, comp framework, retention analysis]. The risk is [e.g., regretted attrition in key roles, slow hiring, inconsistent performance reviews].
What this hire will own: [3-5 outcomes, each measurable].
How we’ll know it worked: [metrics and timeline].
Keep it to one page. If you need context on benchmarks, add a single line referencing the HR to employee ratio by company size, but don’t lead with it. Ratios start debates. Specific work ends them.
Related guides:
How Blomma Helps People Teams Plan Headcount
The “support at scale” bucket is where Blomma fits. Blomma gives every employee a private AI career coach for feedback, hard conversations, goals, and career growth. Those questions get answered right away, consistently, at any hour -- and they stop competing with strategic work for your team’s calendar.
That makes your HR staffing plan sharper. You can show leadership that coaching-shaped demand is covered across the company, which means any new hire you bring on goes straight to the work that needs a person. Previsible, for example, rolled Blomma out to its whole team to give everyone a coach grounded in how they work.
