Capacity — baseline, deductions, available

Planning computes against a member’s capacity. That figure is not one but three — and they stay apart because they answer different questions.

Term	Meaning
Baseline	What would be available contractually
Deductions	Absences and non-working days
Available	Baseline minus deductions

Reading only the baseline means systematically overplanning — the most common reason plannings break in December.

The fields arrive with the module

As soon as the Demand module is active for the tenant, the person type carries the fields weekly hours, employment level (FTE) and full-time/part-time automatically. Nobody has to extend a schema by hand — neither for a new nor for an existing tenant.

AI agents only get throughput (h/week): they have no employment relationship and therefore no employment level.

None of these fields is required. A tenant working without them is not blocked — it simply sees that the limit is unknown.

Maintained at the original

On the person record, in the regular edit form. That means everything that applies there applies here too, without extra work: write permissions on the person type, its approval mode, drafts, history, audit and visibility.

There is deliberately no second form for capacity and no separate permission for it. A second write path to the same statement would be the weaker one — and a person’s working time is personal data, not a planning figure.

If a connector owns the person type as master, the field is read-only there and the interface names the source system. As long as no connector holds authority, it is a field like any other.

Where the figure comes from — three sources, fixed order

Period-specific value from the HR source (e.g. a temporary increase)
Field on the member (weekly hours)
Tenant norm — for humans only

The order is the meaning. The interface always shows where the value came from: a figure whose origin nobody sees gets believed, even when it was guessed.

“No limit on record” does not mean “unlimited”

If nothing is on record, capacity is unknown — a state of its own. That is a gap in the model, not a permission:

Utilisation shows no percentage instead of inventing one.
There is no overbooking warning, because without a reference it would be guessed — and guessed warnings get ignored, including the justified ones.
In the candidate list a member without a recorded limit is not ranked ahead of someone with known partial capacity. Otherwise the sorting would reward a gap in the model.

For agents the tenant norm explicitly does not apply: using it on an agent would be an invented figure.

FTE is a display

Everything is computed and stored in hours. FTE and percentages appear only at display time, by holding a quantity against the baseline of the same period. A stored FTE figure would be wrong the moment working time changes — and nobody would keep it up to date.

Setting the tenant default

What counts as full capacity in this tenant lives under Settings → Capacity default (tenant administration only, and visible only when demand planning is set up):

Value	Effect
Weekly hours	How much a full week holds. Applies to humans only — an AI agent gets no invented figure.
Working days per week	Determines the daily rate at which an absence is deducted.
Non-working days	One day per line. A tenant list, not a calendar service: several sites with different public holidays cannot be represented.
Default granularity	Month or quarter — the preset for new demands.
Planning horizon	How far a run demand is calculated ahead. It never ends by itself; without a horizon there would be no boundary for “covered”.

These values are the fallback, not the truth about any one person: they apply exactly where nothing is recorded for a member — and utilization then states that as the source.

Demand & Resource Planning — Demand, plan and coverage
Resource planning — Where utilisation lives
Reading the candidate list — Availability as the third axis
Capacity from an HR system — When an HR system owns the values
Persons — The person type and its fields