Keep leave balances that both sides accept, with holiday lists by branch.
Leave & Holiday Management keeps leave balances that both sides believe. Applications go to the right manager, approvals are recorded and the balance moves on its own. Your holiday list can differ by branch, so one unit closes for a local festival while another works, and payroll knows which days were paid.
Leave in a small firm is a register in a drawer and an argument in April. Somebody asked the manager on the shop floor, the manager said fine, and nothing was written. Balances are recalculated from memory when the year ends.
With applications and approvals on record, the balance is simple arithmetic. Casual, sick, earned and compensatory leave each have their own count. The manager sees who else is already off that week.
What your team uses today.
The module takes over these, one at a time, so nothing has to stop while it is set up.
- The leave register kept by HR
- Approvals sent as chat messages
- A holiday chart pinned to the wall
The problems this is meant to ease.
What leave & holiday management does.
What this looks like in a working week.
Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.
The people who open this every day.
From first conversation to daily use.
Reading the leave policy
We go through your policy and past registers. You provide the rules and opening balances, and a written summary comes back.
Leave types and accrual
Types, credit rules and carry forward are entered. HR confirms with a few sample employees.
Holiday lists
Each branch gets its own calendar. Managers review their list for omissions.
Approval routes
Reporting lines are linked from the employee list. A test application is walked through each route.
Going live with a group
A branch begins, then others follow. HR keeps the old register for reference.
How you would know it is working.
Record where you stand before it goes live, so the change is measured against your own figures.
- Leave balances disputed after payslips
- Applications waiting for a manager’s decision
- Team members absent on the same day
- Loss of pay days passed to payroll
- Compensatory leave earned and not yet used
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Payroll management
- Employee self-service
- Attendance and time tracking
- Employee database
Products that include it.
How we would put it in.
Questions owners ask about leave & holiday management.
How do workers who do not use email apply?
On a phone, in a browser. There are four fields and no jargon. Where even that is a stretch, the supervisor applies on their behalf, and the record still shows who approved.
Can leave rules differ for staff and workers?
Yes. Different leave types, accruals and approval chains can run side by side. In our software for hospitals and clinics, leave is approved against the duty roster, so a gap in the night shift shows up early.
Does approved leave affect the salary automatically?
It does, once payroll is part of the same system. Paid leave and loss of pay reach the month’s calculation directly. Where payroll sits outside, a monthly statement is exported for whoever runs it.
Is a register enough for eight people?
Honestly, yes. Eight people and one manager manage fine. A register fails at around twenty-five staff, or as soon as a second branch cannot see the first branch’s calendar.
What affects the price of leave and holiday management?
Headcount, branches and the variety of leave types affect it. The payroll and attendance links affect it too. We itemise pricing after reading your policy, and a part may be dropped.
How long does it take before staff can apply?
It rides on how clearly the policy is written. A usable release covers applications, approvals, balances and calendars. You approve the schedule before any work begins.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle leave & holiday management today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements