What are Man-Hours?
Man-Hours
A man-hour, or person-hour, is the amount of work one person can do in one hour, the base unit teams use to estimate task size and plan how much work available people can absorb.
A man-hour, also called a person-hour, is the amount of work one person completes in one hour. It's the base unit behind two everyday planning questions: how big is this task, and how much work can the team take on this week.
Man-hours measure effort, not money and not billing. Multiplying man-hours by an hourly rate produces labor cost, what that time costs the business. Separating out which of those hours get invoiced to a client produces billable hours. Man-hours sit underneath both: the raw count of hours a task or a project takes, before anyone applies a rate or a billing rule to it.
Teams use man-hours in two places. In estimation, a task gets sized in man-hours before anyone assigns it to a specific person, "this feature is about 24 man-hours," independent of who ends up building it. In capacity planning, a team's available man-hours for the week, people multiplied by productive hours per person, sets the ceiling on how much of that estimated work can get scheduled.
Man-Hours vs Labor Cost vs Billable Hours
These three related terms build on each other, from a raw unit of time to a dollar figure to a billing decision.
| Term | What it measures | Formula |
|---|---|---|
| Man-hours | Raw effort: how much time a task takes | People x hours worked |
| Labor cost | What that time costs the business | Man-hours x hourly rate |
| Billable hours | Which of those hours get invoiced to a client | Man-hours tagged as billable x billing rate |
How Man-Hours Are Used in Estimation
Estimating in man-hours separates the size of a task from who ends up doing it. A task estimated at 40 man-hours could be one person working for a week, two people working for two and a half days each, or a mix, the estimate describes the total effort, not a specific schedule.
This matters because man-hours aren't always freely interchangeable across people. Adding a second person to a 40-man-hour task rarely finishes it in exactly 20 hours; ramp-up time, coordination, and work that genuinely can't be split, one person reviewing another's draft, for instance, eat into the theoretical savings. Treating man-hours as perfectly divisible is one of the more common estimation mistakes on tasks that don't parallelize well.
Man-Hours and Capacity Planning
On the planning side, man-hours set the ceiling for how much work a team can take on in a given period. A person working a 40-hour week rarely has 40 man-hours of project capacity available, meetings, admin, and normal interruptions typically take up 20 to 30% of a working week, leaving something closer to 28 to 32 productive man-hours.
At the team level, this adds up quickly. An 8-person team, each with roughly 30 available man-hours a week, has about 240 man-hours of weekly capacity, not the 320 that a plain headcount-times-40 calculation would suggest.
How to Calculate Total Man-Hours for a Project
The calculation is additive: list every task, estimate the man-hours each one requires, and sum them across the whole project. Tasks that involve more than one person, a design review, a client call with three attendees, count the hours for every person in the room, not only the hours the meeting lasted.
A one-hour client call with the PM, a designer, and a developer is three man-hours, not one, even though it occupies a single hour on everyone's calendar.
A Worked Example: Estimating a Landing Page in Man-Hours
A small project estimated in man-hours before it's assigned to specific people on the team.
| Task | Man-hours |
|---|---|
| Discovery call and brief review (3 people x 1 hour) | 3 |
| Wireframe | 6 |
| Visual design | 10 |
| Copywriting | 4 |
| Front-end build | 14 |
| QA and revisions | 5 |
| Client review call (2 people x 0.5 hour) | 1 |
| Total | 43 |
The Limits of Man-Hours as a Measure
Man-hours assume effort adds up in a straight line, and it doesn't always. Fred Brooks's well-known observation from software project management, adding people to a late project often makes it later, holds because new people need time to get productive and existing people spend hours bringing them up to speed, hours that don't show up in the original estimate.
Man-hours also don't capture skill differences. A task estimated at 10 man-hours might take a senior developer 6 hours and a junior developer 14. The unit is useful for comparing task size and planning aggregate capacity; it's a poor tool for predicting how long a specific individual will take on a specific task.
In Melororium
See total man-hours by project and person in Melororium
Common mistakes with man-hours
What teams get wrong most often, and what to do instead.
- 1
Assuming man-hours split evenly across any number of people
Estimating a task at 40 man-hours and assuming 4 people finish it in a day. Coordination overhead and work that can't be parallelized mean the real number is almost always higher than the simple division.
- 2
Planning capacity against scheduled hours, not available ones
Counting a 40-hour work week as 40 man-hours of project capacity. Meetings, admin, and normal interruptions typically remove 20 to 30% of that before any project work starts.
- 3
Never comparing estimated man-hours to logged man-hours
Estimating every task but never checking the estimate against what got logged once the work finished. Without that comparison, estimates don't improve project over project.
- 4
Using one man-hour rate for everyone regardless of skill
Treating a man-hour from a senior specialist and a man-hour from a new hire as equivalent units of output. They're equal units of time, not equal units of work completed.
Frequently asked questions
What's the difference between a man-hour and a billable hour?
A man-hour measures raw effort, one person working for one hour, regardless of whether that time gets charged to a client. A billable hour is the subset of hours that appear on an invoice. Internal meetings and admin time count as man-hours but rarely count as billable hours.
Is 'man-hour' the same as 'person-hour'?
Yes, interchangeably. Person-hour is the gender-neutral term for the same unit and has become the more common phrasing in recent years, though man-hour remains widely used in construction, engineering, and older project management literature.
How do you turn man-hours into a project cost?
Multiply man-hours by an hourly rate. If a task takes 40 man-hours and the blended rate is $75 an hour, the labor cost is $3,000. See labor cost for how that calculation works across a whole project with different rates per person.
Can 10 man-hours always be done by one person in 10 hours or 10 people in 1 hour?
In theory, and rarely in practice. Some work divides cleanly, 10 identical data-entry tasks split across 10 people. Most creative and technical work doesn't: a single design decision, code with internal dependencies, or a document one person has to write coherently resists being split, no matter how many people are available.
How many man-hours does a full-time employee provide in a week?
A standard week is 40 hours, but productive, project-available man-hours typically run lower, 28 to 32 hours once meetings, admin, and normal interruptions are subtracted. Teams that plan capacity against the full 40 tend to overcommit without noticing why.
