Span of Control Benchmarks for Managers in Growing Companies

What are the best span of control benchmarks for growing companies?

For growing companies, the practical span of control benchmark is a range, not a target painted on the wall: about 5 to 12 direct reports for many office teams, 6 to 15 in OpsDog’s HR benchmark guidance, and lower spans for complex expert work. Start with the benchmark, then test it against manager workload, team maturity, and layers.

The spread is the lesson. Gallup reported an average span of 12.1 in 2025, up from 10.9 in 2024, but also found that 66% of managers lead fewer than 10 people and 37% lead fewer than 5. Averages get pulled upward by very large frontline teams.

A useful benchmark does not tell a founder, HR leader, or finance head to chase one span of control ratio. It helps them ask sharper questions: where are we over-managed, where are managers drowning, and where is a narrow span justified because the work is genuinely hard?

What is span of control, and how is it different from layers?

Span of control is the number of direct reports a manager oversees, as Pave defines it. It is not the same as organizational layers, which count reporting levels from the CEO down. It is also not indirect reports, which include people below a manager's direct team. A director can have a small direct span and a much larger indirect scope.

That distinction matters during growth. One company can flatten layers while still leaving managers with too few reports. Another can widen spans while adding extra layers between employees and decision-makers. Those choices change speed, cost, and accountability in different ways.

Use span of control for manager load. Use layer analysis for hierarchy. Use managerial density for cost and shape. For a deeper operating view of reporting lines, role clarity, and management layers, see our org design guide.

The terms leaders mix up

• Direct span: the number of employees who report directly to one manager.
• Average span: total direct reports divided by managers with at least one direct report, or the mean of manager-level spans depending on the method you choose.
• Median span: the midpoint manager span. Gallup's 2025 research shows why this matters: the U.S. average was 12.1, but the median was only about 5 to 6.
• IC-to-manager ratio: individual contributors divided by people managers. Use it to spot top-heavy design.
• Managerial density: the share of employees in management roles. Pave’s tech-company benchmark analysis found a typical company at 77% individual contributors and 22% management.

How do you calculate span of control from HRIS data?

Calculate span of control by dividing direct reports or subordinate FTE by the number of managers. OpsDog defines the HR KPI formula as direct reports divided by managers, and The OrgChart guide gives the standard formula as subordinates divided by managers. Before running the report, define the population: active employees, FTE-weighted employees, contractors, interim managers, vacant positions, and managers with zero reports. Then segment the results, because one blended average hides overload and duplicated supervision.

1. Freeze the population. Decide whether the analysis includes only active employees or also contractors, interns, contingent workers, people on leave, and accepted hires in vacant or reserved seats.
2. Validate reporting lines. Every employee should have one current manager, and every manager title should either have reports or be flagged for review.
3. Choose the denominator. Umbrex span-of-control guidance recommends both unweighted manager spans and FTE-weighted spans, calculated as total direct-report FTE divided by managers with at least one direct report.
4. Calculate average and median span. The average helps with cost modeling. The median shows the typical manager experience and avoids distortion from large frontline teams.
5. Add P10 and P90 dispersion. A healthy company can have different spans by function, but extreme spread often reveals accidental org design.
6. Calculate IC-to-manager ratio and managerial density. Compare management share against stage and function, not against a generic company-wide target.
7. Measure layers from the CEO. Pair span analysis with layer count because narrow spans plus many layers create slow decisions and duplicated escalation.
8. Segment by function, level, site, geography, and work arrangement. Remote teams, regulated sites, and new teams can require more manager attention than a single blended average suggests.

The cleanest reports come from a maintained org chart, not a spreadsheet rebuilt the night before a board meeting. If your company still uses disconnected sheets, our org chart template for small business gives a practical structure for reporting lines, roles, and approval paths.

What does each span bucket usually signal?

Span buckets are a fast screen for organizational health. Umbrex flags spans of 1 to 3 as micro-teams and spans of 15 or more as potential overload. A span of 4 to 7 can fit complex teams. A span of 8 to 12 is often scalable. Spans of 13 to 15 or more need workload review.

This is where averages lie by omission. A company with an average span of 7 can still have five managers with one report and three managers with 18. The average looks sane. The org feels broken.

Why do benchmarks differ by function, level, and company stage?

Benchmarks differ because manager work is not uniform. A frontline supervisor running standardized shifts can often support more direct reports than an engineering manager coaching specialists through ambiguous work. Seniority, team tenure, geography, risk, performance distribution, and whether the manager still owns IC deliverables all change the right number of direct reports.

Function changes the job of management

In standardized operations, the manager's job is cadence, schedule coverage, quality checks, and escalation. Wider spans can work if the rules are visible and exceptions are rare. In HR, finance, legal, clinical, engineering, or design-heavy roles, the manager may be reviewing judgment, risk, performance, stakeholder tradeoffs, and career growth. That takes time.

