Resource planning

The page where planning happens. Describing demands belongs to the detail page — assigning and keeping an overview happens here.

Three tabs, three questions: Backlog (“what is open?”), Utilisation (“who still has time?”) and At risk (“what slipped without anybody doing anything?”).

Backlog

All demands that are not fully planned yet. The list is built to stay workable:

• Ongoing demands do not appear as a whole but with the periods for which nobody is planned yet. An operational demand without an end date would otherwise sit in the list forever and unfinished — and a work list in which nothing ever disappears stops being read.
• Closed and cancelled demands are absent. The status controls that, not the coverage.
• “Not quantifiable” is listed, but without an hour figure. These demands lack their start date or their quantity; somebody has to supply it — which is why they belong in the work list, but not as “0 open”.

Utilisation

Per member and period: how much is planned — running operations and initiatives separately.

The separation is the point. Merged, the figure would be shorter, but the question “how much of my time is already taken by operations?” would no longer be answerable — and that is exactly what initiatives fail on.

Next to it sits the capacity side, broken down rather than as one number: baseline – absent – non-working = available. Planning runs against the available amount, not the contractual one; reading only the baseline means overplanning systematically — the most common reason plans tear in December. Where the baseline comes from is stated (HR source, field on the person, tenant default), and the way to change it leads to the member: it is corrected there, not here. See Capacity — baseline, deductions, available.

Members are humans and AI agents. Both appear in the same table, distinguishable by the icon. An agent is not an unlimited colleague: it shows two bars — throughput and budget — and the view marks which limit binds first (AI agents have limits).

“Limit not recorded” is not “unlimited”. Where a member’s capacity is missing, the view says exactly that and asserts no limit. An invented reference figure would be worse than none: it produces a percentage that looks convincing and means nothing.

Assigning — singly and as a series

The way there runs through the candidate list: next to every suggestion sits “Assign” (only with demand:plan). The dialog preselects the periods that are still open and suggests the largest open gap as the amount; both can be changed.

When assigning you enter hours per period; a sensible suggestion is already there. For run demands there is the series: “20 h/month for twelve months” in one go, and an existing series can be rolled forward. Without it every turn of the month becomes typing work, and a plan you retype month after month rots after the second one. A series is repeatable without doubling up.

Overbooking is warned about, not forbidden. Planning somebody beyond their available capacity is shown clearly — and still allowed. A hard ban only moves the decision into a spreadsheet outside the system, where nobody sees it any more.

At risk

Demands whose coverage has fallen without anybody changing the plan. The cause then lies on the capacity side: somebody dropped out, an absence was added, an employment rate changed.

That distinction is the whole value of the tab. Coverage falling after a change to the plan is normal — you just changed something. Coverage falling without a change to the plan is an event nobody otherwise hears about until the initiative tears.

So that “when did it slip?” stays answerable, available capacity is recorded daily. The trend shows the drop as a kink, not just the new, lower level — retroactively that could not be reconstructed.

What this page is not

Utilisation is a planning view, not a monitoring view. It shows planned values, not working time. Whoever wants to know what was actually worked looks at Effort Booking — deliberately a different page with different permissions.

Who may do what

Permission	What it allows
(none)	see your own assignments — what you are planned for
demand:plan	assign members, create and remove series
demand:report	see other people’s assignments and utilisation

For working time there is deliberately no separate permission: it is personal data and runs through the permissions on the person record.

Related

• Demand & Resource Planning — Demand, plan and coverage at a glance
• Running operations and initiatives — Why ongoing demands are never “done”
• The demand profile — three axes — What makes a member fit a demand
• Capacity — baseline, deductions, available — Baseline, deductions, available capacity
• Absences — What is deducted from the baseline
• AI agents have limits — Why an AI agent has two limits
• Effort Booking — The actuals side