TL;DR
A joiner mover leaver process is normally built around accounts, tested on joiners, and quietly broken at the mover step. The device half is the part most often missing entirely, and the fix is the trigger rather than a longer checklist.
- Joiners work because nobody can start without access. Nothing forces the mover step.
- Fire the trigger from the HR record, which changes first.
- A laptop is an access path. It belongs in the same process as a login.
- Reconcile across three lists, not within one.
- Contractors usually have no signal at all. Find that before refining anything.
- Automate the signal. The physical movement still needs a route.
When you do not need a formal version
Four stages, and the first is genuinely fine without one.
Under about fifteen people. Everyone knows who joined and who left. Writing a process describes something you already do by looking around the room.
Best tools for HR Operations
Growing, still visible. You can name everybody but no longer track what each one has. This is where the first mover case slips past, usually somebody switching team and keeping access to both.
Multiple teams and locations. Changes happen weekly and nobody sees all of them. Manual handling now fails structurally rather than occasionally.
Audited or certified. Somebody will sample ten people and ask you to show that their access matches their current role. The mover gap is exactly what that sample finds.
Why the joiner mover leaver process forgets hardware
The framework came out of identity management, and it shows. The canonical steps are all things you do to an account: create it, change its group memberships, disable it. Every one can be completed from a console.
Hardware does not fit that shape. Issuing a laptop takes days and a courier. Changing somebody’s equipment when they change role takes a conversation about what they actually need. Recovering one takes a collection from an address. None of it is a console action, so none of it ends up in the automation that carries the rest of the process.
The mover step suffers worst, and the reason is structural rather than careless. A joiner cannot work until you act. A leaver sets off something loud. A mover carries on working perfectly well with yesterday’s access and yesterday’s kit, so the absence of action produces no symptom at all. The gap is silent by design.
That silence is why audits find it. Access control expectations in ISO/IEC 27001 rest on access matching the current role, and guidance on digital identity from the National Institute of Standards and Technology treats the lifecycle as a loop rather than two endpoints. A process with a strong start and finish and a weak middle satisfies neither.
The three events, and what each owes the device
- Joiner: provision and record. Equipment ordered against a role standard, delivered before day one, and written into the register with a serial and a holder. The record is the part most often skipped under time pressure.
- Mover: review and reconcile. Does the new role need different equipment, and does the old team still think they have it. This is the step to add if you add only one.
- Leaver: recover and evidence. Collection triggered at notice, device wiped, certificate attached to the asset. Not the last day, and not when somebody notices.
- The signal behind all three. One event in the HR record that everything else subscribes to, rather than three separate human handoffs.
- The reconciliation. A periodic comparison across identity, assets and payroll, looking for people who appear in one and not the others.
Five items, and only the last two are new work for most teams. The first three usually exist in some form and are failing at the handoff rather than the task.
Five questions to diagnose yours
What happens today when somebody changes team? If the honest answer is nothing, you have found the gap in one question.
Where does the signal originate? A system beats a person, every time, and the HR record almost always changes first.
Can you list who holds what, right now? If assembling that takes a day, the register is not feeding the process.
Do contractors appear in the system that fires your triggers? Usually not, which means they have no process at all.
When did you last compare three lists? Identity, assets and payroll. The people in one and not the others are the finding.
How teams wire it, and the trade-offs
A shared checklist per event. Best for getting started this week and for small teams. It struggles as soon as volume rises, because every item depends on a person reading it at the right moment.
Tickets raised by HR. Best for traceability, since each step has an owner and a timestamp. It struggles on the mover case, which rarely generates a ticket because nobody feels urgency about it.
Identity automation from the HRIS. Best for accounts and the strongest option for access. It struggles on anything physical, and it can give a false sense of completeness because the dashboard goes green while the laptop is still in somebody’s flat.
An asset tool reconciled manually. Best for knowing what you own. It struggles on timeliness, because the reconciliation happens quarterly and the gap opens daily.
A lifecycle service carrying the physical half. Disclosure: RemoAsset is owned by the same people who publish this site. It handles procurement, delivery, retrieval and certified wiping across 80 or more countries, so the movement updates the record rather than depending on somebody filing a note. Where it struggles: it is not an identity platform and will not disable an account, review entitlements or tell you somebody changed team. The narrow part it covers is whether the hardware actually moves when the record says it did.
The decision table
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Small, one location | Under 15 | No IT owner | Nothing to fix yet | A checklist per event |
| Growing, first gaps | 15 to 50 | Part time owner | Mover step missing | Add the mover review |
| Weekly changes | 50 plus | HR plus IT | Handoffs depend on memory | Fire one signal from the HRIS |
| Identity automated already | Any | IT owner | Green dashboard, missing kit | Add assets to the same trigger |
| Contractors in the mix | Any | Any | No signal exists | Find the end-date source first |
| Several countries | 100 plus | HR team | Recovery not possible | Fix the route, then the process |
What the mover gap costs
The first cost is accumulated access. Somebody who has moved three times in four years holds the union of four roles, and none of it was granted by mistake. Each grant was correct at the time. The total is not, and it is the thing an attacker inherits if that account is ever taken.
The second is equipment drift. Movers pick up a second machine for a new role and keep the first, so your register slowly understates what people hold while overstating what is available to reissue. You then buy hardware you already own.
The third is the evidence problem. Asked to show that access matches role for a sample of ten, a team with a weak mover step cannot, and the failure is awkward precisely because the joiner and leaver steps are immaculate. The strong parts make the weak part look like neglect rather than design.
The fourth is that the gap compounds quietly. No single uncorrected move causes an incident. Four years of them produces an access map nobody can explain and an asset list nobody trusts.
So the question worth carrying away is not whether you run a joiner mover leaver process. It is what happened the last time somebody changed team, and whether anybody checked.
When the signal works and the movement does not
Plenty of teams fix the trigger and still lose hardware. The signal fires, a task appears, and then nothing physical happens for a month.
Three signs point at the movement rather than the process. Tasks are closed but devices are not in hand. Returns from outside your main market stall or quietly disappear. And you cannot say what your average collection takes, because nobody measures the step that sits outside the system.
Those are logistics problems wearing a process costume. More automation does not touch them, and adding steps to the checklist makes the reporting worse rather than the outcome better.
It is worth separating the two before the next review, because they have different fixes and the diagnosis is cheap. Seeing how collection works as a tracked job with a stated outcome settles which half of the problem you actually have.
See how device movements are tracked against people
Read our guide to connecting the register to your HRIS
Related reading
- Connecting the asset register to your HRIS
- Writing an offboarding policy
- The equipment approval workflow
- Day one equipment readiness
- IT asset management software, compared
Frequently Asked Questions
What does joiner mover leaver mean?
It is the standard way of describing the three points at which somebody’s access and resources should change: when they arrive, when their role changes, and when they go. Most organisations build the joiner and leaver steps properly and treat the mover step as an afterthought, which is where the gaps collect.
Why does the mover case fail most?
Because nothing forces a decision. A joiner needs access before they can work and a leaver sets off an obvious alarm, but somebody changing team keeps working either way. Old access and old equipment stay with them by default, and nobody notices because nothing is broken.
Should the trigger come from HR or IT?
From whichever system records the change first, which is almost always the HR record. IT acts on the trigger but rarely originates it, so a process that waits for IT to be told is a process that waits. Automating the signal out of the HR system removes the dependency on somebody remembering.
Does the device belong in this process at all?
Yes, because the device is an access path. A laptop with cached credentials and local files is as much a joiner mover leaver question as a login is, and treating it separately is how organisations end up with accurate identity records and an inaccurate asset register.
How often should we reconcile?
Quarterly is a reasonable default, comparing your identity records against your asset records and against the payroll list. The useful version looks for people in one and not the others. Comparing a list against itself finds nothing, which is how most reviews pass while the gaps stay.
What about contractors?
They are the hardest population because they often sit outside the HR system that fires every other trigger. If a contractor’s end date lives only in a procurement spreadsheet or in somebody’s calendar, your process has no signal for them at all, and that is worth fixing before refining anything else.
Can this be fully automated?
The signalling can be, and should be. The physical half cannot, because collecting a laptop from somebody’s home involves a courier and a human. Automate the trigger and the record, then accept that the movement itself needs a route, and judge that route on whether devices actually arrive.
