Floating Holiday

Why does a fixed holiday calendar stop serving a workforce?

Because a single published calendar assumes everyone marks the same days, and in most workforces that has stopped being true. A calendar built around one set of religious and cultural observances gives some employees a day off for something that matters to them and gives others a day off for something that does not, while the day that does matter to them is an ordinary working day they have to book leave for. The same problem appears geographically: a distributed team spans several national holiday calendars, and no single list can be correct for all of them. A floating holiday is the usual answer. The employer fixes the quantity centrally and hands the choice of date to the person taking it, which keeps the cost predictable while letting the day land where it means something.

How is a floating holiday different from ordinary annual leave?

By being a separate, named allowance rather than part of the general pool. Annual leave is a bank the employee draws on for anything, and the employer's interest is only in coverage. A floating holiday is granted as a distinct entitlement, usually a small one, and it exists because the holiday calendar could not serve everyone rather than because people need rest. Keeping it separate is what makes it visible: employees can see they have been given something specific, and the employer can see whether the thing it introduced is being used. Merging it into the annual leave balance is administratively simpler and quietly removes the point. Once it is indistinguishable from other leave, nobody knows whether the calendar problem was solved or whether people just took a longer summer.

Why is this the leave type most often introduced without a written rule?

Because it arrives as a gesture rather than as a policy change. Someone raises that the calendar does not work for part of the workforce, a leader agrees, and the outcome is announced in a message: from now on everyone gets an extra day to use as they wish. That message answers one question and leaves every other one open. Nobody has said whether it needs approval, whether a new joiner gets one in their first year, whether it survives into the following year, or whether it is paid out when someone leaves. The gap is filled by whoever is asked first, which means it is filled differently each time. Six months later the organisation holds several precedents that contradict each other, and the first person told no is entitled to point at the person who was told yes.

What has to be decided before a floating holiday is announced?

Six things, and all of them are easier to settle before anyone has used one. How many are granted, and over what period they are counted. Who is eligible, and from when: whether someone who joins partway through the year receives the full quantity, a reduced one, or none until the next cycle. Whether taking one requires approval, or only notice. If approval is required, on what grounds it can be refused, because a manager who can refuse for any reason will eventually refuse for a reason that is difficult to defend. Whether it can be split into part days, which sounds trivial until somebody asks for a half day and there is no answer. And what happens to one that is unused when the period closes, or when the employee leaves. None of these questions is difficult. They only become difficult once there is a live case attached to them.

Write the answers into the leave policy rather than into the announcement. An announcement is read once and then lives in an archive nobody searches; a policy is where a manager looks when they are asked something they cannot answer. The same document should say plainly which answers are the employer's discretion and which are constrained by law, because the two are not the same and the boundary moves. Minimum paid time off, how holidays interact with statutory entitlements, and what must be paid on termination are set by legislation that differs by jurisdiction and changes over time. Nothing of this kind should be published without having the entitlements, and any statutory floor beneath them, confirmed for each work location by an adviser qualified in the relevant employment law. What the organisation chooses to add above that floor is its own decision, and that part is what the policy is really for.

Can a floating holiday request be refused?

That depends on what the employer said when it introduced the benefit, which is exactly why the question needs answering in advance. There are two workable positions. The first treats the day as notice-only: the employee tells the manager and takes it, and the employer accepts that occasionally the timing will be inconvenient. The second treats it as a request like any other leave, refusable on coverage grounds. Both are defensible. What is not defensible is the arrangement most organisations reach by accident, where approval is required but the grounds are unstated, so a refusal reads as a judgement about the employee rather than about the rota. If approval is required, name the grounds. Coverage, a closed period around a known peak, or a limit on how many people in a team can be out at once are all legible reasons an employee can accept without concluding they were singled out.

There is a further reason to be careful with refusals here that does not apply to ordinary leave. The purpose of the entitlement is to let people take a day for something the company calendar does not recognise, so the date requested often carries a religious or cultural reason even when none is given. A pattern of refusals that repeatedly falls on the same observance is a problem of a different kind from an ordinary rota dispute, and it will be read that way. What protections apply, what an employer is required to accommodate, and what counts as a reasonable refusal differ by jurisdiction and change over time. Have the refusal grounds, and the wording around them, reviewed by an employment lawyer in the relevant jurisdiction before the policy is published. Managers should also be told, in plain terms, not to ask what the day is for, and given somewhere to escalate when they think a refusal is genuinely necessary rather than deciding it alone at the counter.

What happens to an unused floating holiday at the year end or on exit?

Whatever the policy says, and if the policy says nothing the answer will be decided by whoever is asked in December. There are three usual treatments and each has a consequence. Letting it lapse is the cleanest and the least popular: it keeps the entitlement inside the period it was granted for, and it produces a rush of requests in the closing weeks that the rota has to absorb. Allowing it to carry forward turns a small annual gesture into an accruing balance, which is manageable for one year and awkward by the third. Requiring it to be taken by a stated point, with the balance visible throughout, is the middle position most employers land on, because it spreads the requests without creating a bank. The choice matters less than stating it before the first year ends. The dispute is never about the treatment itself; it is about learning the treatment at the moment the day is lost.

Exit is the harder question and the one most policies leave out. If the entitlement is treated as leave, an unused balance may have to be paid on termination; if it is treated as a discretionary extra, it may not. Which of those is correct is not the employer's choice alone, because what must be paid on termination is set by legislation, differs by jurisdiction, and is one of the areas where an error is expensive and discovered late. Decide the treatment explicitly, write it into both the policy and the offer documentation, and have the position confirmed for every work location by an adviser qualified in the relevant employment law before anybody leaves. The practical failure here is not a wrong answer. It is having no answer, so the calculation in a full and final settlement is made by whoever is running payroll that day, differently each time.

What does the system need to do with this entitlement?

Hold it as its own balance rather than as a note against annual leave. A separate code is what makes every later question answerable: how many were granted, how many were taken, how many lapsed, and whether the group the entitlement was introduced for is actually using it. If the days are absorbed into the general pool at the point of grant, none of those questions has an answer and the only available report is total leave taken, which was never the thing anyone wanted to know. The balance should also be visible to the employee at the moment they request, not calculated on demand by somebody in HR, because a lapsing entitlement people cannot see is one they will discover at the end of the period rather than during it. Visibility is cheap to build and it removes the most common complaint about this benefit, which is not that it is too small but that nobody could tell where they stood.

Two further behaviours are worth insisting on. The request should appear on the same team calendar as every other absence, because a day granted centrally still has to be covered locally, and a manager who only learns about it on the morning has been handed a rota problem rather than a benefit. And the employee should be able to see the balance, the deadline, and the treatment on exit without asking anyone, which an employee self-service portal does as a matter of course. Where employees can see their own position they correct errors early and cheaply. Where they cannot, the correction happens at the point the entitlement is lost, which is the worst possible moment for both sides and the reason a benefit intended as an accommodation so often ends in a complaint. It is also worth being able to report on the entitlement separately at the end of each period, because that report is the only evidence anyone will have about whether the arrangement did what it was introduced to do, and it is the question a finance or people lead will eventually ask.