Device lifecycle: purchase to certified disposal
Most organisations manage the purchase and the support well, and improvise the two ends. What happens before the device reaches the user, and what happens after it leaves them, is where both the cost and the risk sit.
A device lifecycle has six stages: purchase, staging, delivery, support, replacement and disposal. The two that most organisations do not own are staging and disposal, and both are where money and risk leak out.
Staging means a device arrives imaged, enrolled and labelled, so the user logs in and works. Without it, every delivery costs an engineer between one and three hours and the user loses a morning.
Disposal means data wiped to a documented standard, a certificate you can hand to an auditor, and equipment given a second life where possible. A cupboard of old laptops is a data risk with a lock on it.
The six stages, and who usually owns them
| Stage | What happens | Usually owned? |
|---|---|---|
| Purchase | Specification, quote, order | Yes, well |
| Staging | Imaging, enrolment, labelling, asset registration | Rarely, and it shows |
| Delivery | To a desk, a site or a home address | Ad hoc |
| Support | Faults, warranty, replacements | Yes |
| Replacement | Planned refresh, redeployment | Reactive rather than planned |
| Disposal | Wipe, certificate, resale or recycling | Almost never |
Staging is the cheapest hour you will ever buy
A device that arrives in its factory box costs somebody time before it is usable: unpack, image, join, install, configure, label, register. In an organisation with any volume that is one to three hours per device, repeated, usually done by the person you least want doing it.
Staged delivery flips that. The device arrives with the image, enrolment, applications and asset tag already applied. The user opens the box, signs in and works. For a rollout of forty devices the difference is measured in weeks of engineer time.
Keep an asset register that is true
Almost every organisation has an asset list. Very few have one that matches the building. The register drifts because devices are swapped in a hurry, replaced under warranty, or handed to a new starter without anybody updating a spreadsheet.
The fix is not discipline, it is timing: register the device at staging, when it is already in your hands and being touched anyway. A register maintained at the point of handling stays accurate; a register maintained by good intentions does not.
Plan the refresh instead of waiting for failures
Devices fail on a schedule you can predict but rarely at a moment you would choose. Batteries degrade after roughly three years, warranties expire, and an operating system version stops being supported. Waiting for the failure means the replacement always lands in a busy week.
A planned rhythm, replacing a fixed share of the estate each quarter, evens out both the budget and the workload. It also keeps the estate uniform, which is the single biggest driver of support cost.
The end is where the risk is
A laptop leaving the organisation carries whatever was on it. A cupboard of old devices waiting for someone to decide is a data risk that grows quietly, and it is the finding an auditor reaches for first because it is easy to check.
What good looks like: data wiped to a documented standard, a certificate per device or per batch with serial numbers on it, and a decision on each device between resale, redeployment and recycling. Equipment with life left in it should get a second life; equipment without it should be recycled through a route you can name.
We run this as part of IT lifecycle, and our environmental management is externally audited to ISO 14001, which is what makes the disposal claim checkable rather than a statement.
Across several sites it gets harder, not easier
One office can improvise. Five sites in two countries cannot, because every improvisation becomes five different improvisations and the register stops meaning anything.
What holds it together is a single process and a single register regardless of which site a device sits in, plus delivery and collection that reach every location rather than only the head office. Both are ordinary logistics problems, and both are the reason multi-site estates drift when nobody owns them centrally.
Questions we get about this
What procurement and IT ask about the two ends.
What is a data wipe certificate and why do we need one?
It is a document stating that the storage in a specific device, identified by serial number, was erased to a named standard on a given date. You need it because an auditor or a customer may ask what happened to devices that held their data, and a verbal assurance is not an answer.
Can old laptops be resold instead of recycled?
Often yes, and it is the better outcome. A three-year-old business laptop still has value once wiped. The residual value usually offsets a meaningful share of the disposal cost, and it is the environmentally better route.
What does staging include?
Imaging or enrolment, applications, security configuration, asset registration, labelling and packing for delivery to the user. The result is a device the user signs into and starts working on, rather than one an engineer has to visit.
How long should a device stay in service?
Three to four years for most office users, sometimes five for light use. Battery condition and warranty expiry usually decide it rather than performance. Planning the rhythm beats replacing on failure, because failures cluster in busy weeks.
Where this lands in our work
The services around a device.
Want this looked at for your own sites?
Half an hour on a call is usually enough to tell you whether we are the right party for it, and we will say so if we are not.