Summarise with AI
What a workable span looks like
There is no single correct number, and published rules of thumb (often "five to seven") come from salaried office environments that look nothing like a venue or a warehouse. What actually sets the range is how much of the manager's attention each report needs.
- Narrow (3–7) — complex, variable or high-risk work, or staff who are new
- Moderate (8–15) — established teams doing similar work with clear procedures
- Wide (15+) — routine, standardised work with experienced staff and good systems
Shift-based businesses often run wide spans successfully, because the work is standardised and the rostering system carries much of the admin load.
The hidden multiplier in shift work
A shift-based manager's real span is not their headcount — it is their headcount multiplied by roster churn. A manager with 25 reports across a fortnight, each with availability changes, swap requests and leave, is handling far more interactions than a manager of 25 salaried staff.
That is why the practical limit moves with your systems. Approving swaps by text message caps a manager at roughly a dozen. The same manager can run 30 when availability, swaps and timesheet approval are self-service.
Warning signs it is too wide
- Timesheets and leave approvals consistently late
- New starters not getting inducted properly, showing up as 90-day turnover
- The manager working shifts themselves to cover gaps
- Staff escalating past their manager because they cannot get a response
- Rising absence concentrated in one team
Key takeaways
- Span of control is direct reports per manager — there is no universal right number
- Complexity and staff experience set the range, not a rule of thumb
- In shift work the real load is headcount multiplied by roster churn
- Better self-service systems widen the span a manager can handle
RosterElf lets managers approve timesheets, leave and swaps for their own team only, so a wide span stays workable.
Try RosterElf free