Manpower Loading and Resource Leveling for Construction

From budgeted hours to weekly headcount

Manpower loading converts your labor budget into a forecast of how many workers you need on site each week. The math starts simple: take the budgeted hours for an activity, spread them across the weeks the activity is scheduled to run, and divide by the productive hours per worker per week.

A clean worked example: say a scope carries 2,000 budgeted labor hours and is scheduled over 5 weeks. That is 400 hours per week. At roughly 40 productive hours per worker per week, you need about 10 workers on that scope each week. Do that for every activity in the schedule, add them up week by week, and you have a manpower curve for the whole job.

Peak crew size and the site's real limits

When you sum every activity's weekly demand, the busiest week defines your peak crew size — the maximum number of workers you need on site at once. That single number drives a lot of decisions: parking and facilities, lift and hoist capacity, lay-down and work-area congestion, and whether the labor market can even supply that many of the right trades when you need them.

Peak crew size is also a sanity check on the schedule. If the math says you need 60 ironworkers in week 12 and you can realistically field 35, the schedule is fiction. Better to find that out from the manpower plan months ahead than from a crew that never shows up. The peak is where schedules quietly break.

Resource leveling: smoothing the curve

Raw manpower demand is almost always jagged — a spike here, a valley there — because activities pile up in some weeks and thin out in others. A jagged curve is expensive and unrealistic. It means hiring and laying off in waves, paying to mobilize and demobilize crews, and competing for trades you can only hold if you keep them busy.

Resource leveling reshapes the work to flatten that demand without blowing the schedule:

• •Shift non-critical activities within their float so they fill the valleys instead of stacking on the peaks.
• •Stretch or compress activities where the duration is flexible, trading a slightly longer task for a steadier crew.
• •Re-sequence work so trades flow continuously from area to area instead of arriving, leaving, and coming back.
• •Set a target ceiling — the headcount you can realistically staff — and reshape demand to live under it rather than assuming you can hire to the spike.

The manpower curve and the S-curve are the same data

Your manpower curve and your hours-based S-curve are two views of one dataset. The manpower plan is the per-week labor demand; the S-curve is that same labor accumulated over time. When you level the manpower curve, you are also shaping the S-curve — a smooth, leveled crew produces a clean S, while a spiky crew produces a curve with jumps that are hard to manage and harder to fund.

That connection matters in execution. If your actual S-curve is lagging the plan, the fix is almost always in the manpower plan: ramp the crew, or you will never close the gap during the steep middle of the job. If the actual curve is rising too fast without matching progress, you are overstaffed for the work in front of you. Read them together.

In Field PM, manpower loading is built from the same budgeted hours that feed job costing and the PM dashboard, so your headcount forecast, your S-curve, and your labor budget all reconcile instead of living in three different spreadsheets. The contractors who staff jobs well are not guessing — they are reading a leveled curve they built from real numbers.