Companies may need to record long-term leaves, like parental, maternity, adoption, unpaid leave, or sickness, either as a Lifecycle status (via Flows) or as Time Off.
Here’s a quick comparison 👇
| Lifecycle Status (via Flow) | Time Off | |
|---|---|---|
| Best for | Extended absence periods | Specific days off |
| Who sets it | Admins (or other permitted users) via a Flow | Employees submit requests, or Admins/Managers on their behalf |
| Employee status | Changes from Employed to Leave; can be set to active or inactive | Remains active (cannot be marked inactive) |
| Visibility | Profile shows a Leave status (blue icon) Not shown as OOO in calendar | Profile shows a Time Off emoji Shown as OOO in the Time Off Calendar 📅 |
| Filters/Reporting | Can filter by Lifecycle status | Included in KPIs; no specific filter (custom fields can be used) |
| Accruals & Requests | Configure in policies whether allowance accrues and if requests are allowed while on leave | Policies define if allowance accrues (Proration of allowance > More settings > Days to exclude) and whether requests can be overridden |
| End of leave | Requires manual return via the Actions button (even if an end date is set) | Ends automatically on the defined end date (but can be edited) |
Choosing the Right Method
-
Use Lifecycle status for long-term tracking, employment status changes, and filtering
-
Use Time Off for day-based absences and when you want employees to show as OOO
-
Both methods can be combined 🎯
-
Multiple Leave Flows and Time Off policies can exist side by side
-
A Task List can trigger when time off is approved, reminding you to also use the corresponding Flow
-
The best option depends on your company’s policies and how you want to manage visibility, accruals, and employee status.