Span of control: what the gap between two sites costs

Span of control drifts. A team splits when a supervisor leaves, a lead is promoted to keep them, an acquisition brings its own management layer. Each step makes sense on the day. Years later, two sites doing comparable work carry very different management cost, and the org chart shows the boxes but not the price of the difference.

The difficulty is that a gap is not automatically a problem. A wider span suits standardized, repeatable work. A narrower one can be right where the work is varied, technical or safety-critical. Before you close a gap, you need to know whether the work on each side explains it.

Orgsure measures span the same way at every site, puts a cost on the difference, and shows the work underneath, so you know where to look and what to test.

How it works

1. Load your HR export. Positions, reporting lines and pay, uploaded as CSV through Orgsure’s import templates. No HRIS integration project.
2. Measure span and layers the same way everywhere. Every site, plant and business unit is calculated on one definition, so a 1:15 at one site and a 1:10 at another are a real comparison, not two different counting rules.
3. Compare like with like. Set frontline managers at one site against frontline managers at another doing comparable work. A blended average across all levels, or a corporate office set against a plant, mixes different jobs and overstates the gap.
4. Put a cost on the gap. Manager pay comes from your own pay data, so the difference between two spans is a dollar figure, not a ratio.
5. Check the work behind the ratio. An activity survey across the positions, on a shipped catalog of work activities, shows what the managers and their teams actually spend time on. That is how you tell a gap the work explains from one it doesn’t.
6. Test the change before you announce it. Regroup teams in a simulation and see the change in FTE, cost and structure before anyone hears about it.

What you get

• Span and layers for every site on one scale, with the outliers easy to find.
• The cost of each gap in dollars, built from your own pay data and limited to comparable roles.
• The work underneath each team, so the conversation is about whether the work justifies the structure, not about the ratio alone.
• A tested scenario you can take to the executive team, with the FTE, cost and structure effects already worked through.

An example from a modeled demo organization

In a modeled 2,900-person demo manufacturer, frontline managers at Plant A run 1:15 (41 managers over 626 people). At Plant B they run 1:10 (60 managers over 606 people). At Plant A’s span, Plant B would need 40 frontline managers: 20 fewer manager roles, at a $152K average, about $3.0M a year.

That figure is an opportunity to test, not a committed saving. The next question is whether Plant B’s work is as standardized as Plant A’s. If it is, the gap is worth closing in stages. If it isn’t, the narrower span may be right.

These figures come from a modeled demo organization, not a customer.

Where Orgsure fits in a restructure

Orgsure is the measuring layer under a span-of-control program, not the program itself. It shows where the gaps are, what they cost and what work sits underneath them. Your leadership team, or the consulting firm running the restructure, decides what to change and how fast. The data stays with you after the program ends, so you can see whether spans drift back.

Frequently asked questions

What is a good span of control?

It depends on the work. Standardized, repeatable work supports a wider span. Varied, technical or safety-critical work often needs a narrower one. A single target applied everywhere ignores that, which is why Orgsure compares sites doing comparable work and shows the work itself.

Why compare frontline managers only?

Because they do comparable jobs. Averaging every level of management together, or comparing a corporate office with a plant, mixes very different roles and pay, and makes the gap look larger than it is.

Does a wider span at one site mean we should cut managers at the other?

No. It means there is a gap worth examining. The activity data shows whether the work at the narrower site explains the difference. Where it doesn’t, the gap is an opportunity to test in a simulation before anything changes.

What data do we need?

An HR export with positions, reporting lines and pay. Span, layers and cost come from that alone. The activity survey adds what the work looks like underneath each team.

How long does it take?

The HR export loads in the first two weeks. Span and cost by site come from that export, so they are the first findings, in 30 days. The survey runs as one wave, and the activity findings follow once it closes, within a 60-day pilot.

Will managers see this as a headcount exercise?

It’s positioned as work measurement, not performance measurement. The survey asks what work people do, not how well they do it, and is usually sponsored by the COO or CHRO.