Last-minute leave requests are requests submitted with less notice than the policy requires — often the day before or the same day. They are inevitable and disruptive. The manager’s job is not to prevent them but to have a clear process for handling them that balances employee needs against business requirements. Without a process, managers make inconsistent decisions based on who asks, how they ask, and how the manager feels that day.

This guide covers how to handle last-minute leave requests — from the approval framework to communicating decisions and managing the disruption.

Key Takeaways

  • Last-minute leave is inevitable — have a process before it happens, not after.
  • Differentiate between genuinely unplanned absence (sick leave, emergencies) and planned leave submitted late.
  • Business criticality is the primary criterion for declining a last-minute request.
  • Consistency matters — apply the same criteria regardless of who is requesting.
  • Document every decision, especially declines, to avoid disputes.

Step 1: Classify the request

Not all last-minute requests are the same:

Genuinely unplanned

  • Sick leave — the employee is ill and cannot work. No advance notice is possible.
  • Family emergency — bereavement, hospitalisation, urgent family matter.
  • Bereavement — immediate leave for the death of a close relative.

For genuinely unplanned absence, the standard approval process does not apply. The absence is logged, not requested.

Planned leave submitted late

  • Holiday request — the employee wants time off next week or the week after but did not submit in advance.
  • Personal appointment — a medical appointment or personal commitment that could have been scheduled earlier.
  • Convenience — the employee found a cheap holiday or wants a long weekend.

For planned leave submitted late, apply the approval framework but with the reduced notice period as a factor.

Step 2: Apply the approval framework

Run the request through the standard four-gate framework, but adjust for the late submission:

Gate 1: Eligibility

  • Does the employee have sufficient leave balance? If yes, proceed.
  • Is the absence type eligible for late submission? Sick leave is; planned leave may not be.

Gate 2: Capacity

  • Can the team absorb the absence with no notice?
  • Are there critical tasks, deadlines, or meetings that the employee owns?
  • Is another team member already on leave?

If the request would breach minimum staffing, it should generally be declined.

Gate 3: Fairness

  • Has the same type of request been approved or declined for others under similar circumstances?
  • Does declining this request create an inconsistency?

Gate 4: Documentation

  • Record the decision and the reason in the leave management system.
  • Communicate the decision to the employee promptly.

Step 3: Decide

Approve if

  • The absence is genuinely unplanned (sick leave, emergency).
  • The team can absorb the absence without breaching minimum staffing.
  • The employee has a legitimate reason for the late submission.
  • Declining would cause disproportionate harm to the employee.

Decline if

  • The request is for planned leave that could have been submitted earlier.
  • The team cannot absorb the absence — critical deadlines, minimum staffing breached.
  • The employee has a pattern of last-minute requests.
  • Approving would set a precedent that undermines the notice period policy.

Partially approve if

  • Some of the requested dates are feasible, others are not.
  • An alternative date can be offered.

Step 4: Communicate the decision

Approved requests

  • Confirm the dates and type of leave.
  • Note any immediate actions (handover of tasks, coverage arrangements).
  • Remind the employee of the notice period policy for future requests.

Declined requests

  • State the specific reason for the decline (reference the policy or capacity).
  • Offer an alternative date where possible.
  • Note the right to appeal if the policy provides for it.
  • Keep the tone supportive, not punitive.

For genuinely unplanned absence

  • Acknowledge the absence.
  • Ask for an update on the expected return date.
  • Do not apply the approval framework — the absence is logged, not approved.

Step 5: Manage the disruption

When a last-minute absence is approved:

  1. Redistribute tasks — identify the employee’s critical tasks and assign them.
  2. Notify stakeholders — if deadlines will be affected, tell clients or internal teams.
  3. Adjust the workload — other team members may need to absorb additional work.
  4. Check capacity — if the absence creates a staffing crisis, escalate to senior management.

Step 6: Address the pattern

If the same employee repeatedly submits last-minute leave requests:

  1. Review the absence record — is there a pattern (Mondays, Fridays, around holidays)?
  2. Conduct a return-to-work interview — ask open-ended questions about the pattern.
  3. Discuss the pattern with the employee in a one-to-one meeting.
  4. Refer to occupational health if a medical cause is suspected.
  5. Trigger the formal absence management process if the pattern continues without explanation.

Common last-minute leave handling mistakes

1. Approving without checking capacity

The manager approves because they want to be nice, and the team is left short-staffed. Always check capacity first.

2. Declining without a reason

“We can’t afford to have you off” is not a sufficient reason. State the specific policy criterion or business case.

3. Inconsistent treatment

One employee gets approved, another gets declined for the same scenario. Standardise the criteria.

4. Not documenting

Verbal decisions create disputes. Record the decision and the reason in the system.

5. Not addressing patterns

Repeated last-minute requests signal a problem. Address it early.

Putting it into practice

Five checks cover most last-minute leave situations:

  1. Classify the request as genuinely unplanned or planned-but-late.
  2. Run the request through the approval framework with the late submission as a factor.
  3. Check team capacity before approving — do not approve first and hope for the best.
  4. Communicate the decision promptly and in writing, with the reason.
  5. Monitor patterns and address them through the formal process.
You can take advantage of the free 14 days trial and explore Leave Balance.

A leave management system that tracks last-minute requests, checks team capacity in real time, and flags patterns helps managers make consistent, fair decisions when unexpected leave disrupts the plan.

Frequently Asked Questions

Should I approve last-minute leave requests?

It depends on whether the absence is genuinely unplanned (approve) or planned leave submitted late (check capacity and apply the policy). Always check team capacity before approving.

Can I decline a last-minute leave request?

Yes, if the request breaches minimum staffing, conflicts with critical deadlines, or is for planned leave that could have been submitted earlier. Document the reason.

How do I handle sick leave reported at the last minute?

Sick leave is genuinely unplanned. Log the absence, confirm the expected return date, and arrange cover. No approval is needed.

What if the same employee keeps requesting last-minute leave?

Review their absence record, conduct a return-to-work interview, discuss the pattern in a one-to-one, and trigger the formal absence management process if the pattern continues.

How do I manage the disruption from a last-minute absence?

Redistribute critical tasks, notify stakeholders of any deadline impact, and adjust the team workload. If the absence creates a staffing crisis, escalate to senior management.

This article is general information, not legal advice.

Last updated: 26 July 2026.