Span of Control: How Many Direct Reports Should a Manager Have?

Span of Control: How Many Direct Reports Should a Manager Have?

Someone in your organization is about to argue that their grade should go up because they picked up four more direct reports. Someone else is about to argue that a manager with two reports isn't really a manager at all. Both arguments sound reasonable, and both are asking your job architecture to do something it was never designed to do.

Span of control is a real and useful number. It tells you whether your structure is bloated, whether your managers are drowning, and where you have layers that exist only because someone needed a promotion. What it does not tell you — not reliably, not on its own — is what a job is worth. This guide gives you the benchmarks, the formula, the five factors that should set your spans, and a clear rule for where direct-report counts belong in your leveling logic.

TL;DR

• Span of control is the number of employees reporting directly to one manager. The U.S. average is roughly one manager per 11.4 workers, but the median team is only five to six people.
• Gallup found average team size jumped from 10.9 in 2024 to 12.1 in 2025 — a nearly 50% rise since 2013 — while the median barely moved. A handful of very large teams is pulling the average up.
• There is no universal right number. Gallup's research says the ceiling depends on manager talent, how much individual contributor work the manager carries, and whether feedback happens weekly.
• Span is an input to job evaluation, not a grade. Headcount belongs inside a responsibility or scope factor — never as a standalone promotion trigger.
• Run a spans-and-layers review annually: count reports per manager, flag anyone under three and over 15, and check whether each layer adds a real decision.

What span of control actually means

Span of control is the number of employees who report directly to a single manager. A director with six managers reporting to her has a span of six, not a span of the 70 people underneath those managers. That second number — everyone in the reporting tree — is your span of accountability or total organizational size, and mixing the two up is the single most common error in these conversations.

The related measure is layers: how many reporting levels sit between the CEO and the frontline employee. Spans and layers move in opposite directions. Widen the spans and the structure flattens. Narrow them and you add layers, cost, and distance between the top and the work.

What the benchmarks actually say

Start with the macro picture. The U.S. Bureau of Labor Statistics counted 13.7 million people in management occupations out of 170.3 million total employment in 2025. That works out to roughly one manager for every 11.4 non-management workers across the entire economy.

But the average hides the shape of the distribution. Gallup's 2026 span of control research, drawn from a panel of 16,442 U.S. managers, found the mean number of direct reports climbed from 10.9 in 2024 to 12.1 in 2025 — nearly 50% higher than when Gallup first measured it at 8.2 in 2013. The median over that same stretch stayed flat at five to six.

Here is the distribution Gallup reports:

Read that table carefully before you benchmark yourself against "12." Two-thirds of managers lead fewer than 10 people. The average is being dragged upward by the 13% running very large teams, mostly in frontline operations and mostly as a result of the middle-management cuts of the last three years.

Function matters more than any company-wide target. Frontline production and call center supervisors routinely run spans of 15 to 25, because the work is standardized and the coaching load per person is low. Engineering, R&D, and professional services managers typically land between five and nine, because the coaching is the job. Executive spans run narrow — five to eight — because each report owns a function.

How to calculate span of control

The formula is simple enough that the hard part is deciding what to count:

Span of control = number of employees reporting directly to the manager

Organization-wide average span = total employees ÷ total people managers

Say you have 840 employees and 96 people managers. Your average span is 8.75. Now segment it. If your operations group averages 14 and your corporate functions average 4.2, you don't have a span problem — you have a corporate functions problem, and the company-wide number was actively hiding it.

Three rules keep the math honest. Count direct reports only, not dotted lines. Keep open requisitions separate from filled seats, or a hiring freeze makes your spans look artificially tight. And flag working supervisors — Gallup found 97% of managers carry some individual contributor load, at a median of 40% of their time. A player-coach with eight reports is not running a span of eight in any meaningful sense.

The five factors that should set your spans

Gallup's central finding is that the right span isn't a number you can look up. It depends on conditions you control. SHRM's guidance on direct reports reaches the same conclusion from the workforce planning side. Five factors do most of the work:

1. Work complexity and variability. Standardized, repeatable work supports wide spans. Novel, judgment-heavy work does not.
1. Manager's individual contributor load. Gallup found manager engagement holds steady at 37% across all team sizes when the manager spends 40% or less of their time on individual contributor work. Above that threshold, engagement drops as the team grows — down to 32% at 25-plus reports. Player-coaches need smaller teams.
1. Manager capability. High-talent managers in Gallup's data sustained 46% engagement versus 27% for low-talent managers under the same conditions. Capability, not headcount, is the binding constraint.
1. Geographic and work-location spread. Fully remote managers hit their ceiling faster than on-site managers. Distance costs coaching bandwidth.
1. Team tenure and stability. A team of experienced people who have worked together for years absorbs a wider span than one that is half new hires.

