← Back to blog

Planning Leave Across the Year Boundary

Why two clear requests are better, while open requests still need to stay visible.

Leave & absences

Leave can cross a year boundary. For planning, that may sound like one period. For leave allowance, working days, and assignment to the right year, however, it is two different contexts. Such leave is therefore deliberately not handled as one request across the year boundary but as two clear requests, one for each year.

This is not a detour. It is a decision for traceable data. Each request belongs clearly to the year whose allowance and planning it affects. Nobody has to guess later which part of a longer leave was considered in which year.

Two requests, two clear connections

Someone taking leave across a year boundary submits one request for days in the old year and a second for days in the new year. Both can be reviewed, approved, and assigned to the relevant leave allowance separately.

This separation keeps calculation understandable. It avoids edge cases hidden in one request and makes planning traceable even if one period changes later.

The problem with the old default view

The default view for current requests was initially limited to the current year. This seemed logical at first, but had a drawback: a request from the previous year could still be open and yet disappear from direct view once the new year began.

Open is open, regardless of the year currently on the calendar. A year boundary must not make an item invisible when it still needs a decision or further work.

Flexibly seeing what is truly current

The request view was therefore made more flexible. Open requests from the previous year can also be seen at a glance. Their time context remains clear, but no longer decides whether an important item is visible.

This creates a better everyday experience around year-end: new requests belong to the new year, while open decisions from the old year remain reachable. Nobody has to know that an item sits behind a previous-year filter.

Clear data, no information gap

Combining two requests with a flexible view brings both together: clean annual assignment and a complete overview. The year boundary no longer becomes an information gap but a clear transition in which open work stays visible.

Related articles