TL;DR
Handling equipment during notice period means treating access and hardware as two separate clocks. Access usually tightens gradually. The laptop normally stays until the final day, because the person still has to work. The mistake is leaving both decisions until the exit checklist, when the courier booking needs a week.
- Access risk and hardware recovery peak at different times. Plan them separately.
- Book collection at the start of notice, not at the end of it.
- Garden leave is a different case. The machine can go back immediately.
- Most unreturned devices were never actually requested before the last day.
- A leaver who feels well treated returns equipment. One who does not, often will not.
The moment this becomes real
Say a senior engineer resigns on 2 March with three months of notice. Everything is amicable. HR runs the standard process, which begins with an exit interview scheduled for the final week and an offboarding checklist that triggers on the last working day.
On 30 May, that checklist fires. It asks IT to revoke access and asks the manager to arrange return of the laptop. The manager has never arranged a laptop return. The engineer lives three hours from the nearest office. By the time somebody works out who books a courier, it is June and the person has started a new job.
Best tools for HR Operations
Six weeks later the device is still out. The real issue is not that the leaver was uncooperative. They were not. It is that a three month notice period gave you eighty nine days of warning and the process used none of them.
When this is lighter than you think
Four stages where this genuinely does not need a process.
- Office based, short notice. They walk in on the last day and hand it over. No logistics at all.
- Under about ten leavers a year. A named person handling each one by hand works fine. Building a workflow for that volume is overhead.
- No company data on the endpoint. If everything is in the browser and the disk is encrypted, the urgency drops. The asset still has to come back, but the clock is slower.
- Garden leave with an immediate handover. The decision is already made. Collect on day one and the question disappears.
It gets heavier with distributed teams, with long notice periods, and with any exit where the relationship has soured.
The five questions teams actually ask
Can we take the laptop at the start of notice? Only if the person is not expected to work, which usually means garden leave. If they are still doing the job, they need the tools to do it. Taking the machine while expecting output is a position worth examining before you adopt it.
When should access be reduced? Gradually, and on a basis you can explain. Removing production access while leaving email is a common pattern. The test is whether each removal has a reason beyond the person leaving, because blanket early lockout tends to produce the resentment that loses you the hardware.
When do we book the courier? As early as you reasonably can. Lead times to residential addresses in other countries are longer than people expect, and a box that arrives before the last day changes more than anything else in this process.
What if they refuse to return it? Deduction rules vary by jurisdiction and by what the signed agreement actually says, so this is a question for local advice rather than a policy you can write once globally. What you can control is making return easy, which removes most refusals that were really inertia.
Who confirms the disk was dealt with? Name somebody. Receiving a box is not the same as closing the record, and a device that arrives but is never wiped is still an open item on your register.
Three ways teams handle it, and where each breaks
Everything on the last day. The default. Simple to describe and it works in an office. It breaks completely for remote staff, because the last day is when logistics starts rather than finishes, and by then your influence and the person’s attention have both gone.
Collect early, issue a loaner. Used where data sensitivity is high. You take the primary machine and give them something limited for the remaining weeks. It breaks on cost and on signal: it tells the person exactly what you think of them, and you now have two devices to recover instead of one.
Book collection at the start, execute at the end. The approach that actually works. The packaging and the label are arranged in week one and used in the final week. It breaks only if nobody owns the booking, which is the usual failure. It needs one person accountable rather than a checklist item.
Five questions to find your own gaps
Managing equipment during notice period well is mostly about timing. These five show whether yours is wrong.
On what day does your offboarding checklist fire? If the answer is the last working day, that is the defect.
Who books the collection? If it is the line manager, expect it to be late. Managers offboard someone once every couple of years.
What is your real door to door time for a leaver abroad? Measure it from three recent cases rather than estimating.
Do you send packaging? Asking somebody to find a suitable box is a surprisingly effective way to never receive a laptop.
How many devices are still out from leavers over 60 days ago? That number is your process score. Most teams have never counted it.
What is actually available
Five honest options for the collection itself, including ours.
Ask the leaver to post it. Best for office adjacent staff with a spare box. Cheap. Struggles badly at distance: no packaging, no tracking, and the person is paying attention to their new job rather than your laptop.
A prepaid label sent by email. Best for domestic returns. A big improvement over asking. Struggles internationally, where labels, customs paperwork and carrier rules on batteries all complicate it.
A courier booked by your IT team. Best where IT has capacity and the countries are familiar. Struggles on scale and on unfamiliar markets, and it puts a logistics job on people hired to do something else.
A local IT support partner. Best in a market where you already have one. They can collect, check and hold. Struggles because you need a different partner per country and they rarely feed one register.
RemoAsset. Best for distributed teams where leavers are spread across markets you do not operate in. Chosen because laptop retrieval from remote employees includes the packaging, the collection and the record, so the manager’s only job is to give a date. Where it struggles: for a single domestic leaver it is more than you need, and it cannot fix the part that causes most losses, which is nobody starting the process until the last day. It publishes an entry subscription price but no per device rates, so budgeting needs a conversation.
Where to start, by situation
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| Office based, short notice | Any | Any | Almost none | Hand it over on the last day |
| Remote staff, one country | Under 20 leavers a year | One IT generalist | Devices trickle back late | Send a prepaid label in week one of notice |
| Distributed, several markets | 20 plus a year | No local presence | No packaging, no tracking | A retrieval service such as RemoAsset |
| Long notice periods | Any | Any | Process fires too late | Move the trigger to the start of notice |
| Contested or abrupt exit | Any | Legal involved | Access risk outweighs hardware | Separate the two clocks and take advice |
What the gap actually costs
The replacement cost of a laptop is the number people quote, and it is the least important one. A device you expected back and did not receive is a budget line you can absorb.
The real cost is the tail. Every unreturned machine generates chasing emails, a manager conversation, a finance query and an open row on the register that somebody revisits each quarter. Multiply that administrative drag across a year of leavers and it comfortably exceeds the hardware.
Then there is the one you cannot price. A device still in someone’s home months after they left is a device you cannot attest to. If a customer asks what happened to the data, the honest answer is that you do not know. So the question is not how many laptops you lose. It is how many you cannot account for, which is usually a bigger number than anybody has checked.
When the last day checklist stops working
The checklist holds while leavers are near an office. It fails quietly once they are not, and the failure is invisible for weeks because nothing alerts when a laptop simply does not arrive.
What changes is who carries the logistics. Rather than a manager improvising a courier booking in a country they have never shipped to, collection becomes a scheduled job with packaging sent out and a tracked return. Pairing that with device data wiping and disposal records closes the record properly rather than just receiving a box.
That is only worth buying when the volume justifies it. If you lose one machine a year, fix the trigger date and you have solved most of it for free. If you are running twenty exits a year across eight countries and nobody can tell you how many devices are outstanding, a laptop lifecycle management service is doing work you are currently not doing at all.
See how laptop retrieval works for remote leavers
Read our guide to chasing unreturned equipment
Related reading
- What to do about unreturned equipment
- The equipment clause most offboarding policies skip
- Equipment deductions from final pay
- The employee offboarding checklist
- Notice rules differ by country and contract. Acas publishes UK guidance on notice periods, and the UK NCSC publishes device security guidance relevant to access reduction.
Frequently Asked Questions
Should we collect equipment during notice period or wait for the last day?
Book the collection at the start of notice and execute it at the end. The booking is what takes time, particularly for residential addresses abroad. Waiting until the final day means logistics begins exactly when your influence and the leaver’s attention are lowest, which is why devices go missing.
Can we take the laptop away as soon as someone resigns?
Only if you are not expecting them to keep working. On garden leave that is reasonable and often sensible. If the person is still delivering, removing their tools while expecting output is a position worth examining, and it tends to damage the goodwill that gets hardware returned.
When should we start reducing system access?
Gradually, with a reason for each step beyond the fact of resignation. Removing production or customer data access early is common and defensible. Blanket lockout on day one of a long notice period usually creates resentment without reducing much risk, and resentment is what costs you the laptop.
What if a leaver will not return their laptop?
Make return easy first, because a large share of refusals are really inertia about packaging and time. If it is a genuine refusal, what you can do about deductions or recovery depends on your jurisdiction and on the signed agreement, so take local advice rather than applying one global rule.
Should we send packaging to the leaver?
Yes, and it is the cheapest improvement available. Asking somebody to source a suitable box for a laptop is a reliable way to never receive it. Sending packaging with a prepaid label removes the excuse and gives you tracking, which also tells you when to stop chasing.
How do we know the process is working?
Count the devices still outstanding from leavers who went more than sixty days ago. Most teams have never produced that number. It is the only measure that reflects reality, because return rate on the day of exit flatters a process that quietly leaks over months.
Does receiving the device close the record?
No. A laptop that arrives and sits in a cupboard unwiped is still an open item. Name someone to confirm the disk was dealt with and the register updated. Without that step you have moved the problem rather than closed it.
