Leave planning across branches
A branch manager sees their own team’s calendar, the regional manager sees all of them at once. Approval stays at the branch, visibility sits at the centre.
Employees open a request from their phone and managers approve with one tap. Accrual, balance and carry-over are calculated automatically under Turkish Labour Law No. 4857.
What this runs on today

Leave management

The three situations we run into most often. If one of them sounds familiar, we have something to talk about.
An employee asks how many days they have left and the answer is hunted for in a spreadsheet. Carry-over is reworked by hand every year.
That three people from the same team booked the same week is noticed once the leave has already started.
Unpaid leave and absence deductions have to be remembered and entered separately during the payroll period.
Every item is a real screen or flow in the product; we walk through them one by one in the demo.
Annual, personal, sick, parental and unpaid leave requests are opened from a phone in seconds.
Chains such as department manager → HR → general manager are defined; a pending request lands on the manager as a notification.
Tenure-based entitlements of 14, 20 and 26 days and carry-over are calculated under Turkish labour law, with no manual update at the start of the year.
A manager sees the leave calendar for their team on one screen; clashes raise a warning at the moment of request.
Document requirements, maximum duration and approval steps are defined separately for each leave type.
Approved unpaid leave and absence deductions carry into the payroll calculation on their own.
Once it is set up, every period runs in the same order, and most of the steps happen on their own.
The employee picks a date range; if their balance is short, the system says so right then.
If someone on the same team is off on the same day, the manager sees it while reviewing the approval.
Every step in the chain approves from mobile; the reason for a rejection is sent to the employee.
The balance drops immediately, and if there is unpaid leave the payroll deduction is prepared.
The same data is entered once. What this module takes in and produces is below — you do no extra work to move data between modules.
Takes the data in once and shares the same record with the other modules.
Not promises with numbers, but real setups. Let us go into the one closest to yours in the demo.
A branch manager sees their own team’s calendar, the regional manager sees all of them at once. Approval stays at the branch, visibility sits at the centre.
A leave request is assessed together with the shift plan; any day that would drop the line below minimum staffing is flagged before approval.
Rotation and leave entitlement for crew at sea are defined under different rules from the shore team, and run in the same system.
A demo is not a presentation: we build your scenario and run it on screen. You leave with a written proposal covering scope and timeline.