It's Monday morning. Your new hire walks in on their first day, ready to go. Their manager is excited. HR has done the paperwork. And then someone asks: "Has IT sorted the laptop?" Silence.
The request was submitted. Somewhere. In an email, maybe. Or a Teams message to someone who was on holiday last week. Nobody is sure.
The new employee starts their first day in a meeting that could have been an email. They wait for access that should have been ready before they got there.
This scene plays out in IT departments every week.
Not because the team is incompetent, but because joiner and leaver processes are one of the most coordination-heavy workflows in any organisation, and most IT teams are managing them with tools that were never designed for it.
This article is about what goes wrong, what good looks like, and how IT Asset Management makes the difference.
The joiner problem: coordination across too many people
When a new employee joins, IT is usually the last to know and the first to be blamed.
HR processes the contract. The hiring manager submits a request — sometimes through a form, sometimes via email, sometimes by walking over to the IT desk.
The request might include a role, a start date, and a name. What it rarely includes:
- which software licences are needed,
- whether a specific device type is required,
- which network access the person needs on day one,
- or whether there's a spare laptop available or one needs to be ordered.
IT has to figure that out. Manually. Often under time pressure, because the request came in three days before the start date.
With JML process automation, many of these details are captured up front and routed to the right owners. When this runs inside it help desk software with asset management, tasks, approvals, and asset data stay in one place, improving it asset governance without extra meetings.
The result: a new hire who waits. A manager who chases. An IT team that's reactive instead of prepared.
What this costs in practice
A large food logistics company described their joiner process before implementing ITAM: new hires routinely waited several days, sometimes a week — for the right equipment and access. After implementing an IT asset management solution, they reduced that wait to one hour.
- Equipment was pre-assigned based on role.
- Licences were allocated automatically.
- The HR team stopped fielding asset-related questions entirely.
- Standardising requests also enabled it asset optimization by matching stock to roles instead of buying by exception.
The leaver problem: assets that walk out the door
The joiner problem is frustrating. The leaver problem is expensive.
When an employee leaves, IT needs to:
- recover hardware,
- revoke software access,
- wipe devices,
- and reallocate licences.
In theory, it's an employee offboarding checklist.
In practice, it's a coordination exercise across HR, IT, and the leaver's manager, often with no single solution connecting them.
HR processes the resignation. IT finds out a week later — sometimes from the leaver themselves, sometimes from a manager's offhand comment. By the time IT gets involved, the laptop has already been handed to a colleague ("they said it was fine"), the software is still active, and the access hasn't been revoked.
Nobody acted in bad faith. The process just didn't connect.
The visibility gap
- 1,200+ assets tracked across two countries
- 90% reduction in asset retrieval time
- 3→1 tools consolidated into one view
"Previously, our asset data was scattered across multiple places — laptops in one system, phones in another, SIM cards elsewhere."
— Martin D., IT Manager, European Brewery Group
After consolidating 1,200+ assets into ALVAO , that process changed completely. Every asset assigned to a leaver surfaces automatically when the offboarding is triggered. Retrieval time dropped by 90%.
This consolidation strengthened it asset tracking and eliminated guesswork during handovers.
What good looks like: the automated employee lifecycle
The difference between a chaotic JML process and a clean one is usually not effort — it's connection.
When HR, IT, and asset data are connected in a single workflow, the right things happen automatically — that's JML process automation at work. These same connections support the it asset lifecycle end to end.
- Before day one
The HR team submits a new joiner request. Based on the role, ALVAO automatically generates tasks: allocate a device from stock, assign software licences, set up access permissions. Each task goes to the right team with a clear owner and deadline. IT knows about the new hire before HR has finished the paperwork.
- Day one
The new hire arrives. Their laptop is configured. Their software is licensed. Their accounts are active. The IT team confirmed everything in advance — not because they were chasing, but because ALVAO told them what was needed and when.
- When someone leaves
The offboarding trigger — from Hi Bob, Workday, or a manual submission — kicks off the leaver workflow in ALVAO. Every asset appears on the leaver ticket automatically. Return is confirmed digitally. Account deprovisioning is blocked until hardware is back. Nothing closes until everything is accounted for.
- The lifecycle continues
The returned laptop is assessed, wiped, and reallocated to the next joiner. The software licence is recovered and reassigned. Nothing is wasted. Nothing is forgotten.
Why this matters beyond IT
The joiner and leaver process is not just an IT problem. It has a direct impact on three other parts of the business.
Assets walk out untracked. Licences paid for users who left. Hardware purchased when a spare was in a drawer.
Former employees retain access after their last day. Not deliberate, just a gap the process didn't catch+ This is one of the most cited it asset management risks because lingering access increases exposure.
First days matter. A new hire waiting a week for a laptop is not a neutral event.
ITAM connects all three. It makes the process visible, automated, and accountable — not just for IT, but for every team involved. It also strengthens it asset governance by ensuring ownership, approvals, and returns are tracked.
Three things to check in your own process this week
You don't need to overhaul everything at once. Start here:
If the answer is "someone tells us" or "we see the account go inactive," there's a gap. IT should be notified automatically, before the last day — not after.
If the answer is anything longer than an hour, the joiner process has a coordination problem. That's fixable.
If not, your asset data isn't structured in a way that supports your offboarding process. That's the root cause of most leaver chaos. Centralising records in asset management software makes this query trivial and auditable.
The bottom line
Joiner and leaver chaos isn't inevitable. It's the natural result of managing a coordination-heavy process with disconnected tools — email, spreadsheets, and informal chasing.
IT asset management changes the equation. Not by adding more admin, but by removing it. When HR triggers onboarding, IT is already prepared. When someone leaves, every asset is accounted for before the account closes. The process runs — and IT gets the credit for something working quietly, reliably, in the background.
If you follow it asset management news, you'll see the same pattern: connecting HR, service, and asset data reduces waste and risk across the board.
That's the goal. Not firefighting. Not chasing. Just order.
Want to see what this looks like for your team?
Book a 20-minute walkthrough — no pitch deck, just the product or try it for free.
Q&A
1. Question: What is the "joiner problem," and how does IT Asset Management fix it?
Short answer: The joiner problem is a coordination issue: HR, hiring managers, and IT use disconnected channels (forms, emails, chats), so IT gets incomplete details late and scrambles to prepare. With JML process automation tied to ITAM, role-based requirements are captured up front and routed to the right owners. Devices are pre-assigned from stock or ordered, software licences are allocated automatically, and access needs are clear before day one. In practice, this shifts IT from reactive chasing to proactive readiness—one logistics company cut new-hire wait time from days to about one hour by implementing ITAM and automating role-based assignments.
2. Question: What makes the "leaver problem" so costly, and how does a connected process prevent asset loss?
Short answer: Leaver chaos stems from late IT notifications and scattered data—HR, IT, and managers don't share one view, so devices get informally passed on, licences remain active, and access lingers. A connected ITAM-led workflow triggers offboarding (from systems like Hi Bob or Workday, or manually), automatically lists every asset on the leaver ticket, requires digital return confirmation, and blocks account deprovisioning until hardware is back. A European brewery group consolidated 1,200+ assets into a single ALVAO view, reducing retrieval time by 90% and moving from three tools to one.
3. Question: What does a well-automated employee lifecycle look like end to end?
Short answer:
- Before day one: HR submits a joiner request; tasks auto-generate by role (device allocation, licence assignment, access setup) with clear owners and deadlines.
- Day one: Laptop is configured, software licensed, accounts active—IT confirmed in advance because the system told them what to do and when.
- When someone leaves: The offboarding trigger launches a leaver workflow; all assigned assets surface on the ticket, returns are confirmed digitally, and deprovisioning waits for hardware return.
- Ongoing: Returned devices are wiped and reallocated; licences are recovered and reassigned—nothing wasted or forgotten.
4. Question: Why does this matter beyond IT?
Short answer:
- Finance: Prevents untracked assets, avoids buying hardware when spares exist, and stops paying for licences tied to former employees.
- Security: Closes access gaps so former employees don't retain logins after departure; reducing this exposure addresses key it asset management risks.
- Employee experience: Ensures productive first days; waiting a week for a laptop sends the wrong message.
- ITAM connects the process, creating visibility, automation, and accountability across all involved teams.
5. Question: How can we improve quickly without overhauling everything?
Short answer: Start with three checks:
- How does IT find out about leavers? If it's ad hoc, automate notification before the last day.
- How long until new hires are fully productive on day one? If it's over an hour, you have a coordination gap.
- Can you list all assets assigned to any employee in under two minutes? If not, centralize and structure your asset data.
- These steps close the biggest gaps fast, and ITAM reduces admin by connecting what you already do rather than replacing your entire workflow