Leave Carryover: Sort It in October, Not in December

It arrives on schedule. Some time in early December, someone runs the leave report and discovers that a quarter of the company has barely taken a day off all year, and most of them want to use it between the twentieth and the thirty-first.

Then come the three bad options: let everyone go and run the month with a skeleton crew, refuse and generate a lot of resentment, or pay it out and take a cost nobody budgeted.

None of those are December problems. They are October problems that were not looked at in October.

Run the report now, and look at the shape of it

Pull remaining balances by person and sort descending. The list usually splits into three groups, and each one needs a different response.

At the top there are two or three people with almost everything untaken. This is not thriftiness. It is usually someone who believes the work stops if they leave, which is a risk sitting in plain sight. Their balance is a warning about single points of failure, not a scheduling issue.

The middle group has five to ten days left and no plan. They will take it in December unless you ask them now. Asking now is the whole intervention.

At the bottom sit people who are already at zero, some of whom will ask for unpaid leave in December. Decide your answer to that before you are asked in the corridor.

Pick one rule and say it in October

The rule matters less than the timing. Any of these work: carry over up to five days until March, carry nothing and use it or lose it, or pay out at a stated rate. What does not work is having no stated rule, because then every case becomes a negotiation with a manager who decides based on how the conversation feels.

Whatever you pick, put it in writing, send it in October, and make sure the number each person is looking at is their own balance. A policy announcement without a personal number is background noise.

The staffing question is separate, and easier

Once people start booking, you need a simple constraint per team, not a case-by-case judgement. Something like: no more than a third of any team off at once, and named cover for anything customer-facing. First to book gets the slot.

Publish that alongside the policy. It converts December from a queue of individual requests into a calendar people can look at themselves.

One thing worth checking afterwards

In January, look at who ended the year with a large unused balance for the second year running. Two years in a row is not a scheduling accident. Either that person is covering something nobody else can cover, or their manager is quietly discouraging leave. Both are worth a conversation, and both are cheaper to fix in January than in the next December.

TalentHR shows the balance per person and lets people book against a team limit you set once, so December stops being a queue at your desk. October is the month to switch it on, if you are going to switch it on at all.