Workforce Planning vs Position Management Explained

Workforce planning and position management are not rivals. Workforce planning decides how many people, which skills and what cost your organisation needs over time. Position management defines, approves and tracks the individual positions that carry that plan into the organisation. The plan sets the envelope. Positions are how you stay inside it.

If you only remember one thing: planning is the strategy layer, and position management is a control layer underneath it. You can run one without the other, but the figures tend to drift apart when you do.

The short answer

What is workforce planning?

Strategic horizon and the CIPD view

The CIPD defines workforce planning as "a core business process which aligns changing organisation needs with people strategy". Its guidance describes strategic workforce planning on a three-to-five-year horizon, with a six-stage framework and seven "rights": people, skills, roles, shape, place, time and cost.

That is a long view. It looks at what the organisation is trying to do and what workforce it will need to do it.

What it answers: how many, which skills, what cost

In practice, a workforce plan answers three questions:

• How many people do we need, in which teams and locations?
• Which skills and roles will we need more or less of?
• What will that cost, and can we afford it?

It is also separate from workforce management. Dayforce describes planning as the strategy layer, with workforce management executing it day to day through scheduling, tracking and deployment. Position management sits in neither of those buckets. It is the governance of the roles themselves.

What is position management?

Positions vs employees

Position management is the practice of defining, tracking and controlling distinct positions rather than only employees. Positions stay in the system whether filled or vacant, so headcount and approvals are auditable.

That is the key shift. In a people-first model, a role disappears from view when its holder leaves. In a position-first model, the role remains, and the organisation decides what to do with it.

Position control vs position management

The two terms are often used interchangeably, and vendors blur them. Infisoft notes this, and offers one common split: position control is Finance-owned budget authority, while position management is HR-owned org structure.

Oracle's documentation defines position control as the creation, maintenance and monitoring of positions and their budgets. Whatever your vendor calls it, check what the system actually enforces: structure, budget, or both.

Position lifecycle: create, approve, fill, vacate, close

A position moves through a simple lifecycle:

1. Create: a manager requests a new position.
2. Approve: Finance and HR confirm it fits the plan and budget.
3. Fill: recruitment finds someone for the approved position.
4. Vacate: the employee leaves, but the position remains.
5. Close or refill: the team decides whether to refill, change or eliminate it.

FTE Tree gives a simple example: a 1.0 FTE position with a $70,000 budget rate carries $70,000 of approved capacity. When the employee leaves, that capacity stays attached to the position until someone decides otherwise.

A typical position management system includes approval workflows, headcount and cost tracking, audit trails, role-based access and payroll or recruitment integration.

Workforce planning vs position management: key differences

Scope and time horizon

Workforce planning looks forward. It covers the budget year and often several years beyond, and it deals with scenarios and assumptions. Position management works at the level of the current organisation. It records what has been approved now and what has changed since.

Unit of analysis

A plan line might say "Customer Operations: 10 FTE, average cost of 48,000 per FTE". A position record says "Position CO-0147, 1.0 FTE, approved, vacant since March". One describes capacity in aggregate. The other describes a specific seat.

Ownership

Ownership is where organisations most often go wrong. Planning needs Finance, HR and business leaders working on the same figures. Position management usually splits: HR looks after structure and job definitions, and Finance holds budget authority. If each group keeps its own spreadsheet, you get three versions of headcount.

Outputs

• Workforce planning produces: an agreed headcount and cost plan, scenarios, and a view of skills and capacity needs.
• Position management produces: a register of approved positions, status for each, approval history and an audit trail.

How they work together

From plan to approved positions

The plan sets the approved envelope. Position management turns that envelope into specific, controlled positions. A position should only be created if it fits inside the plan, and the approval step is where that check happens.

From positions to hiring and actuals

Once a position is approved, recruitment can start. When someone is hired, actual cost flows against the position. Comparing actuals with the plan then shows variance: where you are over, under or simply behind on hiring. Position data makes that comparison traceable rather than approximate.

