Organisational structure tends to attract attention only when something has already gone wrong. Decisions are slow, accountability is unclear, or a team has been over-stretched for too long. By then, things may have been quietly drifting for some time. 

Span of control is one of the lenses that makes this drift visible. However, it is not the only one. Role clarity, decision rights, process design, and how work flows across teams all shape how an organisation functions in practice. Because it is measurable, and is one of the easiest dimensions of structure to track continuously, span is a good place to start once the data is connected. 

Span itself is easy enough to calculate at any single moment. Keeping up with how it changes is harder. Every hire, promotion, or restructuring can alter it. Whether these shifts happen deliberately or not determines whether the resulting structure stays aligned with what the business needs, or slowly stops fitting. 

Workforce analytics can identify these patterns early, giving the organisation a chance to course correct, and turning span of control from a periodic audit into a continuous view of how the organisation is structured today and how it got there. 

The distribution problem

Take Engineering and Operations. A manager in Engineering overseeing seven people may be doing substantive work: aligning on technical direction, unblocking decisions, developing specialists. A manager in Operations overseeing twelve may be doing the same job more efficiently, because the work is defined, the processes are repeatable, and the team does not need the same depth of individual attention. 

Both can be appropriate structures for the work they support; workforce analytics can show whether they are suitable in practice. Are Engineering spans narrow enough to support the complexity of the work? Has Operations added reporting layers that the work doesn’t require? Are there functions that look more like each other than the nature of their work justifies? 

The average span of control alone won’t tell you much – instead, one can leverage a number of additional dimensions for a deeper analysis. 

Distribution, not just averages

An organization-wide average span of 7:1 can mask a wide range underneath, with some managers having two and others as many as fourteen direct reports. The average tells you less about where the structure is working than the distribution does. 

But, as the organization grows, tracking full distribution manually across departments and functions becomes impractical. Workforce analytics tools, however, let you track these structural shifts continuously. 

Layer depth over time

How many reporting layers exist today matters less than how that number has changed over the past two or three years. When layer depth grows without headcount growing with it, the structure has usually been added in small pieces over time, sometimes through deliberate choices like career paths in a slower growth phase or an acquisition not yet fully integrated, and sometimes through decisions nobody quite remembers making. The trajectory can point to which is the case. 

Manager-to-IC ratios by function

Where is management density proportionate to team size and work type, and where is it not? Tracking this ratio across functions shows where design attention is warranted. 

A high ratio might reflect promotions that outpaced IC hiring, a restructuring that added roles without removing others, or an acquired team never fully integrated – each calls for a different response. The data points to where to look. The fix depends on which of those causes is in play, and that takes a conversation with the function leaders. 

Context and the shifting shape of work

Context shapes what a healthy structure looks like. 

A software engineer working on a new product feature and a customer service representative handling structured requests need different things from a manager. A manager whose team sits across London, San Francisco, and Singapore has fewer touch points than one whose team sits in the same office. A team of eight analysts who have worked together for three years runs differently from a team of eight hired in the last six months. The same span of control number means different things in those situations. 

Work design itself is also changing. AI and automation are absorbing parts of the work that used to flow through manager-led coordination. Deloitte finds that 36% of managers expect to be managing digital agents within the next five years. That changes what supervision actually means.

The shift moves in two directions at once. Some teams have absorbed more autonomy than the structure reflects, so existing spans may be carrying less than they did. Other teams are doing work that has become harder to supervise, as the routine layer is automated away and only the judgement-heavy work remains. Spans that worked three years ago may not work the same way today, in either direction. 

Workforce analytics incorporates these factors alongside the ratios: the complexity of the work, function type, growth phase, geography, tenure mix, and how work design is shifting underneath. 

Growth and structural drift

Growth is where the span of control structures drift most heavily. Reporting relationships form faster than anyone is actively designing them. A team lead takes on a direct report because it made sense at the time. A new layer gets added to create a promotion path. An acquired team comes in with its own structure that never fully integrates. 

None of these individual decisions is a problem. Cumulatively, across several growth phases, they can produce a structure that reflects history more than intent. That structural debt eventually has to be addressed, usually during a reorganisation that could have been smaller if the drift had been caught earlier. 

Span of control is most useful when it is evaluated continuously rather than only during large reorganisations. When you can track how spans and layers are shifting over time, you can flag functions moving outside the expected range and bring that into workforce planning conversations before it requires a structural reset. 

---

What the data shows

A fictional scenario. 

A tech company with around 800 employees runs span and layers analysis continuously, with the data refreshed monthly and available across HR and organisational effectiveness teams. 

In the first six months of tracking, the organisation-wide average sits at just over 6:1. The number alone looks reasonable. The distribution underneath is uneven. One-third of managers have three or fewer direct reports, concentrated almost entirely in two functions that have grown through promotion rather than external hiring. Layer depth in those functions has reached seven, while comparable functions sit at four. 

Tracked over time, the trend is visible. The two affected functions have been narrowing in average span for three consecutive quarters. The pattern is a structural shift still in motion. 

That visibility changes the conversation. The people closest to the affected functions can adjust earlier, in smaller steps, while the drift is still narrow enough to address without disruption. The eventual reorganisation, if one is needed at all, can be smaller and more targeted. 

If you want to see where your own structure stands, the assessment below is a practical starting point.

From periodic audit to continuous view

The analysis above doesn’t have to be a one-time exercise. When span of control data is available interactively, filterable by function, level, business unit, and time period, the analysis can start to be a continuous view of the organization. An HRBP can pull the manager-to-IC ratio for a specific function before a leadership conversation. An organisational effectiveness lead can compare layer depth across two business units without waiting for a data extract. A workforce planning team can see how the management structure has shifted over the past two years alongside headcount growth, in the same view. 

The historical view is the part that matters most. Knowing where the structure stands today is useful, but knowing how it got there makes the design conversation specific enough to act on: which growth phases added layers, which functions have been moving toward narrower spans, which restructurings left structural debt behind. Continuous tracking matters more now than it did a few years ago, because the underlying work is shifting. Structures that fit the business at one phase of growth are unlikely to fit at the next. 

For some this is foundational work. Organisations that already have workforce structure data in a continuous view are asking more sophisticated questions than the ones this piece sets out. Many are still building towards that: getting the data connected, getting the dimensions on the same page, and getting the structural conversation out of annual reviews and into the operating rhythm. When that’s in place, the questions that used to wait for a formal review start getting answered when they come up. Earlier, faster, by the right people.

Span of control is just one metric. Used consistently over time, it shows whether your organisational design is keeping pace with how the company is growing.

It is also a starting point. Once span is in continuous view, the same approach can extend to engagement, productivity, turnover, and the other dimensions of how the organisation functions. Read together, these signals turn structural design from something you react to into something you direct.