This is why OpsDog’s HR benchmark guidance can say 6 to 15 while Pave’s tech-company compensation data shows Manager and Senior Manager roles averaging 4.9 direct reports. Neither number is wrong. They are measuring different work contexts.

Level changes the shape of the span

First-line managers usually carry the heaviest people-management load because they coach, assign work, approve exceptions, and handle performance issues directly. Directors may have fewer direct reports, but each report may be a manager with a large team underneath. Their direct span looks narrow while their indirect scope is large.

That is why leaders should examine direct span and layers together. A director with 4 direct reports can be efficient if those reports each lead mature teams. It can be wasteful if each report supervises 2 people and escalates every decision.

Stage changes the tradeoff

Early growth often creates narrow spans because founders promote specialists into management before there is a full team under them. Later, the problem flips. Teams scale faster than the management system, and the best managers inherit too many people because they are trusted.

Pave’s tech-company benchmark analysis uses more than 13% directors-and-above or more than 23% managers, directors, and VPs as top-heavy diagnostic thresholds, with caveats by stage. Those are not laws. They are prompts for a deeper review of role purpose, decision rights, and team size.

When is a manager's span of control too wide?

A span is too wide when the manager cannot coach, decide, review work, and remove blockers at the pace the team needs. Numbers help flag risk: Umbrex treats 15 or more as potential overload, while Gallup found 22% of managers have 10 to 24 direct reports and 13% have 25 or more.

Wide spans are not automatically bad. They are bad when the operating system around the manager is weak. Clear policies, documented escalation paths, visible dashboards, and routine approvals that do not depend on manual chasing can let a wider team function without burning out the manager.

When does a narrow span mean too many managers?

A narrow span is suspicious when managers have 1 to 3 direct reports, little distinct decision authority, and no clear apprenticeship or risk reason for close supervision. OpsDog warns that spans below its desired range can indicate redundant or unnecessary management positions, and Umbrex flags 1-to-3 spans as micro-teams.

Narrow spans are justified in some settings: new managers learning the craft, confidential executive teams, regulated review groups, highly specialized expert teams, or teams in turnaround. The test is not the number alone. The test is whether the management role has enough unique work to justify its cost.

A common top-heavy pattern looks like this: directors manage managers who manage two people each, while employees wait for decisions to climb and descend the chain. The cost shows up as SG&A. The deeper loss is decision speed.

For HR leaders building the operating cadence around these decisions, our HR operations guide covers the recurring people processes that usually reveal whether a management layer is helping or just routing work.

How should a growing company use span benchmarks without copying them blindly?

Use external benchmarks to set guardrails, then use internal evidence to decide. Run the analysis quarterly, segment by function and level, flag micro-teams and overloaded managers, connect the findings to outcomes, and model redesign options. Do not flatten because a benchmark says so. Flatten where the work and data support it.

1. Set function-specific guardrails. For example, 4 to 7 for complex expert teams, 8 to 12 for mature office teams, and 12 to 15 or more only where work is highly standardized.
2. Create a span heat map. Mark every manager by direct reports, team function, layer, location, and whether the manager still carries IC work.
3. Review micro-teams first. For spans of 1 to 3, ask whether the manager role should be merged, re-scoped, or kept for a documented reason.
4. Review overload second. For spans of 13 to 15 or more, inspect coaching cadence, attrition, quality, safety, response times, and approval queues.
5. Model the scenarios. Estimate what happens if two micro-teams merge, if a senior IC becomes a team lead, or if one overloaded manager receives an added layer of supervision.
6. Protect decision rights. Redesign reporting lines only after clarifying who approves spend, hiring, leave, performance actions, and policy exceptions.
7. Repeat quarterly. Growth changes the org chart faster than annual planning, especially after hiring waves, restructuring, or founder-led teams professionalize.

Which outcomes should span of control analysis connect to?

Connect span analysis to outcomes leaders already track: engagement, attrition, productivity, quality, safety, decision speed, and SG&A cost. Gallup's 2025 analysis covered 92,252 teams across 104 organizations, 26 industries, and 46 countries, which is why engagement belongs in the discussion, not just manager cost.

For companies tightening approval paths while they redesign roles, an approval workflow template can make decision rights explicit before the org chart changes. The worst redesigns move people first and discover approval confusion later.

How Cogniver helps make span of control benchmarks operational

Cogniver helps turn the org chart from a static slide into an operating layer. Admins can reorganize reporting lines with a drag-and-drop org chart, which is useful when span analysis shows that a team should move, merge, or report through a different manager.

That matters because span-of-control work is not just a headcount exercise. When a reporting-line decision changes who should approve spend, leave, hiring, or policy exceptions, teams need the org structure and the workflow path to stay aligned instead of relying on manual chasing.

Cogniver’s approval and workflow builder supports multi-step routing, branching, and human-set rules. AI workflow agents can help answer employee requests and route work, while human-configured policies and human review remain the safety valve for exceptions.