Span of Control: How Many Direct Reports Should a Manager Have?

Narrow versus wide spans

A narrow span means each manager has few direct reports, perhaps three to five. That allows close coaching and oversight but creates more management layers, which makes the organisation taller, slower and more expensive.

A wide span means each manager has many direct reports, perhaps twelve or more. That flattens the organisation and reduces overhead, but each person gets less of their manager's time. Wide spans work when the team is experienced and the work is predictable; they fail when people need frequent guidance.

Is there an ideal number?

There is no universal figure, but many organisations treat five to ten direct reports as a healthy default for knowledge work. Highly standardised frontline roles, such as contact centres or warehouses, often run spans of fifteen to twenty-five supported by team leads. Senior executives typically have narrower spans because each report runs a large, complex function.

Rather than chase a single number, use the factors below to decide what is right for each team.

Factors that change the right span

• Complexity of work: novel, judgement-heavy work needs narrower spans than routine work.
• Experience of the team: seasoned professionals need less supervision than new starters.
• Manager's other duties: a manager who also carries their own targets can handle fewer reports.
• Geography: remote or multi-site teams take more effort to manage than people in one room.
• Tools and process: good documentation, clear goals and self-service systems let spans widen safely.
• Regulation: roles that require frequent sign-off or supervision need narrower spans.

Warning signs on your org chart

Once your chart is drawn, scan it for patterns. A manager with one or two direct reports often signals an unnecessary layer, or a title given for status rather than need. A manager with twenty or more knowledge workers usually signals overload, slow decisions and staff who feel ignored.

Long chains are another clue. If a frontline employee is seven or eight levels from the chief executive in a company of a few hundred people, information is almost certainly getting lost on the way up and down.

How to measure it

Count direct reports for every manager and calculate the average and the spread. The average tells you about overall cost and layering; the outliers tell you where to act first. Also count layers from the top to the furthest frontline role.

An up-to-date org chart makes this a quick exercise. In the dial369 designer each department box lists its line manager and team members, so unusually long or short boxes stand out immediately, and the best-fit layout shows when one level has grown much wider than the rest.

Fixing a span that is too wide

Introduce team leads who handle day-to-day coordination while the manager keeps responsibility for development and appraisals. Alternatively split the team in two along a natural line such as product, customer segment or region. Before adding a layer, check whether better tools or clearer goals would let the existing span work.

Fixing a span that is too narrow

Merge small teams under one manager, or remove a layer by having managers report one level higher. Handle this with care: people whose roles change need a clear explanation and a credible career path, otherwise you lose good managers along with the layer.

Review it regularly

Spans drift as companies hire. A manager who started with six reports can reach fifteen within a year without anyone deciding it should happen. Reviewing your org chart each quarter with span of control in mind catches the drift before it turns into resignations.