Span of control calculator: managers, reports and layers

How span of control is calculated

A manager’s span is simply the number of people who report to them directly, not the people further down the chain. The average span of a group of managers is the total number of direct reports divided by the number of managers.

If you only know the size of the organisation, use the fact that everyone except the person at the top reports to exactly one manager. That gives the average span from two numbers. The layer estimate asks how many levels a full hierarchy of that span needs to hold everyone; the result is rounded up to whole layers.

Worked example

Five managers have 6, 8, 4, 2 and 12 direct reports.

Average span = (6 + 8 + 4 + 2 + 12) ÷ 5 = 32 ÷ 5 = 6.4. The median, the middle value of 2, 4, 6, 8 and 12, is 6. Riley (2) is below the narrow threshold of 3 and Sam (12) is above the wide threshold of 10.

If the list covers every manager, the organisation has 32 + 1 = 33 people. A full hierarchy with a span of 6.4 needs about log base 6.4 of (33 × 5.4 + 1) ≈ 2.8 levels, which rounds up to 3 layers.

With only totals, 85 people and 21 managers give (85 − 1) ÷ 21 = 4. Because 1 + 4 + 16 + 64 = 85, that is exactly 4 layers.

What is a good span of control?

There is no single right number. How many direct reports a manager can lead well depends on how complex and varied the work is, how experienced the team is, how much of the manager’s week goes to their own tasks, and how much support they have, such as a deputy, an assistant or clear processes.

These are widely quoted rules of thumb. Treat them as starting points for a conversation, not as research findings:

• Senior leaders whose reports each run a whole function: often around 4 to 8 direct reports, because every report brings a large area and a lot of coordination.
• Middle managers coordinating specialists: commonly 5 to 10.
• Leads of similar, routine work such as support or production: 10 to 15 or more can work when tasks are standardised and people need little supervision.
• Player-coaches who still do hands-on work: usually fewer, because their own tasks take up part of the week.

Narrow vs wide spans: the trade-offs

The calculator flags a span under 3 as narrow and one over 10 as wide. Those cut-offs are conventions, not laws, and a flag is a prompt to look closer, not a verdict.

• Narrow spans give close coaching and quick feedback. The price is more managers, more layers, higher management cost and a risk of micromanagement.
• Wide spans mean fewer layers, faster information flow and more autonomy. The price is less time per person, thin coaching and a manager who becomes a bottleneck for decisions and one-to-ones.
• A narrow span is sensible for a new team, new hires or high-risk work. A wide span suits experienced people doing similar tasks.

Layers and how to reduce them

Span and layers are two sides of one equation. For a given headcount, a larger average span means fewer layers: 85 people need four layers at a span of 4, but only three at a span of 9, because 1 + 9 + 81 = 91 covers everyone.

Each layer a message passes through costs time and can distort it, which is why organisations that want faster decisions look at layers first. Before you remove one, check where the narrow spans are. Merging two managers who each lead two people is usually easier than stretching a manager who already leads twelve.

Typical ways to flatten a hierarchy are to merge small teams under one lead, to turn a pure coordination role into a working lead, to widen spans where work is standardised, and to remove a deputy layer that only forwards decisions.

Counting direct reports correctly

Most disagreements about span come from how people are counted. Agree the rules once and apply them everywhere:

• Count people who report to the manager on the solid line. Dotted-line relationships and project leads usually do not count.
• Count part-time staff as people. If capacity matters more than heads, work out the FTE of the team as well.
• Leave open positions out unless the manager is already recruiting and spending time on them, and note them separately.
• Decide once how to treat contractors and interns, and keep the rule the same across teams.
• If a manager role is vacant, count the person who is acting in it.