The first time I was asked how many units I could run, I said "as many as you give me." The person asking took me at my word. I spent the next year quietly overloaded, doing an okay job on every unit and a good job on none of them. That is the whole risk of the span-of-control conversation. If you answer it with pride, you will inherit a scope you cannot honor. If you answer it with math, you will inherit a scope you can run well.
Here is the math. A useful weekly one-on-one with a general manager takes thirty minutes plus fifteen minutes of prep on your side to review their numbers. Call it forty-five minutes per GM per week. Ten GMs is 7.5 hours a week. Twelve GMs is 9 hours. Fifteen GMs is 11.25 hours. Twenty GMs is 15 hours. That is before travel, before crisis, before the standing regional meeting, before your own director calls, before any actual coaching or field visits.
Working backward from a real calendar, you can maintain coaching depth with 8 to 12 direct reports. Not 20. Not 25. Some organizations run bigger spans on paper. What is actually happening in those cases is that either the coaching is not happening or a district layer is quietly absorbing the load without being on the org chart.
The four variables that shrink your span
A raw unit count does not tell you the load. Two regional directors with twelve units each can be running very different jobs. Four variables set the true weight:
Unit complexity
A single-daypart, single-menu unit is a lighter load than a full-service unit doing breakfast, lunch, dinner, catering, and delivery. Complexity doubles the number of things that can drift and the number of things a GM needs to hear from you about. A regional director over twelve complex units has roughly the same coaching load as a regional director over sixteen simple ones.
Geographic dispersion
Twelve units in one metro area is a manageable job. Twelve units spread across three time zones is not, at least not in the same way. Time zones cut into your weekly one-on-one window. Travel replaces coaching hours. The mental switching cost of moving between markets is real and it is not free. At Hana Group I had 21 units across 6 states. The geography alone consumed a full working day per week of my calendar.
Format variation
Twelve identical corporate units is one job. Twelve mixed franchise, corporate, and embedded retail units is three jobs. Each format has different vendors, different reporting, different compliance requirements, different guest expectations. Format variation is the variable operators most often underestimate. It does not add complexity linearly. It adds it in steps.
Operating system maturity
Twelve units with mature SOPs, working dashboards, and a real rhythm is a coaching job. Twelve units with broken SOPs, no dashboards, and a rhythm that has to be built from scratch is a construction job. Construction takes double the time. If you are inheriting a young or broken system, cut your span estimate in half for the first two quarters. You will spend the difference building the machine.
Fig. 1 · Same job title, very different working spans.
When to add a district layer
The trigger for adding a district manager between you and the units is not a fixed number. It is a set of conditions. Any three of the following, and you need the layer:
- More than 12 direct-report units.
- Units across 3 or more time zones.
- Two or more distinct formats (franchise, corporate, embedded retail).
- A regional director calendar with less than 30 percent unstructured time.
- Coaching conversations that are being skipped or shortened.
At Hana Group I hit five of five. Twenty-one units, six states, four retailer formats, my calendar was 90 percent booked before the actual regional work started, and I was compressing weekly one-on-ones into fifteen minutes to make them fit. That last symptom was the tell. I built the district structure in month four, and the region got better within a quarter. Not because the district manager was smarter than I was. Because a fifteen-minute conversation cannot do the work a real one-on-one does.
The moment you find yourself running fifteen-minute one-on-ones, you have already lost the span. You are just not admitting it yet.
What breaks first when the span is too wide
The failure mode is not obvious. It looks like everything is fine. Here is the actual sequence:
Coaching depth collapses
You still meet with every GM. The meeting shortens. The prep gets skipped. The coaching moves from "what should we work on this month" to "what fires do we need to handle this week." It becomes a status meeting with a friendly tone. Nobody complains. Growth stops.
The middle of the pack drifts
You still have attention for your top performers, because talking to them is easy, and for your bottom, because you have to. The middle five or six units, the ones that are okay but could be great, get nothing from you. Six months later, those units are your bottom quartile. You did not create the drift. You allowed it by not showing up for the middle.
Standing meetings run long, then get cancelled
The monthly regional review starts at three hours, then four, then five. GMs who present last stop preparing. Then you cancel it once. Then twice. Then it is gone. The peer accountability layer disappears and nobody notices for a quarter.
You become the bottleneck for decisions
With too many direct reports, you cannot process decisions fast enough. GMs stop bringing them to you. They either freeze or they act without alignment. The first is slow. The second creates variance across units that will show up in the P&L two months later.
What technology actually does for span
A good regional dashboard, a live weekly report, and an asynchronous decision log will buy you two to three units of extra span. That is real and it is worth the setup cost. The technology does two things well. It cuts your prep time for the weekly one-on-one from fifteen minutes to five, because you show up already knowing the picture. And it lets a GM answer their own question by looking at their number, instead of asking you.
What technology cannot do is have the coaching conversation. The dashboard can tell a GM that their labor variance is high. It cannot tell them what to do about it, and it cannot help them build the muscle to see it earlier next time. That coaching is still a human hour, and human hours are still finite.
How to know your real span right now
Three checks. Do all three this week:
- Look at last week's calendar. Did every direct-report GM get a real thirty-minute one-on-one? If two or more got compressed or moved, your span is above healthy.
- Rank your GMs by how much attention they got from you last month. If your top three and your bottom three account for more than 70 percent of your coaching time, your middle is drifting.
- Ask the GMs, individually, when they last brought you a decision that was not a fire. If most of them say "a while ago," they have stopped bringing you the work you should be doing. That is the bottleneck talking.
What I got wrong about my own span twice
Two seasons in my career where I misjudged my own span, and both cost me.
The first was inside a nine-unit portfolio early in my career. Nine units, all in one market, all corporate, all mature. On paper an easy span. I ran it for eight months and did fine. Then I got asked to take on a special project on the catering side, worth about a third of my calendar, on top of the nine units. I said yes. Within six weeks I was compressing weekly one-on-ones into fifteen minutes to make room, and by month three of the special project three of the nine units had drifted on labor. The nine units did not get harder. My real capacity shrank because I had accepted a parallel workstream. The span math was still nine. My effective span was seven, and the two units I could not run properly noticed.
The second was at Hana in the first month, before I built the district layer. Twenty-one units, six states, four retailer formats. I told myself I could hold it directly for the first quarter while I got the picture. That was a mistake. What I actually did was hold ten of the twenty-one and let eleven drift with light-touch check-ins that fooled me into thinking I was covering them. When I finally built the district structure in month four, three of the eleven "light-touch" units had picked up problems I would have caught in month two if I had built the layer earlier. The lesson: do not use "I am still diagnosing" as a reason to delay a structure you already know you need.
What the district layer actually does for you
Once you have added the layer, the regional director's span shifts from unit general managers to district managers. Four district managers, each running four to six units, is a healthy shape for a twenty-unit region. That gives you a direct span of four, which sounds small, but the actual work each district manager brings to your one-on-one is much heavier. You are not talking about one unit. You are talking about six units, ranked, with patterns, with a bench conversation, with a capital ask. The thirty minutes is fuller, not lighter.
The district manager also becomes the coaching surface for the general managers. Your one-on-ones stop being about last week's labor and start being about the six-month arc for a market. You become the second-brain for a leader who has their own portfolio. That is a different conversation, and it is what makes the regional seat feel like a regional seat, rather than a very tired general manager multiplied by twenty.
What happens if you refuse to add the layer
I have seen operators resist the district structure for two reasons, both wrong. The first is cost. A district manager is a real headcount, real salary, and it looks like an expense line without an obvious return. The math is deceptive because the loss you avoid is invisible. A region that drifts one and a half points on prime cost across twenty units is losing more per year than the salary of two district managers. You do not see that loss as a line item. It hides in the P&L as "the region underperformed."
The second is identity. Some regional directors like being close to the units. They like knowing every general manager well. Adding a layer feels like being moved further from the work. That is real, and it is uncomfortable, and it is also the job. The regional seat exists to see patterns and make capital calls. The unit-level warmth is a district manager's job, and if you insist on holding it, you are running a district, not a region. Somebody will notice, and it will be your director.
The point
Span of control is a math problem the operator dressed up as a leadership problem. The math is 8 to 12 direct reports, adjusted down for complexity, geography, format variation, and system maturity. Bigger numbers on paper are almost always the sign of either a hidden district layer or a coaching function that has been quietly abandoned.
The strongest multi-unit operators I know are the ones who ask for a smaller span and do the work fully, then earn the next expansion. The weakest are the ones who took the bigger scope for the resume and ran a diluted job that hurt every unit in it. Choose the first path. Cadence beats charisma, and cadence needs time in the calendar to exist.