What it means
The measure sounds simple but depends entirely on what counts as an hour worked. Paid holiday, sick leave and training are usually excluded so that the figure reflects productive time, while overtime is included because it is real work.
Writing the definition down matters more than the exact choice, because comparisons across teams or years are meaningless if the rules keep shifting. It matters because headcount on its own hides a great deal.
Two departments of 40 people each look identical on an organisation chart, yet one may be working 1,900 hours a head and the other 1,400, a difference of 40 x 500 = 20,000 hours a year. That gap eventually shows up as overtime cost, turnover and missed deadlines.
Finance teams pair the measure with revenue and cost per hour to see whether extra output is coming from more people or from the same people working longer. Human resources teams use the trend to flag burnout, since a steady climb in hours per head almost always precedes a rise in sickness absence and resignations.
Operations teams use it to size recruitment ahead of a busy season. The number is only comparable when headcount is expressed in full time equivalents.
Counting someone who works two days a week as a whole employee drags the average down and makes a stretched team look comfortable. Averages also hide distribution, so a team can post a healthy figure while three individuals carry a punishing load.
A common variant is contracted hours against actual hours, and the gap between them is the interesting part. If contracted hours are 1,725 a year and actual hours come in at 1,900, the business is running on overtime that will not last indefinitely.
In practice
Real-world examples.
Example
A hospital trust finds its radiography team averaging 1,980 hours a year against 1,725 contracted, almost entirely from overtime. The finance director calculates that hiring two more radiographers would cost less than the premium overtime rate being paid.
Example
A software firm sees average hours per employee fall from 1,700 to 1,480 after a hiring push while revenue stays flat. The chief operating officer concludes the company over-hired rather than that the team suddenly became less productive.
Example
A seasonal food producer tracks the measure monthly rather than annually. It spikes to 220 hours per employee in October, prompting the plant manager to bring temporary staff in three weeks earlier the following year.
Think of it
“Hours worked shows actual working time per person-how much employees are working.
Formula
Calculation
Hours worked per employee = total hours worked in the period / average full time equivalent headcount
A logistics company records 249,600 hours worked across a financial year and employs an average of 160 full time equivalent staff. Hours worked per employee = 249,600 / 160 = 1,560 hours.
To judge whether that is high, compare it with contracted time. A 37.5 hour week across 46 working weeks, after holiday and public holidays, gives 37.5 x 46 = 1,725 contracted hours. At 1,560 actual hours the company is running at 1,560 / 1,725 = 90% of contracted time, which points to absence or idle capacity rather than overwork.Case study
Seen in the real world.
The following is an illustrative and fictional case. Kestrel Precision Tools, an invented components maker with 210 employees, had grown revenue 22% over two years without adding a single member of staff. Its board treated that as a productivity win until the human resources director presented hours worked per employee alongside the revenue chart.
Actual hours had risen from 1,680 to 2,016 a head, an increase of 20%, so nearly all of the extra output had come from longer hours rather than better methods. Sickness absence had risen by a third over the same period, and two of the four shift supervisors had resigned in the final quarter.
In this fictional outcome Kestrel recruited 24 additional operators, which brought total hours of 210 x 2,016 = 423,360 down to 423,360 / 234 = roughly 1,809 hours a head. Overtime savings covered most of the new salaries, and the invented company's board added the measure to its monthly reporting pack.
Watch out
Common mistakes.
- Dividing by raw headcount instead of full time equivalents, which understates how hard the full time staff are actually working.
- Including paid holiday and sick leave in the hours figure, so the measure stops showing productive time at all.
- Reading a comfortable average as evidence that nobody is overloaded, when the distribution behind it may be badly skewed.
Questions
People also ask.
Is a higher figure always better?
No, because beyond a point extra hours buy less output each and bring absence, errors and turnover with them.
How often should the measure be reviewed?
Monthly for operational teams with seasonal swings, and quarterly for stable office based functions.
What counts as a normal annual figure?
It varies widely by country and sector, so the useful comparison is against your own contracted hours and your own trend rather than an external benchmark.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related