Span of control and layers: how many reports is right?
The number of direct reports and the number of layers pull against each other. See the trade-off in numbers, then read your own chart with a simple method.
Get a DemoAll guide partsSpan and layers in one minute
Span of control is the number of people who report directly to a manager. A layer is a level between the top and the front line. The two move against each other: widen the span and you need fewer layers; narrow it and the chain gets longer.
The trade-off, with numbers
Take 120 people. The chart below shows the least number of managers and layers you need at four different spans. These are idealized minimums, but they make the point: going from a span of 4 to a span of 12 removes twenty management roles and two layers.
Fewer layers usually means faster decisions and less overhead. A wider span also means each manager has less time per person. Neither is better in itself. What matters is whether the span fits the work.
What pushes the right number up or down
- Type of work. Routine, similar jobs can be supervised in wider spans than complex, varied ones.
- Experience of the team. Experienced teams need less direction.
- The manager’s own work. A manager who also carries a full workload has less time to lead.
- Distance. Teams in several time zones are harder to supervise.
Reading your own data
Skip the search for a magic number. Use span as a prompt to look closer. A simple method:
- List every manager with their number of direct reports.
- Flag the extremes, for example fewer than three reports or more than twelve. Pick your own limits.
- For each flagged manager, ask one question: is there a reason? A new team, a specialist, a seasonal peak are reasons. “It has always been like this” is not.
- Look at the same numbers by unit. A pattern in one department tells you more than a single outlier.
| What you see | What to check |
|---|---|
| A manager with one or two reports | Is this layer needed, or could the team report one level up? |
| A manager with a very wide span | Is the work routine enough? Would team leads help? |
| A long chain of single reports | Which decisions have to climb the whole chain? |
| Wide differences between similar units | Is the gap in the work, or only in how the units were built? |
Pitfalls when counting
- Vacancies. Decide whether an empty position counts toward the span, and apply the rule everywhere.
- Dotted lines. If your structure has matrix reporting, say which line your numbers use.
- Working time. Three half-time people are less work to lead than three full-time people. Look at FTE as well as heads (see Part 3).
- Titles. A “manager” with no reports is a senior specialist. Do not let the title decide.
How this looks in OrgChart Agile
- Span of control and hierarchy level are calculated from the data you load, so you do not count by hand.
- The KPI panel next to the chart shows direct reports, total reports and structure depth for the branch you are looking at.
- In the pivot you can use span of control as a field and break it down by unit. See Org chart analytics.
Questions people ask
What is a good span of control?
There is no single number. It depends on the work, the team and the manager’s other duties. Use a working band to flag cases worth a look, and decide case by case.
Is a wider span always cheaper?
It needs fewer managers, but a manager stretched too far costs you in slower feedback and slower decisions. Look at the whole picture, not only the number of management roles.
How do I count span with matrix reporting?
Choose one line, usually the line that owns performance and pay, and count only that. State the rule next to the number.
Continue the guide
Read span from your own data
Request a free trial and see span of control, structure depth and team size for your organization.
Request a free trial