β±οΈ Man-Hours Calculator
Total labor hours from crew size and schedule.
Total man-hours
Estimates for planning only, not financial advice.
A man-hour is one hour of work by one person, and it is the fundamental unit of project estimation. Six workers, 8 hours a day, 22 days: 1,056 man-hours. Multiply by the loaded hourly rate and you have the labor budget; divide by crew size and you have the schedule. This calculator converts crew and calendar into total man-hours, man-days, and estimated labor cost.
Every failed project estimate traces back to fuzzy labor math. Hours are where optimism hides: tasks expand, productivity varies, and coordination eats the gains of bigger crews. Putting the arithmetic in the open is the first defense.
How to Use This Calculator
Enter the crew size, hours per workday, number of workdays, and optionally the hourly labor rate. The calculator returns total man-hours plus man-days, hours per worker, and labor cost.
Enter the number of workers and hours per day for the crew.
Enter the number of workdays in the schedule.
Add the hourly rate for a labor cost estimate. For pricing the finished work, our freelance rate calculator sets rates that cover real costs.
The Formula
The loaded rate is the number that matters. Wages are only the start: payroll taxes, workers' comp, benefits, and overhead ride along. A $35 wage with a 1.6 burden multiplier is $56 per man-hour, which turns the default 1,056 hours into $59,136 of labor cost, not the $36,960 the wage alone suggests.
Estimating Realistically
| Adjustment | Typical factor | Effect on 1,056 hrs |
|---|---|---|
| Productive time only | 70% of paid hours | Need 1,509 paid hours |
| Coordination overhead, large crew | +10 to 20% | 1,162 to 1,267 hrs |
| Contingency, familiar work | +10% | 1,162 hrs budgeted |
| Contingency, novel work | +25% | 1,320 hrs budgeted |
The productive-time row is the one estimators skip and regret. If only 70 percent of paid hours are time on task, a 1,056 productive-hour job needs 1,509 paid hours of crew time. Bid the productive number at the wage rate and the job loses money before it starts. For service businesses turning hours into invoices, our invoice generator keeps billing clean.
Worked Example
With the defaults: 6 workers x 8 hours x 22 days = 1,056 man-hours, or 132 man-days. Each worker contributes 176 hours. The crew delivers 48 hours per day. At a $35 hourly rate the estimated labor cost is 1,056 x 35 = $36,960 in wages, which a 1.6 burden multiplier would lift to about $59,136 all-in. Cutting the crew to 4 workers stretches the same 1,056 hours over 33 days, showing the direct trade between speed and headcount.
Tracking Against the Estimate
The estimate is only half the system. Collect daily hours by task, compare actuals to the estimate weekly, and investigate any task running 15 percent over while there is still time to recover. Patterns across jobs are gold: if electrical always runs 20 percent over, the next estimate fixes itself.
My rule: estimate in productive hours, bid in paid hours, and track in both. The three numbers tell you respectively what the work needs, what it costs, and where your estimating went wrong. Teams that keep all three get sharper every quarter; teams that keep one keep guessing.
Estimating Man-Hours Before the Job Starts
Prospective estimation is where the money is. Break the project into tasks, estimate each in man-hours from historical data or published production rates, then add contingency: 10 percent for familiar work, 25 percent or more for novel work. Multiply by your loaded labor rate, which includes wages, benefits, insurance, and overhead, often 1.5 to 2 times the hourly wage. That loaded rate times man-hours is your labor budget.
The classic errors are estimating with your best worker's pace instead of the crew average, forgetting non-productive time like setup, cleanup, and weather delays, and letting scope creep add tasks without adding hours. Track actuals against estimates on every job and refine your rates; a contractor whose estimates run 15 percent light will slowly go broke while staying busy. For pricing the job once hours are set, our freelance rate calculator builds the rate from costs up.
Man-Hours and the Mythical Man-Month
Fred Brooks showed decades ago that man-hours are not interchangeable: adding people to a late software project makes it later, because communication overhead grows with the square of team size while output grows linearly at best. The same applies to any complex, interdependent work. Nine women cannot make a baby in one month, and nine developers cannot ship a nine-month project in one.
The practical fix is smaller teams, clearer interfaces between workstreams, and estimates built from the actual crew, not an idealized one. For divisible, independent work like data entry or harvesting, man-hours scale fine. Know which kind of work you are estimating before doing the multiplication.
Estimates for planning only, not financial advice.Frequently Asked Questions
How do you calculate man-hours?
Multiply the number of workers by hours per day by number of days. Six workers at 8 hours a day for 22 days is 6 x 8 x 22 = 1,056 man-hours. The unit counts every hour of human labor, so two people working one hour equals two man-hours.
What is the difference between man-hours and man-days?
A man-day is one worker for one full workday, usually 8 hours. Man-hours are finer-grained: 1,056 man-hours at 8-hour days equals 132 man-days. Use man-days for rough scheduling and man-hours when costing, since overtime and partial days only show in hours.
Why do project managers track man-hours?
Because labor is the largest cost on most projects and the unit everything else hangs on. Estimates in man-hours convert directly to cost via the hourly rate, to schedule via crew size, and to bids via historical productivity. A bid without man-hour math behind it is a guess.
How do man-hours convert to project duration?
Divide total man-hours by daily crew hours. A 1,056 man-hour job with 6 workers at 8 hours a day needs 22 days. Double the crew to 12 and the math says 11 days, though in practice coordination overhead means doubling people rarely halves the time, the classic Brooks's Law effect.
Should overtime count as extra man-hours?
Count actual hours worked, so overtime hours are man-hours too, but cost them at the overtime rate. Ten overtime hours at time and a half cost 15 straight-time hours of budget. Mixing the two without the rate adjustment is how labor budgets silently overrun.
What is a productive man-hour versus paid man-hour?
Paid hours include breaks, setup, weather delays, and rework; productive hours are time on task. Construction studies often find 60 to 75 percent productive time. Estimate with productive hours but budget with paid hours, or the bid wins the job and loses the money.
How do you estimate man-hours for a new project?
Break the job into tasks, estimate each from historical data or published productivity rates, and sum them. Then add contingency: 10 percent for familiar work, 25 percent or more for novel work. Bottom-up beats top-down guessing every time because errors surface per task instead of hiding in a total.
Do man-hours include supervision and management?
Track them separately. Direct man-hours build the product; indirect hours manage it. Bids usually carry supervision as a percentage of direct hours or a fixed weekly cost. Blending them understates the true cost of both.
What is the man-hour rate on a construction bid?
The all-in hourly cost: wages plus payroll taxes, insurance, benefits, small tools, and overhead allocation. A $35 wage can easily be a $55 to $65 man-hour rate loaded. Bidding at the wage rate instead of the loaded rate is the fastest way to lose money on every job.
How do you track man-hours during a project?
Daily timesheets by task code, ideally submitted the same day. Weekly, compare actual hours per task against the estimate to catch overruns while recovery is still possible. The estimate is a hypothesis; the timesheet is the experiment.