Span of Control: How Many Direct Reports Is Too Many?
Span of control decides how much attention each person gets. Here are the ranges that work, the factors that change them, and what a wide span says about your role.

Span of control is the number of people who report directly to one manager. It looks like an organisational detail. In practice it decides how much attention each person gets, how fast decisions travel, and whether a manager is leading or simply processing.
If you manage people, or you are being considered for a role that does, the number matters to your career for a simple reason: hiring committees read span as a proxy for level, and they read it wrong as often as they read it right.
What span of control actually measures

Span measures direct reporting lines, not influence. A programme lead coordinating forty people across three departments has a span of zero if nobody reports to them formally. A team manager with nine reports has a span of nine even if the work is routine.
Two related numbers give the full picture:
- Span of control. Direct reports.
- Depth. Layers between you and the most junior person in your organisation.
Wide spans with shallow depth mean a flat organisation. Narrow spans with many layers mean a tall one. Most companies drift towards tall structures because promotion is easier than redesign, then correct with a delayering programme every few years.
The ranges that hold up in practice
There is no universal correct number. There are reliable ranges by type of work.
| Type of work | Workable span | Why |
|---|---|---|
| Routine, standardised, co-located | 15 to 25 | Exceptions are rare and rules cover most cases |
| Operational teams with defined processes | 8 to 15 | Coaching is needed, but problems repeat |
| Professional or technical specialists | 5 to 9 | Each case is different and judgement is required |
| Senior leaders running functions | 5 to 8 | Every conversation involves priorities and trade offs |
| New team, new process or turnaround | 3 to 6 | Attention per person is the scarce resource |
The pattern behind the table is variability. The more unpredictable the work and the more judgement each person needs from you, the narrower the span has to be.
The four factors that change the number

- Task variability. Identical work supports a wide span. Bespoke work does not.
- Team maturity. Experienced people who have worked together for years need direction rarely. A newly assembled team needs it weekly.
- Geography and time zones. Distributed teams add coordination cost that consumes the same hours coaching would use.
- Non management load. A manager who is also the technical escalation point, the customer contact and a project owner has far less capacity than their title suggests.
The last factor is the one most often ignored. Many managers carry a full individual contributor role plus eight reports, then conclude they are bad at management.
Signals your span is too wide
- One to ones get cancelled first when the week is busy.
- You learn about problems in escalation meetings rather than from the person.
- Development conversations happen once a year, during the review cycle.
- Your calendar is booked solid but you cannot name what you decided this week.
- People start routing decisions around you because waiting is slower than guessing.
A useful test: multiply your reports by one hour per fortnight of one to one time, then add preparation and follow up. If that number is more than a quarter of your working week, something else in your role has to move.
Signals your span is too narrow

Narrow spans have a cost too, and it is usually career cost rather than operational cost.
- Two or three reports doing similar work often means the layer exists to give someone a title.
- Decisions pass through more approvals than the risk justifies.
- Your reports have little scope to make their own calls, so they do not build the evidence they need for their next step.
If you manage two people and your organisation has four layers below the executive team, expect a delayering programme to review your role at some point.
What span means for your positioning
Here is where this becomes a career question rather than an org design question.
Recruiters and hiring committees use span as a shorthand for scope. It is a weak shorthand, but it is used, so your CV needs to make the real picture visible. Three numbers do most of the work:
- Direct reports, and indirect reports if you lead through other managers.
- Budget or cost base you own, with the currency and period.
- Decision rights that are yours rather than recommendations you make.
Compare these two lines:
Managed the operations team and improved performance across sites.
Led 6 direct reports and 41 indirect across three sites, owned a 12 million euro cost base, and held sign off on capital requests up to 250,000 euro.
The second version answers the level question in one sentence. The first version leaves the reader guessing, and readers guess low.
How to change your span deliberately

If you want a wider span, the route is rarely to ask for more people. It is to remove the variability that keeps the span narrow: document the recurring decisions, promote a senior person into a coordinating role, and hand over the escalation path. A manager who has made their team predictable is the obvious candidate when two teams merge.
If your span is already too wide, propose the intermediate layer with numbers rather than complaint. Show attention per person, the escalation backlog, and the cost of decisions that waited. That case is a leadership argument, and it reads well in a promotion discussion.
The short version
Span of control is not a scorecard. It is a design choice that should follow the variability of the work and the maturity of the team. Use it to diagnose whether your role is set up to succeed, and make sure your CV states the numbers behind it so nobody has to guess your level.
If you want an outside read on how your scope reads to a hiring committee, the CareerSynth Career Direction Preview analyses your CV and tells you which parts of your leadership scope are visible and which are still invisible.





