Leave requests processed manually take 3+ days and create payroll errors — every month, finance runs corrections because a leave balance was wrong or a deduction was mis-keyed. Without a structured workflow, requests arrive by email or chat, the manager checks a shared spreadsheet for conflicts, HR verifies the balance in the HRIS, and payroll gets notified by yet another email.

The compliance angle is real too: missing leave authorizations, undocumented absences and expired carry-over create legal exposure during a labor inspection.

The leave request is submitted via the self-service portal with exact fields: employee_id (lookup, auto-filled), leave_type (select: Paid-leave/RTT/Unpaid/Sick/Family/Overtime-recovery), start_date (date), end_date (date), half_day_start (boolean), half_day_end (boolean), comment (textarea), attachment (file upload, e.g. medical certificate), requested_days (number, auto-calculated from dates).

The workflow is structured as a decision tree with 3 branches (balance-reject, conflict-flag, fast-track) after Step 2, and 6 steps end-to-end. Every action is appended to the timeline_leave audit subtable.

• Step 1 (Start — employee): the employee submits the leave request via the self-service portal with leave_type, start_date, end_date and comment.

• Step 2 (sql-query — balance check): the sql-query module reads the employee's leave balance from the HRIS database and compares requested_days against the remaining balance for leave_type. Sub-branch A (balance-reject): if requested_days exceeds the remaining balance, the workflow rejects automatically and emails the employee with the balance detail. Sub-branch B (conflict-flag): the AI copilot scans the team calendar for overlapping absences (same team, same dates, quorum risk) and flags them to the manager. Sub-branch C (fast-track): if leave_type is Sick and a medical certificate is attached, the request bypasses manager approval and routes straight to payroll notification.

• Step 3 (email — manager approval): for branches B and C-non-sick, the workflow emails the manager with the request, balance status and team-calendar conflicts; the manager approves, rejects or asks for modification directly from the email link. Escalation: if no decision within 48h, the workflow emails the next-level manager.

• Step 4 (email — payroll notification): on approval, the workflow emails payroll with leave_type, dates and deduction so the next payslip is accurate.

• Step 5 (usePDF — leave authorization): the approved leave is generated as a signed PDF leave authorization via usePDF with employee name, leave_type, dates, requested_days and approval chain.

• Step 6 (Calendar update): the workflow updates the team calendar and the employee's out-of-office auto-reply.

Teams deploying Utilyx leave management cut request-to-decision time from 3+ days to under 4 hours, eliminate payroll corrections on leave balances, and achieve 100% leave-document compliance for labor inspections.

The HRSD vocabulary (leave balance, RTT, team calendar, quorum, leave authorization, usePDF, useArchive) is native to the platform, so the AI copilot proposes the right schema directly — and the no-code visual designer lets any HR analyst adjust approval thresholds and escalation rules without coding.