TL;DR
- Equipment in redundancy is the part of the process planned last and the part most likely to go wrong, because it happens after the difficult conversation.
- Plan retrieval before the announcement. Improvising it in the following week is what produces unreturned devices and avoidable distress.
- Separate three things: access, the device, and the data on it. They have different urgencies and different owners.
- What a company may require or deduct regarding equipment differs by jurisdiction and circumstance. Take local advice; do not copy a template.
- Handle this with more care than an ordinary leaver, not less. The person is not leaving by choice and the process should reflect that.
- A prepaid return arrangement sent in advance recovers more devices than any clause in a letter.
The Retrieval That Made a Bad Week Worse
The consultation was handled properly. Careful conversations, clear timelines, people treated decently by managers who found it difficult. Then on the final Friday somebody from IT sent a group email to nine people asking them to return their laptops within three working days, with a line about company property.
Three of the nine replied asking who to contact because the email came from an address nobody recognised. Two had already been locked out of their accounts, so they could not read it. One pointed out, reasonably, that she had no box, no label and no idea where to send anything. And the tone, which would have been unremarkable in a routine offboarding, landed badly on people who had just been told their roles were ending.
Six of the nine devices came back within a fortnight. Two arrived over the following two months. One never did. The hardware loss was the smallest part of it; the larger part was that a process handled with real care for six weeks was remembered for a brusque email on the last day.
Best tools for HR Operations
The real issue with equipment in redundancy is not recovery rates. It is that this step gets designed by whoever picks it up last, at the point when everybody involved is tired.
Why This Step Gets Designed Last
Worth understanding, because the fix follows from the cause rather than from more process.
A redundancy process is owned by people whose attention is correctly on the consultation, the conversations and the legal position. Those are the parts that matter most and they consume the available care. Equipment is downstream of all of it, happens after the difficult part is over, and involves logistics rather than judgement.
So it falls to whoever is free on the day, and that person has not been in the conversations, does not know the tone that has been established, and is reasonably treating it as an asset-recovery task because that is what it looks like on a task list.
The structural fix is to pull it forward, which costs almost nothing. Three decisions at day minus 21, taken by the people who are already in the room discussing everything else: who owns it, what happens to access, what the return arrangement is. Twenty minutes inside a meeting that is already happening.
The second fix is to connect it to the people who set the tone. Whoever ran the consultations reads the equipment message before it goes. Not for approval, for register.
What not to do is build a heavier process. Nothing in this article asks for more steps; the recommendations are mostly about deciding earlier and removing friction. A redundancy is not the moment to introduce procedure, and a long equipment protocol will be ignored by the person holding it on the final Friday.
An Important Boundary on What This Article Can Tell You
Worth stating before anything else, because this is an area where generic advice does real harm.
What a company may require of somebody whose role is ending, regarding company equipment, differs by jurisdiction and by circumstance. Whether any deduction from final pay is permissible, whether any agreement to that effect is enforceable, what may be withheld pending return, what notice or consent is needed, and what obligations attach to anybody in the process all depend on where the person works, the terms in place, and the specific facts.
We are not going to tell you what any law requires, permits or prohibits anywhere. The honest answer is that it varies, and a clause copied from guidance written for a different jurisdiction is a liability rather than a safeguard.
We also will not tell you what happens to somebody's employment, what notice applies, or what anybody is owed. Those are questions for qualified local advice and they sit well outside what an article about equipment can responsibly address.
What this article covers is the operational sequence, the communication, the practical design that recovers devices, and the specific questions to put to somebody qualified. Those parts transfer. The legal position does not.
Plan Equipment in Redundancy Before the Announcement
The single change that improves everything else: decide the equipment steps while the process is still being planned, not in the week people are leaving.
Decide who owns it, by name. Not a function. One person, who will handle the messages and the logistics, and who is briefed on the tone the rest of the process has used.
Decide the access timing deliberately. This is the decision with the most consequences and the one most often made by default. Covered in its own section below.
Decide the return mechanics and prepare them. Boxes, labels, collection arrangements, ordered before they are needed. A return kit that arrives the week before the final day recovers far more than one requested afterwards.
Draft the message and have it reviewed by whoever ran the consultation. Equipment messages written in isolation by somebody who was not in those conversations are how the tone slips.
Agree what happens if a device does not come back, including how long you will chase and who decides to stop. Deciding this in advance prevents an open-ended pursuit during a period when nobody has appetite for it.
Equipment in Redundancy: the Three Things to Separate
Conflating these produces most of the problems, and they have genuinely different urgencies.
Access. Can the person reach company systems. Within your control, immediate, and reversible if you get the timing wrong.
The device. Physical hardware, slow to recover, and worth considerably less than most people assume relative to the effort.
The data on it. The part that actually matters for risk, and the part that encryption and access revocation largely resolve regardless of whether the hardware comes back.
| Element | Urgency | Who owns it | What if it fails |
|---|---|---|---|
| Access | Immediate on the agreed date | IT | An open door; the serious case |
| Data | Addressed by encryption plus revocation | IT | A disclosure question, not a hardware one |
| Device | Weeks, sometimes never | Named equipment owner | A write-off, usually modest |
The useful consequence is that a device which never returns, from an encrypted machine with revoked access, is a hardware write-off rather than an incident. Knowing that lets you handle recovery proportionately instead of treating every outstanding laptop as urgent.
Access Timing, Which Is the Hardest Decision
There is a genuine tension here and pretending otherwise produces bad outcomes in both directions.
Cutting access at the moment of the conversation is the standard security posture and it is appropriate in some circumstances. It also means somebody who has just been told their role is ending cannot retrieve a personal file, a reference contact or a photograph, and cannot read the email explaining what happens next.
Leaving access open until the final day is kinder and carries whatever risk your own assessment says it carries, which for most roles in most companies is low.
The middle option, which is usually right: restrict rather than revoke. Remove access to sensitive systems immediately, leave email and personal file access available for a defined window, and say clearly how long that window is.
What to do: decide this by role rather than universally, document the reasoning, and tell the person what is happening and when. The worst version is an undisclosed revocation that somebody discovers when they try to log in, because it turns a difficult but respectful process into one that feels punitive.
And always leave a route to reach a human. If access is cut, the person needs a phone number or a personal-email contact that works. The three people in the opening story who could not reply were locked out of the only channel they had been given.
The Personal Data Question, Both Directions
This cuts two ways and only one direction usually gets considered.
Their personal data on your device. Photographs, documents, saved passwords, browser history, personal email signed in. Most people have some, and after years in a role they may have a great deal. Telling them clearly how long they have to retrieve it, and keeping access open long enough to do so, is both decent and avoids a request two months later that is considerably harder to satisfy.
Your data about them on the device. A work laptop may hold documents concerning colleagues, customers or the person themselves. Wiping handles this, which is why the wipe record matters and why an unwiped device sitting in a batch for three weeks is a loose end rather than a neutral state.
Be specific about what you will and will not look at. If nobody will review the contents before wiping, say so, because people assume the opposite. If something does need reviewing for business continuity, say that too, and say who will do it. Silence on this point generates more anxiety than either answer.
Do not ask them to prove they removed personal files. It is unverifiable and it reads as mistrust. Give the window, state what happens at the end of it, and leave it there.
What to do: two sentences in the equipment message. How long they have, and what happens to the machine afterwards. That is the whole treatment and omitting it is the most common gap in an otherwise careful process.
What to Say, and How
The message does more work than the logistics, and it is short.
Lead with the practical, not the obligation. What is being collected, how, by when, and who to contact. A message that opens with a statement about company property reads as mistrust at a moment when very little goodwill is left.
Say what is already arranged. A box arriving Tuesday, a prepaid label inside, a courier collection you have booked. People who are handed a solution return devices. People handed a requirement have to solve a logistics problem on a bad week.
Be explicit about personal data. Tell them to remove personal files and tell them how long they have. This is the question most people have and are least likely to ask.
Name one person, with a working contact. Not a shared inbox. Somebody who will reply.
Say what happens if something is damaged or missing. If the answer is that ordinary wear and ordinary accidents are not a problem, say so. The absence of that sentence invites worry that produces delay.
And keep it separate from anything about the redundancy itself. The equipment message should not restate the circumstances, reference the consultation, or carry any implication about the person. It is a logistics note.
The Return Design That Recovers Devices
Everything measurable about recovery comes down to friction, and the friction is nearly always physical rather than attitudinal.
Send the packaging unprompted. Box, protective material, prepaid label, instructions. Before the final day. This single step does more than every clause and reminder combined.
Book the collection rather than asking them to post it. A courier arriving at an agreed time requires nothing of the person except handing something over. A trip to a post office during a difficult week does not happen.
Give one date, not a deadline range. Ambiguity produces delay. A specific collection date with a fallback is clearer than a window.
Collect on the final day where you can. For anybody on site, this removes the problem entirely because the device never leaves. For distributed teams the prepaid arrangement is the equivalent, prepared in advance.
Chase twice, gently, then stop. A short reminder at one week and another at three, then a decision. Extended pursuit after a redundancy costs goodwill and recovers very little. We have written about retrieval timelines and return packaging, and the mechanics apply directly, with the one difference that the tone here needs more care.
And make the write-off decision explicitly. A device that will not come back should leave the register through a documented decision with a date and an approver, rather than being quietly deleted, as covered in equipment compliance evidence.
The Remaining Team Is Watching
The audience for the equipment process is larger than the people leaving, and this is the consideration most often missed because it is not in anybody's remit.
Colleagues who stay observe how departing people were treated, and they draw conclusions about the organisation from the details rather than from the announcement. The equipment interaction is one of the few parts of the process they can actually see, because the consultation conversations were private and this one involves boxes, couriers and messages that get forwarded.
Three things get noticed specifically. Whether people were given a workable way to return equipment or left to solve it. Whether the tone of the final message matched the tone of everything before it. And whether anybody was pursued aggressively for a laptop afterwards.
The reissue question is also visible. Handing a remaining colleague a machine they recognise as a departed person's is a small decision with an outsized effect, which is why wiping, resetting and mixing the batch into general stock is worth the minor extra effort.
And the people who stay will be asked. Former colleagues keep in touch, and the first question after a reduction is usually how it was handled. The equipment step is the part most likely to be described in detail, because it is the part with concrete grievances available.
What to do: have whoever ran the consultation read the equipment message before it goes out. Not for compliance, for tone. That single review takes five minutes and it is the difference between a process that is remembered as careful and one remembered for an email.
What to Do When Somebody Will Not Return a Device
It happens, and having a position in advance prevents an improvised one during a difficult period.
Establish whether it is refusal or friction. They look identical from the outside and they are completely different. Somebody who has not returned a laptop because they have no box is not refusing. Confirm the practical arrangement reached them before concluding anything.
Check whether a dispute is in progress. If there is an ongoing matter about the redundancy itself, the equipment question becomes part of a wider situation and should be handled with advice rather than independently. Pursuing hardware in parallel with a dispute is how a modest write-off becomes a complication.
Do not improvise a financial consequence. Whether anything can be withheld or deducted depends on jurisdiction, terms and facts, and this is precisely the moment people reach for a clause nobody has checked. The answer has to come from qualified advice, obtained in advance per the list below.
Decide the stopping point and record it. Two reminders then a write-off, with a date and an approver, is a defensible and complete position for equipment in redundancy. Indefinite pursuit is neither, and it consumes attention from people who have just been through something difficult.
And keep the record factual. What was issued, what arrangements were offered and when, what was returned, what was not, what was concluded. No characterisation of the person. That record may be read later by somebody with no context, and a neutral one serves everybody.
Questions to Put to Somebody Qualified
The list is short and worth having answered before the process begins rather than during it.
Can anything be withheld pending the return of equipment, in each jurisdiction where affected people work? The answer varies and may be no.
Is any deduction for unreturned or damaged equipment permissible, and does an existing agreement change that? Again, varies, and the existence of a signed policy does not settle it everywhere.
What are we required to do about personal data on a company device? Both the person's personal data and company data about them.
Does any consultation or notification obligation touch the equipment process at all? Usually not, and worth confirming rather than assuming.
How long must we retain records of what happened to each device? Relevant because the records outlive the process and may be needed.
What to do: ask these once, per jurisdiction, before the first announcement, and write down the answers. The alternative is somebody improvising an answer during the week it matters, which is how a well-run process acquires a problem.
A Timeline for Equipment in Redundancy
Written as days relative to the final working day, because that is the fixed point everybody involved already knows.
| When | Step | Owner |
|---|---|---|
| Day minus 21 | Equipment owner named, access policy agreed, local advice obtained | Process lead |
| Day minus 14 | Return kits ordered, collections provisionally booked | Equipment owner |
| Day minus 10 | Destination for returned devices decided: pool, reissue or disposal | Equipment owner |
| Day minus 7 | Return kit arrives with the person, message sent | Equipment owner |
| Day minus 7 | Personal-file retrieval window opens, length stated | IT |
| Final day | Collection, or on-site handover | Equipment owner |
| Day plus 2 | Access fully revoked where it was restricted rather than cut | IT |
| Day plus 3 | Wipe performed and recorded for returned devices | IT |
| Day plus 7 | First gentle reminder for anything outstanding | Equipment owner |
| Day plus 21 | Second reminder, then the write-off decision | Equipment owner |
The two rows that matter most are day minus 21 and day minus 7. The first is where the legal questions get answered while there is still time; the second is where the box physically arrives, which is the single step that determines recovery.
Note what is absent from this timeline. There is no step where somebody chases repeatedly, no step where final pay is held, and no step requiring the person to solve a logistics problem. Each of those is either ineffective, legally dependent on jurisdiction, or both.
Adapt the day numbers to your own notice periods, which vary and which this article deliberately says nothing about. The sequence is what transfers; the spacing depends on circumstances we cannot know.
The Numbers Worth Having in Advance
Four figures, each a single number, and together they turn this from a judgement call into a plan.
How many devices are involved. Obvious and frequently uncounted until late, because the affected list and the asset register are maintained by different people.
How many are encrypted, confirmed. This is the figure that determines whether an unreturned device is a write-off or an incident, and it should be established before the first conversation rather than after a device goes missing. A fleet at 98 per cent confirmed is in a very different position from one at 70.
What a replacement costs. So the recovery effort can be proportionate. Chasing a 4-year-old machine with 6 months of life left, for 3 months, is effort spent badly.
Your historical recovery rate, if you have one. From ordinary leavers. It will be worse in a redundancy, so treat it as a ceiling rather than an expectation.
What to do: produce those four before the announcement. They take under an hour from existing records and they prevent every subsequent decision being made on instinct during a week when instinct is poor.
Where the Equipment Goes Afterwards
A redundancy produces returned devices in a batch, which is operationally different from the trickle of ordinary leavers.
Decide the destination before they arrive. Wiped and back into the spare pool, reissued to remaining staff, or disposed of. A batch of unassigned machines in a cupboard with no decision attached becomes untracked stock within a quarter.
Wipe promptly and record it. The wipe is the control that matters, and the record of it is the artefact anybody will later ask for. Devices sitting unwiped because the batch was large is a common and avoidable gap.
Reassess the age profile. Returned machines from a reduction are frequently reissued, and a device partway through its life being handed to a remaining colleague is sensible provided somebody checks it against your refresh point rather than simply passing it on.
Do not reissue visibly. Handing a colleague the laptop of somebody who was made redundant, recognisably, is a small thing that lands badly. Wipe, reset, and where practical mix the batch into general stock rather than doing a direct handover.
RemoAsset is one option for the retrieval and processing side, and disclosure matters: RemoAsset is owned by the same people who publish this site. It handles collection, wiping and redeployment, which for a batch retrieval across several locations removes both the logistics and the record-keeping from a team that has other things to do that month. Where it struggles, stated plainly: pricing is quote-based and requires a demo, so it cannot be compared against alternatives on cost without a call; and it is a newer platform with a smaller footprint than the legacy global resellers, which matters if affected people are in unusual markets. It has nothing to say about the legal questions above, which remain a matter for local advice.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Small reduction, on site | Under 10 | Office collection possible | Little | Collect on the final day |
| Distributed team affected | Any | No return logistics | No box, no label, no route | Prepaid kits sent in advance |
| Multiple jurisdictions | Any | One template | Clause may not hold locally | Local advice before announcing |
| Access already cut | Any | Standard security posture | Person cannot be reached | A phone or personal-email route |
| Large batch returning | 20 plus | No destination decided | Untracked stock in a cupboard | Decide wipe and redeploy first |
| Devices not coming back | Any | Chasing indefinitely | Goodwill cost, low recovery | Two reminders, then write off |
| Remaining staff need kit | Any | Returned batch available | Visible reissue lands badly | Wipe, reset, mix into stock |
When Only Part of a Team Is Affected
A partial reduction is harder than a whole-team one, operationally and otherwise, and the equipment handling has to account for it.
Equipment gets redistributed within a team that just lost colleagues. That is sensible use of assets and it is also the most visible possible reminder of what happened. Wiping and resetting is the minimum; mixing the batch into general stock before reissue is better where you can.
Shared equipment becomes ambiguous. Monitors, docks and desk setups in a shared office may have been used by somebody leaving and somebody staying. Deciding ownership of shared items in advance avoids an awkward conversation between two colleagues.
The remaining team may inherit work and need different kit. A role absorbing additional responsibility sometimes needs a better machine, and that request will arrive within a month. Anticipating it is better than treating it as an unrelated upgrade request in a quarter when budgets are sensitive.
Access scoping may need revisiting. If departing people held permissions that nobody remaining has, somebody will need them, and the request will come as an urgent escalation at an inconvenient moment. Reviewing that before the final day is a half-hour exercise.
What to do: treat a partial reduction as two workstreams rather than one. Retrieval from those leaving, and provisioning for those staying who absorb their work. Running them together, with one owner, prevents the second from being discovered later as a surprise.
Documenting It So Nobody Has to Remember
The record matters more here than in ordinary offboarding, for reasons that have nothing to do with suspicion.
Redundancy processes get reviewed. Sometimes internally, sometimes by somebody external, sometimes a year later when nobody involved is still in post. A factual record of what was issued, offered, returned and concluded is what makes that review straightforward.
Keep it per person, not per batch. A batch note saying nine devices were recovered from eleven is useless for the two questions anybody will actually ask, which concern specific individuals.
Record the offer, not just the outcome. That a prepaid return kit was sent on a given date is the fact that distinguishes a reasonable process from an unreasonable one, and it is the fact nobody thinks to record because it felt routine at the time.
Store it where it survives the team. Equipment records from a reduction have a habit of living in the personal drive of somebody who themselves left in the following year. A dated folder in shared storage, with a one-line index.
And retain it for as long as you retain the rest of the process papers, which is a question for whoever advises you rather than a decision for the equipment owner. Ask it at the same time as the other questions above so the answer arrives before the records do.
What Nobody Plans For and Should
Who answers questions after access is cut. A named person with a contact that works from outside your systems. The most common gap and the easiest to close.
Personal files. People have photographs, documents and references on work machines. Telling them how long they have to retrieve them is both decent and prevents a later request that is harder to satisfy.
Devices the person bought themselves. If anybody in the affected group was using their own hardware, there is nothing to retrieve and the control is entirely about access.
Peripherals. Monitors, docks and chairs are frequently not on any register and are both awkward and expensive to collect. Deciding in advance whether you want them back is better than deciding per person, and for most companies the honest answer is that a monitor is not worth a courier booking across two countries.
The person who handles it. Batch retrieval after a redundancy is an unpleasant job and it usually lands on somebody junior. Brief them properly, give them the tone, and do not leave them to compose the messages alone.
What Getting This Wrong Costs
The hardware is the least of it. One unreturned laptop from a batch of nine is a modest write-off and entirely survivable.
The real cost is to the process that preceded it. An organisation can handle a reduction with genuine care for six weeks and have it remembered for a brusque three-line email on the last day, because that email is the final interaction and final interactions carry disproportionate weight. The people affected talk to former colleagues, and the remaining staff are watching closely to see how departing colleagues were treated. That is the audience the equipment message is actually written for, whether or not anybody intends it.
The second cost is the legal one from a copied clause. A provision about withholding or deducting, lifted from a template written for another jurisdiction and applied to somebody whose role is ending, is the highest-risk sentence in any equipment policy. It is also the sentence most likely to have been copied, which is why the one firm recommendation here is to have it reviewed where you employ people.
And the third is operational drift. Batches of returned devices with no destination decided become untracked stock, and untracked stock is how a register that was accurate before a reduction is wrong afterwards, with nobody able to say by how much.
So the question is not how to recover equipment in redundancy. It is whether the step was designed while there was still time to design it, or picked up on the final Friday by whoever was available.
There is one further cost worth naming because it is paid by the people doing the work. Handling equipment in redundancy is a genuinely unpleasant task: writing logistics messages to people who have just lost their roles, then following up when devices do not arrive. It usually lands on somebody junior, unbriefed, composing the wording themselves at the end of a difficult week. That is unfair to them and it produces exactly the tone problems described above. Briefing that person properly, giving them approved wording and making clear that non-return is not their failure to fix, costs twenty minutes and is the kindest part of this whole process to get right.
When You're Ready to Plan It
Decide three things while the process is still being planned: who owns the equipment step by name, what happens to access and when, and what the return arrangement physically is.
Then order the packaging before you need it and book the collections. That is the step that recovers devices, and it has to happen in advance to work at all.
And get the questions above answered by somebody qualified, per jurisdiction, before the first conversation. Not because the equipment matters more than the people, but because improvising a legal answer during a difficult week is how a carefully handled process acquires the one problem it did not need.
Frequently Asked Questions
When should we plan the equipment step in a redundancy?
While the process is still being planned, not in the week people are leaving. Three decisions need making in advance: who owns it by name, what happens to system access and when, and what the physical return arrangement is. The characteristic failure is that this step is picked up last by whoever is available, which is how a carefully handled process ends with a brusque message on the final day.
Can we withhold final pay until equipment is returned?
What a company may withhold or deduct regarding company equipment differs by jurisdiction and by circumstance, including whether any existing agreement changes the position. We deliberately will not state a general rule, because this is the clause most often copied from guidance written for somewhere else and getting it wrong creates a problem far larger than a laptop. Have it reviewed where you employ the affected people.
Should we cut access immediately?
Decide by role rather than universally, and consider restricting rather than revoking. Removing access to sensitive systems immediately while leaving email and personal file access for a defined window is often the right balance, and it avoids the situation where somebody cannot read the message explaining what happens next. Whatever you choose, tell them what is happening and leave a contact route that works from outside your systems.
What actually improves device recovery?
Removing physical friction, which means sending the box, the protective material and a prepaid label before the final day, and booking a courier collection rather than asking somebody to visit a post office. Recovery failures are almost never unwillingness. In our experience a prepaid arrangement prepared in advance recovers more devices than any clause in a letter or any number of reminders.
How long should we chase an unreturned device?
Two gentle reminders, roughly at one week and three, then a decision. Extended pursuit after a redundancy recovers very little and costs goodwill with both the former employee and the remaining team, who are watching. Make the write-off an explicit decision with a date and an approver rather than letting the device quietly disappear from the register, because an undocumented disappearance raises a question later.
What happens to the returned devices?
Decide before they arrive, because a batch with no destination becomes untracked stock within a quarter. Wipe promptly and record the wipe, since that record is the artefact anybody will later ask for. If you are reissuing to remaining staff, reset and mix the batch into general stock rather than handing a recognisable machine directly to a colleague, which is a small thing that lands badly.
Does it matter if a device is never recovered?
Operationally less than people assume, provided two things are true: the disk was encrypted and the account access was revoked. On that basis an unreturned device is a hardware write-off rather than a security incident, which lets you handle recovery proportionately. If either is not true, the position is different, which is why the encryption percentage matters more than the recovery rate.
Who should send the equipment message?
The named owner, with the wording reviewed by whoever ran the consultation, so the tone matches the rest of the process. The message should lead with what is already arranged rather than with an obligation, name one contactable person, say explicitly how long they have to retrieve personal files, and stay entirely separate from anything about the redundancy itself. It is a logistics note and should read like one.