👷 Operations guide

How to Calculate Man Hours

Man hours — or labor hours — measure the total work time contributed by a team to a task, project, or shift. This guide covers the core formula, a full calculation waterfall with labor cost and efficiency factor, step-by-step instructions, four worked examples aligned with the calculator's presets, how efficiency affects effective hours, and the most common mistakes in labor planning.

Last updated: March 28, 2026

What are man hours?

A man hour — also written as labor hour or person-hour — is one unit of work performed by one worker in one hour. When you multiply workers by time, you get a single number that captures total labor effort regardless of how many people were on the team or how long the project ran.

Five workers putting in 8 hours each produce 40 man hours. One worker putting in 40 hours produces the same 40 man hours. The metric normalizes team effort so you can compare projects, estimate staffing needs, calculate labor cost, and track whether actual effort matched what was planned.

🏗️
Construction & field work
Crew hours for site tasks, framing, electrical runs, and project phases. Efficiency factor critical for field conditions.
🏭
Manufacturing & operations
Labor input per production run, shift scheduling, overtime planning, and labor cost per unit.
💼
Project management
Estimating effort for project phases, comparing planned vs actual, and resource allocation across teams.
🖥️
Knowledge work
Sprint capacity in software development, consultant billing, design estimates, and writing engagements.

Man hours formula

The core formula is:

Man Hours = Workers × Hours per Day × Working Days
Workers = number of people contributing labor
Hours per Day = productive hours worked per person per day
Working Days = calendar days excluding weekends and holidays

The calculator also computes three derived metrics using the same inputs:

Worker-Days = Man Hours ÷ Hours per Day
Hours per Worker = Hours per Day × Working Days
Effective Man Hours = Man Hours × Efficiency Factor (%)
Total Labor Cost = Man Hours × Hourly Rate

Full calculation waterfall — standard workweek preset

Default preset: 5 workers · 8 hours/day · 5 working days · $25/hr · 100% efficiency:

Workers 5
× Hours per day 8 hrs
× Working days 5 days
= Total man hours 200 hrs
÷ Worker-days (200 ÷ 8) 25 days
$ Labor cost (200 × $25) $5,000

The efficiency factor

One of the most useful — and most often ignored — aspects of man-hours planning is the efficiency factor. In practice, workers rarely produce at 100% for every minute of every shift. Field conditions, setup time, transitions, fatigue, and brief breaks all reduce the effective output per scheduled hour.

The calculator lets you apply an efficiency percentage. Effective Man Hours = Total Man Hours × Efficiency. Here are common benchmarks:

100% Full theoretical capacity Office work / knowledge work with minimal interruption. Rarely achieved in field or production settings.
80–90% Typical field work efficiency Construction and maintenance crews in normal conditions. The calculator's crew and shift presets use 80–85%.
70–80% Overtime or challenging conditions Extended shifts, adverse weather, complex task switching, or high-heat environments. The overtime preset uses 90%.
60–70% Low efficiency — investigate May reflect rework, equipment downtime, supply delays, or poor task design. Usually requires root cause review.

Always distinguish between scheduled man hours (the theoretical maximum) and effective man hours (what actually gets done). Using scheduled hours for project estimates without an efficiency factor consistently produces underestimates.

How to calculate man hours — step by step

1
Count the number of workers. Include all people contributing direct labor to the task or project during the measurement period. For mixed teams with different schedules, you can calculate each group separately and add the results.
2
Determine hours per worker per day. Use productive hours — typically 7–7.5 in an 8-hour shift after accounting for short breaks. For planning, use expected productive hours; for reporting actuals, use clocked hours.
3
Count the working days. Exclude weekends, public holidays, and planned shutdown days. For a 5-day work week, a two-week project = 10 working days.
4
Multiply: Workers × Hours per Day × Days. Example: 12 workers × 8 hrs × 20 days = 1,920 man hours. This is the scheduled man-hour total.
5
Apply an efficiency factor if needed. For field or production work, multiply by your efficiency percentage: 1,920 × 80% = 1,536 effective man hours. For knowledge work at 100%, skip this step.
6
Calculate labor cost if needed. Multiply total man hours (not effective man hours) by the average hourly rate: 1,920 × $35 = $67,200 total labor cost. You pay for scheduled hours, not just effective output.

Worked examples

Four scenarios aligned with the calculator's four presets — standard workweek, construction crew, overtime schedule, and 12-hour shift.

Example 1 · Standard workweek preset

5 workers · 8 hrs/day · 5 days · $25/hr

A small office or service team working a standard week at 100% efficiency.

Man hours = 5 × 8 × 5 = 200 hrs
Labor cost = 200 × $25 = $5,000
Worker-days = 200 ÷ 8 = 25 days

