TL;DR
An equipment amnesty is a short window where people can declare company devices they hold without anybody asking how or why. It exists because registers drift and audits only find what they already know to look for. Run it once, make it genuinely blameless, and plan what happens to whatever arrives.
- An audit samples your list. An amnesty finds what is not on it.
- Blameless has to be real, or the declarations stop at the easy items.
- Two weeks is long enough. Longer and it becomes background noise.
- Decide before you start what happens to declared equipment.
- The output is a better register, not a pile of recovered laptops.
The moment this becomes real
Say a new Head of IT joins and asks a reasonable question in their second week. How many laptops do we have? The register says 212. Purchasing records suggest about 240 have been bought over four years, minus a disposal batch of 15.
Nobody can explain the difference. The obvious theory is that devices went missing, and the obvious response is an audit. But an audit tests the 212 rows you already have, which tells you nothing about the ones that were never written down.
Best tools for Device Management
So the register is not wrong in the way people assume. It is incomplete, and no amount of checking existing rows will fix that. The real issue is not finding lost devices. It is that there is no safe way for somebody to say they have a spare laptop in a cupboard from a project three years ago.
When this is lighter than you think
Four stages where an amnesty is the wrong tool.
- Your register reconciles against purchasing. If the two numbers agree, you do not have an undeclared population and an amnesty will find nothing.
- Under about 50 devices. Just ask everyone directly. It takes an afternoon and does not need a programme name.
- You have never had a disposal process. Fix that first. An amnesty will produce devices you then have nowhere to send.
- Trust is currently poor. If people expect blame, an amnesty announced from a standing start will be ignored. Build the ground first or the exercise fails quietly.
It earns its place after acquisitions, after long periods without a register, and anywhere headcount has grown faster than process.
The five questions teams actually ask
Does blameless actually mean blameless? It has to, and people will test it. If the first person to declare an undocumented device gets asked why they had it, the exercise is over within a day. Decide in advance that no declaration leads to a consequence, and say so plainly.
What are we asking for? Be specific. Laptops, desktops, monitors, phones, docking stations, storage drives, anything with a company asset tag. People under declare when the question is vague, because they are unsure whether a four year old monitor counts.
Do they have to send it back? Usually not, and saying so increases declarations substantially. Most of what surfaces is equipment people are actively using and simply never had recorded. The point is the record.
How long should it run? Two weeks. Short enough to feel like an event, long enough for people on leave to catch it. An open ended amnesty gets ignored because there is no reason to act today.
What about devices from people who have left? Those will surface too, usually as a manager saying they have a box of old laptops. Plan for that before you ask, because it is the hardest category to deal with afterwards.
Three ways to run it, and where each breaks
A company wide announcement. One message, a form, a deadline. Cheapest and most common. It breaks on response rate, because a general request to everybody is a request to nobody, and the people most likely to hold undeclared kit are the least likely to read it.
Manager led, team by team. Each manager walks their team through it and reports back. Much better response. It breaks on consistency, since some managers will do it properly and others will tick the box, and you will not know which is which.
Pre populated confirmation. Send each person what the register says they hold and ask them to correct it. The highest quality data by a distance, because correcting a list is easier than recalling from memory. It breaks on effort, since somebody has to generate and send a personalised list.
Five questions before you announce it
An equipment amnesty is easy to announce and hard to finish. These five decide whether yours will work.
What is the gap between purchasing and the register? If you cannot produce that number, you do not yet know whether you have a problem.
Where will declared equipment go? If the answer is nowhere, you will create a pile somebody has to deal with and a promise you did not keep.
Who sends the message? It carries more weight from a senior sponsor than from IT, because the blameless promise has to be credible.
What happens to data on a surfaced device? A four year old laptop in a drawer may hold a great deal. Have the wiping path ready.
Will you do it again? If this is annual, say so. One off amnesties teach people that holding on quietly usually works.
What to do with what comes back
Five honest options for handling the output, including ours.
Record it and leave it in place. Best for devices in active use. Zero logistics and it achieves the main goal, which is an accurate register. Struggles only where the device should not be where it is.
Collect to an office cupboard. Best where most staff are near one. Cheap and immediate. Struggles for distributed teams and creates a storage problem you have not sized.
Redeploy to a new hire. Best outcome when the machine is still good. Saves a purchase. Struggles on readiness, since a surfaced device needs wiping, checking and possibly a battery before anyone can use it.
Dispose through an ITAD specialist. Best for old hardware, and it gives you documentation. Struggles on the first step, which is getting the device from somebody’s spare room to the specialist.
RemoAsset. Best when the devices that surface are spread across countries and there is no office to send them to, which is the usual outcome for a distributed team. Collection from remote staff, storage between assignments and wiping with a disposal record run as one chain, so a surfaced laptop can be redeployed rather than parked. Where it struggles: it does nothing for the hard part, which is persuading people to declare in the first place. That is a trust exercise and no vendor can run it for you. 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 |
|---|---|---|---|---|
| Register matches purchasing | Any | Any | No hidden population | Skip the amnesty, run a sample audit |
| Small team, one office | Under 50 | No register | Nothing written down | Ask everyone directly over a week |
| Post acquisition, two estates | Any | Two registers | Neither list is complete | Pre populated confirmation per person |
| Distributed, grown fast | 100 plus | Spreadsheet only | Large unexplained gap | Two week amnesty, then collect what should move |
| Devices surfacing across countries | Any | No local offices | Nowhere to send anything | A retrieval and storage service such as RemoAsset |
What the gap actually costs
The recovered hardware rarely justifies the exercise on its own. Some of it will be too old to redeploy, and a share of what surfaces is in active use and stays where it is.
The value is in the denominator. Every security answer you give, every insurance figure, every depreciation schedule and every statement about what happens to company data rests on knowing how many devices exist. If that number is wrong by twelve per cent, so is everything built on it.
There is also a cost to not asking. Undeclared devices do not become less of a problem over time. They age, they fall out of patching, the people who know about them leave, and eventually the only record that a laptop existed is a purchase invoice nobody can match to anything. So the question is not whether an amnesty pays for itself in hardware. It is what else you are currently calculating from a number you know to be wrong.
When the pile has nowhere to go
The failure mode of an amnesty is not a poor response. It is a good one. Forty people declare equipment, you promised it would be easy, and now there are devices in fifteen countries that somebody has to do something about.
That is why the destination question belongs before the announcement rather than after it. For an office based team the answer is a cupboard and an afternoon. For a distributed one there is no cupboard, and asking people to post laptops themselves undoes the goodwill the amnesty just built.
Having collection, storage and wiping arranged in advance turns a declaration into a booking rather than a problem. It also makes the promise credible, because you can tell people exactly what will happen next. If most of what surfaces will stay in use anyway, you may need none of this, and the register update alone was the win.
See how collection works when devices are spread across countries
Read our guide to unreturned equipment
Related reading
- What to do about unreturned equipment
- Writing an asset management policy
- Producing equipment compliance evidence
- Choosing IT asset disposal services
- Knowing what you own underpins most security guidance. See the NCSC device security guidance and the inventory controls in ISO 27001.
Frequently Asked Questions
What is an equipment amnesty?
A short, announced window in which anyone can declare company devices they hold without being asked to justify how they got them. It exists to find equipment that was never recorded, which is the population a normal audit cannot reach because an audit only tests rows that already exist.
How is this different from an audit?
An audit samples your existing register and checks whether those entries are true. An amnesty asks the opposite question: what do you hold that we do not know about. They find different problems, and most teams only ever run the first one.
Does an amnesty have to be genuinely blameless?
Yes, and people will test it early. If the first person to declare an undocumented device is asked why they had it, word travels and declarations stop. Decide in advance that nothing follows from a declaration, and have a senior sponsor say so in their own words.
How long should an amnesty run?
About two weeks. Short enough that it feels like an event worth acting on, long enough to catch people who are away. Open ended amnesties get ignored, because there is never a reason to deal with it today rather than next month.
Do people have to return what they declare?
Usually not, and saying so clearly increases how much surfaces. A large share of undeclared equipment is in daily use by the person who has it, and the goal is an accurate register rather than a pile of recovered hardware. Collect only what should genuinely move.
What should we do before announcing one?
Work out your gap between purchasing records and the register, decide where declared equipment will go, and arrange a wiping path for anything that comes back. Announcing first and planning afterwards is how an amnesty turns into a pile of laptops nobody owns.
Should we repeat it?
Annually works well, and saying it is annual changes behaviour. A one off amnesty quietly teaches people that staying silent is usually fine. A recurring one makes declaring the normal thing to do, and each round should surface less than the last.