The workflow in short: plan, approve positions, recruit, then reconcile actuals to plan.

Worked example

Suppose the plan for Customer Operations in the next financial year includes 10 FTE, at an average cost of £48,000 each. That is a £480,000 envelope.

1. The plan is approved at 10 FTE and £480,000.
2. Ten positions are created, each at 1.0 FTE with a budget rate of £48,000.
3. Seven are filled in the first quarter. Three stay open.
4. One employee leaves. The position stays, and the team decides to refill it.
5. Each month, actual cost is compared with the £480,000 envelope, and open positions show the remaining capacity.

If a manager asks for an eleventh position, the request fails the check. It is outside the approved plan, so it needs a plan change, not a quiet addition.

This is the kind of plan-to-position governance Kivos is built for. The planning features hold the financially governed plan, and approvals control changes against it, so Business, Finance and HR see the same figures.

Common problems when they are disconnected

Spreadsheet drift. The plan lives in one file and the position list in another. Within a quarter they disagree, and nobody can say which is right.

Positions approved outside the plan. Without a link between the two, a position can be created that the plan never funded.

Plans that stop at budget time. Visier argues that position-based plans work at budgeting but fall apart in-year when positions change. It recommends plan-to-actuals comparison and continuous planning. Visier is promoting an alternative approach, so read it with that in mind, but the criticism has a fair point. A static list of positions is not a plan.

The answer is not to drop positions. It is to keep the plan live and compare actuals against it regularly, so position changes show up as plan variance, not as a surprise.

Separate systems for HR and Finance. When each function uses its own tool, reconciliation becomes a manual job. A shared plan removes much of that work. For a related distinction, see workforce planning vs headcount planning.

Do you need both? Position, job or headcount-based models

Not every organisation needs full position control. The choice depends on how sensitive your budget is and how much audit detail you need.

In Workday, position management suits roles with higher budget sensitivity, compliance needs and reporting granularity. Job management can serve other organisations, and both can coexist. That mixed approach is common: tight control where cost and compliance matter, lighter control elsewhere.

Whatever the model, you still need a plan. Position management without planning controls seats but has no view of whether they are the right ones.

Implementation checklist

• Agree one set of definitions for position, FTE, headcount and vacancy.
• Decide who owns what: Finance for budget authority, HR for structure, business leaders for demand.
• Set the plan as the approved envelope and require positions to fit within it.
• Define the position lifecycle and who approves each step.
• Decide how vacated positions are handled: refill, change or close.
• Compare actuals with plan on a fixed cycle, not only at budget time.
• Check access control, audit trail and data location with IT before rollout. Kivos publishes its approach in its Trust Center.
• Start with the roles where cost and compliance risk are highest, then widen.

See one plan across your organisation

When the plan and the positions share one set of figures, approvals become a check instead of an argument. If you want to see how Business, Finance and HR can work from one governed plan, see Kivos for your leaders.

Frequently asked questions

Is position management part of workforce planning?

It is closely linked but not the same thing. Workforce planning sets how many people, which skills and what cost you need. Position management controls the individual roles that put that plan into practice, so it works best as the control layer beneath the plan.

What is the difference between position management and position control?

The terms are often used interchangeably, and vendors blur them. One common view is that position control is Finance-owned budget authority, while position management is HR-owned organisation structure. Check what your system actually enforces.

What happens to a position when an employee leaves?

The position stays in the system, along with its approved budget. The team then decides whether to refill it, change it or eliminate it. This keeps headcount and approvals auditable.

What is the difference between workforce planning and workforce management?

Workforce planning is the strategy layer. Workforce management carries it out day to day through scheduling, tracking and deployment. Position management is a separate control on which roles are approved.

Who owns position management, HR or Finance?

Usually both. HR tends to own structure and job definitions, while Finance holds budget authority. Problems start when each keeps separate figures, so agree one shared set of numbers.