✓ 200 scheduled hours · $5,000 labor cost

Example 2 · Construction crew preset

12 workers · 8 hrs/day · 20 days · $35/hr · 80% eff.

A field crew over a 4-week project in typical outdoor conditions.

Man hours = 12 × 8 × 20 = 1,920 hrs
Effective = 1,920 × 80% = 1,536 hrs
Labor cost = 1,920 × $35 = $67,200

→ 384 hrs lost to field efficiency · $67,200 total cost

Example 3 · Overtime schedule preset

6 workers · 10 hrs/day · 6 days · $30/hr · 90% eff.

A compressed sprint week including Saturday with extended shifts.

Man hours = 6 × 10 × 6 = 360 hrs
Effective = 360 × 90% = 324 hrs
Labor cost = 360 × $30 = $10,800

→ 36 hrs lost to fatigue factor · $10,800 cost

Example 4 · 12-hour shift preset

4 workers · 12 hrs/day · 14 days · $28/hr · 85% eff.

Maintenance or security crew on extended 2-week rotation.

Man hours = 4 × 12 × 14 = 672 hrs
Effective = 672 × 85% = 571.2 hrs
Labor cost = 672 × $28 = $18,816

→ 100.8 hrs lost to shift fatigue · $18,816 cost

What to do with man hours after you calculate them

Man hours are an input, not a final answer. The most useful applications:

  • Labor cost estimation. Multiply man hours by your average hourly rate to get a total labor budget for the project or period. Add a 10–20% contingency for real-world variability.
  • Staffing requirement planning. If you know how many man hours a project requires, divide by hours per day and days available to find the minimum crew size needed.
  • Planned vs actual comparison. Estimate man hours before a project and track actuals during it. The variance reveals schedule overruns, efficiency problems, or scope changes early enough to act on.
  • Output per labor hour. Divide total output (revenue, units, orders) by total man hours to get productivity per hour — a consistent benchmark across teams with different sizes and schedules.
  • Bid and quote preparation. Service businesses quote labor cost from man-hour estimates. A 5% variance in the man-hours estimate translates directly to a 5% variance in the labor line of a quote.

Common mistakes to avoid

  • Confusing headcount with man hours. A crew of 12 working for 20 days is not 12 man hours — it is 1,920. Always multiply by both time dimensions.
  • Using 8 hours when productive hours are lower. An 8-hour shift typically yields 7–7.5 productive hours after breaks. Using 8 hours for planning consistently overestimates available capacity.
  • Ignoring the efficiency factor for field or production work. At 80% efficiency, a 100 man-hour job takes 125 scheduled hours to complete. Ignoring this gap is the most common cause of budget and schedule overruns.
  • Not adjusting for different worker schedules. If workers have different hours, calculate each group separately and add — do not use a simple average unless schedules are genuinely uniform.
  • Mixing planned and actual hours without labeling them. Planned man hours (estimates) and actual man hours (recorded) must be clearly labeled when comparing. Mixing them in a report makes the variance meaningless.
  • Assuming more man hours always means more output. Higher man hours can reflect inefficiency, rework, or scope creep — not necessarily more progress. Pair man hours with output measures to check whether effort is translating into results.

FAQ

What is the formula for man hours?

Man Hours = Workers × Hours per Day × Working Days. Worker-Days = Man Hours ÷ Hours per Day. Total Labor Cost = Man Hours × Hourly Rate. Effective Man Hours = Man Hours × Efficiency Factor.

Are man hours the same as labor hours?

Yes — in most practical business, project, and operations contexts, the terms are interchangeable. Some organizations prefer "labor hours" or "person-hours" as more inclusive language, but the calculation is identical.

Can man hours include overtime?

Yes. If workers put in overtime hours, include those hours in the total. Many organizations track regular and overtime hours separately for payroll purposes (since overtime is paid at a different rate), but both count toward total man hours for project planning and productivity analysis.

What is the efficiency factor and when should I use it?

The efficiency factor (%) accounts for the reality that workers do not produce at 100% for every scheduled minute — setup time, transitions, short breaks, and working conditions reduce effective output. Apply it for field work, production environments, and any setting where you need effective (productive) hours rather than just scheduled hours. Leave it at 100% for knowledge work or when tracking actuals from time sheets.

How many man hours are in a work year?

A standard US work year is approximately 2,080 hours (52 weeks × 40 hours). After accounting for 10 public holidays and 10 days of PTO, effective available hours are typically closer to 1,900–1,960 hours per worker per year. Multiply by your team size for total annual labor capacity.

Can man hours be used for non-physical work?

Yes — man hours apply to any type of labor: software development, consulting, design, writing, analysis, and customer support. In software development, story points are often used for sprint planning, but they are ultimately converted to hours for capacity and cost analysis.