Understanding Man-Hours in Project Planning
Man-hours represent the cumulative work time across your entire team. If five people each work 8 hours on a task, that's 40 man-hours of effort—regardless of whether they worked simultaneously or in shifts. This metric is essential for:
- Resource allocation: determining if you have enough staff to meet deadlines
- Budget forecasting: calculating payroll for a fixed project scope
- Capacity planning: understanding how many concurrent projects your team can handle
Many organizations track man-hours to compare actual costs against estimates, identify productivity bottlenecks, and justify staffing decisions to stakeholders. In construction, consulting, and software development, accurate man-hour tracking directly impacts profitability.
Man-Hours and Cost Formulas
Two straightforward relationships drive project costing: first, total man-hours multiply workforce size by individual work time; second, total cost multiplies man-hours by the hourly wage.
Man-hours = Number of people × Hours per person
Total cost = Man-hours × Hourly pay
Cost per person = Hourly pay × Hours per person
Man-hours— Sum of all working hours contributed by the entire teamNumber of people— Total workers assigned to the projectHours per person— Duration each individual spends on the taskHourly pay— Wage rate per hour for each workerTotal cost— Complete labor expense for the project
Common Pitfalls in Man-Hour Estimation
Avoid these frequent mistakes when planning labor costs and timelines.
- Ignoring overhead and indirect time — Man-hours often exclude meetings, training, administrative work, and context-switching. A team member may bill 40 hours per week but spend only 30 hours on billable client work. Always factor in a realistic efficiency ratio—typically 70–85% of clocked time is productive.
- Assuming linear scalability — Doubling the workforce doesn't halve project duration. Communication overhead, dependencies, and onboarding friction mean additional staff may temporarily slow progress. Use historical data from similar projects to predict actual completion time.
- Forgetting benefits and payroll taxes — Hourly pay is only the base wage. Most employees cost 25–40% more once you include employer taxes, insurance, benefits, and equipment. Use fully-loaded labor rates when budgeting to avoid cost overruns.
- Mixing experience levels without adjustment — Senior engineers and junior contractors rarely contribute equal value per hour. Assign different hourly rates based on seniority, or track man-hours separately by skill level to reflect actual productivity differences.
Real-World Applications
Project managers use man-hour calculations to bid on work, monitor spending, and adjust team size mid-project. For example:
- A web design firm quotes £12,000 for a website redesign. At £75/hour, that's 160 billable man-hours. If three designers work equally, each should allocate roughly 53 hours.
- A manufacturing plant completing a production run expects 500 man-hours. With 10 operators working 8-hour shifts, the job takes 6.25 days of round-the-clock staffing.
- A consulting engagement budgets £50,000 for research and analysis. At an average blended rate of £150/hour, the team has 333 man-hours to deliver value before hitting margin limits.
Tracking actuals against these estimates reveals whether your estimation process is reliable and where inefficiencies hide.