Very few people object to being told no. What they object to is being told no after three weeks of silence, for reasons that appear to be different from the reasons applied to the person who asked before them.

A holiday policy is a decision procedure. If the procedure is clear, published and applied consistently, you can decline requests all summer without generating a single grievance. If it isn't, you will generate grievances even when you approve everything.

Here is what a policy that holds up actually contains.

1. The entitlement, stated in a unit people recognise

Days or hours - pick one and stick to it. For anyone working variable shifts, hours are the honest unit. A "day" of holiday for someone who works a four-hour Tuesday and a ten-hour Saturday is meaningless, and the ambiguity always resolves in the employer's favour, which people notice.

State the entitlement, the accrual method, the leave year boundary, and what happens to unused balance at that boundary. Include how public holidays are treated - this is the single most common source of confusion in shift-based businesses.

2. Notice periods, proportional to the length of the request

A blanket "four weeks' notice for all leave" is unworkable. A single day is not the same planning problem as a fortnight. Something like:

  • One or two days: one week's notice
  • Three to five days: two weeks
  • More than a week: four weeks
  • Peak periods: a fixed deadline, published in advance

The point is not the specific numbers. It is that people can see the rule and plan against it.

3. A stated decision deadline

This is the clause most policies omit and the one that removes the most friction. Commit to a turnaround - 48 hours, five working days, whatever is realistic - and hold it.

The value of the deadline is not speed. It is that the requester knows when they will hear, so they stop chasing, stop speculating, and stop asking colleagues whether they have heard back yet.

4. Explicit capacity limits

Say how many people can be off at once, and per what unit. Per site is usually too coarse - two people off is fine unless they are both the only ones who can do the thing.

The honest version is a limit per role or skill: one supervisor at a time; two team members at a time; never both first-aiders. Publishing this converts "no" from a personal judgement into arithmetic, which is much easier to accept.

5. A tie-break rule, written down before it is needed

Two people want the same week. You need a rule, and it needs to exist before the conflict, not be invented during it. Common options:

  • First come, first served. Simple, transparent, and it rewards whoever is most organised - which quietly disadvantages people with less predictable lives.
  • Rotation. Whoever was declined last time gets priority. Fairest over a year, requires you to keep a record.
  • Seniority. Predictable, easy to apply, and it means new starters never get August.

Any of the three is defensible. What is not defensible is having no rule, because then every decision looks like favouritism, whether or not it was.

6. What happens in a blackout period

If there are weeks nobody can take off, say so at the start of the leave year, not in June. And be honest about the length: a six-week blackout in a business with a four-week entitlement is a serious constraint on people's lives and should be justified, not merely announced.

7. Where the balance lives, visible to the person it belongs to

Half of all holiday queries are "how much have I got left?" If the answer requires emailing a manager, you have built a process that generates its own workload.

Self-service balances remove that entirely, and they also remove the end-of-year surprise where someone discovers they have eleven days to use in five weeks.

The failure mode to design against

Almost every holiday dispute comes down to the same complaint: the rule appeared to change depending on who was asking.

Sometimes it genuinely did. More often the rule was consistent but invisible, so people reconstructed it from outcomes - and outcomes always look arbitrary when you cannot see the constraint that produced them.

Publish the constraint. Publish the tie-break. Answer within the deadline you set. You will decline exactly as many requests as before and hear about it far less.