By Andreas Pettersson, Founder, Leaders ADAPT
Count the one-on-ones on your calendar this week. Now count the people who left the last one feeling heard, and could not tell you what done looks like. If the two numbers match, you don't have a direct reports problem. You have a calibration problem, and the org chart can't see it.
Most pages on this term stop at the dictionary. This one gives the definition, the hours per report arithmetic behind how many is too many (the US average hit 12.1 in 2025), and the four things the 1:1 Protocol says every report is owed.
Quick answer: A direct report is an employee who reports straight to a specific manager, with no one in between: that manager assigns their work, reviews it, and is accountable for their results. Indirect reports sit one or more layers below. How many a manager can carry depends on hours available per report, not on a fixed ratio; the average US manager had 12.1 direct reports in 2025 (Gallup, 2026).
What is a direct report?
A direct report is a person whose work is assigned, reviewed and answered for by one named manager, with no other manager between them on the org chart.
Three words in that sentence do the work. Assigned: the manager decides what the person owns. Reviewed: the manager sees the result and says whether it met the standard. Answered for: when the work is late or wrong, the manager's name is on it too.
If any of the three is missing, the line is decoration. A person whose work you review but whose priorities someone else sets is a shared report, and shared reports are where work goes to die. The accountability chart forces the question: one name per seat.
Direct report vs indirect report, dotted line and subordinate
| Term | Who it describes | Who assigns and reviews their work | Example |
|---|---|---|---|
| Direct report | Reports straight to you | You | Your head of sales |
| Indirect report | Reports to one of your direct reports | Their own manager, not you | The account executives under your head of sales |
| Dotted line report | Reports to another manager, works with you on a project | Their solid line manager; you give input | A marketer supporting your sales team half time |
| Subordinate | Anyone below you, direct or indirect | Depends on the layer | Legacy term |
"Managed a team of 40" usually means forty indirect reports. Six direct reports who each run six people is a different job from forty direct reports.
How many direct reports should a manager have?
The honest answer is arithmetic, not a ratio.
Gallup's January 2026 analysis of 16,442 US managers found the average number of people reporting to a manager rose from 10.9 in 2024 to 12.1 in 2025, a nearly 50 percent increase in team size since Gallup first measured in 2013 (Gallup, 2026). The same study found that employees who strongly agreed they had received meaningful feedback in the past week were highly engaged, about seven in ten, regardless of team size. Without it, one in four.
So the question isn't the right span of control. It's how many hours a week you can give each report.
The hours per report table
Take the hours you spend in one-on-ones and team meetings you run, add a half hour a week of unplanned contact per report, and divide by the number of reports. The span of control calculator runs this calculation; here it is by role type against a 40 hour week.
| Role type | Reports | Scheduled 1:1 hours per week | Unplanned contact (0.5 h each) | Hours per report | Share of a 40 hour week on direct contact |
|---|---|---|---|---|---|
| Team lead, individual contributors doing similar work | 8 | 4.0 (30 min each) | 4.0 | 1.0 | 20 percent |
| CEO or executive, direct reports are managers | 5 | 5.0 (60 min each) | 2.5 | 1.5 | 19 percent |
| Same CEO at 16 without a layer | 16 | 8.0 (30 min each) | 8.0 | 1.0 | 40 percent |
Read the last row. The manager didn't get worse; the calendar ran out.
At 16 reports, direct contact takes 40 percent of the week, and Gallup found managers spend a median 40 percent of their time on their own individual contributor work. Something gets skipped, and it's always the one-on-one, the only meeting nobody else is waiting on.
The span of control statistics page will publish what leaders entering the calculator carry; it sits below its 30 completion floor as of September 22, 2026 and refreshes October 12, so there is no first party figure yet.
What does a manager owe each direct report? The four things
Here's the problem with the glossary answer. "Assigning tasks, giving feedback, running reviews" describes a manager whose team leaves every 1:1 feeling heard and still doesn't know what done looks like. Four things fix that, straight from the Delegation Protocol and the 1:1 Protocol in The 5-Minute Leader.
1. An outcome, not a task
"Send the monthly report to the board" is a task. "The board has complete visibility into our performance and feels confident about our trajectory" is an outcome. When you delegate tasks, people remain waiters taking your order. When you delegate outcomes, they become owners building something.
The full handoff is in how to delegate.
2. A stated authority level
Level 1, decide and inform me after. Level 2, decide but tell me before you implement. Level 3, recommend options and I'll decide. Say the number out loud.
Ambiguous authority kills ownership; it's why a capable report routes every decision back to your inbox.
3. A calibration, not a status update
A status update asks what are you doing. Calibration asks how are you really. The status version trains people to perform "fine."
Calibration runs 40 percent on their agenda, 40 percent on your read of them, 20 percent on alignment, and one question does most of the work: on a scale of 1 to 10, what's your energy level right now? Below 7, ask what it would take to get to an 8.
If your one-on-ones have drifted, the fix is a check-in meeting with the weight put back, not more meetings.
4. Feedback inside 24 hours
Feedback has a half-life. After 48 hours, it's archaeology, not coaching. See it, name it inside a day, thirty seconds, no formal setup: "Quick feedback from yesterday. Got 2 minutes?"
Save it for a 1:1 five days out and you've taught the report the standard is negotiable.
How often should you meet with direct reports?
Frequency follows the person's state, not their level.
- Weekly, 30 minutes: new hires in their first 90 days, anyone drowning in a role they're not yet good at, anyone in a crisis or transition, a high performer you're stretching, and anyone whose energy answer dropped below 6.
- Every other week, 45 minutes: stable high performers, capable people who are bored, and experienced people with strong ownership.
- Monthly, 60 minutes: senior leaders with a proven track record, and people being transitioned out.
- The override: a personal crisis, a fresh promotion, or a sudden energy drop moves anyone to weekly.
And one rule for the founder with too many people and no managers yet: keep running the one-on-ones yourself, as short as 20 minutes every other week, before you hire a team lead to take them over. The one-on-one is where the culture transfers; hire the layer first and the new lead defaults to their own style. The agenda for one on one meetings with direct reports is on the one-on-one meetings page.
What do you do when you have too many direct reports?
Between employee thirty and seventy at Arcules, managers appeared between me and the work. Problems hid in layers. Information arrived filtered. My 1:1s became 1:1s about their 1:1s.
What worked at ten people broke at forty, and the fix wasn't to run my one-on-ones harder. I couldn't just delegate well. I needed my managers to delegate well. By the time we passed 150 people my week had gone from 60 hours to 45, because the layer worked.
Three moves.
Move 1: run the arithmetic honestly. Count the reports who actually come to you, not the ones on the chart. Over a third of your week on direct contact is a structural limit, and no time management trick fixes it.
Move 2: add a layer only after you've modeled the one-on-one. Hand the reports to the person who already gets the four things right, then check the cascade in your own 1:1s: what have you delegated this week, and how did you frame it?
Move 3: replace the 1:1s you gave up with skip-levels. Open with "This isn't about your manager. I want to understand your experience directly," then four things: what's working well, what's frustrating, what would you change, and is there anything you're not comfortable telling your manager. The skip-level meeting keeps you calibrating two layers down. The tripwire: three skip-levels in a row that say "I don't really know what I own" or "my 1:1s are just status updates" means the layer isn't working, and that's yours to fix.
One more test for remote managers under you: ask how many one-on-ones they had last week and what they learned. A remote manager who cannot name each direct report's energy level is meeting, not calibrating. That is the difference between a direct report and a name on a chart, and why the manager as coach role has to be learned before the team gets bigger.
Direct reports FAQ
Are direct reports the same as subordinates?
Not exactly. Subordinate is the older, broader term for anyone below a manager in the hierarchy, one layer down or five. Direct report is narrower: only the people who report straight to that manager, with no one in between. Most companies now say "direct report" or "team member," because those terms describe a working relationship rather than a rank.
What is the difference between a direct report and an indirect report?
A direct report reports straight to a manager, who assigns and reviews their work and is accountable for their results. An indirect report reports to one of that manager's direct reports, with at least one layer in between. A department head with five managers and forty staff has five direct and forty indirect reports.
How many direct reports is too many?
There is no fixed number that fits every role. The practical test is hours per report: scheduled one-on-one hours plus roughly half an hour a week of unplanned contact per person, measured against the working week. When direct contact passes about a third of the week, most managers stop meeting each report often enough to catch problems early. The average US manager had 12.1 direct reports in 2025 (Gallup, 2026).
Do contractors and virtual assistants count as direct reports?
On a legal org chart, usually not, because they are not employees. In practice, if a manager assigns their work, reviews it and answers for the result, they take the same hours per report as an employee and belong in the span count. Leaving them off is a common reason a calendar shows a heavier load than the org chart predicts.
How do you run one-on-ones with direct reports at scale?
Once direct reports are themselves managers, the leader's one-on-one changes job: it checks whether the manager's own one-on-ones are happening and what they surface. Common practice is a regular 1:1 with each manager plus periodic skip-level meetings with the manager's reports, framed as being about the employee's experience rather than a judgment of the manager.
The line on the chart is not the relationship
A direct report is a working agreement, not a box. The agreement has four terms: an outcome the person owns, an authority level they can say out loud, a one-on-one that reads how they're really doing, and feedback fast enough to still be useful. Get the count right and skip the terms, and a small team still won't know what done looks like. Get the terms right and the count becomes arithmetic plus one well chosen layer.
From your calendar count to a system your managers can run
The four things above are pieces of two protocols in The 5-Minute Leader, the system I wrote down after scaling a company to 150 people as one of Canon's youngest CEOs. Four protocols, one per week.
The Delegation Protocol makes the work stay handed off: outcome, authority level, read-back. The 1:1 Protocol surfaces problems early. The Accountability Protocol puts the standard where everyone can see it, so nobody chases. The Rhythm Protocol sets a cadence the team keeps running when you're out.
Part 2 cascades each one through your managers, including a two-by-two grid you fill in after every 1:1 that tells you who is about to leave before they've decided to.
Tomorrow morning, before your first meeting: count your real direct reports, put your real hours into the span of control calculator, and read the band you land in. Then hand your managers the protocols in The 5-Minute Leader and run the first one this week.
