Resource planning
Overview
Planning answers three questions: who works on what? (board), how full are we? (capacity and utilisation) and where is a bottleneck coming? (forecast).
Capacity is not a plain calculation from weekly hours. Absences and a reserve share are taken into account — without a reserve you plan at 100 %, and every disturbance becomes a delay.
Core tasks
Plan on the board. You drag allocations onto people and periods. Overallocation is made visible rather than prevented — sometimes it is the deliberate decision.
Read utilisation. The capacity view shows target and actual per person and period; the breakdown says what a utilisation consists of. The Team filter narrows the view to the employees of one team — the team set on the employee counts. A role limited to "own team only" sees, on the planning board, checklist and timeline, just the employees of its own teams and those without a team.
See bottlenecks early. The forecast weighs known demand against capacity and shows when it gets tight.
Try out scenarios. A scenario is planning on trial: you move things without changing the live state, and apply only when it fits.
Staff by skills. Skill matching suggests people who cover the requirement.
Fields in detail
| Field | Required | Values / format | What it does |
|---|---|---|---|
Employee employeeId | yes | an employee | Who is planned in. |
Project projectId | yes | an existing project | What for. |
Period from / to periodStart, periodEnd | yes | date | Over what period the plan runs. |
Planned hours plannedHours | yes | 0 or more | How much work is foreseen. Set against available time it yields utilisation — minus absences and public holidays, because planning goes against real availability, not against the calendar. |
Distribution distribution | no | even or weekly | How the hours spread across the period. |
Confidence confidence | no | planned, committed, tentative | How firm the allocation is. This is the most important distinction on the mask: tentative for a quote not yet accepted, committed for work someone is relying on. Without it a plan looks full that is half hope. |
Role roleHint | no | text | In what function the person is planned. |
Task title taskTitle | no | text, max. 1000 characters | What is to be worked on. A task can arise from it. |
Note note | no | text | A note on the allocation. |
Settings & permissions
- Own allocation/utilisation:
resources.allocation.view_own· Team:resources.allocation.view_team - Manage allocations:
resources.allocation.manage - View capacity:
resources.capacity.view· Reserve share:resources.capacity.manage - Forecast:
resources.forecast.view· Skill matching:resources.skill.match - Scenarios:
resources.scenario.manage
Module flag: module.resources.
FAQ & troubleshooting
Someone appears overloaded although little is planned. Check absences and the reserve share — both reduce available capacity.
A scenario has no effect. Scenarios take effect only after being applied. Until then they are a thought experiment.
The forecast shows no bottleneck although it feels otherwise. It calculates with RECORDED demand. What is not planned does not appear there.