Building a planning function: roles, structure and first hires

Leadership · ~6 minute read

The function that grows by accident

Plenty of planning teams were never designed; they accreted. One analyst started doing the forecast, then picked up the schedule, then got dragged into real-time, then someone asked for an MI pack — and now a single overloaded person holds the whole operation together with spreadsheets and goodwill. That works until it doesn’t. Building a planning function on purpose — deciding which roles exist, how they’re structured, and in what order to hire — is one of the highest-return things an operations leader can do, because the function that schedules everyone else is usually the worst-planned team in the building.

The roles, and the order they arrive

There are five core jobs, and they have genuinely different rhythms. Forecasting looks weeks-to-months ahead and rewards analytical depth. Scheduling turns the forecast into rosters and lives in the medium term. Real-time runs the day and needs a completely different temperament — fast, calm, decisive. MI and reporting turns activity into insight. Capacity and long-term planning owns the hiring and budget horizon. In a small operation one capable generalist does all five, and that’s fine. As you grow, the first split is almost always to carve real-time out, because its rhythm is so different that asking the same person to forecast next quarter and firefight this afternoon means one of those jobs is always being neglected. After that, specialise forecasting and scheduling, then MI, then a capacity lead — roughly in that order, as volume and complexity justify each hire.

The order to build the team 1. Generalist 2. Split out real-time 3. Forecasting + scheduling 4. MI 5. Capacity lead Specialise as volume justifies it — real-time comes out first, every time.
You don’t need all five roles on day one. You need them in the right order — and real-time is almost always the first to deserve its own person.

Structure and the credibility question

Two structural choices shape how much the function is trusted. The first is centralised versus embedded: a central team is consistent and efficient but can feel remote; embedded planners are close to the operation but drift apart in method. Most mature functions centralise the craft and embed the relationships. The second, and more important, is the reporting line. A planning function that reports into the operation it sizes is under quiet pressure to tell that operation what it wants to hear; one with a degree of independence — reporting alongside operations, or with a dotted line to finance — can hold the unwelcome number, and that independence is the root of its credibility. Build the team in the right order, give it a line that lets it tell the truth, and you turn planning from an overloaded spreadsheet into the function the whole operation runs on.

Pair this with planning credibility, the planning operating rhythm, and the planning career ladder.