From the business case that justifies a role, through hiring and onboarding, to the day someone leaves — one continuous record, and an approval trail behind every decision.
Emails, spreadsheets, and WhatsApp groups are doing the heavy lifting. HR AIVA brings it all into one place.
Who approved this role, at what salary, and when — reconstructed from inboxes.
Everything gathered during recruitment is stranded in the recruitment tool.
Nobody can answer 'is anyone covering Sunday night?' without asking someone.
Rest gaps, overtime and clearance checklists depend on somebody remembering.
Every stage from business case to exit in one connected record.
A living hierarchy from head office to individual positions.
Visual rotas with compliance checks built in — no more WhatsApp groups.
Configurable multi-step approvals with full audit trail.
Automatic ranking against role criteria with manipulation detection.
Candidates and employees complete tasks in their own space.
Lifecycle Stages
User Roles
Approval Chains
Integrations
Audit Coverage
Each module feeds the next. Nothing is re-entered, nothing is lost.
Prove the role is worth funding — before it exists.
A business case carries the problem statement, the headcount per location and the cost, then walks a six-step approval chain in which only the Rewards team can touch the money.

Turn an approved budget into a live vacancy.
The requisition references its approved business case, so the money and the role can never drift apart. Once it clears its own chain it converts straight into a job opening.

Publish once, reach everyone.
A single opening can run internally, externally or both — with a public careers site, an internal board for existing staff, and one-click publishing to LinkedIn.

Read every CV, even the four hundredth.
Applications and bulk-uploaded resumes are scored automatically against the role, so recruiters open a ranked shortlist instead of a folder of PDFs.
Get the hiring panel to decide, not to meet.
Shortlisted candidates are shared with named reviewers, who record an accept or reject with their reasoning in their own time. The tally shows on the pipeline.

Scheduled in the calendar people actually use.
Interviews are booked against real availability and land as Microsoft calendar invitations — a Teams link for online, a room and address for onsite. Feedback is structured, so rounds can be compared.

The number gets approved before it gets promised.
The candidate workspace walks the offer through four steps. Documents are verified, the Rewards team builds the package, three approvers sign off — and only then can the offer be sent.
Compensation is built in five bands rather than one salary figure, so base, guaranteed cash, incentives and benefits are each approved on their own terms.

Paperwork done before day one, not on it.
Between acceptance and start date the new joiner completes everything in their own portal. HR watches the checklist fill in rather than chasing it.

A first week that was actually planned.
Each new joiner gets a line manager, a set of orientation sessions, and named people responsible for delivering them. Those people schedule their own slots, and the joiner rates each session afterwards.

Leaving is a process too.
An employee raises their own resignation, or HR raises it for them. It routes through the line manager and HR, triggers a structured exit interview, and ends with departmental clearance.

The org chart everyone asks for and nobody maintains.
Regions, cities, restaurants and departments modelled as a real hierarchy — with every employee sitting in it. This is the backbone the rest of the platform hangs off.
Headcount, filled positions and vacancies summed live. Search by name, employee ID or job title, filter by department, export the result.

Replace the rota on the WhatsApp group.
A weekly grid per restaurant showing who works when. Coverage is summed as you edit, and the system flags the scheduling mistakes people make when they are tired.

Stages, transitions and who may act at each one are stored as data. Every module inherits the same engine, the same permission model and the same audit trail.
Validates the actor's role, enforces required comments, records every transition.
Permissions stored per role and checked per action, not per screen.
Every email and offer letter editable, with variable substitution.
Raised automatically to whoever is next to act.
HRAIVA · Next.js · FastAPI
See how one platform replaces the spreadsheets, inboxes, and WhatsApp groups your HR team is running on today.