Resource planning: capacity, allocation and utilisation explained

Start with the planning horizon

Choose the period and people the decision covers. A weekly staffing meeting and a quarterly hiring decision need different levels of detail. Record working patterns, planned leave and any other known availability adjustments. Do not assume every person contributes the same hours or skills.

For a fictional design agency, the immediate question is whether two client projects can share a designer next week. The agency needs that person’s working time and existing commitments. A company-wide average can conceal the individual conflict that determines whether the proposed deadline is realistic.

Define capacity and allocation separately

Float’s reporting guidance distinguishes available capacity from scheduled work and offers different percentage views. Check the selected report’s definitions and filters before comparing its output with another tool.

For the agency, capacity is the time available under its chosen planning convention. Allocation is the time assigned to work. A person can be allocated beyond capacity, but the software displaying that number does not create more available time. The team still needs to move work, change scope or arrange suitable cover.

Work through a simple example

Suppose the fictional designer has 35 working hours in the week and seven hours of planned leave. Under this example’s definition, remaining capacity is 28 hours. Assigning 21 hours to Project A and 14 to Project B creates 35 allocated hours, or seven hours above that capacity.

If only the 21 Project A hours are billable, billable allocation divided by available capacity is 75%. Dividing the same 21 hours by all 35 allocated hours gives 60%. Both calculations can be arithmetically correct while answering different questions. Label the numerator, denominator and period rather than presenting either percentage simply as utilisation.

Separate scheduled and actual time

A scheduled forecast and a report of logged time should not be silently combined. If the tool shows past actuals and future plans in one view, inspect the transition date and labels. Otherwise a manager can mistake an optimistic future allocation for evidence of work already completed.

Keep skills and uncertainty visible

Hours are not interchangeable when work needs a specific skill or customer relationship. Identify the people or roles eligible for a task. Keep unassigned demand visible rather than filling a schedule with a placeholder that looks like a confirmed person.

For the agency, another available designer may not yet know the client’s production process. Record that constraint without assuming the substitute cannot help. A useful planning discussion considers onboarding, review and scope changes. It does not turn a coloured availability cell into a guarantee of equivalent delivery.

Test changes during the trial

Enter planned leave, a tentative project and an urgent change. Inspect the individual and team views, then change the report scope. Ask how the product handles partial working days, archived people and tentative work in the selected report. Use a small dataset with calculations the team can reproduce.

The portfolio-management guide explains where shared-resource decisions sit. Compare whether the planning tool helps the team make that decision and leaves a usable record of the revised commitment, rather than judging it only by the appearance of the chart.

Use the measures as decision inputs

Do not set a universal utilisation target without understanding the work and what the formula includes. Internal maintenance, learning, coordination and unplanned support may all be necessary. A high ratio can coexist with missed commitments if the wrong activities or denominator are being measured.

Research the monday.com, Asana and Harvest profiles for planning and time-recording context. Choose definitions the team can explain consistently, then use them to discuss tradeoffs in workload and delivery.

Frequently asked questions