Hours per person calculator
Team totals hide individuals. Sixteen hundred hours across ten people sounds ample. Then one of them turns out to be carrying three projects, so this divides the pool down to one person's share.
Fill in every field to see the result.
How to use it
Step 1
Set up the period exactly as the capacity calculator does: headcount, contracted day, working days, leave and holidays.
Step 2
Read the per-person figure rather than the total. That is the share one average person holds for the period.
Step 3
Compare it against the largest commitment any one person already carries.
Step 4
Where somebody's commitment beats their share, the plan is short a person or long a project, and no amount of averaging fixes it.
Step 5
Run a long absence on its own. One person away for three weeks hurts more than a team average shows.
Step 6
Hold back time for meetings and handovers, and plan a smaller share for new joiners while they ramp up.
Questions people ask
Why look at a per-person figure at all?
Because totals hide the constraint. A team can hold plenty of hours in aggregate. Meanwhile the one person who knows the payment code is booked solid, and the average never shows it.
How should part-timers be handled?
Run them separately. Mixing a four-hour day and an eight-hour day into one average produces a share that fits nobody on the team.
Does PeopleMuster show this per person?
The capacity grid shows each person by day, with a monthly total beside them. Per-person load is read directly there rather than averaged out of a team figure.