Department Planner

What it produces

Standing up or restructuring a department is a high-stakes design problem that most organisations approach informally — a rough sense of the roles needed, a headcount pulled from a comparable company, and reporting lines improvised as people arrive. The Department Planner replaces that with a considered blueprint. It produces the roles the department needs, how many of each, who reports to whom, how many organisational layers that implies, and the span of control at each level — the structural decisions that quietly determine whether a team scales gracefully or collapses into confusion.

Alongside the structure it generates the operational detail that plans usually omit: coverage schedules matched to your operating model, full-time-equivalent ranges rather than single points, and complete job descriptions for every role. And because the right answer depends on appetite and budget, it presents three scenarios — lean, recommended and aggressive — so you can see the trade-off between cost and capability rather than committing to a single guess.

The approach behind it

The planner combines two bodies of knowledge. The first is a structured model of how departments are actually composed — the canonical roles, functions and success metrics for twelve common departments, drawn from how well-run organisations organise these teams. The second is the same workforce-planning logic that underpins the FTE Calculator: headcount is derived from the work and the operating model, adjusted for productivity, shrinkage and coverage requirements, rather than copied from a template.

This is why context matters so much to the output. A customer-service function running standard hours in a small business needs a fundamentally different shape from one running twenty-four-seven at enterprise scale, and industry changes the picture again. The planner scales roles by organisation size, applies an industry staffing factor, and adjusts coverage for your operating hours — so the structure it recommends is fitted to your situation, not a generic org chart with your logo on it.

Reporting lines and layers are inferred with deliberate restraint, following the principle that structure should be as flat as the work allows. Managers are proposed where span of control genuinely requires them, not by reflex, because every unnecessary layer slows decisions and adds cost. The accompanying methodology makes these choices explicit, so you can see why the structure looks the way it does.

How it helps you

It compresses weeks of design work into minutes. Producing a considered department structure with roles, headcount, reporting lines, schedules and job descriptions normally means either an expensive consulting engagement or a lot of internal guesswork. The planner gives you a strong first draft immediately, which you can then refine — a far better starting point than a blank page.

It also makes trade-offs visible. The lean, recommended and aggressive scenarios turn an abstract budgeting argument into a concrete choice: here is what you can deliver with fewer people and where the risk sits, versus what a fuller structure buys you. That clarity leads to better-informed decisions and fewer regretted ones.

And it produces artefacts you can use immediately. The job descriptions can seed real recruitment, the org structure can anchor a leadership discussion, and the methodology gives you the rationale to defend the plan to whoever controls the budget. It is not just advice; it is a set of working documents.

Who it is for

It is made for leaders building a new department or function, for organisations restructuring an existing team, for HR and operations partners designing operating models, and for consultants and founders who need a credible structure quickly without commissioning a full engagement.

Whether you are launching a customer-service operation, scaling a commercial team or reshaping a corporate function, it gives you a defensible starting structure grounded in how similar teams are actually built.