Approving leave requests is not a rubber-stamp exercise — it is a decision that balances employee wellbeing against business needs. The best managers approach it with a structured framework that ensures consistency, fairness, and transparency. Without a framework, approval becomes arbitrary, driven by the manager’s mood, the employee’s persuasiveness, or who asked first. A decision framework removes subjectivity and makes the process defensible.

This guide provides a step-by-step decision framework for approving or declining leave requests.

Key Takeaways

  • Use a checklist approach — every request passes through the same set of criteria before a decision is made.
  • Eligibility is the first gate — does the employee have sufficient leave balance and meet the notice requirements?
  • Capacity is the second gate — can the team operate effectively during the absence?
  • Fairness is the third gate — is the decision consistent with how other similar requests have been handled?
  • Documentation is the final step — record the decision and the reason in the system.

The approval decision framework

Use this checklist for every leave request:

Gate 1: Eligibility

  1. Does the employee have sufficient leave balance? If no, the request must be declined or partially approved.
  2. Has the employee met the required notice period? If not, is the absence genuinely unplanned?
  3. Does the employee meet any eligibility conditions for this leave type (e.g., service length for enhanced maternity)?

Decision: If any eligibility condition fails, decline and explain why. If all pass, proceed to Gate 2.

Gate 2: Capacity

  1. Will the team maintain minimum staffing levels during the absence?
  2. Are there critical tasks or deadlines that the employee owns during the requested period?
  3. Has another team member already been approved for leave on the same day?

Decision: If capacity is insufficient, offer an alternative date or negotiate partial attendance. If capacity is sufficient, proceed to Gate 3.

Gate 3: Fairness

  1. Has the same type of request been approved or declined for other employees under similar circumstances?
  2. Does the decision comply with the leave policy — or does it create an inconsistency?
  3. Could the decision be perceived as discriminatory?

Decision: If the decision creates an inconsistency, review the policy and adjust. If fair, proceed to Gate 4.

Gate 4: Documentation

  1. Record the decision in the leave management system.
  2. State the reason (approved or declined) in writing.
  3. If declined, note the specific policy criterion that was not met.

Applying the framework: examples

Example 1: Annual leave during a busy period

Request: Employee requests a week off during December year-end close.

Gate 1 — Eligibility: Leave balance is sufficient. Notice period met. Pass.

Gate 2 — Capacity: December close is a blackout period defined in the policy. Minimum staffing would be breached. Fail.

Decision: Decline the request, citing the blackout period. Offer an alternative week (e.g., the first week of January).

Example 2: Sick leave on a Monday

Request: Employee reports sick on a Monday morning.

Gate 1 — Eligibility: No notice required for unplanned absence. Pass.

Gate 2 — Capacity: Team can absorb the absence. Pass.

Gate 3 — Fairness: Check the Bradford Factor — is this part of a pattern? If not a pattern, approve. If a pattern, flag for review.

Decision: Approve the absence. Conduct a return-to-work interview on the employee’s return.

Example 3: Part-time employee requesting a full week

Request: Part-time employee (works Tuesday, Wednesday, Thursday) requests Monday to Friday off.

Gate 1 — Eligibility: Sufficient balance. Notice met. Pass.

Gate 2 — Capacity: The employee only works three days. Monday and Friday are not their working days. Pass.

Gate 3 — Fairness: Consistent with policy. Pass.

Decision: Approve three days of leave (Tuesday, Wednesday, Thursday). Monday and Friday are not working days and do not require leave.

Handling difficult scenarios

When multiple employees request the same popular date (e.g., the Friday before a bank holiday):

  • Approve on a first-come-first-served basis.
  • If requests arrive simultaneously, use a rotation system — the employee who did not get the date last time gets priority.
  • Never decline one employee without a clear, documented reason.

The emergency request

For genuinely urgent personal circumstances (bereavement, family emergency):

  • Bypass the notice period requirement.
  • Approve immediately and log retrospectively.
  • Compassionate leave does not follow the standard framework — it is treated as an emergency.

The pattern

An employee repeatedly takes sick leave on Mondays or Fridays:

  • Use the Bradford Factor to identify the pattern.
  • Conduct a return-to-work interview and ask open-ended questions.
  • Refer to occupational health if a medical reason is suspected.
  • Escalate through the formal absence management process if the pattern continues without explanation.

Common approval framework mistakes

1. Approving without checking capacity

The most common error. A manager approves because they like the employee, not because the team can handle the absence.

2. Declining without a policy reason

“We need you here” is not a sufficient reason. The refusal must reference a specific criterion in the leave policy.

3. Inconsistent treatment

Different managers making different decisions for the same scenario. Standardise the framework across all managers.

4. Not documenting the decision

Verbal approvals create disputes. Every decision must be recorded in writing with the reason.

Putting it into practice

Five checks cover most leave approval decisions:

  1. Run every request through the four-gate framework: eligibility, capacity, fairness, documentation.
  2. Check team capacity before approving — do not approve first and hope for the best.
  3. Apply the same criteria to every request, regardless of the employee or the manager.
  4. Document every decision with the reason in the leave management system.
  5. Review the framework quarterly and adjust the criteria based on real decisions.
You can take advantage of the free 14 days trial and explore Leave Balance.

A leave management system that embeds the approval framework — checking balances, capacity, and policy compliance automatically — makes the decision consistent, fast, and auditable.

Frequently Asked Questions

How do you decide whether to approve or decline a leave request?

Run the request through a structured framework: check eligibility (balance and notice), check capacity (minimum staffing and critical tasks), check fairness (consistency with other decisions), and document the outcome.

Can you decline a leave request for business reasons?

Yes, if the business reason is defined in the leave policy — minimum staffing, blackout periods, or insufficient notice. The reason must be documented and communicated to the employee.

How do you handle multiple requests for the same day?

Use first-come-first-served or a rotation system. Document the reason for the decision and offer alternatives to those declined.

What if the employee disagrees with the decline?

If the leave policy provides for an appeal, the employee should be able to appeal the decision to a more senior manager or HR. The appeal should be heard promptly.

Should leave approval decisions be in writing?

Yes. Every decision should be recorded in the leave management system with the date, the decision, and the reason. This creates an audit trail and prevents disputes.

This article is general information, not legal advice.

Last updated: 26 July 2026.