Leave types
Configure different leave categories for your organization.
Flowwkkr supports leave types, employee requests, approvals and leave summaries as part of the HR workflow.
Explore the product area in more detail and see how it fits into the wider Flowwkkr HR workspace.
Configure different leave categories for your organization.
Employees can submit leave requests with dates and reasons.
Authorized HR and management roles can review and approve or reject requests.
Use leave summaries and approved leave records to understand usage.
Keep approval capabilities limited to the roles allowed to manage leave.
Connect leave activity with the broader employee and attendance workspace.
Leave tracked in a spreadsheet drifts out of sync with attendance and is easy to approve twice. Flowwkkr manages leave types, requests, approvals and balances in the same system as attendance, so approved leave deducts automatically and balances stay accurate.

Configure the leave types your organisation actually uses, with their own accrual rules and eligibility. Flowwkkr supports the types Pakistani employers typically run, including annual, sick, casual, maternity, and religious or Eid leave.
When leave and attendance are separate, they inevitably disagree. Someone approves leave in one tool, and nobody tells the attendance tool, so a fully present employee is reported absent and their salary is reduced.
This is the single most expensive class of HR data error, because it is always visible to the affected employee and always expensive to reverse. Integrating them removes the failure rather than documenting it.
| Stage | Without integration | With Flowwkkr |
|---|---|---|
| Leave approved | Recorded in the leave sheet only | Recorded once, in the employee record |
| Attendance calculation | Employee marked absent, salary reduced | Leave deducted, employee correctly present |
| Balance check | Manual count from the sheet | Live balance per leave type |
| Month end | Reconcile the two by hand | Nothing to reconcile |
Employees submit leave requests from their own view. Managers and HR review and approve them, with a clear trail of who approved what and when. Approved leave flows straight into the attendance calculation.
Each balance is tracked per leave type and per leave year, so employees can see what they have remaining before requesting, rather than after. Carry-forward rules are configurable per leave type: capped, carried in full, or lapsing.
Carry-forward policy is worth deciding deliberately. An uncapped balance accrues an unfunded liability, and a policy of no carry-forward is a de facto pay cut that employees notice immediately.
Many Pakistani employers run the leave year on the fiscal year, or even on a shift cycle that rolls over at a different point. Flowwkkr tracks balances per leave year, so the year boundary is a configuration choice rather than a data migration.
A system that only understands whole days forces every short absence into a full-day column, which overstates leave taken and understates the balance remaining. Half days, hourly leave and short-notice absences are ordinary in most workplaces.
Flowwkkr supports partial-day leave, so a half day is recorded as a half day and deducted from attendance at the same granularity. This is what stops the balance and the attendance record disagreeing with each other.
| Request | Whole-days-only system | Partial-day support |
|---|---|---|
| Half day in the morning | One full day deducted | Half day deducted |
| Two hours for an appointment | One full day deducted | Two hours deducted |
| Balance after a year of odd requests | Drifts low, appears unfair | Accurate to the hour |
| Attendance for the same day | Half-day or absent | Correct fraction of the shift |
Leave balances are easy for a stable workforce and surprisingly hard for a growing one. New joiners need a policy decision about what they are entitled to and from when. Employees who move department or change contract type need their balance recalculated. Leavers need a final figure that survives an audit.
Flowwkkr keeps entitlement and balance per employee per leave year, so these are recorded events rather than annual data cleaning. The alternative is a spreadsheet that is correct once a year and quietly wrong in between.
Leave approval processes fail in two directions. Too loose, and people take leave nobody agreed to and cover is not arranged. Too slow, and employees stop submitting requests properly and take the day anyway, which is worse because the record is wrong.
Routing approvals to the reporting line on the employee record fixes most of this, because the approver is already known and does not have to be asked. Delegation matters too, since a manager on leave will otherwise become an accidental bottleneck for their whole team.
Yes. Leave entitlements and rules can vary by employment type, department, designation or individual employee, which matters when different staff groups have contractually different allowances.
Yes, and this is the point. Approved leave is deducted during the attendance calculation, so an employee on sanctioned leave is not marked absent and is not paid as absent.
Flowwkkr supports configurable public holidays, so religious and national holidays are excluded from absence calculations. Bring your calendar and we will configure it for you.
Yes. Year-end carry-forward is configurable per leave type, so you can cap it, carry it in full, or let it lapse.
Yes. Approvals route to the reporting line recorded on the employee record, and managers only see and approve requests from their own team.
Bring your device model, shift pattern and employee count. We will confirm fit on a private 2-hour demo.
Request a private 2-hour live demo and explore the HR workflow.