Automating onboarding and offboarding: joiner mover leaver without ticket ping pong
Joiners, movers, and leavers are scattered across inboxes and half-finished checklists today. As a controlled flow, they become repeatable, traceable, and complete.
A single joiner creates a dozen tasks today: create accounts, assign rights, order a device, set up software, grant access, answer follow-up questions. Spread across HR, IT, and the business unit, coordinated through emails, reminders, and checklists that are rarely fully completed. Offboarding is the same in reverse, only with higher risk: access that stays active too long is noticed only when someone deliberately checks.
That this pattern is not an isolated case was shown by an anonymized nara analysis of 43,676 ServiceNow incidents for a European manufacturing group: joiner mover leaver cases and directory rights were among the prioritized automation candidates in that ticket history.
One process, scattered across many inboxes
The core problem is not the individual task. Creating accounts and assigning rights are routines. The problem is coordination: nobody sees the overall state, dependencies are invisible, and progress lives in heads and inboxes. This is exactly where automation helps. Instead of many separate tickets, the joiner becomes a single case with states, owners, and dependencies.
A joiner as a controlled flow
On the nara platform, a joiner runs through four phases.
Intake. The agent collects role, start date, location, and required systems, and creates the case as a ticket. It asks for missing details directly instead of collecting them over days.
Knowledge and rules. nara Memory records which role needs which accounts, rights, and devices. The agent derives the task list from that. It does not decide what a role receives; it applies the approved role logic.
Execution. Approved tools trigger accounts, rights, and orders, through integrations such as Microsoft Graph and, via the Edge Connector, also in systems that are only reachable internally.
Approval and completion. Critical rights go to the responsible people for approval before anything is executed. Every step remains traceable in the ticket, and open items become visible and are escalated instead of forgotten.
As a side effect, an entire class of follow-up questions disappears: managers and HR can ask for the state of a joiner in chat instead of searching tickets or interrupting colleagues.
Movers: adjusting rights instead of only adding them
The mover process is the most frequently forgotten of the three. When someone changes role or department, new rights usually arrive quickly, while old ones often simply remain. Over the years, this creates permission profiles nobody can explain anymore. A controlled flow actively checks old access on every change, collects new requirements, obtains the necessary approvals, and records every step.
Leavers: the lock list needs evidence
In offboarding, speed is not the only thing that counts; evidence does too. The agent works through the lock list: disable accounts, revoke rights, track devices and returns. What is done and what is still open is visible in the ticket at any time. If someone later asks when an access right was revoked, there is an answer with a timestamp instead of a guess.
What stays with people
The boundaries are clearly drawn. Whether a person is hired, which exceptional rights a role receives, and how exceptions are handled is decided by HR, the manager, or the IT owner. Critical approvals happen before execution, not after. The agent coordinates, executes what is approved, and documents. It does not make personnel decisions.
nara is deliberately not a finished HR product. The platform provides agents, a knowledge layer, ticketing, and operations; connecting your HR and IT systems happens through integrations and custom tools. Which steps can be automated in your stack is validated together.
The first step: look at the current state
How many tickets a joiner creates for you today, how long a leaver takes, and where cases get stuck is written in your ticket history. In a ticket analysis, we walk through your joiner mover leaver flow and show which steps can be automated under control in your environment.