Workforce
Headcount and budget, planned in the same place
There is a familiar gap between the way HR talks about growth and the way finance does. HR counts people: we need two more engineers and a coordinator. Finance counts money: what does that do to the run rate, and can we carry it to year end? Both are describing the same plan, and yet they usually describe it in two separate documents that never quite reconcile. Every workforce planning problem starts there - in the space between a headcount list and a budget.
A workforce plan closes that gap by holding both facts on the same line. Each row is a department and a role, with the headcount you have now and the headcount you intend to have, and beside them the salary cost of each. Do that consistently and the plan stops being a wish list and becomes a costed proposal - the version finance can actually sign.
Open roles are a calculation, not a guess
The first thing the two-column discipline gives you is your true hiring demand, computed. Open roles for any line are simply planned headcount minus current, floored at zero so a team you are shrinking does not show as negative recruitment. Sum that column and you have the number of vacancies the business is actually committed to funding - not the number people remember being discussed, which is always higher and always vaguer.
Keeping open roles as a live calculation rather than a typed figure matters because plans move. A role gets filled, a team gets re-shaped, a hire gets deferred. If the open-roles number is derived from the headcount you have and the headcount you planned, it corrects itself the moment either changes. If it is a number someone typed in March, it is wrong by April and nobody notices.
The figure finance asks for first
The headcount conversation is the easy half. The question that decides whether a plan survives is the money one: what is the total salary budget, and how far does it move from where we are today? Cost the current establishment, cost the planned one, and the variance between them is the number a budget-holder wants before they will discuss anything else. Present a plan without it and you will be sent away to produce it; present it with the variance already worked out and you are having a different, faster conversation.
Finance does not trust a headcount list. It trusts a headcount list that has already told it what the headcount costs.
This is where a plan built as a live workbook pulls ahead of one built in a slide. When each row carries its own cost, the total salary budget and the variance against today roll up on their own, and they stay right when you change a single role. A slide showing the same numbers is correct only at the instant it was made; the moment the plan is revised, someone has to remember to update the total, and eventually someone forgets.
Roll it up onto one page
The plan should end where it will be read: on a single dashboard. Current and planned headcount, net change, open roles, the total salary budget and the budget-versus-current variance - the whole workforce story on one page, with the detail beneath it for anyone who wants to interrogate a line. Add a simple status per line - growing, flat, reducing - and the shape of the plan is legible at a glance before anyone reads a single figure.
None of this is complicated, but it is the difference between a plan that gets approved and one that gets queried. Give a budget-holder a page that already answers "how many, and what does it cost" and you have removed the two questions that stall most workforce discussions. And because it is one file rather than an HR document plus a finance model, there is only one version of the truth to keep current - which is, in the end, the only version anyone trusts.
A plan finance will trust
Computed open roles, total salary budget and budget-versus-current variance, rolled up with native headcount and cost charts - and a fully worked example. A planning tool, not HR or finance advice.