Matching work to team capacity: Rostered hours minus leave and non-project work shows true project capacity.; Total assigned hours must not exceed available capacity in the same period.; Check software settings to ensure hours, not tasks, are being counted.
Image: Project Software Guide

Capacity Planning

Part of Project resource and capacity planning

Distinguishing assigned hours from actual team capacity

Calculate available project capacity, compare it with assigned hours and avoid double-counting leave or other work.

Assigned hours are planned demand. Actual available capacity is the time a person can reasonably offer for that work in the same period, after accounting for their roster, absence and other commitments. It remains a planning estimate, not a record of hours worked. An assignment total below a standard full-time week can therefore signal overload.

Use one period and one unit

Choose the week or other period you are deciding on. Keep every figure in hours for that period; do not compare monthly assignments with weekly capacity. Start with rostered hours, then deduct absence and time reserved for work outside the project pool. Do not subtract an absence again if the starting calendar already excludes it.

A hypothetical week for one team member:

Item / Hours

Rostered time
32
Planned leave within that roster
−8
Meetings and operational work in the remaining time
−4
Available project capacity
20
Project A assignment
12
Project B assignment
10
Total assigned project work
22

Assignments exceed available project capacity by two hours. This is a planning gap, not evidence of overtime. If a project estimate already includes a meeting, keep it there rather than deducting it again as operational work.

Put estimates in the right period

An estimate is expected effort for a task; an allocation places some of that effort with a person in a specific period. A ten-hour task estimated for this month may need only four hours next week.

Comparing all ten hours with next week's capacity would exaggerate the immediate clash. Time already recorded describes past work and does not, by itself, establish the effort still needed; ask the task owner for an updated forecast.

Check what the software counts

Some workload views count tasks rather than hours; others spread estimated hours evenly across a date range. Workload views may also spread estimated hours across working days and use a work schedule that allows for shorter days and non-working days. These counting choices can affect the apparent capacity.

A weekly total may still conceal a review or handover that must happen on a particular day.

Check whether the view includes the person's other projects, dates, leave and work without estimates. Inspect assignments before accepting an apparent gap or surplus. In Australia, applicable public holidays can vary by state, territory or region; a shared team calendar may need adjustment for people in different locations.

Make the next decision explicit

When assigned hours exceed capacity, check the inputs, then decide which work moves, which commitment changes or who else is qualified to do it. When hours appear available, check whether the person has the required skill and whether the time falls before the handover. Unassigned hours are not automatically usable for every task.

More from Capacity Planning

Capacity Planning

Workload views across project tools—Asana/monday.com/ClickUp

Compare Asana, monday.com and ClickUp workload views by project scope, effort units, capacity settings, missing work and plan limits.

Capacity Planning

Planning shared staff across several projects

Build one schedule for staff shared across projects, resolve competing requests and keep affected project plans aligned.

Capacity Planning

Managing a shared backlog across several product teams

A shared product backlog needs one view of priority and clear ownership of each item. Otherwise, the same feature may be promised in several team plans while …