Employee leave tracking: from an e-mail chain to staged approval by phone
What is employee leave tracking software? Manage phone leave requests, manager and HR approval, current balance and the team calendar in one record.
The question “Can I take Monday off?” first lands on the manager’s phone, then becomes an e-mail forwarded to HR and then a spreadsheet row; if it stalls at any link in the chain, nobody notices. Employee leave tracking software is software that keeps the leave request, manager and HR approval, remaining leave balance and team calendar in a single record.
In this article we explain how the leave process works in a digital flow, which problems it solves and what to watch for in the transition, using the Mobile Leave Management module inside YazSis KurumsalPortal.
Three problems of scattered leave tracking
- Balance disputes: the employee does not know how many days they have left, and HR’s spreadsheet and the manager’s note do not match. The effort spent reconciling balances at the end of every year comes from here.
- Approval uncertainty: whether a request is waiting with the manager or with HR is found out only by asking; meanwhile the employee cannot make plans.
- Calendar clashes: that most of the team will be on leave in the same week is noticed only after approvals are given, and going back is both hard and damaging to trust.
The digital journey of a leave request
Employee: request by phone
The employee creates the leave request as self-service from their phone’s browser; they do not need to install a separate app. This means that employees who do not work at a desk, or who are not near their computer at the moment they want to ask for leave, can open the request without delay. The request is checked against the remaining leave balance; there is no need to ask HR separately for balance information.
Manager and HR: staged approval
The approval flow is multi-stage. In the basic flow the request goes first to the employee’s manager and then to HR, and the leave is not final until the chain is complete. Every approval step stays on record; that is, who the request is waiting with and who approved it and when can be queried later. This gives both the employee and the manager some assurance: nobody is left alone in a debate of “I approved it” or “the request never reached me”, because the record shows what happened and when.
Calendar and balance: one current source of information
When HR approval is complete, the leave is entered in the team calendar and the remaining balance is updated. The employee, the manager and HR work with the same current information. Leave records can also be exported as an XLSX report; at the end of a period or before a managers’ meeting, when you want to look at the distribution of leave, you do not need to compile the data by hand.
What stands out in this flow is that every stage has an owner. The request is either with the manager or with HR; there is no link that gets lost in between. Because leave is not final until the approval chain is complete, uncertainties such as “it was approved verbally” also disappear. For the employee this means being able to plan with confidence; for HR, not having to correct balances by hand.
A fictional example: one week in the life of a request
Imagine an employee opens a one-day leave request for Monday from their phone on Thursday evening. The request is checked against their remaining balance and lands with their manager. The manager approves the request the next morning, and it moves to HR approval. When HR completes its approval, the leave is entered in the team calendar and the balance is updated. If someone else on the team also asks for leave in the same week, the manager evaluates the second request by looking at the team calendar. In this process there is no need for an e-mail chain, a spreadsheet update or a “where is my request?” phone call, because the stage of the request is visible in the record.
Relationship with time-and-attendance (PDKS) and payroll systems
The module manages the leave request, approval chain, balance and calendar inside the portal. Data flow with a time-and-attendance (PDKS) or payroll system is an integration matter; no ready-made connection is offered. The data to be shared, the method and the scope are agreed with you during the needs analysis, depending on the project. The scope of the module is the leave process; if you need a data flow with these systems, discussing it at the start spares you surprises later. As with the rest of the portal, the data is kept on the organization’s own server.
What to decide before you start
- Put the approval chain on paper: whose request goes through whom? The basic flow is manager and HR approval; if your company needs a different order or an extra stage, discuss it before setup.
- Clarify in the process design beforehand who the approval rests with when the manager is absent.
- Transfer the current leave balances into the system from a single, verified source; if the balance is wrong at the start, the whole chain runs wrong.
- Tell employees that the portal is used from their phone’s browser and that they do not need to install anything; also say clearly that in the first weeks leave requests will be accepted only through the portal, otherwise e-mail and verbal requests will continue.
You can see the module’s details on the Mobile Leave Management page and how it works with the other HR modules on the KurumsalPortal page.
Frequently asked questions
How does an employee request leave from their phone?
The employee logs in to the portal from their phone’s browser and creates a leave request; they do not need to install a separate app. The request is checked against the remaining leave balance and then sent to their manager for approval.
How many stages of approval does a leave request go through?
The approval flow is multi-stage: in the basic flow the request goes first to the employee’s manager and then to HR, and when HR approval is complete the leave is entered in the calendar. Every approval step stays on record.
How does the leave balance stay current?
Every request is checked against the remaining balance when it is created, and approved leave is entered in the calendar. Because the balance is tracked through these approved records, the employee, the manager and HR work with the same current information.
Can Mobile Leave Management connect to a PDKS or payroll system?
The module manages the leave request, approval chain, balance and calendar inside the portal. Data flow with a PDKS (time-and-attendance) or payroll system is an integration matter; the data to be shared, the method and the scope are agreed with you during the project.
More articles
What is a hotel folio? Tracking room and extra charges in a single guest account
The check-out queue is growing and the guest does not remember the restaurant receipt. We explain what a hotel folio is, show a sample folio, the steps to close it at check-out and where the typical problems come from.
November 22, 2026 · 8 min readRecruitment process steps: flowchart from job posting to offer, and reference checks
To understand why a position has stayed open for months, you first need to see at which stage the process is stuck. We describe the recruitment process in an eight-step flow, with what to record at each stage.
November 22, 2026 · 9 min read270-hour overtime limit in Turkey: what if it is exceeded, and is overtime mandatory?
Under Turkish labour law, the annual overtime limit of 270 hours applies per employee. Using the text of the law, we explain how the limit is counted, which penalty provisions apply if it is exceeded and what role the employee’s consent plays.
November 22, 2026 · 8 min read