How to model workforce planning in SAP Analytics Cloud

Workforce planning is a perfect fit for SAP Analytics Cloud Planning: it needs data entry, several versions, and a clean separation between people you have and people you plan to hire. Done in a spreadsheet it breaks every reorg; done as a SAC model it survives them. Here is how to structure it.

Analytics or Planning?

If managers will enter figures — hiring requests, attrition assumptions, budgeted FTE — this is a Planning model, not Analytics. That gives you data entry, the Version dimension and Data Actions. Our guide on the Analytics vs Planning difference covers the one-question test.

Headcount is a stock, hires and leavers are flows

This is the modelling crux. Headcount and FTE are stocks — a level at a point in time. Across the time dimension they must use a LAST aggregation, or your year-end headcount sums twelve months and reads twelve times too high. Hires and leavers are flows — they sum. Getting this split right is the difference between a plan that reconciles and one that doesn't; see the time-dimension aggregation exception.

Dimensions

Model a Department dimension, a Job family or grade, a Location, the mandatory time dimension and the Version dimension. This lets you drill from total FTE down to the team and grade driving a gap, and compare plan against actual.

The hiring plan and attrition

Opening headcount, plus planned hires, minus expected leavers (attrition), gives closing headcount — a movement structure exactly like a financial roll-forward. Model attrition as a rate applied to headcount, and let managers enter the hiring plan by month. The FTE gap (target minus projected) falls out as a calculated measure.

Payroll forecast with Data Actions

Once FTE is planned, payroll follows: average cost per grade times planned FTE. A driver-based Data Action computes and spreads it across months, and re-runs instantly when the hiring plan changes — no re-keying.

Versions for scenarios

Hold Actual, Budget and a re-estimated Forecast side by side using the Version dimension, and run an optimistic and a conservative attrition scenario to see the FTE and payroll impact before you commit.

Start faster

The Workforce Planning template ships with this structure — headcount on LAST, flows on SUM, a Version dimension and a payroll driver. Browse more HR templates or build your own with the generator.