Organizational Layers Benchmark by Company Size: A Practical Guide

How many organizational layers should a company have at each size?

Company size alone cannot determine the right number of layers. Bain found eight to nine layers in an average organization and no more than seven among best-in-class companies. Those figures are cross-company reference points, not targets for employee bands. Work type, operating complexity, manager capacity, and practical spans should drive the decision.

This distinction prevents bad redesigns. Published figures do not support a credible schedule in which a small company needs one layer count, a midsize business another, and an enterprise a third. Any useful organizational design benchmark should disclose its scope, measurement method, sample, and operating context.

Treat the first two rows as directional references, never quotas to impose across the chart. The other rows explain why. Bain reports that work type changes appropriate spans, while the IANS Research and Artico Search benchmark shows that specialist functions can carry their own leadership structures.

Why employee bands cannot produce a universal layer schedule

Equal headcount does not create equal managerial work. A software research group requires technical judgment, coaching, and coordination among specialists. A contact center relies more heavily on standardized tasks and repeatable supervision. Bain places skills-based roles at spans of six to eight and task-based roles at 15 or more. Companies with the same workforce size can therefore need different structural depths.

Headcount is a filter for choosing peers, not a formula for choosing layers.

How should organizational layers be counted?

Alpha Apex Group defines organizational layers as the hierarchical levels from the CEO to frontline employees. Count each distinct level along an actual formal reporting path, declare the counting convention, and apply it consistently. Keep job-title grades, pay bands, project responsibilities, and dotted-line relationships separate unless they form part of the formal hierarchy being measured.

• Organizational depth: the hierarchical levels along a CEO-to-frontline reporting path, following the Alpha Apex Group definition.
• Span of control: the number of direct reports each manager oversees, as defined by HRBench.
• Manager percentage: the share of active employees who hold management roles, as defined by HRBench.

The Alpha Apex Group definition includes the CEO at the top and frontline employees at the bottom of the hierarchy. Apply that definition consistently across every path. Record manager, position, function, employment status, and reporting-line type in your org chart data fields so another analyst can reproduce the result.

How does span of control affect organizational depth?

Span of control and organizational depth are connected, but they are not interchangeable. HRBench defines span as a manager’s direct reports, while Alpha Apex Group defines organizational layers along the path from the CEO to frontline employees. Narrow spans tend to require more managers and can create extra layers. Broader spans can support a flatter structure when the manager’s capacity and the team’s work make that arrangement practical.

Bain’s average organizations paired spans of six to seven with eight to nine layers. Its best-in-class group paired spans of 10 to 15 with no more than seven layers. That relationship is directional, not an instruction to widen every team. Apply detailed span-of-control benchmarks by role and work type rather than issuing one target to every manager.

Where broader spans stop working

Bain’s benchmarks reflect the effect of work type: skills-based roles such as engineers and brand managers are usually served by spans of six to eight, while task-based roles such as shop-floor and call-center supervisors can reach 15 or more. Joshua Burgin’s technology guidance suggests six to 10 reports for line managers and eight to 12 for directors and higher roles.

• A manager has unusually few reports without a clear specialist or risk-control reason.
• Several consecutive managers mostly relay information or forward approvals.
• A broad span leaves too little time for coaching, decisions, and escalation handling.
• A function is judged against spans designed for fundamentally different work.

What percentage of employees should be managers?

HRBench defines manager percentage as the share of the workforce holding management roles and distinguishes it from span of control. It does not show how tall the hierarchy is. HRBench places the typical mid-market range at 10% to 20%, with a national median near 16%. Use manager share beside layer depth and span distributions, never in place of them.

Two organizations can report the same manager percentage and operate through very different structures. One may stack managers in a long chain of narrow reporting lines. The other may distribute them across parallel teams with shorter CEO-to-frontline paths. Their percentages match, but their decision distance, spans, and management overhead do not.

Use all three structural measures together

Report the maximum, median, and common path depth for each function. Pair those results with the distribution of direct reports and the percentage of active employees classified as managers. A company-wide average alone can hide one-report managers, overloaded supervisors, and unusually deep reporting chains.

Should layer benchmarks be company-wide or function-specific?

Set benchmarks by function and role archetype first, then roll up the findings for a company-wide view. Bain’s work-type benchmarks and the IANS Research and Artico Search security benchmark show why engineering, frontline operations, and security leadership should not automatically be assessed against the same structural reference. The best peer is not simply close in headcount. It performs comparable work at comparable operating complexity.

The Fortune 500 security benchmark shows the problem with careless comparisons. IANS Research and Artico Search report that organizations of that scale typically have four or more security leadership layers, often with dedicated heads for SecOps, GRC, IAM, and Architecture and Engineering. That finding describes cybersecurity functions, not the total depth of a Fortune 500 company.

How should a company audit its management layers?

Start with actual reporting paths, not the polished chart used in board presentations. Calculate span distributions, then inspect management roles function by function. The objective is not to hit one fashionable layer count. Find avoidable handoffs, managers with unusually few reports, overloaded leaders, and structures that no longer fit the work.

1. Lock the definitions. Decide which workers qualify as managers, whether the CEO and frontline levels both count, and how dotted-line relationships will be treated.
2. Map every reporting path. Trace each active employee through formal managers to the CEO, then flag broken, duplicated, or ambiguous relationships.
3. Calculate depth by function. Record the shortest, longest, median, and most common CEO-to-frontline paths instead of relying on one company-wide average.
4. Build the span distribution. Group managers by direct-report count and role archetype so unusually narrow or broad spans become visible.
5. Calculate manager percentage. Divide employees classified as managers by active employees, then reconcile the result with the layer and span findings.
6. Investigate exceptions. Determine what work each low-span manager performs and whether the layer owns decisions, develops people, or merely passes information.
7. Compare relevant peers. Match function, work type, operating complexity, and measurement method before treating another organization’s figure as a benchmark.

Document proposed layer removals, wider spans, reporting changes, and the reasons for retaining specialist layers. Check the plan against common organizational design mistakes before changing titles or reporting lines. A good audit clarifies accountability. A shorter chart by itself proves nothing.

How Cogniver helps benchmark and reshape organizational layers

Cogniver gives HR and operations leaders one editable source of truth for reporting lines. Its drag-and-drop org chart exposes each CEO-to-frontline path, while automatic tree layout keeps the structure readable during redesign. Groups and grades on the same chart determine approver resolution and module access, so structural decisions carry into daily work.

Reorganizations remain controlled while roles move or disappear. When a position is deleted, its direct reports move to the grandparent rather than becoming orphaned. Incoming hires appear as reserved seats before their first day, allowing leaders to model the intended organization alongside the current one.

The hierarchy then runs real processes. Purchase, leave, and document approvals follow visual workflows with branches, merges, and multi-step approval chains. Groups and grades select the appropriate approvers. Each workflow can also have an isolated AI agent that routes requests and chases approvers, turning the org chart into an operating structure rather than a static presentation.