TL;DR
Equipment handover between managers matters because an internal move changes who is accountable for a device without changing anything physical. The laptop stays on the same desk. The budget line, the approver and the person who will chase it at offboarding all change, and almost no process captures that.
- Internal moves are more common than leavers and far less tracked.
- The device does not move, so nothing triggers a check.
- Cost centre and approver change. The register usually records neither.
- Accessories and second machines are where the losses actually happen.
- A move is a free opportunity to verify what somebody holds.
The moment this becomes real
Say a support specialist moves from Customer Operations to Sales Engineering in April. Same building, same laptop, same everything. HR updates the reporting line. That is the entire process.
What nobody records is that they also hold a second machine for testing, a docking station and a loaner phone, all approved by their old manager for a project that ended last year. The new manager has never seen a list of what their report holds. The old manager assumes it went with them.
Best tools for HR Operations
Two years and three moves later the person resigns. The offboarding checklist asks for the return of one laptop, because that is all the register shows. The real issue is not the missing test machine. It is that every internal move was a moment to check and none of them was used.
When this is lighter than you think
Four stages where this genuinely does not need a process.
- One device per person, no accessories. If everyone has exactly one laptop and nothing else, there is little to get wrong.
- Small company, everyone visible. Under about 40 people, somebody knows what everyone has. That stops being true quickly.
- No cost centre accounting for devices. If hardware comes from one central budget, half the problem disappears.
- Rare internal moves. A handful a year can be handled by noticing. Dozens cannot.
It gets heavier with matrix structures, with frequent reorganisations, and anywhere teams hold specialist kit that the standard issue list does not cover.
The five questions teams actually ask
Does the device move with the person? Almost always yes, and that is the reason nothing gets checked. The physical continuity hides the accountability change, which is the part that matters.
Who approves their next request? The new manager, who has no history of what was approved before. Without a handover they will approve a second monitor for somebody who already has two.
Does the cost centre change? Usually, and often retroactively at the next budget cycle. If your register has no cost centre field, the device stays charged to a team that no longer has the person.
What about shared or project equipment? This is where things actually go missing. Test devices, demo units and loan kit were issued for a reason that may have ended, and nobody owns the decision to recover them.
Who updates the register? In most companies, nobody, because an internal move fires no device workflow at all. It is a reporting line change in the HR system and nothing else.
Three ways teams handle it, and where each breaks
Do nothing. The near universal default. Costs nothing today and works because the laptop has not moved. It breaks slowly and invisibly, surfacing years later as an offboarding gap or an audit finding nobody can explain.
Add a device step to the internal move workflow. The new manager receives a list of what their report holds and confirms it. Cheap, and it works. It breaks when the list comes from a register that was already wrong, because confirming bad data makes it look verified.
Run a verification at each move. The person confirms what they actually hold, not what the system thinks. Slower, and the only version that corrects errors rather than propagating them. It breaks if you do it for every minor reporting line change, because people stop reading it.
Five questions to find your own gaps
A good equipment handover between managers takes ten minutes. These five show whether you need one.
Does your register have a cost centre field? If not, every internal move makes your device cost reporting slightly less true.
Can a manager see what their reports hold? If they have to ask IT, they will not ask, and they will approve duplicates instead.
How many people hold more than one device? That population is where internal moves cause real losses.
What fires when a reporting line changes? In most HR systems, nothing beyond the org chart. Check rather than assume.
When did a person last confirm what they hold? If the answer is at onboarding, your register is as old as their tenure.
What is actually available
Five honest options, including ours.
A line in the internal move checklist. Best for most teams. Nearly free, and it makes the new manager aware. Struggles because it relies on existing data being right.
A self service view for employees. Best when you already have a tool that can show it. People correct their own record more reliably than managers do. Struggles if the list is wrong often enough that people stop trusting it.
An annual confirmation for everyone. Best as a backstop rather than a primary control. Catches drift from all causes. Struggles on timing, since it finds problems up to a year late.
An IT asset tool with ownership history. Best for larger teams with an ITAM owner. Gives you a trail rather than a snapshot. Struggles on anything it cannot discover, which includes accessories and powered down machines.
RemoAsset. Best where the estate is spread across countries and the register is the thing you cannot trust, because asset tracking tied to the physical chain records what was actually delivered and collected rather than what was requested. Where it struggles: an internal move is a purely administrative event with no physical step, so a logistics service has no natural trigger for it. This one is mostly on your HR workflow, not on a vendor, and it is worth being plain about that. It also publishes an entry subscription price but no per device rates.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| One device each, small team | Under 40 | No IT function | Very little | Do nothing beyond the HR record |
| Frequent internal moves | 40 to 200 | Spreadsheet register | Nobody confirms holdings | Add a device line to the move checklist |
| Specialist kit in some teams | Any | Mixed approvals | Project equipment never comes back | Verify holdings at every move |
| Device costs charged to teams | 100 plus | Cost centre reporting | Charges follow the wrong team | Add a cost centre field and update it on move |
| Distributed, register unreliable | 100 plus | No single source | Cannot trust the baseline | Fix the physical record first, then the workflow |
What the gap actually costs
Very little, on any single move. That is exactly why it persists. No individual handover is worth building a process for, and the cost only becomes visible in aggregate.
What it produces is a register that degrades at a rate nobody measures. Each move adds a small error. After three years of reorganisations your list describes a company that no longer exists, and the people who could have corrected it have moved on themselves.
The bill arrives twice. Once at offboarding, when you ask for one laptop back from somebody holding three. And once in an audit, when somebody samples the list and finds devices charged to teams that were dissolved. So the question is not whether this move matters. It is what your register will be worth after a hundred of them.
When the checklist is not enough
A move checklist fixes the workflow and does nothing about the data underneath it. If the register was already wrong, asking a new manager to confirm it just adds a signature to an inaccurate list.
That is the case for fixing the physical record first. When delivery, collection and storage are recorded as they happen, the baseline stops depending on anybody remembering. A laptop lifecycle management service gives you a list built from events rather than from intentions, and storage between assignments means recovered project kit has somewhere to go instead of a drawer.
Be honest about the limits, though. No vendor is going to notice that somebody changed team. The trigger for this has to come from your HR system, and the only thing a service fixes is whether the list it shows the new manager is true. If your register is already accurate, write the checklist line and stop there.
See how asset tracking follows devices through their life
Read our guide to writing an asset management policy
Related reading
- Writing an asset management policy
- Connecting the asset register to your HRIS
- Allocating device cost to teams
- Designing an equipment approval workflow
- Inventory accuracy is a recognised control. The ISO 27001 standard covers asset inventory, and the UK NCSC publishes device security guidance that assumes you know what you own.
Frequently Asked Questions
Why does equipment handover between managers get missed so often?
Because nothing physical happens. The laptop stays with the same person at the same desk, so no delivery, collection or ticket is triggered. The only change is administrative, and most HR systems treat a reporting line update as an org chart edit rather than an event with asset consequences.
What should the new manager actually receive?
A short list of every device and accessory their report holds, with issue dates and the reason anything non standard was approved. That last column is the useful one, because it tells the new manager whether a test machine issued for a finished project should still be out.
Should the employee confirm the list rather than the manager?
Ideally both. The employee knows what is physically in their home. The manager needs to know what they are now accountable for. Asking only the manager risks confirming whatever the register already said, which is how bad data acquires a signature.
Does the cost centre need to change with the person?
If you charge device costs to teams, yes, and most registers have no field for it. Without one, hardware stays charged to the team the person left, which quietly distorts cost per head reporting for every team involved.
What usually goes missing during internal moves?
Not primary laptops, which are visible and in daily use. It is second machines, test devices, docking stations, monitors and loan equipment issued for specific projects. Those were approved by someone who no longer manages the person, and nobody owns the decision to recover them.
How often should we verify what people hold?
At every internal move is ideal, with an annual confirmation as a backstop. If that is too much, start with people who hold more than one device, since that population accounts for most of the drift and is usually a small share of headcount.
Can a tool solve this on its own?
Only partly. Discovery tools see machines that are powered on and enrolled, which misses accessories and spare devices entirely. The trigger still has to come from your HR system when the reporting line changes, so this is a workflow problem with a data problem underneath it.
