Leave types
Organize the time-off types your organization offers.
PLETOX / LEAVE MANAGEMENT
Time off, without the chase.
Clarity for everyone.
Bring leave balances, requests, and approvals into one place. Give employees a clear way to ask for time off and managers the context to make a decision.
Acme IndustriesPeople operations / SeptemberTIME OFF, WITH EVERYONE IN THE LOOP
Clear requests. Considered decisions.
Recent requests3 sample records
| Employee / type | Dates | Duration | Status |
|---|---|---|---|
| Asha ShahAnnual leave | 28 - 29 September | 2 days | Pending |
| Neha PatilCasual leave | 24 September | Half day | Approved |
| Riya DesaiSick leave | 21 September | 1 day | Approved |
A pending request is not approved time off. Decisions follow the configured review process.
Asha Shah / Leave balancesSample policy year
Annual leave
18 days allocated / 6 usedSick leave
8 days allocated / 2 usedCasual leave
6 days allocated / 1 usedIllustrative balances for Asha Shah. Pending requests are shown separately; balance treatment follows your policy.
FROM AVAILABLE DAYS TO APPROVED TIME OFF
A simpler request.
A more connected decision.
Keep the policy, the employee, and the working-day impact in the same conversation.
Balance visibility
Show available balances in the request workflow.
Date ranges
Record the dates the employee is requesting.
Full & half days
Support full-day and half-day leave requests.
Reasons & context
Keep the reason alongside the requested dates.
Supporting files
Attach the documents needed for a review.
Approval flows
Route decisions through configured reviewers.
Request status
Follow pending, approved, and other permitted outcomes.
Attendance context
Connect approved leave to working-day review.
TIME OFF STARTS WITH CLARITY
Know the balance.
Before the request.
Give employees access to the leave types and balances available to them, with eligibility guided by your configured policies.
Keep leave types distinct
Separate the types your organization offers instead of treating all time off alike.
Show the available balance
Give employees the balance context available for their selected leave type.
Keep policy decisions explicit
Apply the configured entitlement and eligibility rules rather than assuming one policy fits everyone.
Balances and eligibility follow your setup. Pending requests are not the same as approved leave.
AS
Asha ShahOperations / Sample policy year
Annual leave
18 days allocated / 6 usedSick leave
8 days allocated / 2 usedCasual leave
6 days allocated / 1 usedIllustrative balances for Asha Shah. Pending requests are shown separately; balance treatment follows your policy.
Request awaiting review
Annual leave / 28 - 29 September / 2 days
PendingA CLEAR REQUEST, FROM THE START
The dates. The reason.
Everything ready for review.
Let employees submit a request with the right dates, duration, and supporting detail without scattering the information across messages.
Choose the leave type
Select from the types available to the employee.
Set full-day or half-day leave
Capture the date range and supported day selection in the request.
Add the context reviewers need
Include a reason and supporting attachment where required by your process.
Requested duration and eligibility are validated by your configured workflow. Submission does not guarantee approval.
AS
Asha ShahSubmitted 22 September
PendingFrom28 SEP
To29 SEP
- Leave type
- Annual leave
- Requested duration
- 2 full days
- Available balance
- 12 days
- Attachment
- Not added
Reason
Planned personal time off. Current work and handover notes have been shared with the team.
The request is pending. These dates are not approved leave yet.
DECISIONS WITH CLEAR OWNERSHIP
Less approval chasing.
A visible decision trail.
Give authorized reviewers the leave request and its context, with decisions following the approval flow configured for your organization.
Route to the right reviewers
Use enabled leave approval levels and the configured approval mode.
Review before deciding
Consider dates, duration, reason, and available supporting detail.
Keep the outcome visible
Record approval, rejection, or permitted cancellation in the request workflow.
Approval responsibilities and available actions depend on role, request status, and configuration.
AS
Asha Shah / 2 days28 - 29 September
Pending- 01
Request submitted
Dates, leave type, and reason recorded.
22 September / Employee - 02
Manager review
Vikram Kapoor to review the request.
Awaiting decision / Example reviewer - 03
Final outcome
The result follows the configured approval flow.
No final decision recorded
The reviewer follows your setup
Levels and approval mode determine who can act and when a decision is complete.
TIME OFF, CONNECTED TO THE WORKING DAY
Approved leave.
A clearer attendance record.
Bring approved time off into attendance review so the team can distinguish requests waiting for a decision from accepted leave.
Separate pending from approved
Keep the decision status visible before treating time away as approved.
Review the working-day impact
Use leave dates and day selections alongside the relevant attendance records.
Carry reviewed inputs toward payroll
Let payroll treatment follow the configured leave, attendance, and salary rules.
Paid or unpaid treatment follows your policies and payroll configuration. A request alone does not determine salary.
NP
Casual leave24 September / Half day
ApprovedMon21-
Tue22-
Wed23-
Thu24Half day
Fri25-
- Decision recordedThe request is approved, not pending.
- Working-day contextReview the approved half day with attendance.
- Pay treatment follows policyUse configured leave and payroll rules.
This preview shows leave context, not a calculated payroll result.
PART OF YOUR PEOPLE OPERATIONS
Time off connects.
From the person to payroll.
Keep leave alongside the employee records, working patterns, and pay processes your team uses.
BEFORE THE NEXT REQUEST
Your leave management questions,
answered.
Understand balances, requests, and the decisions that connect them.
Book a demoAvailable leave types can show balance information when employees select a type. Entitlement, eligibility, and balance treatment depend on your configured policies.
Yes. The request workflow supports full-day and half-day selection. The dates and permitted selections are validated by the configured workflow.
Yes. Employees can include a reason and supporting attachment. Required information follows your organization process and leave policy.
Yes. Leave approval flows support configured reviewers and approval modes. Available actions depend on the reviewer permissions, request status, and enabled flow.
Authorized users can reject requests or use cancellation where the request status and permissions allow it. These actions follow the existing workflow rather than being available on every request.
No. A pending request still needs the decision required by your approval configuration. Employees should follow the recorded request status.
Approved leave can inform the working-day record. Paid or unpaid treatment and payroll calculations follow your configured attendance, leave, and salary rules.
You can configure the leave types and rules appropriate to your organization. Confirm employee eligibility, balances, and approval responsibilities during setup rather than assuming one policy applies to everyone.