A day in the life of a workforce planner

Forecasting · A day in the life · ~7 minute read

Planner job descriptions talk about forecasts, schedules, and Erlang. They miss most of the actual job — which is judgement, translation, and the disciplined refusal to staff something the operation hasn’t yet agreed to do. Here’s what a real week actually looks like.

7:15am — the dashboard check

Open the WFM. Read yesterday’s actuals against forecast. Service level, abandonment, AHT, shrinkage. Anything more than ~5% off? Note it for the 9am stand-up. The planner who reads this with care catches forecast drift weeks before it becomes a board paper.

A specific routine: read the variance, write a one-line cause hypothesis, log it. By month-end you have 20 data points and a clearer view of whether the model needs re-calibrating or yesterday was genuinely an outlier.

9:00am — ops stand-up

Five minutes per function. Planning reports yesterday’s variance, today’s forecast, anything unusual. The honest version is short; the version that defends bad numbers is long.

The discipline: report variance even when it’s your forecast that was wrong. Operations leaders learn quickly whose numbers to trust based on how the planner handles being wrong, not on how good the forecasts are.

11:00am — the marketing meeting that wasn’t on your calendar

Marketing has decided to run a campaign Friday. It wasn’t in the plan. They want service level held. The marketing manager is friendly and apologetic; they want a yes.

The disciplined planner: calculates honestly. If staffing can absorb, says yes with the trade-off named. If it can’t, says no with the alternative offered (later go-live, smaller scale, accept the SL hit). The planner who always says yes ends up running an operation that’s under-served and resented; the one who always says no ends up cut out of the conversation. The middle is the discipline.

14:00 — building the next-quarter forecast

Two hours of model work. Refresh history, fit the seasonal pattern, layer the known drivers (campaigns, product launches, weather), run sensitivity, write the assumptions document.

The temptation is to skip the assumptions document. Don’t. In three months when someone asks why the forecast missed, the document is the only defence against blame — and the only honest record of what the planner believed at the time.

16:30 — the finance challenge

The finance partner has reviewed the headcount business case. They want it cheaper. Specifically, they want the shrinkage assumption dropped from 32% to 28%.

The planner’s job: defend the number with evidence, not with seniority. Pull the actual 12-month shrinkage data. Show the components. Negotiate where there’s genuine discretion (planned holiday distribution, training schedule) and hold the line where there isn’t (sickness, statutory). The planner who folds gets staffed at fiction; the one who defends with data earns the next conversation.

The planner’s day — the real shape What’s on the calendar ▸ Dashboard check ▸ Ops stand-up ▸ Forecast review ▸ Schedule publication ▸ Finance / business case ▸ WFM data work What actually consumes time ▸ Translating between vocabularies ▸ Defending numbers honestly ▸ Saying no calibrated, not absolute ▸ Documenting assumptions ▸ Reading drift before it’s a board paper ▸ The unscheduled marketing meeting Forecasting is the visible craft; translation is the actual job

The honest planner’s discipline

The planner’s actual job is translation, judgement, and the disciplined refusal to staff fiction. The forecasts and the schedules are visible; the conversations that get the operation to a plan it can deliver are the work. Most planners aren’t trained for that part — but it’s the part that decides whether the operation respects planning or talks around it.

See also