One habit changes the math more than any of these. Gallup found that employees who strongly agreed they received meaningful feedback in the past week were engaged at roughly seven in 10 — and that this held regardless of whether the team had four people or 25. Without that weekly feedback, engagement fell to about one in four at every team size. If you are going to widen spans, widen the feedback discipline first.

Building the leveling logic to support this? Our job leveling guide walks through how to define levels that hold up when structure changes.

Where span of control belongs in job evaluation — and where it doesn't

This is where comp teams get burned.

Managing more people is a legitimate increase in responsibility, and a point-factor job evaluation system should capture it. The right place is inside a scope or responsibility compensable factor, scored alongside budget accountability, decision authority, and organizational impact — where it competes with every other factor for weight instead of overriding them.

The wrong place is as a standalone promotion trigger. The moment "12 or more direct reports equals Director" enters your leveling rules, three things happen. Managers start empire-building, because headcount becomes the cheapest path to a grade. Reorganizations turn into pay events. And you produce outcomes you can't defend: a manager of 15 warehouse associates and a manager of six data scientists land in the same grade, even though the second job carries far more complex decisions and a much larger financial footprint.

Score the work, not the org chart. A manager's grade should reflect the complexity of the decisions they own, the knowledge the role requires, and the consequence of getting it wrong. Headcount is evidence about scope. It is not scope itself.

Use this test. If a reorganization moved four people from Manager A to Manager B tomorrow, should both grades change? Almost always no — the jobs didn't change, the boxes did. Your job architecture should survive a reorg without a repricing exercise, and when you convert evaluation points into pay grades, a defensible curve matters more than any single factor's contribution.

How to run a spans-and-layers review

Do this once a year, ideally before headcount planning rather than after.

1. Pull the reporting data. Every people manager, their direct report count, level, and function.
1. Segment before you judge. Operations against operations, engineering against engineering. Company-wide averages are close to meaningless.
1. Flag the tails. Fewer than three reports and more than 15 both deserve a conversation — for opposite reasons.
1. Count the layers. Trace CEO to frontline in three functions. Most organizations under 5,000 people need six or fewer.
1. Test each layer. What decision does this level make that the levels above and below cannot? No clean answer means the layer holds a title, not a job.
1. Check the title-only managers. A "manager" with one report is usually a leveling workaround. Fix it with a dual career ladder, not a fake team.
1. Re-evaluate only what changed. Scope genuinely shifted? Score it. Only the reporting line moved? Leave the grade alone.

FAQ

What is a good span of control? For most professional and knowledge work, five to nine direct reports. For standardized frontline work, 10 to 20. For executives, five to eight. Gallup's U.S. median sits at five to six across all functions.

What is the average span of control in 2026? Gallup measured an average of 12.1 direct reports in 2025, up from 10.9 in 2024. BLS employment data implies roughly one manager per 11.4 workers economy-wide. The median team, however, is only five to six people.

Is a wider span of control better? Only under specific conditions. Wide spans cut management cost and speed up decisions, but Gallup's research shows they hold up only when managers have the capability, a light individual contributor load, and a weekly feedback habit. Widening spans without those conditions trades short-term savings for performance.

Should span of control determine a manager's pay grade? No. Score it inside a responsibility or scope compensable factor, weighted against decision authority, complexity, and financial impact. Using headcount as a standalone grade trigger invites empire-building and produces outcomes you can't defend in an audit.

How many layers should an organization have? Most organizations under 5,000 employees can operate with five to seven layers between CEO and frontline. If a layer doesn't own a decision the layers above and below can't make, it's a title-holding device.

What's the difference between span of control and span of accountability? Span of control counts direct reports only. Span of accountability counts everyone in the reporting tree beneath the manager. Job evaluation cares about both, but they are not interchangeable.

Does a manager with two direct reports count as a manager? Not on headcount alone. What matters is whether the role carries real people-management accountability — hiring, performance, pay decisions — or whether the reports were assigned to justify a title. Job slotting these roles instead of scoring them is how title inflation starts.

Get your leveling logic right before you restructure

Spans and layers change constantly. Your grade structure shouldn't. The organizations that survive a flattening with their pay structure intact are the ones that scored the work first — so when the boxes move, the grades hold.

PointFactors scores every job against weighted compensable factors and shows you exactly why each role landed where it did, with an audit trail you can put in front of a manager, a works council, or a plaintiff's attorney. If you are heading into a restructure and want your leveling defensible before the org chart moves, book a demo or see how job evaluations work in the platform.

Justin Hampton is founder and CEO of PointFactors.