Workflow Template
Leave Request and Approval Workflow
Handles end-to-end employee leave requests: captures leave type, dates, reason, and supporting documents; checks eligibility; routes to manager for review and approval or rejection with optional change requests; notifies the employee of the outcome; and records approved leave.
Managing leave requests manually means lost emails, missed eligibility checks, and frustrated employees waiting on decisions. This workflow handles the entire process — capturing leave type, dates, reason, and supporting documents, checking eligibility, routing to the right manager, and notifying the employee at every stage. HR teams and operations managers run it directly inside assess.one to keep leave records accurate and decisions moving.
Business Outcomes
- Reduce leave approval turnaround from days to hours
- Eliminate manual eligibility checks with automated balance verification at submission
- Ensure every request is tracked with a full audit trail from submission to approval
- Cut HR admin time spent chasing managers for decisions
- Give employees real-time status notifications so they stop asking HR for updates
Workflow Steps
Steps
- 1Create Leave Request Recordcreate record
Creates a new leave request record and sets the initial status to Submitted.
- 2Set Status: Submittedupdate record
Records the leave request status as Submitted.
- 3Eligibility & Balance Checkcreate task
HR or system checks whether the employee has sufficient leave balance and meets eligibility criteria for the requested leave type.
- 4Record Eligibility Outcomeupdate record
Persists the eligibility outcome and available balance to the leave request record.
- 5Route on Eligibility
Routes eligible requests to manager approval; ineligible requests are rejected and the employee is notified.
eligibility_outcome: "Eligible"→Manager Review & ApprovalDefault→Set Status: Ineligible - 6Set Status: Ineligibleupdate record
Updates the record status to Rejected due to ineligibility.
- 7Notify Employee: Ineligiblesend email
Emails the employee that their leave request could not proceed due to ineligibility.
- 8Manager Review & Approvalrequest approval
Sends the leave request to the employee's manager for approval or rejection, with the option to request changes.
- 9Route on Manager Decision
Routes approved requests to final recording; rejected requests allow the employee to revise and resubmit.
approval_status: "approved"→Set Status: Approvedapproval_status: "rejected"→Notify Employee: Changes RequestedDefault→End - 10Notify Employee: Changes Requestedsend email
Emails the employee that their manager has requested changes or rejected the request, prompting them to revise and resubmit.
- 11Employee Revises Leave Requestcreate task
Employee reviews manager feedback and submits a revised leave request with updated dates or details.
- 12Update Record with Revised Datesupdate record
Persists the employee's revised dates and reason to the leave request record.
- 13Resubmit to Managerrestart from step
Restarts the workflow from the manager review step with the revised request details.
- 14Set Status: Approvedupdate record
Updates the leave request record status to Approved.
- 15Notify Employee: Approvedsend email
Emails the employee confirming their leave has been approved.
Fields
- Employee Full Name*
- Employee Email Address*
- Employee ID*
- Department*
- Leave Type*
- Start Date*
- +7 more fields
Forms
Employee Leave Request
10 fields
Data Views
All Leave Requests
employee_name, leave_type, start_date, end_date +3 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
How long does it take to get this workflow live?
You can publish the template and have it running in minutes. There is no implementation project, no IT involvement, and no external software to install. Once published, your team runs live leave requests through it immediately.
How do I set up the workflow for my organisation?
Open the template inside assess.one and customise the steps, roles, and approval logic directly in the platform. You can adjust leave types, eligibility rules, and notification content without writing any code. Changes take effect as soon as you republish.
What do I need to configure before going live?
You will need to assign roles — typically an employee submitter, an HR eligibility reviewer, and one or more managers for the approval step. You should also configure your notification messages and connect your preferred notification channel, such as email or Slack, inside assess.one. No third-party developer work is required.
Who needs access to run this workflow?
Employees need access to submit requests, HR staff need access to run the eligibility check step, and managers need access to review and approve or reject. You control role assignments directly inside assess.one. Access can be scoped so each person only sees the steps relevant to them.
How does the eligibility check step work?
The Eligibility & Balance Check step is a structured task assigned to the appropriate HR role. The reviewer records the outcome, and the workflow automatically routes the request — either notifying the employee of ineligibility or passing it to the manager for review. You can customise the eligibility criteria and the fields captured at this step inside the platform.
What happens if a manager requests changes instead of approving or rejecting?
The workflow routes the request back to the employee with a notification explaining what needs to change. The employee revises the dates or details, the record is updated, and the request is automatically resubmitted to the manager. This loop continues until the manager approves or rejects.
Can I customise the approval routing for different managers or departments?
Yes. You can configure routing logic inside assess.one to direct requests to different managers based on department, leave type, or any other field captured in the form. No external development is needed — routing rules are set directly in the workflow editor.
How are employees notified of the outcome?
Notifications are triggered automatically at each decision point — ineligible, changes requested, and approved. You configure the notification content and delivery channel, such as email or Slack, inside assess.one. Employees receive updates without HR needing to send anything manually.
Does the workflow create a record of approved leave?
Yes. Every approved request results in a completed record inside assess.one with the full history of the request, eligibility check, manager decision, and any revisions made. This gives HR a reliable audit trail without maintaining a separate spreadsheet or system.
Can this workflow handle compliance or policy requirements around leave approval?
The workflow enforces your approval process consistently on every request — no steps can be skipped and every decision is logged. You can add mandatory fields, required documents, or additional approval stages inside assess.one to match your specific HR policy or regulatory requirements.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
