Span of Control: Small Business Practical Guide
Span of control for small business: formula, benchmarks by team size, wide vs narrow, and when to hire your first middle manager.
Span of Control for Small Business
How many direct reports is too many, when to add a management layer, and how to structure a growing team
Most small business founders end up managing too many people for too long. It happens naturally: you hire your first five employees, then your tenth, and at some point you realize you are running one-on-ones with 12 people, each getting a fraction of the attention they need. The company's performance shows that attention gap before anyone names the problem.
Span of control is the management concept that addresses this directly, and this guide gives you the small business version: what span of control means, how to calculate it, how to structure your team at different headcounts, and when to hire your first middle manager. It skips academic and enterprise theory to focus on growing a team you can actually manage well.
What Is Span of Control?
Span of control is the number of direct reports a single manager supervises. A founder with 8 employees all reporting directly has a span of control of 8. A team lead with 6 direct reports has a span of 6. The question behind the number is how many people one manager can effectively supervise and develop.
Organizational theorists have argued about the right maximum since the early 1900s and never settled on a number. That is the honest answer, and it is the useful one: a span that works for 8 people doing the same job breaks for 8 people doing 5 different jobs. Context sets the ceiling, not arithmetic.
According to Gallup, the manager or team leader alone accounts for 70% of the variance in team engagement. That is why span of control is worth measuring rather than assuming: the manager is the single largest input into engagement scores, so when one manager runs short of capacity, the shortfall lands on everyone reporting to them.
The Span of Control Formula and Benchmarks
The span of control formula is simple: divide the number of employees at a given level by the number of managers overseeing them. A team of 24 people managed by 3 team leads has a span of control of 8 (24 divided by 3).
The formula is most useful when you run it forward, on the team you are about to have rather than the one you have now. If you have 7 direct reports today and plan to hire 4 more this year, you will have 11 by year end. That projection tells you whether to add management capacity now, before growth makes the problem acute.
The following table applies the 5-to-8 rule of thumb to common small business team sizes. Read each assessment as a starting point, not a research finding:
| Team Size | Number of Managers | Span of Control | Assessment |
|---|---|---|---|
| 5 employees plus the manager | 1 (founder or manager) | 5:1 | Inside the rule of thumb. A single manager has room to give each person meaningful attention every week. No restructuring needed. |
| 8 employees plus the manager | 1 | 8:1 | At the top of the rule of thumb. Holds up if roles are similar, and feels stretched if roles span multiple functions. |
| 10 employees plus the manager | 1 | 10:1 | Above the rule of thumb. Can work for experienced managers with similar-function teams. Risky if the team is cross-functional. |
| 12 employees plus the manager | 1 | 12:1 | Well above the rule of thumb. The test is whether all 12 still get meaningful feedback every week: in Gallup’s research, about seven in 10 employees who get it are engaged, whatever the team size. |
| 15 employees plus the manager | 1 | 15:1 | Far above the rule of thumb. Unless the manager has a real talent for managing and little individual contributor work, the team ends up largely self-managing, which works only if all employees are senior. |
| 20 people, founder included | 2, reporting to the founder | 8 to 9:1 per manager | One management layer puts each manager at or just above the top of the rule of thumb. The founder manages the 2 managers, who split the other 17 people 8 and 9. |
| 35 employees | 4 managers + 1 director | 7 to 8:1 per manager | Inside the rule of thumb. Requires clear role definition at each management layer. |
| 50 employees | 6 managers + 1 to 2 directors | 7 to 8:1 per manager | Two full management layers, with directors over managers. May need functional specialization (engineering lead, operations lead, etc.). |
Why Span of Control Numbers Vary
The span of control numbers you will see run from a one-to-five guideline for incident management to Gallup's finding that highly engaged, well-managed teams of 12 or more can thrive. The variation reflects genuine differences in context.
Emergency management doctrine keeps spans deliberately narrow. The FEMA ICS Review Document (March 2018), which covers the Incident Command System, puts the optimal span for incident management at one supervisor to five subordinates, while noting that real incidents frequently require ratios significantly different from that. In an emergency, a coordination failure costs so much that the extra management overhead is worth paying.
Gallup tracks where real teams actually sit. According to Gallup (January 2026), the average number of people reporting to a manager rose from 10.9 in 2024 to 12.1 in 2025, while the median held at about five to six. A minority of very large teams pulls the average up: 37% of managers oversee fewer than five people and 66% fewer than 10, while 13% oversee 25 or more.
Gallup does not name an optimal span. Instead, it found that employees who strongly agreed they had received meaningful feedback in the past week were highly engaged (about seven in 10) regardless of team size. For a small business, that is the practical test of any span: whether each person still gets that feedback from their manager.
How much of the week goes to managing also shapes the span a manager can carry. The same Gallup analysis found that 97% of US managers report some individual contributor work, and the median manager spends 40% of their time on it. Managers above that 40% mark have lower engagement, and it gets worse as the number of people they manage grows.
Small business managers are almost always player-coaches of this kind, which is why this guide uses 5 to 8 direct reports as a rule of thumb rather than a research finding. A manager with real talent for the job, and a week mostly spent managing, can carry more.
Retention is where a span that is too wide finally shows up on a number you track. According to the Gallup Q12 meta-analysis (11th edition, 2024), business units in the top quartile of engagement record 21% lower turnover than bottom-quartile units in high-turnover organizations and 51% lower in low-turnover ones.
The manager drives most of that engagement gap, so a span wide enough to starve people of manager time arrives months later as voluntary turnover. The lag is what makes it hard to see: by the time the resignations cluster, the structural cause is a year old and nobody connects the two.
3 Real-World Span of Control Examples for Small Businesses
Abstract benchmarks are less useful than seeing how span of control decisions play out at specific headcounts. The three examples below cover the inflection points that most growing small businesses encounter.
Wide vs Narrow Span of Control: Which to Choose for a Small Business
The choice between wide and narrow spans is a trade-off between management cost, employee autonomy, and oversight quality. Wide spans push the company toward a flat organizational structure, narrow spans toward a taller company hierarchy. For small businesses (SMBs), it is often a payroll decision as much as an organizational design one.
| Factor | Wide Span (8 to 12+ reports) | Narrow Span (3 to 5 reports) | SMB Default |
|---|---|---|---|
| Management cost | Lower: fewer managers needed | Higher: more managers required at each layer | Wide. Most SMBs cannot afford management-heavy structures. |
| Employee autonomy | Higher: employees must self-direct more | Lower: more frequent manager touchpoints | Wide favors experienced, senior hires. |
| Communication speed | Faster from top to team: fewer layers to traverse | Slower: more layers mean more filtering and delay | Wide enables faster founder-to-team communication. |
| Manager workload | Higher: each manager carries more reports | Lower: manageable report count per manager | Wide creates burnout risk if managers lack capacity. |
| Visibility into team performance | Lower: harder to catch issues early with many reports | Higher: closer management means faster problem detection | Narrow is better when team members are junior or roles are complex. |
| Appropriate for | Experienced, autonomous teams; similar-function roles; stable work environments | Junior teams, high-complexity roles, rapid growth phases, cross-functional teams | Most SMBs: wide spans with senior hires; narrow spans when growing fast. |
The SMB Default: Start Wide, Narrow as Complexity Grows
Most small businesses start with wide spans because they cannot afford a management-heavy structure early on. That works well while the founding team is small and senior. Once you hire more junior employees, expand into new functions, or speed up hiring, each person needs more attention, so one manager can handle fewer of them. Add management capacity before that point, not after performance starts to slip.
Onboarding is where the cost of a wide span arrives first. According to Gallup, employees are 3.4 times as likely to call their onboarding successful when the manager takes an active role in it, and about a third of all new employees do not last 90 days.
A manager already carrying 11 people while doing their own work is the one most likely to run out of time for that active role. For a small business where every hire is a real investment, that bandwidth decides whether the person you just spent a month finding is still there in six months.
When a Narrow Span of Control Is the Right Call
A narrow span of control, roughly three to five direct reports, is the right structure when a mistake is expensive and the work has to be watched rather than reviewed afterward. Safety-sensitive trades, licensed and regulated services, and any team where most people are still inside their first year all need a narrower span than the raw headcount suggests.
The cost is real, so spend it on purpose. Every layer added to narrow a span puts another person between the founder and the work, slows decisions by a step, and adds a salary that produces nothing a customer pays for directly. Narrow the one team that needs it rather than the whole company.
Then write down the condition that lets you widen it again. Usually it is tenure: once the group has been doing the work for a year and the error rate has settled, one lead can carry eight of them instead of four. Without that written condition, a temporary narrow span quietly becomes a permanent management layer.
When to Hire Your First Middle Manager
The most common span of control mistake in small businesses is failing to add a management layer as the company grows, not getting the initial structure wrong. Founders who managed 6 people well often find themselves managing 14 or 15 before they admit the structure has outgrown them. By that point, management quality has been slipping for months.
Five signals suggest that a middle manager hire is due, and you do not have to wait for all five to act:
Run all five signals against every person who has direct reports, including yourself, and write the answers down where you will see them next quarter. The first tab below does the arithmetic that matters, which is the projection rather than today's count; the second turns the five signals into a decision you can date.
| A | B | C | D | E | F | G | H | |
|---|---|---|---|---|---|---|---|---|
| 1 | Manager | Functional areas covered | Direct reports today | Hires planned in the next 12 months | Projected reports at year end | Hours a week on management | Reading | Action, and by when |
| 2 | One row per person with direct reports. Include the founder. | |||||||
| 3 | ||||||||
| 4 | ||||||||
| 5 | ||||||||
| 6 | ||||||||
| 7 | ||||||||
| 8 | ||||||||
| 9 | ||||||||
| 10 | Key | 5 to 8 | Inside the rule of thumb | No change | ||||
| 11 | Key | 9 or 10 | Above the rule of thumb | Plan the layer before it is urgent | ||||
| 12 | Key | 11 or more | Well above the rule of thumb | Add a management layer | ||||
| 13 | Note | Cross-functional teams read narrower than the raw count | Adjust the reading, not the count |
What Kind of Manager to Hire First
Put your first middle manager over the functional area with the highest headcount, the most junior team members, or the most complex work. If 8 of your 15 direct reports work in operations and 7 in sales, the operations manager comes first, because the larger team needs more management. Those 8 reports should move across in stages over the new manager's first 30 to 60 days rather than all on day one.
In most small businesses, that first middle manager should also be a player-coach rather than a pure people manager: someone who carries individual contributor work alongside management. A pure manager is often both too expensive to justify at this scale and short of enough work to stay engaged.
Be deliberate about who gets the job. According to Gallup, companies fail to choose the candidate with the right talent for a management role 82% of the time, and only about one in 10 people have the natural talent to manage. The best individual contributor on the team is not automatically the one who can run it.
Whoever takes the role needs preparation, not just a title. Promoting someone on Friday and handing them 8 reports on Monday is how a capable employee becomes a poor manager.
The team pays for that. According to a 2023 survey of 2,066 employees reported by SHRM, 34% of workers who had a negative experience with a poor manager wanted to leave the organization, and 41% said they were stressed or anxious about reporting to work.
Visualizing Your Span of Control With an Org Chart
Span of control problems are often invisible until you draw them. A founder managing 12 people may not feel overwhelmed day to day, because the overload builds gradually. Looking at an org chart where 12 names connect directly to one box makes the structural problem immediately obvious.
An org chart also shows when spans are uneven. One team lead with 10 reports and another with 4 means each person on the larger team gets less of their manager, and that is where weekly feedback is most likely to slip. Without a visual, this imbalance often goes unaddressed until someone on the larger team leaves.
In FirstHR, the org chart is drawn from your department records: each department sits under the one it reports to, with its head and everyone in it. New hires appear in their department while still moving through the onboarding workflow, and naming a new manager as department head updates the chart.
In my experience, teams that keep their org structures documented and visible argue less about who owns what, and new hires stop asking who to go to somewhere in week two instead of week six. Treat the org chart as a communication tool as much as a record: it shapes how the team understands itself.
Start by drawing your chart as it stands today. Count the lines running into each box, including your own, then run the same count against next year's hiring plan. Any box that lands above the 5-to-8 rule of thumb, or any manager who trips one of the five signals, is where your next management hire belongs.
Frequently Asked Questions
What is span of control in management?
Span of control in management refers to how many people report directly to one manager or supervisor. If 8 people report to you, your span of control is 8. The concept was formalized in organizational theory in the early 20th century, and it is still one of the basic choices in designing an organization because it answers a practical question: how many people can one person manage well? No single number fits every team. The right span moves with how complex the work is, how experienced the people are, how alike their roles are, and how hands-on the management has to be. In a small business, the span you settle on directly affects how many management layers you need and when your first middle manager should come on board.
What is the ideal span of control for a small business?
No single number is ideal for every small business: Gallup’s 2026 span-of-control study names no optimal span and finds that a manager’s open communication with employees matters more than how many people report to them. As a working rule of thumb, this guide uses 5 to 8 salaried direct reports per manager. That range leaves room for weekly one-on-one meetings without overwhelming a manager who also does individual contributor work, gives enough visibility for early performance issue detection, and does not require an excessive number of management layers. Spans of 8 to 10 can work when team members are experienced and roles are similar. Above 10, the test is whether every person still gets meaningful feedback each week: in Gallup’s research, highly engaged teams of 12 or more can thrive under effective management, while poorly managed teams struggle even when small. The right answer for any specific team depends on role complexity, employee experience level, and how much individual attention each role requires.
What is the span of control formula?
The basic span of control formula divides the direct reports at one level of the company by the number of managers at that level. If 3 team leads share 24 employees, the span is 8 (24 divided by 3), meaning each lead carries that many people on average. To test your own structure, list every manager, count the people who report to each one directly, and hold each count up against the 5 to 8 rule of thumb; anyone carrying more than 10 is a candidate for restructuring. For a growing team, run the same math on next year’s headcount. A manager with 7 reports today will have 13 by year end if you add 6 more people to that team, which is well past that rule of thumb.
How many direct reports should a founder manage?
As a rule of thumb rather than a research finding, a founder who also carries sales, product or operations work should plan for 5 to 8 direct reports. Gallup’s 2026 span-of-control study names no optimal span, and its data show that managers who spend more than 40% of their time on individual contributor work have lower engagement, which gets worse as their teams grow. The challenge is that founders in early-stage companies often manage everyone by default, with spans of 10, 15, or more as the company grows without deliberate structure. Past 8 direct reports, one of three things tends to happen: management takes so much time that strategic work suffers; strategic work gets its time but management quality drops; or the founder hires a chief operating officer (COO) or first management layer to take on direct reports, which is the correct structural response. A practical trigger for a founder’s first management hire is 8 to 10 direct reports with steady growth ahead.
What is the difference between wide and narrow span of control?
A wide span of control means each manager has many direct reports, typically 8 or more. It requires fewer management layers and lower overall management cost but demands more self-direction from employees and can limit individual attention. A narrow span of control means each manager has few direct reports, typically 3 to 5. It enables closer oversight, more frequent coaching, and faster performance issue detection, but requires more management layers and higher total management cost. Most small businesses default to wider spans for cost reasons, which works well with experienced, autonomous employees. Narrow spans are appropriate when teams are junior, roles are highly complex, or growth is rapid enough to require close onboarding support for each new hire.
When should a small business hire a middle manager?
A small business should hire a middle manager as soon as one of five conditions holds, not once all of them do. The first is headcount: a manager with more than 8 direct reports and a team that is still growing. The second is time, when one-on-ones, reviews, hiring, and coordination take up more than 15 hours of a manager’s week and push strategic work aside. The third is breadth, when one person oversees more than 3 distinct functions that each need specialized attention. The fourth is pace, with 4 or more new people joining each year and a steady onboarding load to match. The fifth is blind spots, when performance problems slip past a manager who no longer has the bandwidth to see them. Most companies wait too long, and adding capacity only after the team has outgrown the structure means months of weaker management that hurt retention and performance.