How to Approve Leave Requests Fairly

Two people on your team both want the last week of July off. So does a third. They each booked time with the in-laws, the flights are cheap, the kids are off school — and you can run with at most one person away that week. Now you're the bad guy, whatever you decide.

Every manager hits this eventually. Leave isn't infinite, weeks aren't interchangeable, and "first to ask" isn't always "most deserving." Here's how to approve requests in a way your team will accept as fair — even when the answer is no.

Why fairness is the hard part

Approving leave is rarely about the numbers. The balance maths is easy: someone has the days or they don't. The friction is in the clashes — when two reasonable requests collide and you can only grant one.

Get this wrong and the cost is quiet but real: the person who always asks first hoards the good weeks, the polite ones who wait get squeezed out, and resentment builds. The goal isn't to make everyone happy every time — that's impossible. It's to make the process something people trust, so a "no" feels like the rules working, not like favouritism.

The three common approaches

When requests clash, most teams fall back on one of three tie-breakers. Each has a logic — and a downside.

Approach	How it works	Pros	Cons
First-come-first-served	Whoever requested first wins	Simple, transparent, hard to argue with	Rewards the organised/pushy; planners hoard peak weeks months out
Seniority	Longer-serving staff get priority	Recognises tenure; predictable	Newer staff feel locked out of every popular week
Coverage-based	Approve up to a cap, judged on who else is off and skills needed	Protects the business; flexible	Needs clear criteria or it looks like favouritism

In practice, the best teams blend them: a coverage cap that protects the business, with first-come-first-served deciding ties underneath it. Seniority works as a tie-breaker for genuinely fixed, must-have dates (school holidays, religious festivals) — but leaning on it for everything alienates new hires fast.

Set the rules before the clash, not during

The single biggest fairness upgrade costs nothing: decide the rules in advance and write them down. A request denied against a published rule feels fair. The same denial made up on the spot feels personal.

Put these in your leave policy (see our annual leave policy template for a starting point):

• How many people can be off at once, per team — e.g. "no more than 2 of 6 engineers away on the same day."
• Tie-breaker order — e.g. "coverage cap first, then first-come-first-served, then seniority for fixed dates."
• Notice periods — longer breaks need more notice (e.g. 1 week's leave = 2 weeks' notice).
• Blackout dates — periods where leave is limited or closed (see blackout periods explained).
• Response time — managers respond within, say, 3 working days, so requests don't rot in an inbox.

This is general guidance, not legal advice — statutory rules on how much leave staff can take and how requests must be handled vary by country, so check your jurisdiction.

Avoiding favouritism (and the appearance of it)

Fairness has two halves: being fair, and being seen to be fair. You can do everything right and still look biased if your reasoning is invisible.

• Decide on rules, not relationships. "We're at the coverage cap that week" is a reason. "I'd rather Sam was here" is a vibe.
• Apply the same bar to everyone, including your stronger performers. The moment the rules bend for one person, they're not rules.
• Record the why. When you decline, log the reason. A short note ("declined — 2 of 4 already off, suggested the following week") turns a flat no into a defensible decision.
• Don't approve in DMs and forget. A verbal yes nobody can find later is how two people end up "approved" for the same week.

Approval chains: who approves whom

A clear chain stops requests vanishing into the wrong inbox. Map it once:

1. Employee → their manager. The default route. The manager sees the request, the team's existing bookings, and the balance.
2. Manager → their own manager (or an admin). Managers take leave too — their requests need an approver above them.
3. A defined backup. Critically: who approves when the usual approver is themselves on leave? If the answer is "nobody, it waits," requests stall exactly when people most want them granted. Name a deputy in advance.

That last point catches teams out constantly. The approver goes on holiday, requests pile up unanswered, and people either book blind or give up. A backup approver — or auto-escalation after a few days — keeps things moving.

How Absenca keeps approvals fair

Absenca is built so the rules enforce themselves instead of living in your head. Requests route automatically to the right manager (with a named backup when that manager is away), and the approver sees the full picture before deciding: the person's balance, and — crucially — who else on the team is already off those exact dates, flagged as a clash.

You set a "max people off at once" cap per team and define blackout periods, so the system surfaces conflicts before you approve rather than after. Every decision — approved, declined, by whom, when, and any reason given — is written to a full audit log, so "who approved this?" always has an answer. Balances update the instant a request is approved, with no spreadsheet to reconcile.

It's free for up to 15 people, then $0.75/user/month — so you can put a fair, visible process in place today.

Frequently asked questions

Is first-come-first-served actually fair? It's the most transparent tie-breaker, which is why it's popular — but on its own it rewards whoever plans furthest ahead and can let one person monopolise peak weeks. Pair it with a coverage cap and notice periods so it doesn't become a land-grab.

What if two people request the exact same week and only one can go? Fall back to your written tie-breaker. If you haven't published one, that's the real problem — decide an order now (coverage, then first-come, then seniority for fixed dates) so the next clash isn't a judgement call.

Should managers explain why they declined a request? Yes. A one-line reason — ideally logged, not just spoken — turns a decline from "the boss said no" into "the rule said no." It also protects you if the decision is ever questioned.

Who approves leave when the manager is on holiday? Decide this in advance and name a backup approver, or set requests to escalate after a few days. Otherwise requests stall exactly when staff most want a quick answer.

---

Make every "yes" and "no" defensible. Absenca routes requests to the right approver, flags clashes before you decide, and logs every approval — free for up to 15 people. Related: why every team needs a shared leave calendar and how to track employee PTO without spreadsheets.