DonkeyHR

Leave approval chains: manager first, then HR

A clear leave approval chain lets managers check work cover, HR check policy, and employees know who decides when someone is away or a request stalls.

DonkeyHR Team · 2026-10-27 · 5 min read

A practical leave approval chain sends the request to the employee’s manager first, then to HR for a policy and record check. Name a backup for each approver, explain when a stalled request moves to someone else, and define how long leave is handled. Keep the request, decisions and changes together so employees know whether their leave is approved and payroll receives the correct information.

Who should approve leave, and in what order?

The manager should check whether the team can cover the absence. That means looking at handovers, customer commitments and other planned leave. The manager should explain any concern about the requested dates rather than simply marking the request rejected.

HR should then check the leave category, available balance and the relevant policy. HR should also check that the recorded dates match the request and that similar cases receive consistent treatment.

In a small business, the owner or office manager may perform the HR role. Make that responsibility explicit. Employees should not have to guess whether the owner’s verbal agreement replaces the normal process.

Explain what each stage means. A manager’s recommendation should not appear to be final approval if an HR decision is still pending.

What should employees include in a request?

Ask for the dates, leave category, expected return and a short handover note where needed. Show employees how to report an urgent absence when they cannot use the usual request route.

Keep explanations proportionate. Approvers generally need enough information to make the decision, rather than a detailed personal account. If supporting information is needed, explain where to submit it and restrict access to those who need it.

Agree where requests belong. A conversation or message can alert the manager, but the decision should reach the agreed record. Otherwise, an employee may believe leave is approved while the attendance record still shows an unexplained absence.

Who approves when the manager or HR is absent?

Choose a named backup for each approval role. The backup should understand the team or policy well enough to decide, and have access to the information needed.

Define when delegation starts and ends. Planned absence allows a handover; unexpected absence needs a clear fallback. Tell employees who is covering, rather than asking them to chase whichever senior person happens to be available.

Delegation should transfer decision-making responsibility for the relevant requests. Record who actually approved each request. Do not record the absent manager as the decision-maker when someone else made the decision.

Avoid self-approval. Where the usual approver requests leave, route it to another authorised person. In a very small team, the owner may need to handle that exception.

What should happen when a request stalls?

Set an internal response window that suits your business and communicate it in the policy. Explain when employees should expect an acknowledgement and when they should receive a decision.

If a request remains unanswered, send it to the named backup or escalation owner. Escalation should identify who must act next. It should not mean that silence automatically becomes approval unless your policy expressly defines that outcome.

Keep pending requests visible, especially when the requested absence is approaching. Tell the employee that the request has moved and who is now responsible.

If the manager and HR disagree, assign a final decision-maker. Record the reason for the outcome and explain it to the employee. Avoid sending the request back and forth without a clear owner.

How should long leave follow the chain?

Define long leave in your own policy using the needs of the business. Do not present an internal threshold as a legal rule.

Keep the manager-then-HR sequence, but add a fuller handover review where appropriate. Consider ongoing assignments, access to shared work, customer contacts and responsibility during the absence.

Some leave categories may need different handling. Do not apply ordinary scheduling preferences to every situation without checking the applicable requirements. Rules can change as labour codes and related rules develop; check the current notification or official portal.

Where an additional decision is needed, name the person and explain their role. Avoid adding approvers merely because a request feels unusual.

What does an illustrative approval flow look like?

Illustrative worked example: An employee requests 3 working days of leave. Assume all the requested days count against the selected balance, with no intervening holiday or non-working day. The employee has an illustrative balance of 8 days, so approval would leave 8 − 3 = 5 days.

The manager checks the handover and recommends approval. HR checks the category and balance, records final approval and confirms the dates. If the manager is absent, the named backup performs the manager’s check and their decision is recorded.

For an illustrative long request, assume the employee asks for 12 working days from a balance of 18 days. On the same counting assumptions, approval would leave 18 − 12 = 6 days. These are example balances and durations, not statutory entitlements or limits.

The manager reviews a fuller handover. HR checks the policy and recorded balance. If the policy requires an additional decision, the named decision-maker resolves it before final confirmation. Until then, the request remains pending.

What records should you keep?

Keep enough information to reconstruct the decision without relying on someone’s memory. Record the requested dates, leave category, submission, approvers, decisions, reasons for changes and final outcome.

When approved dates change, preserve the earlier decision and record the amendment. Recheck work cover and the balance where needed. Make sure the employee receives the revised outcome.

Use this checklist before putting the chain into practice:

  • Name the manager and HR approver for each employee.
  • Name a backup for each approval role.
  • Explain when delegation applies.
  • Set a response window and escalation route.
  • Define how long leave and urgent absences are handled.
  • State what counts as final approval.
  • Keep decisions and amendments with the request.
  • Confirm how approved leave reaches attendance and payroll records.
  • Restrict access to personal supporting information.

Common mistakes

A frequent mistake is asking every senior person to approve every request. This adds waiting without making responsibility clearer. Give each approver a distinct purpose.

Another is treating a positive conversation as completed approval. Employees need an explicit outcome, with agreed dates and a clear status.

Avoid letting a backup approve without recording their identity. Also avoid changing an approved request quietly. Both practices make later questions about attendance or leave balances harder to resolve.

FAQ

Does every business need a separate HR approver?

The role can sit with the owner or office manager. What matters is that someone is responsible for the policy check and final record, and employees know who that is.

Should a delayed request become approved automatically?

Do not leave that open to interpretation. State the rule in your policy. A named escalation route gives an unanswered request an owner without making employees guess its status.

Can an employee change leave after approval?

Explain how to request an amendment. Review the changed dates, record the new decision and confirm the result. Update any affected handover, attendance or payroll information.

How can software support the agreed chain?

Write the responsibilities and exception routes before configuring the process. DonkeyHR, currently in beta, supports configurable leave approval chains, including manager then HR. Keep your delegation, escalation and long-leave rules clear so everyone understands who makes each decision.

Related reading