IT asset lifecycle management is the structured process of overseeing IT assets from acquisition to retirement. Each stage of a device’s lifecycle involves specific policies and workflows within the broader IT environment.
Clear, well-defined processes enhance asset performance, reduce downtime, support business objectives, and ultimately help organizations cut costs while maximizing ROI.
This document outlines these phases and how the Reftab platform ensures your team adhere to them.
Planning Phase
A well-defined IT asset lifecycle starts with strategic planning. As an IT manager, this means aligning tech investments with business goals, assessing your current environment, and identifying how new assets will support long-term success.
Focus first on understanding business needs before selecting hardware and software. Each asset should drive productivity, streamline operations, and add measurable value.
Before making new purchases, evaluate whether existing assets are being fully utilized—this helps reduce unnecessary spend and ensures better ROI.
Reftab supports this strategic planning stage by giving IT managers clear visibility into asset usage and performance, helping them make informed, cost-effective decisions before investing in new technology.
Request / Acquiring Phase
Having users submit a request is best way to understand what a user needs. Ex. Laptop vs desktop with specific configurations or software with access rights. The request process ensures the details about the request are captured such as quantities, details, date needed by, their manager, their business group, etc.
Once submitted a request should go to their manager for approval. The manager is the best person to understand the business requirements and understand what the user needs to do.
Within Reftab: The requests feature can be used to provide request forms.
Deployment Phase
The ITAM team will be involved with pulling items from inventory if available or determining if new purchases are needed. Key thing here is to utilize inventory instead of making unnecessary purchases.
Tag the hardware asset with an asset tag. Checkout the device to the user in Reftab, then give the asset to the end user. If it’s a software request, make sure to log the license in Reftab and then assign the license seat to the user. It is important to note if software is installed locally or if it’s cloud-based SaaS software.
Within Reftab: This is the checkout of assigning the asset / software licenses to the end user. This should also be done automatically by taking advantage of provided integrations. For example, Intune, Jamf, etc. for hardware. For software tracking, Reftab integrates with MS Entra, Microsoft, Okta, etc.
Using Phase
During the time that the user is using the hardware or software, ITAM team needs to keep monitoring the usage of the asset.
Tracking software, for example, you’ll want to ensure software is not sitting idle and that the user is actually using the application. For hardware, make sure the user is using the hardware and not leaving it somewhere or not using it at all.
Within Reftab:
• The custody verification feature can be used to verify ownership of hardware.
• The license survey feature can be used to verify software usage and needs.
• The audit feature can be used to verify hardware inventory matches data in Reftab.
Verify Custody of Assets
License Surveys – How To
How to Audit Fixed Assets in Reftab
Maintaining Phase
Asset gets into this phase once it needs maintenance. Two categories of maintenance:
- Preventive
- Reactive
There are four primary types of maintenance:
- Corrective – performed after a problem is detected (most common)
- Emergency – sudden failure of asset and repair work is needed (threat to safety, etc.)
- Preventive – routine, scheduled maintenance to prevent unexpected breakdowns (based on time or usage)
- Condition-based – maintenance triggered by actual usage, monitoring, or calibration
Within Reftab: The maintenance feature can be used to log maintenance work.
Disposing Phase
If an asset is out of warranty, too damaged, past its usable life, or no longer supported by the vendor, it needs to be disposed. Accounts must be deprovisioned, data backed up, and data erasure methods applied. The item should be tagged as “Retired” in Reftab. Logs must be kept for software uninstalls or SaaS account deprovisioning.
Within Reftab:
• Status labels can be used to tag assets as disposed
• Reports can be used to return assets from offboarding users
• Offboarding Tickets can be used to log proper procedures
Viewing Archived Assets
Automatically Report on Disabled Users with Equipment
Setup and Utilize Onboarding & Offboarding