WizzHire HR · Time off
Time off that counts itself.
Leave types, policies and holiday calendars are yours. People request from their own account, the request lands with whoever approves it, and the balance updates on its own. No spreadsheet, and no approval that lives in a chat message.
- 14-day free trial, no card
- Bosnian or English, per person
- Data in the EU
Self-service
People ask for their own days off.
Everyone sees their own balance, the days they have used and anything still pending. A request is a kind of leave, a start and an end, an optional half day at either end, and a note if they want to explain it.
- The form prices the request before it is sent: how many days it costs, and what the balance looks like afterwards.
- It flags an overlap with something they already asked for, and offers to merge two requests that sit next to each other.
- It warns when a range has no working days in it at all, which is usually a weekend or a company holiday nobody spotted.
Approvals
Requests route themselves to the right person.
You set one approval rule per kind of leave: the person's own manager decides, their manager with a fallback, or the same named people every time. Anybody away on leave is skipped.
The approver sees the context
Dates, the kind of leave, the note, and who else from the same department is away at the same time. That last part is usually what decides it.
A rejection carries a reason
A reason is required to turn a request down, and the person sees it on their own request. Nobody has to go and ask why.
Nobody approves their own
Whatever their level. A quiet queue can be cleared with Approve all, and each request is still sent on its own, so one failure does not undo the rest.
The count
A balance you can always explain.
The arguments about leave are never about the policy. They are about the number. So every number here has a rule behind it that you set, and a history you can read.
What a day off spends
Set per kind of leave.
- A working day
- Weekends and public holidays are skipped. Annual leave, almost always.
- A calendar day
- Weekends counted too. How sick leave is often counted.
When the days arrive
Two accrual models.
- All of them on 1 January
- The full allowance from day one. Simple, and somebody who leaves in March may have taken more than they earned.
- A twelfth each month
- Days are earned as the year runs, so a person can only spend what has arrived so far.
Somebody hired part-way through the year is asked about separately, on their own record: the prorated share, the whole year, or a figure you agreed.
What survives 31 December
Nothing carries
Unused days are lost on 1 January.
Up to a limit
The most common rule. Set the ceiling, and set the date the carried days expire.
Everything carries
No ceiling at all.
Carried days that expire are removed on the date you set, and the removal is written into the balance history. A number that dropped can always be explained.
See it with your own leave types.
A short call, your rules on the screen. We set up your leave types, holidays and approvers while you watch.
More in detail
The rest of WizzHire HR.
- Hire to employeeThe hired candidate becomes an employee record, already filled in.
- Employee recordsOne personnel file per person, documents and expiry dates included.
- Org chartDepartments and reporting lines, drawn from the records themselves.
- OnboardingThe first week runs off a checklist that starts itself.
- Absence calendarWho is out and when, on one calendar the whole team reads.
- Performance reviewsSelf, manager and peer answers, side by side for the conversation.
- Employee self-serviceEveryone keeps their own details. You watch the whole team.
- Your rulesLeave types, holidays and approvers are yours to set, not ours.