Spans and Layers

What is Spans and Layers?

Spans and layers is an organizational analysis that measures how many direct reports each manager has and how many management levels separate the top leader from frontline staff, to find costly or slow structures.

Updated November 2026 · 5 min read


When organizations grow, their structures tend to get taller and narrower without anyone deciding they should. A manager is added to give a strong performer a promotion, a new team is created under an existing one, an acquisition brings its own management layers. Each change makes sense on its own, but together they add cost, slow decisions and distance leaders from customers. A spans and layers review is the standard way to see this clearly. It uses HR data to measure the number of direct reports each manager has, which is the span, and the number of management levels in the organization, which is the layers.

Consulting firms popularized spans and layers analysis during the delayering programs of the 1980s and 1990s, and it remains one of the most common diagnostics in organizational design work. Modern reviews tend to be more nuanced than early delayering efforts, recognizing that the right span depends on the type of work and that cutting layers without changing how decisions are made rarely delivers lasting benefits. For executives, HR and finance leaders, a spans and layers review provides a fact base for deciding where the structure needs to change.

Definition of Spans and Layers

Spans and layers is a quantitative assessment of organizational structure that measures the span of control of each manager and the number of hierarchical layers across the organization, typically benchmarked against targets set by type of work, to identify opportunities to simplify the structure and reduce management cost.

It builds directly on span of control, uses data that can be visualized in an org chart and is a common first step in organizational restructuring.

What a Review Measures

Average and distribution of spans, showing how many managers lead one or two people and how many lead very large teams.

Number of layers between the chief executive and frontline staff in each part of the organization.

The share of employees who are managers and the share of payroll spent on management.

Patterns such as single-report chains, where a manager leads one person who also manages one person. Reviews also often compare management cost per employee across similar units, which can highlight areas that have grown top-heavy.

Typical Targets

Targets usually vary by type of work. Standardized, transactional teams may support spans of 10 to 15 or more, while specialist or complex work may suit spans of 5 to 8.

Many large organizations aim for no more than six to eight layers between the chief executive and the front line, with smaller organizations needing fewer.

Managers with fewer than three or four direct reports are often reviewed to see whether the role is needed or could be combined.

Targets should be treated as guidelines, with exceptions where the work genuinely calls for them. Some roles, such as heads of small specialist functions, may lead few people for good reasons and should be excluded from span targets.

Importance of Spans and Layers in Workforce and Operations

Spans and layers reviews reveal hidden cost. Excess management roles can make up a significant share of payroll without being visible in normal budget reports.

They point to faster decision-making. Fewer layers mean shorter approval chains and less distortion of information between leaders and the front line.

They also improve roles. Managers with meaningful teams and individual contributors with more autonomy both tend to find their work more satisfying.

Spans and Layers and Financial Management

Reviews quantify the cost of management overhead by layer, function and region, linking structure to the total cost of workforce.

Modeling different span and layer targets shows potential savings before any decisions are made.

Savings often come from not refilling management roles as people leave and from combining small teams, rather than only from layoffs.

The cost of the transition, including lost productivity and severance where it applies, should be set against expected savings.

Common Challenges

HR data on reporting lines is often inaccurate, so the first step is frequently a data clean-up.

Applying one target to every team ignores real differences in the work and can harm areas that need closer support.

Removing layers without redefining decision rights leaves remaining managers overloaded and decisions just as slow.

Reviews can create anxiety if they are seen purely as a cost-cutting exercise, so communication matters. Benefits can also fade over time if no one keeps watching, as new layers return through promotions and new teams.

How to Conduct a Spans and Layers Review

Conducting a spans and layers review involves gathering accurate reporting data, analyzing spans and layers by area, setting targets by type of work, designing changes and tracking results.

The best reviews combine data with conversations with leaders, who understand why the structure looks the way it does.

Analyzing the Structure

Extract reporting relationships from the HR system and check them with managers to correct errors.

Calculate spans, layers and management cost for each function, region and level, and compare them with targets.

Identify hot spots, such as single-report chains, very narrow spans and areas with more layers than their size justifies.

Interview leaders in these areas to understand the reasons, which may be valid, such as regulatory needs or very complex work. Share the findings with leaders before drawing conclusions, since they can often explain anomalies or spot data errors.

Designing and Implementing Changes

Design changes area by area, combining small teams, removing unnecessary layers and widening spans where the work allows.

Redefine decision rights so decisions move down as layers are removed.

Phase changes over time where possible, using natural attrition and redeployment, and track engagement and performance in affected teams. Repeat the analysis each year using the same method, so leaders can see whether the structure is drifting back.

Examples of Spans and Layers in Practice

The examples below show spans and layers reviews in practice.

Both use illustrative figures. The first reduces management cost, and the second targets one function.

In each, data revealed what the org chart had hidden.

Reducing Management Cost

A telecommunications company with 12,000 employees finds an average span of 4.2 and up to eleven layers in some functions.

It sets targets by type of work, combines small teams and removes two layers in operations and customer service over two years.

Management costs fall by about 14%, and frontline teams report faster answers on customer issues.

Targeting One Function

A bank's technology function has grown quickly, and a review finds that 35% of its managers lead three or fewer people.

It creates senior engineer and architect roles at the same pay levels as management, and moves many managers with small teams into these roles.

The function removes a layer, and engineers report clearer career options and fewer approval steps.

Conclusion

Spans and layers is an analysis of how many direct reports managers have and how many management levels exist, used to identify slow or costly structures. It measures span distribution, layers and management cost against targets set by type of work.

In workforce and operations, spans and layers reviews reveal hidden cost, point to faster decisions and improve roles. Cleaning the data, setting targets by type of work, talking to leaders, redefining decision rights, phasing changes and tracking results help organizations simplify their structure well.