Annualisation lets working hours flex above or below 35h depending on periods, respecting an annual average. Essential for seasonal businesses (tourism, food industry, retail).
Step-by-step #
-
Check the collective agreement #
Annualisation requires a collective agreement. It sets the reference period, average duration, low/high bounds.
-
Configure the cycle #
4 to 12 months. Typical low bound: 0h, high bound: 48h weekly. Average: 35h over the period.
-
Enter the planned calendar #
Import the yearly calendar or let managers enter it team by team.
-
Track the counter #
The annualisation balance updates daily. Mid-period, check the gap to target.
-
Settle at period end #
If balance positive (hours owed): time off in lieu or overtime pay. If negative: settled by agreement or deducted per policy.
Standard cycles #
| Cycle | Best for |
|---|---|
| 4 months | Short seasons (summer only) |
| 6 months | Semestrial activity |
| 12 months | Multi-season (tourism + ski) |
| Rolling 52 weeks | Continuous with repeated peaks |
FAQ #
Annualisation and overtime?
Within the high bound = no overtime. Above = overtime paid immediately.
What if employee leaves mid-cycle?
The balance is settled on departure: overtime pay or deduction.
Notice delay?
Often 7 working days per agreement. Illizeo enforces the delay and blocks late changes.
What about onerous work?
Night or Sunday hours feed the onerous-work counter, separate from annualisation.
