Your team submits an annual leave request during a period you'd flagged as tight for staffing. Your first instinct is to decline it, but then you wonder: is that fair? Can you even refuse? And how much should the reason for the request matter? For most employers, the answer turns on whether the request creates genuine operational hardship — not on the personal merit of the reason.
The choice employers face
You have two paths: treat all annual leave reasons equally and assess requests purely on timing and coverage, or make judgments based on what the employee says they need the time for. Under Australian employment law, only the first approach is defensible. The Fair Work Act 2009 (Cth) and the National Employment Standards don't create a hierarchy of acceptable reasons — annual leave exists for "rest and recreation", and employees don't need to justify how they rest. Your role is to manage when leave happens, not why.
The confusion often comes from mixing annual leave with paid personal/carer's leave. Personal leave can require evidence (a medical certificate, for example) and is tied to specific circumstances. Annual leave is broader and asks only that you balance the employee's entitlement with operational reality.
What to weigh when assessing a request
Timing and operational impact
This is the dominant factor. Can you sustain service delivery if this person is away at this moment? Consider whether the requested dates coincide with known peak periods, critical handovers, or product launches. An employee requesting two weeks during your busiest fortnight creates different pressures than the same request during a quiet month.
Document what "operational hardship" means in your context. Examples:
- A customer-facing role where no colleague can cover the account
- A specialist skill with no backup available
- A project deadline that hard-locks before the employee returns
If you can absorb the absence through temporary staffing, leave coverage, or pushing deadlines slightly, the timing factor weakens. If you genuinely cannot, it's your strongest ground for refusal.
Notice and the employee's cooperation
How much warning did they give? Two weeks' notice for a week away is lean. Six weeks' notice is standard. The Fair Work Ombudsman notes that "reasonableness" in refusal is context-dependent; notice length matters because short notice forces you into reactive staffing.
Did the employee offer to solve the coverage problem — working handover notes, training a colleague before they leave, or shortening the request? Employees who cooperate to reduce impact are easier to approve than those who don't.
Other approvals and fairness
If multiple team members have already requested overlapping dates and you've approved them, refusing the third creates a fairness problem. You'll face claims of inconsistency. Conversely, if you've already declined three requests for the same period, consistency may support declining a fourth.
Track approvals visibly. Use a simple leave calendar that everyone can see so the "who got approved" question is answered transparently.
Role and coverage availability
Some roles are easier to cover than others. A generalist administrator is often replaceable on short notice; a technical specialist isn't. An employee in a team of five can usually be covered; an employee who's the only person doing their function can't.
Be honest about your constraints. If you tell an employee "I can't cover your role even with two months' notice," that's fair. If you're turning down requests because you'd prefer not to pay for casual coverage, that's not.
Award and agreement rules
Your applicable award or enterprise agreement may set specific rules about peak periods, notice requirements, or the employer's right to direct leave. These rules can strengthen your position but shouldn't be substitutes for sound judgment. If your award says you can restrict leave during "peak trading periods" and defines them clearly, reference that rule in your decision.
When approval is reasonable
Most employers can approve requests that come with:
- At least 2–4 weeks' notice (depending on role and team size)
- Timing outside your documented peak periods
- A fair share of approvals across the team (no employee routinely blocked while others are approved)
- A workable handover plan from the employee
Most employers can justify refusing requests that involve:
- Insufficient notice for meaningful coverage planning
- Timing that genuinely blocks critical work
- Patterns of conflict with peak periods or known deadlines
- No attempt by the employee to ease the coverage burden
Distinguishing annual leave from other entitlements
The source article mentions scenarios that often confuse employees and employers. A quick guide:
If the employee is unwell or caring for someone: That falls under paid personal/carer's leave, not annual leave. You can request evidence (a medical certificate). If personal leave is exhausted and they ask to use annual leave instead, you can consider it, but apply the same fairness and operational rules.
If the employee has built up excessive leave (typically 8+ weeks): You can direct them to take it, provided you follow due process — offering to consult on timing first and ensuring they retain at least 6 weeks after the direction. This protects their wellbeing and your balance sheet.
If the employee wants to cash out annual leave: This requires a written agreement each time, and they must retain at least 4 weeks after cashing out. The payment must equal what they'd earn taking the leave. Awards and agreements may set additional limits.
If you shut down the business (e.g., between Christmas and New Year): You can direct employees to take annual leave during a shutdown if you give reasonable notice and the shutdown period is clear and documented. Public holidays falling during a shutdown period aren't deducted from annual leave balances.
How to make and document the call
A simple, repeatable process reduces disputes and shows fairness:
- Check notice and coverage. Has the employee given reasonable notice for your industry and role? Can you realistically cover the absence?
- Map overlaps. If multiple requests clash, use objective tiebreakers — first in, then length of service, then rotation across peak seasons. Don't use the "reason" as a tiebreaker.
- Plan the handover. What does the employee need to hand over? What documentation, customer briefings, or delegate responsibilities? Require a written plan.
- Communicate the decision. Approve with any conditions, or decline with a clear, factual explanation of the operational reason. Offer alternative dates where possible.
- Keep simple records. Note the request date, the decision, the reason, and any conditions. This supports payroll, audits, and dispute resolution.
Make sure you avoid the following red flag practices:
- Asking invasive questions about the reason ("Is it a holiday? Where?")
- Treating the same request differently for different employees
- Delaying responses beyond a reasonable timeframe (one week is standard)
- Making ad-hoc promises that undercut your policy (the easiest way is to just direct people to the official policy for leave applications, rather than giving an on-the-spot answer)
Where professional help is usually required
A lawyer can help you design a leave policy that aligns your operational needs with the law, model the fairness implications of peak-period restrictions, and draft clear documentation that protects you if a dispute arises. If you've declined a request and the employee has escalated to the Fair Work Ombudsman or mentioned discrimination, you'll want help framing your decision-making process and ensuring it's defensible on the record.
What's the take-home lesson?
Timing and coverage, not reasons. An employer's job in assessing annual leave is to ensure the business can function. It's not to judge whether a mental health break is more valid than a wedding or a holiday. The moment you start assessing reasons, you invite discrimination claims and lose the clarity that makes your decisions fair. Focus on whether you can staff the period. If you can, approve it. If you can't, say so clearly and offer an alternative.
The secondary rule: be consistent. If you approve mental health breaks for one employee, approve them for all. If you decline requests with less than two weeks' notice, decline them all. Consistency is what turns a tough call into a defensible decision.
So the key takeaways we'd leave you with are:
- Annual leave is for rest and recreation; employees don't need to justify their reasons, and you shouldn't judge the merit of their request.
- Refusal can be reasonable if operational needs genuinely require it — timing, coverage, and role criticality are the deciding factors.
- Document your decision process and apply it consistently across your team to reduce disputes and show fairness.
- Distinguish annual leave from personal/carer's leave, excessive leave directions, cashing out, and shutdown periods — each has its own rules.
- Use a simple approval framework (notice, coverage, handover, decision, records) that managers can apply without guesswork.