- >
- Workflow>
- Leave Request Approval Workflow: Steps, Routing Rules, and Exception Paths
Leave Request Approval Workflow: Steps, Routing Rules, and Exception Paths
A leave request approval workflow is a structured process that moves a time-off request from employee submission through manager review to employee notification and a shared calendar update. A second approver or HR review joins that path only when a routing rule calls for it.
TL;DR
- The employee submits leave type, dates, and a reason by form or portal, and the direct manager approves or rejects
- Standard leave needs one approver, and leave type, length, or reason code can add HR or a department head
- Microsoft Forms, Power Automate, SharePoint, and Outlook cover a basic build, Workday and SAP handle leave in the system of record, and Kissflow adds a governed approval layer beside them
The sequence holds until a request falls off it. A manager goes on vacation with requests pending, two teammates ask for the same week, or a request exceeds the balance. If nobody decides in advance what happens next, the request waits, the employee plans around an unanswered question, and HR reconstructs the decision later from an inbox.
If you run approvals around a core HR system and IT has to sign off on how they run, design for those moments first. The standard steps, the common tools, and the routing rules you configure all follow from them. Keep the approval layer separate from the system that owns the employee record, such as Workday or SAP.
Standard leave request workflow steps
This five-step sequence is the default path. The exception table later on this page lists the situations that branch off it.
- Submission: The employee completes a request in a form, portal, or HR system with the leave type (vacation, sick, or parental), start and end dates, a reason, and handover notes
- Manager review: The direct manager gets a notification by email, Teams, or Slack, checks the leave balance and team coverage, and approves or rejects from the inbox
- Second approver or HR review: A department head or HR decides next only when a routing rule applies, and standard leave skips this step
- Decision and notification: The employee receives the outcome by email, app, or status update
- If approved: The request moves to the final step with its approval on record
- If rejected: The manager’s comments reach the employee, and nothing goes on the calendar
- Calendar and balance update: Approved leave appears on a shared team calendar such as Outlook or Google Calendar, and the balance is updated in the system that owns it
Each action in the sequence joins the audit trail, so the record builds as the request moves.
Common tools for a leave approval workflow
Microsoft Forms, Power Automate, SharePoint, and Outlook form a common build in Microsoft 365, and Teams can carry the approval notifications.
- Request intake: Microsoft Forms, a portal, or an HR system records the leave type, dates, and reason.
- Approval routing: Power Automate sends the request to the manager and waits for a decision.
- Request log: A SharePoint list records each request, and a flow can start when an item is created.
- Calendar: Outlook or Google Calendar shows approved leave to the team.
- Core HR modules: Workday and SAP handle leave inside the system of record.
Why leave requests stall
Leave requests stall when the approver is out and the record lives in an inbox.
On email and spreadsheets, that request has no route:
- Employees wait without a status and plan around an answer they do not have yet
- Balances drift out of date, and payroll inherits the mismatch
- Someone searches old threads when compliance asks who approved an absence and when
IT sees a different risk: a spreadsheet or unsanctioned form that nobody reviewed. Manual handling is one driver you can fix, though staffing gaps and unclear policy need their own answers.
Leave approval workflow practices
A short chain with named backups keeps requests moving when an approver is out.
- Short chain: Use single-level approval for standard leave and add a second level only where policy requires it
- Backup approvers: Name a substitute for each approver when you design the chain
- Response target: Give every approver a written response window, because a request with no deadline has no point at which to escalate
- Written exceptions: Decide each off-script route before launch, then record it where HR and IT both review it
- Rule history: Log changes to routing rules as carefully as you log leave decisions
What to decide before a leave workflow goes live
A twelve-day parental leave request arrives from a team already short that week: who approves it first, and who covers? Forms, calendars, balance ownership, routing, and exceptions each need an owner before that request arrives, because it exposes any rule someone assumed and nobody wrote down.
Working days and holidays for each group
A team on a six-day week and an office on a five-day week need separate calendar logic, or the same absence counts differently for each. Set working days and holidays for each group, then limit the form to the fields an approver actually uses to decide.
Balance handling when a request is canceled
Read the balance from the human resources information system (HRIS) at review and update it there after the decision. A withdrawn request has to return its days, or the next employee conversation starts with a dispute.
The status that releases leave to payroll
Payroll needs only approved days, so agree which status releases a record to payroll, and HR’s reports on leave trends will match what payroll paid.
Routing by leave type, length, reason code, and department
A flat “send it to HR” rule breaks quickly, so write the conditions down. Every threshold below is an example you configure, not a standard. The twelve-day parental leave request above meets two conditions at once, so decide which approver goes first.
| Condition | Example rule | Who decides |
|---|---|---|
| Standard vacation or PTO within balance | Single-level approval | Direct manager |
| Leave of more than ten days | Adds a second approval | Department head |
| Parental or other special leave | Adds an HR review | HR |
| Sick leave with a surgery reason code | Routes to an HR review | HR |
| Department with a minimum-coverage rule | Flags team overlap before the decision | Line manager or project lead |
Routes for each off-script situation
Approver absence, a missed response window, insufficient balance, a manager’s question, an HR trigger, and cancellation each need an outcome, a recipient, and a record before the workflow goes live.
| Situation | What happens | Who is notified | What is logged |
|---|---|---|---|
| Approver out of office | A substitute approver receives the request | Substitute approver and employee | The handoff and who acted |
| No response inside the window | The request escalates, auto-approves, or auto-rejects, based on your configured timeout | Next approver, original manager, and employee | Timeout reached, rule applied, and outcome |
| Insufficient balance at approval | The request stops before final approval and returns to the employee | Employee and manager | Balance at the check and resulting status |
| Manager needs more information | The request goes back to the employee with a question | Employee | Question, reply, and timestamps |
| Leave type or reason code that triggers HR | The request moves to an HR review | HR and manager | Reason code and routing path |
| Request canceled | The request is withdrawn, the days return to the balance, and the calendar entry comes off | Manager, plus HR if already approved | Who canceled, when, and the balance change |
How the main ways to run a leave approval workflow compare
Who changes a rule, and what evidence remains afterward, separate these routes more than the request form does.
| Approach | Who can change an approval rule | Audit evidence | Exception routing | IT governance |
|---|---|---|---|---|
| Email and spreadsheets | Whoever maintains the process informally | Inboxes and file versions | Handled by hand, case by case | Sits outside formal IT controls |
| Microsoft Forms, SharePoint, and Power Automate in Microsoft 365 | The flow owner, by editing the flow | A SharePoint list of requests | Built as steps in the flow | Depends on who owns the flow and the list |
| HRIS-native module (Workday) | Administrators, through the Request Time Off business process | Held in the system of record | Workday routes a request to approvers when it requires approval | Managed with the core HR system |
| Enterprise application platform (Kissflow) | Business teams and IT, on a platform IT governs | Audit logs with every action timestamped and attributed | Each exception gets a named route before launch | Requires adding a platform beside the system of record, while IT governs what business teams build |
How an approval layer sits beside Workday or SAP
Your HR system stays at the home of the employee record. A separate approval layer picks up the routing work around it: finding a substitute approver, resolving a coverage clash, and passing the case to HR.
Kissflow, an AI-powered enterprise application platform, fills that role for leave. Business teams set the approval rules, IT oversees the platform, and the core system keeps the record.
Governance is part of the platform from the start, which is what makes speed safe. An admin controls what goes live. For a closer look at routed approvals, read the no-code approval workflow guide.
- Every action is timestamped and attributed in the audit log
- Kissflow works as the governed execution and exception layer around systems of record such as Workday and SAP
- Its certifications include SOC 1 Type II, SOC 2 Type II, SOC 3, ISO/IEC 27001, HIPAA, GDPR, and CCPA
Frequently asked questions
When does a leave request count as approved?
A request counts as approved once the calendar entry and the balance in the owning system reflect the decision, so check both before treating leave as final.
Can I customize the leave approval process for different departments?
Yes. Thresholds such as a second approval above a set number of days are configurable examples, so set them from your own leave policy.
What do I need to build a leave approval workflow in Microsoft 365?
Microsoft Forms, Power Automate, SharePoint, and Outlook cover the standard path. Assign an owner to maintain the substitute approver and timeout branches, and keep the balance update in the system that owns it.
How do I give leave approval as a manager?
Approve or reject from the notification after checking balance and coverage, adding comments if you reject. Two cases change the route: if the balance is short, the request stops before final approval and returns to the employee, and if you need more detail, send it back with a question.
