A staff member asks for two days off next month. The request goes to their supervisor, who is on leave. It waits. A week later the staff member asks HR what happened. HR does not know who has it. By then the roster for that week is already published.
Nobody did anything wrong, and the process still failed. A leave approval process stalls when nobody owns the next step, or when the owner is away. This guide shows you how to design steps that keep moving.
What is a leave approval process?
A leave approval process is the set of steps a leave request goes through before it is approved or rejected. The leave approval workflow says who decides at each step, what they check, and how long they have. It ends when the employee knows the answer and the roster shows it.
The leave approval process, step by step
- The employee sends the request. It gives the dates, the leave type, a full or a half day, and any document or reason the policy asks for.
- The request goes to the first approver. This is a role, such as the supervisor or branch manager of the employee's site.
- The first approver checks cover. They look at the roster and at who else is off on those dates.
- HR checks the rest, if you have a second step. HR checks the balance, the leave policy and any document.
- The last approver decides. They approve the request, or reject it with a reason.
- The employee hears the result. The balance changes, and a rejection shows its reason.
- The roster catches up. The person comes off their shifts on those days, and someone plans the cover.
Most small teams need only steps 1, 2, 3, 5 and 6, with one approver. Add the HR step when it checks something the supervisor cannot.
An example leave approval flow
Here is a two-step flow for a company with several branches and HR in head office. A cashier asks for two days of leave next month.
| Step | Who | What they do |
|---|---|---|
| Request | Employee | Sends the request for two full days from their phone. |
| Step 1 | Supervisor (branch manager) | Checks that the branch still has enough cashiers on the roster on those days, then approves. |
| Step 2 | HR | Checks the balance after other pending requests and the leave policy, then approves. |
| Result | Employee and roster | The employee sees the approval. The scheduler sees the leave when they build that week. |
If the supervisor is away, the request should not wait for them. The rest of this guide shows how to set time limits, a backup and a handover so it keeps moving. To run this flow in software, see leave management and approval workflows.
A note on the law
Some kinds of leave and the days that come with them are set by law. Check the current DOLE rules or ask a payroll specialist before you write a rule that refuses, delays or limits a type of leave. This guide is about the approval process, not the entitlements.
Why approvals stall
- Too many steps. Each step adds a wait. Three people who each take two days make a request wait almost a week.
- A named person, not a role. When the request goes to "Maria" and Maria is away, it stops.
- No time limit. Without a deadline, a request sits at the bottom of the inbox.
- No backup. Nobody else is allowed to decide, so nobody does.
- Missing information. The approver cannot see the roster or the balance, so they ask around first.
- Two steps that check the same thing. The second approver repeats the first one's work.
Five rules for steps that move
- Use as few steps as you can. Most leave needs one approver. Add a second step only when it checks something the first step cannot.
- Give each step one job. The supervisor checks cover. HR checks the balance, the policy and any document. Write down what each step is for.
- Assign roles, not people. "The branch manager of the site" still works when the branch manager changes.
- Set a time limit for each step. Choose a limit that suits your business, for example two working days. Send a reminder when it passes.
- Name a backup. Decide who can act when a step waits too long, and let approvers hand over before they go away.
How many steps do you need?
| Situation | Steps | Who checks what |
|---|---|---|
| One site, owner manages the team | 1 | The owner checks cover and the balance. |
| Several branches, HR in head office | 2 | The branch manager checks cover. HR checks the balance, the policy and documents. |
| Large teams with department heads | 2 or 3 | The team lead checks cover. The department head checks workload. HR checks the policy. |
These are starting points, not rules. If a step rarely says no, ask whether it needs to be there.
Give the approver what they need
An approver decides fast when the facts are in front of them. For a leave request, that means:
- The dates, the leave type, and whether it is a full day or a half day.
- The person's balance after any requests that are still pending.
- Who else in the team is on leave or on the roster on those dates.
- Any document the leave type needs, such as a medical certificate.
- The reason, if your policy asks for one.
If the approver has to open three spreadsheets and a group chat, the request will wait.
Time limits, reminders and escalation
A time limit only works when something happens at the end of it. A simple pattern:
- The request reaches the step, and the approver is told.
- When the time limit passes, the approver gets a reminder.
- If the request still waits after a second period, a backup role can decide as well.
The backup is not a punishment for the first approver. It is a safety net for the staff member, who is waiting to book a bus ticket or tell their family.
Hand over before you go away
Approvers take leave too. Before they go, they should hand their approvals to a colleague for a set period, with a start and an end date. The colleague decides on their behalf, and the record shows both names. When the period ends, the approvals come back without anyone having to remember.
Keep it fair
- Nobody approves their own request. A supervisor's leave goes to their own manager or to HR.
- One person, one step. If the same person approves two steps, the second step checks nothing.
- Every no has a reason. "Two others are already off that week" is a reason. A silent rejection is not.
- Offer another date. When cover is the problem, suggest dates that work.
- Decide in order. Two requests for the same dates are handled in the order they came in, unless your policy says otherwise.
Tell staff how it works
Put the process in your leave policy in plain words. Say how early to request planned leave, who approves it, and how long each step usually takes. Tell staff where they can see the status of their request. People chase approvals when they cannot see where a request is.
When you change the steps, apply the new steps to new requests. A request that is already open should finish on the steps it started with, so nobody has to start again.
Connect leave to the roster
An approved request is only half the job. The person must also come off the roster for those days, and someone must cover the gap. Check approved leave before you build each week. For the cover, read how to fill open shifts and call-outs fast.
Leave approvals in Workforce Pinas
Workforce Pinas lets you set up to three approval steps for leave. Each step lists the roles that can approve it and where they apply: one site, one legal employer or the whole organisation. You set the hours that each step has for a decision, and the approvers get a reminder when that time passes. If the request still waits, the escalation roles you choose can act. An approver can delegate to a colleague for a set period.
Nobody approves their own request, and one person acts on one step only. A rejection needs a reason. A change to the steps does not change requests that are already open. Approvers see new requests in one approvals list and in the in-app notifications, and staff see pending days next to their balance in the app. The roster warns you when a shift falls on a day of approved leave. See leave management and approval workflows, or ask us for a demo.
