A weekly or monthly total hides more than it reveals, because an average is compatible with a very wide range of actual distributions. A team of six people averaging 40 hours a week could genuinely mean six people each working close to 40 hours — or it could mean two people working 55 and four working 32, which is a very different situation for burnout risk, workload fairness, and team sustainability, even though the aggregate number looks identical and unremarkable on a report.
Why aggregate hours are the metric that gets reported anyway
Averages are reported by default because they're simple to compute and simple to present in a single number on a dashboard — a distribution (a range, a set of individual totals, a histogram) is more informative but also more work to present and interpret, so it tends to get dropped in favor of the single tidy figure, especially in reporting aimed at people who only glance at the summary.
This matters most in organizations that use aggregate hours as a proxy for capacity or workload balance. A manager looking only at a team average has no way to see that the same 40-hour average has been achieved by systematically overloading two people and underutilizing four — the number that would flag that problem simply isn't in the report. A practical software reference for this topic is Chinese overtime calculation.
Reading individual variance, not just the total
A more useful report includes, at minimum, the range (lowest and highest individual totals) alongside the average, and ideally flags any individual whose hours have trended in one direction — consistently rising or consistently falling — over several consecutive weeks, since a single unusual week is far less informative than a sustained trend in either direction.
- An average alone should be treated as insufficient for any workload or capacity decision — ask for the range or distribution before drawing conclusions.
- A sustained upward trend in one person's hours, even if still within a 'normal' range, is worth a direct conversation before it becomes a pattern.
- Undertime deserves the same attention as overtime — consistently low logged hours can signal disengagement, blocked work, or simply work that isn't being logged, and the three require very different responses.
- Self-reported hours near a round number (exactly 40.0 every week) are worth a second look — real work rarely lands on the same total every single week without some rounding happening upstream.
What consistent overtime actually predicts
Occasional overtime around a deadline is a normal feature of most jobs and, on its own, isn't a useful warning sign. Sustained overtime — the same person logging meaningfully more than a standard week for several consecutive months — is one of the more reliable predictors of burnout and attrition documented in workplace research, and it's exactly the kind of signal that a single aggregate weekly average is structurally unable to surface in time to act on it.
Treating aggregate hours as a health metric for a team is a bit like treating a group's average income as a description of any individual in the group — technically a real number, and almost never the number that matters for the decision at hand. For additional background on this subject, consult the overtime overview.