|
|
|
|
|
by tzs
2582 days ago
|
|
> Personally I'm not sure it's something that makes sense, it should just be factored in to the wage. Most hourly paid jobs I know of don't have regular hours, even - how much do you pay for a week's holiday when some weeks the employee works 8 hours and some 24 hours? An average? Of what, if they've only been there a few months, say? If you want full time hourly employees (40 hours per week) to earn two weeks of paid vacation per year, then you have hourly workers accrue vacation time at a rate of 1 hour vacation earned for every 25 hours on the clock. This system handles people who hours worked varies from week to week, and it handles people who have not been there long enough to earn the full two weeks--ever 5 weeks they have accumulated a vacation day, so if they want to take a week off 6 months in, say, that works. It also works for tracking vacation time for salaried employees. For salaried employees you just force the hours worked to 8 per day in the program that calculates vacation accrual, regardless of the actual hours worked (assuming that you even track actual hours worked for salaried employees). |
|
So let's say under your system an employee works an average of 8 hours a week. After half a year they've accrued 8 hours of holiday.
That's 1 day.
The pay isn't the issue but the legal obligation to allow the worker to not work, if that makes sense.
Whether holidays are unpaid or paid is just shuffling cashflow in time, the real problem is the amount of holiday that's possible.