WizzHire HR
Inside WizzHire HR, in detail.
One full section per capability, from the day the hire becomes a colleague. The hiring half lives on the WizzHire ATS page.
The handoff
The hire becomes a colleague.
When you mark a candidate as hired, their employee record opens with the details hiring already collected. People who were here before WizzHire come in from a spreadsheet, with a dry run before anything is written.
Employee records
One record per person, documents included.
Employment details, contracts, and certificates sit on the person's profile, with the visibility you decide.
- Contracts, certificates, and medical checks in categories you name yourself.
- A reminder arrives before a document expires.
- For every document, decide whether HR alone sees it or the employee too.
Org chart
A structure the whole team can see.
The departments and reporting lines you set, drawn as an org chart that keeps itself current.
- The chart is drawn from the manager on each record, nothing to draw by hand.
- Statuses such as onboarding, on leave, and offboarding show on the chart itself.
- Filter the directory by department, status, or contract type.
Onboarding
The first week runs off a checklist.
Publishing a record starts the default onboarding checklist on its own; a leaver starts the offboarding one. Every task has an owner and a due date.
Save lists as templates: questionnaire and meeting tasks reuse the questionnaires and booking links you already have.
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.
Holiday calendars you edit yourself, more than one if teams work to different ones.
Everyone sees their own balance, days used, and pending requests.
Approvals with the balance before and after, and a reason whenever a request is turned down.
Absence calendar
Who is out, and when.
One calendar for the whole team: who is off, on which days, and which days are not working days at all.
- Approved leave lands in that person's own calendar and in Google Calendar.
- Non-working days and holidays never end up in the day count.
- An absence report by person and period, ready to export.
Performance reviews
Reviews and the growth talk.
A cycle where the person, their manager, and their colleagues each answer, then a conversation with the answers side by side.
- Self-rating, the manager's rating, and the peer average, question by question.
- Peer comments stay hidden until enough responses arrive.
- Visibility rules decide what the manager shares and what stays private.
Self-service
Everyone sees their own record. You see the whole team.
People maintain their own contact details and follow their leave, while you watch headcount, starters and leavers, and leave utilization.
My profile
An employee sees their employment details, updates their contact details, and follows their own leave, without writing to HR.
HR analytics
Headcount over time, starters and leavers, turnover, and annual leave utilization per person.
Your rules
Nothing here arrives preloaded with somebody else's rules.
You set the leave types, the holidays, and who approves what, and everyone on the team works in Bosnian or English.
- Leave types and policies
- Holiday calendars
- Who approves what
- Bosnian or English, per person
Before the hire
The other half of the system: WizzHire ATS.
Every employee record here started as an application there: a board for every role, WizzAI scoring, and a team decision on the record.
- Every application on one board, in your stages
- WizzAI scores every CV; your team decides
- Questionnaires, interviews, and offers on one profile