Project resource planning in Australia: Check each person's working pattern and local public holidays for accurate capacity.; Use workload charts to spot clashes; record decisions when demand exceeds availability.; Review plans when commitments change, including specialist unavailability or revised estimates.
Image: Project Software Guide

Capacity Planning

Project resource and capacity planning

Compare project demand with available people, skills and time, then resolve competing commitments before promising dates.

Project resource and capacity planning compares the work you intend to deliver with the people, skills and time available to deliver it. Start with existing commitments, allow for non-project duties and absences, then decide which new work can fit. A workload chart can reveal a clash; someone still has to decide which commitment moves.

Separate demand from availability

Resource demand is the effort and skills a project needs during a particular period. Capacity is the time people can reasonably offer during that period. Assigning work does not create more capacity.

InputRecord
Project demandDeliverable, required skill, estimated effort and work period
Existing commitmentsWork promised to other projects and recurring duties
AvailabilityEach person's working pattern, planned leave and relevant public holidays
FlexibilityWork that can move, be divided or be done by another qualified person
Decision ownerWho may change scope, dates or staffing commitments

For an Australian team working across locations, check the applicable public holidays for each person. Use each person's working pattern rather than copying one standard week across the team.

Build a plan people can challenge

Choose a period short enough to expose clashes. A weekly view may help with near-term delivery; a broader view can show demand for a specialist later in the quarter. A broad estimate is not a precise daily booking.

Break deliverables into work that can be assigned and estimated. Identify the required skill as well as the proposed person. Include operational work and approved absence, then compare demand with available time for each person or skill group. Spare time in one role does not solve a shortage in another unless the work can genuinely be transferred.

Where demand exceeds capacity, record a decision: move flexible work, change scope with approval, find qualified help or revise the delivery date. Check the effect on handovers.

Treat early timeframes cautiously

For architectural design and documentation, time taken may exceed the period first indicated. This can lead to client dissatisfaction or disputes between the client and architect, so communicate about timing and manage the relationship throughout the project.

Standard Institute Client and Architect Agreements do not provide for an architect's pre-contract administration services to follow a set or stated program. Clients may still want a known timeframe because their own project program, particularly the tendering date, can depend on how long the architect's work takes.

Read workload views with care

Ask what a workload view counts: tasks, estimated hours, points or a percentage of capacity. Five short tasks may require less effort than one substantial task. Check which projects are included and whether missing dates or estimates leave work out.

Calendar settings matter too. Displayed capacity depends on the working days and other commitments represented in the plan. Before promising a date from a chart, inspect the underlying assignments and ask the people involved whether the estimates and timing remain credible.

Review commitments as they change

Review the plan when a project is approved, a specialist becomes unavailable or an estimate changes materially. Keep proposed work separate from approved commitments.

At each review, ask what demand has arrived, what availability or skills have changed and which decision will keep current commitments feasible. Record that decision and tell the affected project leads.

In this guide

  1. Workload views across project tools—Asana/monday.com/ClickUpCompare Asana, monday.com and ClickUp workload views by project scope, effort units, capacity settings, missing work and plan limits.
  2. Planning shared staff across several projectsBuild one schedule for staff shared across projects, resolve competing requests and keep affected project plans aligned.
  3. Distinguishing assigned hours from actual team capacityCalculate available project capacity, compare it with assigned hours and avoid double-counting leave or other work.

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

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 …

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.