Holidays in TimeWriter

The reference hours were discussed in the previous blog.

I can tell TimeWriter how many hours each employee normally works and I can also have TimeWriter checked on that. This is important to prevent employees from working too few or too many hours.

TimeWriter also knows when a day is a holiday. These days are indicated in the weekly schedule with a different color. They are easily recognizable in this way. On the holidays, the employee must manually book the hours that he / she would normally have worked. TimeWriter cannot do this for you automatically. In this blog I explain why that does not happen automatically.

Suppose TimeWriter would automatically book hours on holidays. Then all work schedules of all employees must be entered into the system correctly and correctly. That is quite a job if the company has many employees. Now I enter the number of contract hours per employee, so TimeWriter knows how many hours a person should book per week. That is a lot easier than entering on which days someone works how many hours.

Moreover, this should also be kept well up to date, as soon as an employee goes to work one day more or less, it must be adjusted so that it is always right. That is quite a lot of work for the average company, and is fairly error-prone. It becomes completely impossible if the employees work in changing shifts or rosters. Keeping schedules within TimeWriter good and correct then becomes impossible. It is all technically possible, but I believe it is very labor-intensive and, moreover, very sensitive to errors.

Suppose TimeWriter would automatically book hours on holidays.

Suppose the system would automatically book the hours on public holidays, based on the reference hours that can already be entered into the system.

With the standard full-time working week in which employees work 8 hours as standard every working day, the system could do that technically well. But even then all working days and the 8 hours per working day have to be entered, which can be quite a time-consuming job for many employees.

For employees who work part-time, automatic booking goes wrong.

Suppose Anna works on Monday, Tuesday and Wednesday.
Her colleague Bernard works on Thursday and Friday.

Monday, Easter Monday, Anna would normally have worked, but because it is a public holiday, she is free. Her hours that she would normally have worked must now be booked as a public holiday.

Bernard never works on Monday, so nothing needs to be booked for him this day. If TimeWriter were to automatically book a holiday here, Bernard would receive free overtime as a gift.

With Ascension Day that is the other way around. Bernard would normally have worked on Thursday 30 May but is now free. These hours must therefore be booked as a public holiday. Anna does not have to work on Thursdays, so nothing has to be booked for her.

The solution.

Because there are so many snags on having TimeWriter booked automatically and moreover it would take a lot of time to keep everything properly up-to-date and correct in the system, it is much more logical to let the employees book the holidays themselves . The employee himself knows well whether he / she would normally have worked or not and booking is a small operation.




« Previous | Back | Next »

Share this page