Who it fits
For teams that request leave through a portal and managers who build the rota.
Description
Leave asked for in the portal, decided where the plan is.
Define leave types with an annual allowance, a paid flag and an approval rule; each employee has a balance with carry-over. Requests are made in the portal with a period, half-day option and reason; a manager approves or rejects with a reason. Approved leave appears in the calendar and warns scheduling before a shift is planned.
Why it matters
The problem it removes.
Leave requested by message is easy to approve twice and easy to plan over. A balance and a request history make the answer visible to both sides.
How it works
Three steps, in the same system.
Set it up once; the work then follows the normal flow of the business.
Set the leave types
1/3Name, code, days per year, paid or unpaid, and whether approval is required.
The employee requests
2/3Choose the type and period, a half day if needed, add a reason; the balance is shown before sending.
The manager decides
3/3Approve or reject with a reason; the calendar, balance and scheduling view update.
What you can do
In daily work.
The things this module takes care of, in the order they happen.
01/04
Leave types with code, days per year, colour, paid flag and whether approval is required.
02/04
Balances per employee: allowance, carry-over, used, pending and remaining days.
03/04
Requests with period, half-day morning or afternoon, working days counted Monday to Friday and a reason; approve or reject with a reason.
04/04
Calendar view; approved leave is marked in the plan and shown as a conflict before a shift is assigned.
On screen
The screens it opens.
Each one is a working screen in SovranPOS, with its own place in the menu.
Leave
1/1Leave types, balances and requests with period, half-day and approval.
How it fits
What it needs.
What has to be switched on for this module to work.
See SovranPOS on your own products.
Not on a sample menu — we show you the till on your own menu, with no obligation.