Leave planning & requests

Employees request leave themselves, from a tile on the Today dashboard. Every request creates a task for everyone allowed to approve absences, who then approve or reject it. As long as nobody has decided, the employee can withdraw the request. Only approved leave takes effect in planning. This requires a user account linked to the employee – a shared terminal has no leave of its own.

Immediately and without retyping: approved absences reduce the employee’s capacity on those days, half days proportionally. The Gantt chart marks these days with the reason, and automatic scheduling skips them. Anyone who still places an order on a leave day gets a notice, not a block. Employees come from the shared master data; their working time model and public holidays feed into the same calculation.

In the holiday calendar: rows are employees, columns are the days of a month. Public holidays, non-working weekdays and absences are shown in different colours, so not every day off looks like leave. The server calculates the values from absences, working time models and public holidays. Each employee sees their own absences, including requested and rejected ones, in a tile on the Today dashboard.

The basics stay in the core: recording absences such as holiday, sickness or training, leave entitlement and remaining leave per employee, holiday models and the effect on capacity in planning. POM Absence adds the holiday calendar and the request workflow with approval. Clocking in and out is not part of it: POM Zeiterfassung, the time recording module, is in preparation and cannot be booked yet.