Absences

An absence states: in this period this member is not available. Nothing more — and that is the entire point.

The reason is not recorded

There is no field for a reason or a category. Not as a requirement, not as an option, not switchable.

This is not frugality out of convenience. Illness and care would be health data under Art. 9 GDPR — a special category with substantially stricter requirements. And a field that can hold them pulls the whole application into that regime, regardless of whether a tenant uses it.

A field that does not exist needs neither justification, nor protection, nor deletion.

For planning it fully suffices that someone is away. Analyses such as “sick days per department” are therefore structurally impossible — not merely undesired.

If an absence comes from an HR system and that system supplies an absence type, it is discarded on import. There is no column it could land in.

How it is computed

Deduction happens per day, not per period. Three things follow that are otherwise easy to get wrong:

A period crossing a period boundary falls pro rata on both periods.
Two overlapping absences count once, not twice.
A non-working day inside an absence is not deducted twice.

Counting uses working days, not calendar days: 38.5 h over five days is 7.7 h per day. Half days are possible.

Utilisation shows the result broken down — “available 111.5 h of 150 h”. A single figure does not answer the question; the breakdown does.

Where they live

On the person record — where the person is maintained anyway. In the normal view on the “Absences” tab next to Overview and Relationships, in the expert view as a section below the overview. The tab only appears for persons and only when demand planning is set up in the tenant.

Who maintains them

Path	Who
HR system	the connector, where one is attached
By hand	whoever may maintain the person concerned (`person:write`)

There is deliberately no separate permission for absences: they are personal data, and whoever may maintain the person maintains them too.

Seeing them: everyone sees their own — always, without any special permission. Other people’s are visible to whoever may maintain the person (person:write) or may read the demand reports (demand:report). Read-only viewers get the list without the entry form and without delete buttons; whoever may not read them at all does not see the tab.

A connector run replaces its own absences in the delivered period completely — otherwise a withdrawn holiday would stay forever. But only its own and only within the delivered window: manually entered periods and anything outside stay untouched.

What this is not

Not absence management. There is no request, no approval, no remaining-leave tracking — only the capacity effect. The truth about leave lives in the HR system.

Capacity — baseline, deductions, available — Baseline, deductions, available
Resource planning — Where utilisation lives
Capacity from an HR system — Absences from the HR system
Demand & Resource Planning — The overview

Where absences live

On a person you find them in the Absences tab of the detail page.

The tab is tied to the demand module: it only appears when your tenant has subscribed to it. If the service item was removed in the Platform Admin, the tab disappears — and a bookmark carrying ?tab=absences lands on the overview instead of a dead tab. The same applies to resource planning and the capacity settings.