How is skills-based workforce planning different from headcount planning?

Headcount planning counts seats by job title. Skills-based planning counts capability by skill and level, so it can tell you that every seat is filled and the work still cannot be done.

What time horizon should a workforce plan cover?

Two. The next 12 months, where the answer is mostly development and redeployment, and the next two to three years, where hiring and structural change have time to land.

Who owns workforce planning?

HR or a people analytics team usually runs the process, but demand comes from operations and supply comes from managers who assess. Without both inputs the plan forecasts headcount, not capability.

Do we need an assessed inventory before we can plan?

Yes. Planning against self-declared or title-inferred skills produces a plan built on estimates. A first assessment cycle for the roles in scope is the prerequisite.

How does workforce planning connect to learning?

Every build decision is a development plan with a target level and a date. Learning that is not tied to a named gap in the plan is spend, not planning.

Learn · Talent

Workforce Planning

Workforce planning is the discipline of comparing the capability an organization has against the capability its strategy will require, by role, location, and time, and deciding how to close the difference by building, buying, borrowing, or redeploying.

By Samantha, SkillsDB|Published Aug 17, 2026|Updated Sep 18, 2026

What It Is

Workforce planning began as headcount arithmetic: how many people, in which jobs, at what cost, next year. That version still runs in most finance and HR teams, and it fails at the moment it matters, because a headcount says nothing about whether the people counted can do the work the plan assumes. Skills-based workforce planning changes the unit from positions to capabilities. Demand is expressed as roles with required skills at required levels, multiplied by how many of each role a site, shift, or initiative needs. Supply is the assessed inventory: who holds those skills today, at what level, and where. The plan is the difference, read across the organization's own dimensions, and each shortfall gets a decision: develop the people who are close, hire where nobody is, redeploy where a skill is deep in one place and absent in another. The plan is only as good as the inventory beneath it, which is why assessment comes first.

Key Facts

Demand is a set of role profiles times the required count of each role, per location and period; a headcount figure alone is not a demand statement.
Supply is the assessed skills inventory, not the HRIS job title, which describes a seat rather than a capability.
The unit of a gap is a skill at a level in a place: eight technicians below level 3 on chiller operations at one site, not "short four FTE."
Every gap resolves to one of four moves: build (develop), buy (hire), borrow (contract), or redeploy (move capability that exists elsewhere).
Organizational dimensions such as division, department, region, site, and shift are what let the same data answer different planning questions.
Plans decay with their data: an inventory last assessed more than a year ago describes a workforce that no longer exists.

The Four Planning Questions and the Data Each Needs

Question	Data required	Output
What can we do today?	Assessed skills inventory, filterable by division, department, region, and site	Capability map: depth and coverage per skill
What will we need?	Role profiles with required levels, and the count of each role per site and period	A demand statement in skills, not seats
Where are the gaps?	Supply compared to demand, skill by skill, along each dimension	Ranked shortfalls: how many people, how far below, and where
What do we do about each one?	Gap size, time available, and internal candidates near the required level	A build, buy, borrow, or redeploy decision with a date

How SkillsDB Models It

In SkillsDB demand is written into Careers, supply is the graded record, and planning is the comparison across the organization's dimensions. Take a Data Center Technician career with a Level 2 benchmark of 3 on Electrical Systems, assigned to 60 people across three sites. An administrator opens Company → Careers → Skills Matrix and filters by Department, Division, or Region, then applies the Below Target filter: the grid returns the 14 technicians whose manager grade is below 3, and switching to the Bar Chart view shows the average grade per skill. A regional manager sees the same picture in My Team Skills → Career Overview, where Meets Target and Below Target percentages, Total Skills, and Skills w/ Training appear for their org, and can export the matrix to Excel for the headcount plan. SkillsDB does not forecast; it tells you, by site and role, how many people are short and by how much. See Workforce Strategy and the Workforce Strategy feature.

Read the full guide

Workforce Planning Needs Skills Data, Not Just Headcount

Skills Gap Analysis

the calculation under every shortfall

Skills Inventory

the supply side, and why assessed beats declared

Job Roles and Job Architecture

how demand is expressed as roles

Succession Planning

workforce planning for one critical role at a time

Workforce Strategy

how customers run it in SkillsDB