Getting the Equipment Back From Every Leaver
Thursday, 09:30, at Stonebridge Insurance. Ola runs a desk of five and arrives to find a laptop on the counter in a supermarket carrier bag, with a sticky note on the lid: "Jo's. She left Friday. No charger, sorry." There is no ticket. There is no receipt. There are two people called Jo in the claims department, one of whom is at her desk. The laptop's asset tag has been peeled off at some point in its life. Ola opens the desk's loan spreadsheet to find out which Jo. While she is there, she notices that three other laptops are recorded as "out" to people whose names she recognises only because they left last year.
The carrier bag is not the failure. The carrier bag is the best outcome of a process that does not exist. The three laptops that never came back are the normal outcome. Equipment return is the part of offboarding that brings every device the organisation lent the leaver back to the desk, receipted, quarantined, and eventually wiped and re-issued. It is the one part of the exit that depends on a person who has stopped working for you doing something for you. That is why it needs a process rather than a hope. This article is part of our Employee Offboarding series, where the order of the last day is in The Offboarding Checklist: Disable First, Delete Later. This article takes one line of that checklist, "device received", and opens it up.
It covers why the return is a task and not a hope, then the office leaver and the last-day handover. Next come the remote leaver and the courier kit, the signed receipt, and what to do when the equipment never comes back. Then it covers wiping and re-issue, and why the wipe waits, followed by the note on the ticket and the asset record. It ends with a short war story and the return letter to copy, in that order.
Why the Return Is a Task, Not a Hope
The equipment a leaver holds is worth more than its price, and the price alone is usually enough to justify a process. There is a laptop, its charger, a dock, and a second monitor that went home during a long stretch of remote work. There is a company phone, a headset, and the hardware token or key fob used as a second factor. Then there is the odd thing nobody remembers lending, such as the label printer or the spare projector. They add up to a sum finance would notice if it walked out of the building in one go. That is what it does when a leaver walks out with it. Across a year of leavers at a mid-size organisation the unreturned pile is a line in the accounts. It is a line nobody is responsible for.
The data on the device matters more than the device. A laptop that was never returned is a laptop with the organisation's files on its disk, in whatever state they were on the last day. It sits in a cupboard in a house the organisation has no right to enter. Disk encryption, where it is switched on, reduces that to a risk the organisation can live with. Where it is not, the device is a copy of everything the leaver worked on, protected by a password the leaver knows. The return is the only way to close that question with certainty. Every other answer is "probably fine".
Then there is the next starter. A desk with a loan pool of twelve laptops and three that never came back is a desk with nine. The new starter whose kit is not ready on day one has a story to tell at lunch about how the organisation welcomed them. The loan pool is a system, described in the loaner and spares article of the hardware series. A system leaks from the exit end faster than from any other. Returns are how the pool refills. Returns are not a hope; they are a stock movement with a date.
The Office Leaver: The Last-Day Handover
For a leaver who works in the building, the device comes back on the last day, collected by the manager and brought to the desk, with a receipt signed by both. The manager collects rather than the desk because the manager is already in the handover conversation and knows what the leaver was lent. The manager is the person the leaver would rather hand things to than a technician they have met twice. The desk's part starts when the equipment arrives at the counter. It checks the items against the list on the leaver's ticket, looks each one over, writes the condition down, and signs. The whole exchange takes five minutes if the list exists and an afternoon if it does not.
The check is physical, not technical. Is each listed item present? Is the laptop intact, with its screen, keyboard and ports undamaged, and the asset tag readable? Is the charger the right one, and the dock, and the cable? Does the phone power on? The desk is not auditing the files on the device, not asking the leaver to sign in, and never asking the leaver for their password. The account is disabled or about to be. The desk has its own administrative means of reaching the disk for the data hold. A technician who asks a leaver for a password has just taught them that the organisation's security is negotiable at the counter. Write down what is missing or damaged in neutral words ("charger not returned; dock not returned; small crack at lower left of screen") and move on. The argument about whether the crack was there when the laptop was issued is one the desk wins only if the issue record said so. That is the argument for the issue record.
Personal items are handled with ordinary courtesy. A leaver who wants their photographs off the company laptop is referred to HR's policy. Where the policy allows it, the copy is made by the desk, supervised, onto a medium the leaver brings or HR provides. The copy is made before the wipe and never by handing the device back. A leaver who has left personal belongings in the laptop bag gets them back. A leaver who has left stickers on the lid is a maintenance task for later, and not a conversation to have on their last day.
The Remote Leaver: The Courier Kit
For a leaver who has never been in the building, or who lives too far away to come in, the device comes back by courier. The organisation pays for every part of that journey. The desk sends a return kit before the last day. It contains a box that fits the laptop and its accessories, padding, and a pre-paid and pre-addressed return label. It also contains a one-page instruction sheet and a message saying what to put in the box and by when. The mechanics of the kit, which courier service to prefer, the labelling and the tracking are all in Shipping and Swapping Hardware, which this article leans on rather than repeats. Here the subject is the exit-specific part, which is the timing and the ask.
The timing is that the kit arrives at the leaver's home before the last day. That lets the leaver pack the laptop on the last afternoon and drop the box at the courier the next morning. They still feel like an employee then, and the organisation still feels like somewhere they work. A kit that arrives a week after the exit asks a favour of a stranger. The home address comes from HR, on the leaver's ticket, and is used for this purpose only. The ask is in writing, short and friendly. It names every item expected, gives a date for the drop-off, and gives the leaver one contact at the desk for problems. Those might be "the box is too small" or "the courier never came". A leaver who hits a snag with nobody to tell is a leaver who puts the box in the hall and forgets it.
Track the parcel from the desk's side, not the leaver's. The ticket holds the tracking reference, the date the kit went out, the date the leaver was asked to drop it off, and the date the courier recorded collection. The technician checks those dates rather than waiting to be surprised. A remote return that has not been collected two working days after the drop-off date gets a polite nudge, which is the first step of the chase in the section after next. Most remote returns arrive on time. The process exists for the rest.
The Signed Receipt
The receipt is a short list of the items returned, their condition, the date, and two signatures. It exists because in three months nobody will remember what was handed over and both sides will remember differently. For the office leaver it is signed at the counter by the leaver or the manager and by the technician. A copy goes to the leaver if they want one. For the remote leaver it is the courier's collection record plus the desk's own note on opening the box, with a photograph of the contents taken before anything is moved. It is sent to the leaver as "received, thank you" the same day. Both go into the ticket as attachments.
The receipt is not a legal document and should not read like one. It is a list with dates on it, and its value is that it is boring: "laptop, asset tag 4471, charger, dock, headset; screen intact; one key cap missing (F7); received 16:10 by Ola, handed over by Jo's manager, Priyanka." The desk that writes receipts like that never has the argument about the charger, because the receipt says whether the charger came back. The desk that does not write them has the argument every quarter. Where a hardware token or key fob is among the items, the receipt names it, because that one is small, forgettable, and still a key until the desk de-registers it. That happens at the counter.
If the leaver has already gone and the equipment arrives by a route that has no receipt, as Jo's did, in a carrier bag, write the receipt anyway, from what arrived, signed by the technician alone. Attach it with a note saying how it came. "Received in a carrier bag, no charger, from the claims department, person unknown" is a fact the ticket should hold. A receipt with one signature is a weak record. No receipt is no record.
When It Never Comes Back
Some equipment never comes back. The process for that is a sequence of dated steps that the desk follows and HR finishes. That is because the desk can ask and remind and record, and only HR can do anything about it. The sequence is the same for an office leaver who "forgot" the laptop at home and a remote leaver whose box never moved. It is written in the ticket as it happens, with dates. It is calm throughout, because the leaver is a person who owes the organisation a laptop and nothing more. Most of them are simply busy with a new job.
| Working days after the due date | Who | What happens | Recorded in the ticket |
|---|---|---|---|
| 2 | The desk | Friendly reminder by e-mail to the leaver's personal address and, if given, by phone; offer help with the kit or a collection | Date sent; any reply |
| 7 | The desk | Second written request naming the items, the original due date, and a new date; copy to the manager | Date sent; new date |
| 15 | The desk to HR | Ticket handed to HR with the full history; the desk's requests stop; HR writes under its own name | Date handed over; HR contact |
| 30 | HR, with the desk | HR decides what the contract and the law allow; the desk treats the device as lost, marks it so, and takes the lost-device steps | Decision; device state changed to lost |
Those intervals are one fictional desk's choice, shorter for an immediate exit and longer for a leaver abroad. The shape is what to copy, which is that the desk asks twice, hands over once, and never threatens. The desk does not mention deductions from final pay, does not cite the contract, does not say "legal action", and does not turn up at the house. The desk has no authority in any of those areas. The organisation's position is weaker for every sentence a technician writes in that direction. HR knows what the contract says and what the law in the organisation's jurisdiction permits. The desk's job is to give HR a ticket so complete that HR's letter writes itself.
Meanwhile the device is treated as a lost device, which is a security task the desk already knows how to do. The account's sessions were revoked on the last day. The management profile, where the device is enrolled in one, is told to remove the organisation's data the next time the device connects, in plain words a remote wipe. The instruction is logged whether or not the device ever does connect. And the disk encryption, where it was on, is the reason the organisation can say the data is protected. The practice for all three is in Lost and Stolen Devices, which handles the same steps when a phone goes missing from a train. A laptop that never came back from a leaver is a lost device with a known last location. The desk does nothing about the location. It does everything about the data.
Wiping and Re-Issue, and Why the Wipe Waits
To wipe a device is to erase everything on it and return it to a clean state ready for the next person. The one rule about wiping a leaver's device is that it waits until the data hold is cleared. The device sits on the quarantine shelf, labelled with the leaver's name and ticket number, for as long as the manager might still need something from it. It is wiped only when the manager has confirmed, in the ticket, that nothing on it is needed or that everything needed has been copied. The reasons, the hold period and the manager's sign-off are in The Leaver's Data and Mailbox. The equipment article's contribution is the shelf. A shelf with a label beats a drawer with a memory.
The quarantine shelf has a second purpose, which is that the device is not used by anyone in the meantime. Not lent to the new starter "just for a week", not borrowed by a technician to test something, and not used by the manager to look for the file. That is done through the file service or by the desk copying the data off under the hold procedure. A device in quarantine is evidence of what the leaver had, until the hold ends. A device that has been used by three people since is evidence of nothing.
When the hold clears, the wipe is a re-image in plain words. The disk is erased. The operating system and the standard applications are put back from the desk's standard build. The device is re-enrolled in whatever management the organisation uses, and it goes into the loan pool as stock. Before it does, the condition noted on the receipt becomes a decision. A cracked screen or a battery that no longer holds a charge is repaired, written off, or retired. This uses the same swap-repair-or-retire reasoning the desk applies to any faulty device. Note the model and the fault. A desk that keeps that note across a year of returns learns which model comes back broken. That is a different article's subject and a conversation with whoever buys the laptops.
The Note on the Ticket and the Asset Record
The return ends with two records updated. The leaver's ticket says what came back, when, in what condition, and what happened to it next. The asset record says where the device is now. The ticket note is the receipt plus the subsequent steps: "received 16:10, receipt attached; quarantine shelf B; hold cleared by Priyanka on the ticket; wiped and re-imaged; returned to stock as loan pool unit 14." The return is its own task under the leaver's parent ticket, because it can take three weeks while the account was disabled in three minutes. A task with its own dates and its own owner does not get lost inside a parent that looks finished.
The asset record is wherever the desk keeps the list of devices and who has them, which for most small desks is a spreadsheet with a column for state. The states worth having are few: in stock, issued (to whom, when), returned and in quarantine (which leaver, which ticket), wiped and in stock, under repair, retired, and lost. A device moves through them in order and never skips one. The asset tag on the lid is the key that ties the row to the ticket. Most small-team help desks have no asset module; QuerySolv is one of them. A custom field on the leaver form that carries the asset tag of every device on loan is enough to tie the return task to the row in the spreadsheet. The approach, and when it stops being enough, is in Linking Devices Without an Asset System.
The record is also what makes the chase possible. A desk whose spreadsheet says "out, to Jo, since the spring" and nothing else cannot write a return letter that names the items. A letter that cannot name the items is a letter the leaver can reasonably ignore. The issue record, written when the device went out, is the return letter's source. The return record, written when it came back, is next quarter's audit. The two together are the only reason the desk ever knows how many laptops it owns.
Remember: the manager collects on the last day. The courier kit arrives before it. Every return gets a receipt with a date and two signatures. The device waits on a labelled shelf until the data hold is cleared. The chase is two polite requests from the desk and then HR. The desk never threatens, and never wipes before the hold ends.
A word on the thing that keeps this process honest, which is the ticket itself. The leaver's reply to the return request, "the box is too small" or "I dropped it off yesterday", belongs on the same ticket as the request. In a tool where a requester's reply reopens the ticket, as it does in QuerySolv and in many others, the thread stays in one place without anyone forwarding anything. The technician reads the reply, updates the dates, and the record is the conversation. A return chased across three personal e-mail threads and a chat message is a return nobody can account for later.
| Item | Who collects | What to check | If missing |
|---|---|---|---|
| Laptop | Manager (office) or courier kit (remote) | Present, intact, asset tag readable; condition noted | Chase sequence; lost-device steps; management profile wipe instruction |
| Charger, dock, cables | With the laptop | Present and the right ones | Named in the first reminder; written off if not returned |
| Monitor and home-office kit | Courier kit, or a collection booked by the desk | Present, intact | Chase sequence; HR decides |
| Company phone | Manager in the room, or courier kit | Powers on; not locked to a personal account where that is possible to check | Lost-device steps immediately; number and service handled per policy |
| Hardware token or key fob | With the laptop or the phone | Present; de-registered at the counter | De-registered anyway, the same day |
| Badge and keys | HR or facilities, not the desk | Recorded by the function that owns them | Their process, not the desk's |
A Short War Story: The Laptop in the Hall at Larkspur Travel
Larkspur Travel, a tour operator with a remote sales team, lost a sales agent called Denise to a competitor, disabled her account on the last day, and sent nothing: no kit, no request, no letter. That was because the desk assumed that HR had arranged the laptop's return and HR assumed the desk had. Eleven months later a customer complained to the regulator that her passport details had appeared somewhere they should not have. The investigation asked, among other things, where every device that had ever held the customer file was. Denise's laptop was in a cupboard in her hall. She had, she said, been waiting for someone to ask for it. She posted it back the following week, unencrypted, with the customer file still on it. That was the honest truth and no help at all to Larkspur's answer to the regulator. The firm could not show when the laptop had last been in anyone's control. It could not show that its data had been protected. It spent about thirty hours of desk, management and legal time establishing that the complaint had in fact nothing to do with that laptop. That was the only good news in the file. The lesson Larkspur wrote into its process was that the return is a task on the leaver's ticket with an owner and a date. The lesson also said that the kit goes out before the last day, and that a laptop nobody has chased is a laptop nobody can account for.
The Return Letter
The letter below is the written request for the equipment, in three stages that match the chase sequence. The first goes out with the courier kit or on the last day as a reminder of what is expected. The second goes out when the first due date has passed. The third is not the desk's to send, and is the handover note to HR with everything they need. All three are plain, friendly and specific, and none of them mentions money, contracts or consequences, because those are HR's words and not the desk's. Fill in the items from the issue record, the dates from the ticket, and the contact from whoever on the desk will actually answer.
EQUIPMENT RETURN LETTER — THREE STAGES STAGE 1 — THE REQUEST (sent with the courier kit, or on the last day) Subject: Returning your [Organisation] equipment Hello ______________, As part of your leaving arrangements, we need the following items back: - ______________________ (asset tag ________) - ______________________ - ______________________ Office: please hand these to ______________ on your last day, __________. Remote: a pre-paid return box is on its way to you; please pack the items and drop the box at ______________ by __________. The label and instructions are in the box. If anything is missing, broken, or the box does not fit, reply to this message or call ______________ on ______________ and we will sort it out. Thank you, ______________, IT desk, [Organisation] STAGE 2 — THE REMINDER (after the due date has passed) Subject: Reminder: [Organisation] equipment not yet received Hello ______________, We have not yet received the items below, which were due back on __________: - ______________________ - ______________________ Could you drop the return box at ______________ by __________, or let us know if there is a problem with the box or the courier? We are happy to arrange a collection from your address if that is easier. Thank you, ______________, IT desk, [Organisation] STAGE 3 — THE HANDOVER TO HR (internal; the desk sends nothing further) To: ______________ (HR) Leaver: ______________ Last day: __________ Ticket: ________ Items outstanding: ______________________________ Issue record attached: Y / N Kit sent on: __________ Tracking: ______________ Requests sent: Stage 1 on __________; Stage 2 on __________; replies: ______________ Device state: marked lost on __________; sessions revoked __________; management profile wipe instruction logged __________; disk encryption: on / off / unknown The desk will take no further action until HR advises.
Ola found which Jo it was by the only method available, which was asking the claims manager. She wrote the receipt from the carrier bag: laptop, no charger, tag missing, one signature. The three laptops from last year went through the chase. Two came back inside a fortnight with apologies. The third was written off by HR after a letter the desk did not have to write. The issue record now exists, the kit goes out before the last day, and the carrier bag has been retired, with honours, to the stationery cupboard.
Frequently Asked Questions
The leaver has gone and we do not know what they were lent. Where do we start?
Can we ask the leaver to deliver the laptop to the office themselves?
Should the desk wipe the laptop as soon as it comes back, for security?
The leaver says the laptop was stolen from their car after they left. What now?
Can we deduct the cost of an unreturned laptop from the leaver's final pay?
Who de-registers the hardware token or key fob, and when?
From the QuerySolv team: we build self-hosted help desk software for Windows. QuerySolv runs as one Windows service on your own network. It takes requests by web form, e-mail, live chat, social messages and REST API. It is licensed once per installation rather than per agent per month. The free trial runs the full product for 30 days.
