What One Man-Hour Actually Represents
A man-hour is the labor of one worker for one hour — the smallest practical unit for pricing and planning work. Two workers for four hours, four workers for two hours, and one worker for eight hours all equal eight man-hours, which is why the unit lets you compare crew plans directly. Total man-hours stay the same no matter how you split the work across people or days; only the calendar duration changes.
The standard equation is crew size x hours per worker per day x working days. This calculator's defaults — 5 workers, 8-hour days, 10 working days — produce 400 paid man-hours. Industry convention treats one man-day as 8 man-hours, so the same job is 50 man-days, and a full-time year at 40 hours a week comes to roughly 2,080 hours.
Man-hours measure labor input, not output. A 400 man-hour job finished in 10 calendar days with a 5-person crew and the same job finished in 5 days with 10 people consume identical labor. That distinction is what makes the unit useful for bidding, for schedule compression decisions, and for the safety-rate math every contractor reports.
Reading the Results: Hours, Man-Days, and Cost
The headline number is total paid man-hours: 5 x 8 x 10 = 400 with the defaults. Divide by 8 and you get 50 man-days, the unit many subcontractors quote — a crew-day price is simply the man-day count times a loaded daily rate. The result label stays in hours because hours are what payroll runs on and what OSHA logs are built from.
The efficiency factor converts paid time into productive time. At the 85% default, 400 paid hours contain 340 hours of direct task work; drop the factor to 70% and only 280 hours are productive. The gap between paid and productive hours is where estimators lose money on bids they won too cheap or pad budgets they misjudged in the other direction.
The cost line multiplies hours by your burdened rate. At $45 per hour, 400 paid hours cost $18,000, while the 340 productive hours within them account for $15,300. Reading both numbers side by side shows what each point of productivity is worth in cash — 5% of a 400 hour job is 20 hours, or $900 at that rate.
Paid Hours vs Productive Hours
Paid hours cover everything between clock-in and clock-out: breaks, toolbox talks, mobilization, waiting on materials, and rework. Productive hours cover only hands-on task time. Published estimating guides and most experienced superintendents plan construction work at somewhere between 65% and 85% productive time; numbers above that on a real site usually mean the measurement is generous.
The efficiency input exists so you can price the gap instead of pretending it away. At 70% efficiency, the default 400 hour job delivers 280 productive hours — the equivalent of losing three full worker-weeks to indirect time. If your time cards show 300 direct hours out of 400 paid, your true factor is 75%, and that measured number belongs in the next bid rather than the assumed one.
Rework is the quiet destroyer of productive hours. A job that requires 10% rework effectively burns one extra paid hour for every nine productive ones delivered. Track rework separately from breaks and mobilization where you can; the fix for each is different, and a blended average hides which problem you actually have.
Estimating Man-Hours Bottom-Up
Multiplication only helps once you know the total hours a job needs. Bottom-up estimating builds that total from unit rates: quantity of work x labor hours per unit. Hanging and finishing 2,000 square feet of drywall at 0.25 labor-hours per square foot is 500 man-hours — and a 5-person crew at 8 hours a day burns through that in 12.5 days (500 / 40).
Unit rates are strongest when they come from your own completed jobs. Divide actual man-hours by installed quantity on five to ten past projects and you have a rate that already carries your crews' real pace, break habits, and rework. For production lines, the same logic runs per machine: take the hours per unit implied by your cycle time calculator output and multiply by the batch size.
Sanity-check any bottom-up total against crew-day history before committing. If your drywall crew historically hangs 1,000 square feet per 32 man-hour crew-day, a bid assuming 1,300 square feet per crew-day is a schedule you cannot staff honestly. The man-hours calculator is the bridge: it turns a defensible unit rate into calendar days and a payroll number.
Man-Hours for Safety Metrics
OSHA incidence rates are normalized per 200,000 man-hours, which is 100 full-time workers laboring a 2,000-hour year (100 x 8 x 250 working days). That constant is why a plant with 40 employees and a 40-person construction crew can compare injury performance despite very different sizes. Without total man-hours, a recordable count is just an anecdote.
Example: a contractor logs 400,000 man-hours in a year and records 3 recordable injuries. The TRIR-style rate is (3 x 200,000) / 400,000 = 1.5. The same hours feed the DART calculation for days-away, restricted, or transferred cases — run your case count through the DART rate calculator once total hours are known.
Running totals matter mid-year, too. If your crews have burned 200,000 man-hours by June with 2 recordables, you are pacing at a 2.0 annualized rate — the signal to act before the OSHA 300 log gets worse. Man-hours pulled from payroll are the denominator for every one of these safety numbers, so keep the count as carefully as the cases themselves.
Crews, Shifts, and Overtime Trade-Offs
The same 400 man-hours can be shaped into different calendars: 5 workers for 10 days, 8 workers for 6.25 days, or 10 workers for 5 days. Compressing the calendar by adding workers keeps paid hours flat on paper but adds coordination, supervision, and congestion — the productive share usually dips as crews crowd the work face.
Overtime compresses differently: 5 workers moving to 10-hour days for 10 days produces 500 paid man-hours, a 25% jump in cost for at best a similar jump in output. Industrial studies repeatedly find that output per hour falls during sustained long weeks, so the productive-hours line grows slower than the paid-hours line. For shift design, compare schedules with the 8 hour shift calculator or the 12 hour shift calculator before committing to an overtime plan.
The decision framework is simple: adding workers trades money for calendar time at roughly constant man-hours; overtime trades money for calendar time at rising man-hours. Pick the lever that matches your constraint, then re-run the calculator with the new crew size or hours so the cost of the compression is a number you chose, not one you discover later.
From Man-Hours to Labor Cost
Man-hours become budget the moment you attach a burdened rate. The burden is everything beyond base wage: payroll taxes, workers' compensation, unemployment insurance, benefits, and small tools. Many contractors carry a burden multiplier between 1.3 and 1.5, so a $30 wage becomes a $39 to $45 burdened rate — the number that belongs in this calculator's rate field.
The default math: 400 paid man-hours at $45 equals $18,000, and the 340 productive hours within it carry $15,300. That $2,700 difference is the price of normal indirect time, priced per job instead of hiding in overhead. For a deeper breakdown including per-unit labor cost, feed the same hours into the labor cost calculator.
Service businesses run the identical conversion with billable time. A consulting team that fields 400 paid hours but bills 340 has 85% utilization, and every non-billed hour is revenue the rate never captures — the same arithmetic consultants and attorneys apply with the billable hours tool. Whether the hours are hammered or billed, the math of paid versus productive never changes.
Tracking Actuals and Converting Units
A man-hours estimate is only as good as the actuals that check it. Collect hours from time cards weekly — the time card calculator converts clock in and clock out records into paid hours — and compare cumulative actuals against the 400-hour plan. A 20% overrun at 40% completion is a schedule problem you can still fix; found at 90%, it is a write-off.
Conversions keep reporting consistent. 400 man-hours is 50 man-days, 0.19 of a full-time-equivalent year (400 / 2,080), or 10 worker-weeks at 40 hours. For staffing and budget roll-ups, translate crew hours with the full time equivalent calculator; for calendar planning, pair the day count with the working days calculator to land on real dates.
Keep one hours log per project rather than mixing jobs, and total it the same way every week — the hours calculator keeps daily entries consistent. Bidders who can produce three years of man-hour actuals by task type estimate tighter than any guidebook, and they can defend the number when an owner pushes back on it.