Request a quote
Emergency SectorsCareers About us Blog Get in touch
Warehouse worker scanning a box on a rack with a handheld scanner; a sensor and a small camera are mounted on the racking

IT asset lifecycle management: from a list to a process

Almost every organisation has a spreadsheet of laptops. IT asset lifecycle management only starts when that list changes by itself at every purchase, issue, repair and disposal, and when someone can make a decision from it. This article is about that step: what you track, who changes what, where the data comes from and what you do with it tomorrow.

7 min read Written by the ITproposal team
Short answer

An inventory says what is there. IT asset lifecycle management also says what is about to happen: when warranty ends, when something must be replaced and what you still pay for that has already gone.

Track few fields and give every status change one owner. Twelve columns that are right are worth more than forty nobody fills in.

Let the list check itself: compare it every month with what your device management sees. Whatever appears in only one of the two is that month’s work.

What IT asset lifecycle management is, and why an inventory is not enough

An inventory is a snapshot: on the day of the count, this is what was there. IT asset lifecycle management is the process that keeps that list current afterwards and ties decisions to it. You notice the difference as soon as someone asks a question about the future: which laptops fall out of warranty next quarter, which phones no longer get updates, and what are we still paying for devices that have already gone?

The register itself, and how to fill it properly once, is described on our page about the IT asset register. This article is about what comes next: keeping the register in step with what happens in the organisation.

The test is simple. Is your list updated because something happens, or because somebody remembers? In the second case you have an inventory, however detailed it is.

What counts as an asset, and what does not

Try to track everything and you end up tracking nothing. Agree beforehand what belongs in it:

  • Devices with a serial number and data on them: laptops, desktops, phones, tablets, servers, network equipment, scanners. These always belong in it.
  • Peripherals without data: monitors, docks, headsets. Track them individually if there is a reason (expensive screens, kit lent to home workers), otherwise as a count per site.
  • Software and subscriptions: belong in the same process, because a licence is often tied to a device or user. How to save there is in our article on software licence management.
  • Leased and rented equipment: not yours, but your responsibility. This is exactly what must go back complete at the end.
  • Spares and devices in a cupboard: no management system sees them, because they are switched off. That is why they must be added explicitly.

Employees’ personal devices do not belong in it as assets. If they access business data they belong on another list: that of device management.

The fields you will actually use

Every product offers dozens of fields. Start with the ones a decision depends on:

  • Serial number and model. Without a serial number a row is a quantity, not a device.
  • User and location. Who has it and where it is, even if that is “at home”.
  • Status. Ordered, in stock, in use, in repair, returned, disposed of.
  • Purchase date, supplier and order number. Needed for warranty and for finance.
  • End of warranty and end of updates. Two different dates, and the second is often the more important.
  • Ownership. Bought, leased or rented, and if so until when.
  • Disposal. Date, party and the proof that the data was removed.

An asset tag on the device helps with counting, but it does not replace the serial number. Tags come off; the serial number is also in the firmware and on the invoice.

From ordered to disposed of: every status has an owner

A register goes out of date at the transitions. So agree who makes each transition, and make it part of work that happens anyway:

  • Ordered to in stock: whoever receives the delivery, using the serial numbers on the delivery note or from the supplier’s file.
  • In stock to in use: the service desk at issue, linked to the new starter’s ticket.
  • In use to repair or return: the service desk, on the fault ticket.
  • In use to returned: the leaver process, driven by HR. This is where it fails most often, because IT is the last to hear that someone is leaving.
  • Returned to disposed of: only once the certificate of wiping or destruction is in, not when the box has left the building.

A transition without an owner is a gap. Usually it is the last one: devices that have gone and stay on the list.

Let the list check itself

The register is not the only source that knows something. Device management (Intune or another MDM solution) sees which devices check in, purchasing knows what was ordered, HR knows who joins and leaves. Compare them, ideally every month:

  • In the register, not seen by device management: lost, in a cupboard, or already gone and never recorded.
  • Seen by device management, not in the register: bought outside the process, or a personal device that does not belong.
  • User in the register no longer employed: a device that has not come back.

Those three short lists are the month’s work, and they shrink as the transitions improve. If they stay long, you also know which transition is the problem.

Spreadsheet, service desk tool or a dedicated ITAM product

The tool matters less than the process, but it has to fit your size. Three questions decide it:

  • How many devices, and how many transitions a month? A small, stable organisation can manage with a shared spreadsheet, as long as there is one owner. With a lot of joiners and leavers, manual work becomes the weak point.
  • Where do the transitions already happen? If issue and repair run through a service desk tool with an asset module, the register belongs there, so the ticket changes the status.
  • Can it connect to what you already have? To device management for the comparison, and to your supplier for serial numbers on delivery. Without that you type everything twice.

A dedicated ITAM product makes sense with many sites or a lot of software. For most SMEs it is more tool than process.

What you do with it tomorrow

A register that is right turns questions that would take an afternoon into a report:

  • Refresh planning. Which devices fall out of warranty or updates over the coming year, per quarter. That is a budget line instead of a surprise.
  • Warranty. When something fails you see straight away whether it is covered and who to call.
  • Leavers. Someone leaving has a list of what must come back, instead of a question whether they “still have anything of ours”.
  • Audit and ISO 27001. The standard asks for an inventory of information and other associated assets, with owners. A register with statuses and owners is that answer, and for Cyber Essentials it tells you which devices are in scope.
  • Insurance and theft. What was there, on which serial number, and what it was.

Where our work stops

What we do. We supply equipment with the serial numbers attached, so it is in the register on delivery; we set up the statuses and the link with device management, handle issue, repair and collection, and dispose of devices with a certificate of wiping or destruction. We are ISO 9001 and ISO/IEC 27001 certified, and that is how we work.

What we do not do. We are not accountants: how you capitalise and depreciate equipment, and the tax treatment, is for your accountant. We are not an insurer and do not say what is covered. And we certify nobody: whether your register meets ISO 27001 is for a certification body to assess.

Frequently asked

Questions we get about this

The five that come up most often.

What is IT asset lifecycle management?

IT asset lifecycle management is the process of tracking which IT assets you have, where they are, who uses them and which stage they are in, from order to disposal. Unlike an inventory, the list updates itself at every purchase, issue, repair and disposal. That is what lets you plan replacements from it.

What are the stages of the IT asset lifecycle?

Usually: ordered, in stock, in use, in repair, returned and disposed of, with planning before the order and proof of data removal at the end. Each transition needs an owner, such as the service desk at issue or HR when someone leaves. Most registers go wrong at the last stage.

Which data should you record for each device?

At minimum the serial number and model, user and location, status, purchase date and supplier, end of warranty and end of updates, ownership (bought, leased or rented) and, on disposal, proof that the data was removed. More fields only help if someone actually maintains them.

Is a spreadsheet enough for IT asset management?

For a small organisation with few changes, yes, as long as one person owns it. With many joiners and leavers, manual work becomes the weak point and it is better to let the service desk update the register and link it to device management.

Can you track depreciation of our equipment?

No. We record the purchase date, order number and ownership so the data is available, but how you capitalise and depreciate equipment is work for your accountant. We are not accountants and do not advise on it.

Related services

Further reading

What this process connects to.

Shall we make your list keep up by itself?

Tell us roughly how many devices there are and where you track them now. You will get back which transitions lack an owner and how the list then stays current without anyone chasing it.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call