Handling leave requests is one of the most frequent management tasks — and one of the most poorly handled. Inconsistent approval, unclear criteria, and slow responses erode trust and create frustration. A structured process ensures every request is treated fairly, team coverage is maintained, and the employee knows exactly what to expect. The goal is not to say yes to everyone — it is to have a transparent process that makes the decision clear.

This guide covers how to handle leave requests from submission to decision, including approval criteria, conflict resolution, and communication.

Key Takeaways

  • Consistency is the foundation — every request must follow the same process regardless of who submits it.
  • Clear criteria prevent disputes — define what constitutes a reasonable approval or refusal before requests arrive.
  • Timeliness matters — a request left unanswered for a week is a management failure.
  • Transparency builds trust — employees should understand why their request was approved or declined.
  • A system is essential — manual processes create delays, inconsistency, and errors.

Step 1: Define the submission process

Employees need a clear, single way to submit leave requests:

  1. Use a leave management system — the request goes into one place, visible to the manager and HR.
  2. Set notice periods — define minimum notice for each leave type (e.g., 2 weeks for annual leave, 15 weeks for maternity).
  3. Require essential information — dates requested, type of leave, reason (they do not need to provide a diagnosis for sick leave).
  4. Acknowledge receipt — the system should confirm the request has been submitted and is pending approval.

Eliminate email and Slack as submission channels. They create duplicate records, lose requests, and provide no audit trail.

Step 2: Set clear approval criteria

Managers need criteria to make consistent decisions. Define:

Automatic approval conditions

  • Request meets the notice period
  • Sufficient team coverage exists (e.g., no more than 20% of the team off on the same day)
  • No blackout period applies
  • The employee has sufficient leave balance

Reasons for refusal

  • Insufficient notice (unless genuinely unplanned)
  • Critical staffing shortfall — fewer than the minimum number of staff on that day
  • Blackout period — pre-defined busy periods where leave is restricted
  • Repeated requests on the same day (e.g., every Friday) without business justification

What is not a valid reason for refusal

  • The manager’s personal preference
  • “Everyone else wants that day off” without a capacity analysis
  • Retaliation for previous absence
  • Discrimination on any protected characteristic

Step 3: Respond promptly

Set a service level for leave request responses:

  • Standard requests — approve or decline within 2–3 business days.
  • Urgent requests — respond within 24 hours.
  • Long-lead requests (e.g., holidays abroad, weddings) — respond within one week.

If the manager does not respond within the defined period, the system should escalate or auto-approve. Silence is not a decision.

Step 4: Check team capacity

Before approving, check whether the team can absorb the absence:

  1. Minimum staffing — define the minimum number of people required on any given day.
  2. Overlap check — if multiple team members request the same day, the first approved request takes priority.
  3. Critical tasks — check whether the employee has critical tasks or responsibilities that cannot be delegated.
  4. Cross-coverage — can another team member cover the essential duties?

If the request would drop the team below minimum staffing, offer an alternative date or negotiate a partial attendance.

Step 5: Communicate the decision

Every decision should be communicated clearly:

Approved requests

  • Confirm the dates and type of leave
  • Note any pre-departure tasks or handover requirements
  • Remind the employee of the return date

Declined requests

  • State the specific reason for the decline (refer to the policy criteria)
  • Offer an alternative where possible
  • Note the right to appeal if the policy provides for it

Partial approvals

  • If only some of the requested dates can be approved, state clearly which dates are approved and which are declined
  • Explain the reason for the partial approval

Step 6: Handle special situations

Last-minute requests

For genuinely unplanned absences (sick leave, family emergencies), the submission and approval process adapts:

  • The employee notifies the manager immediately (phone, Slack, or Teams)
  • The absence is logged in the system retrospectively
  • The manager confirms the absence and records it

Overlapping requests

When two employees request the same day:

  • First come, first served is the simplest approach.
  • For critical dates, use a rotation or lottery system.
  • Never approve one and decline the other without a clear, documented reason.

Bank holidays and peak periods

  • Define blackout periods in advance (e.g., December close, product launches).
  • Communicate blackout periods to the team well ahead of time.
  • If an employee requests leave during a blackout, the refusal should reference the pre-defined policy, not ad-hoc judgement.

Common leave request handling mistakes

1. Inconsistent approval

Different managers approving the same type of request differently erodes trust. Standardise the criteria.

2. Slow response

A request submitted on Monday and not answered until Friday is a management failure. Respond promptly.

3. No written record

Verbal approvals create disputes. Every decision should be recorded in the leave management system.

4. Refusing without reason

Declining a request with “we need you here” is not a sufficient reason. State the specific business case.

5. Not checking capacity

Approving leave without checking team coverage creates staffing gaps that could have been avoided.

Putting it into practice

Five checks cover most leave request handling:

  1. Use a centralised system where all requests are submitted, tracked, and responded to.
  2. Define approval criteria in the leave policy so every manager applies the same rules.
  3. Respond within the defined service level — do not leave requests in limbo.
  4. Check team capacity before approving, and offer alternatives when coverage is insufficient.
  5. Communicate every decision clearly, in writing, with the reason and any next steps.
You can take advantage of the free 14 days trial and explore Leave Balance.

A leave management system that automates the submission-to-approval workflow, checks team capacity, applies consistent criteria, and records every decision makes handling leave requests fair, fast, and auditable.

Frequently Asked Questions

How long should it take to respond to a leave request?

Within 2–3 business days for standard requests. For urgent or last-minute requests, respond within 24 hours. Set a service level and hold managers accountable to it.

Can a manager refuse a leave request?

Yes, if the refusal is based on legitimate business reasons defined in the leave policy — insufficient notice, minimum staffing requirements, or blackout periods. Refusals must not be discriminatory.

What if two employees request the same day?

Use a first-come-first-served approach, or a rotation system for popular dates. Document the reason for the decision.

How should last-minute leave requests be handled?

The employee notifies the manager immediately and logs the absence in the system retrospectively. The manager confirms the absence and records it.

Should leave approvals be in writing?

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

This article is general information, not legal advice.

Last updated: 26 July 2026.