| IT asset management keeps a current record of the devices, software and cloud services your business uses, with clear responsibility for each one. It connects what you have with the support, costs and decisions that need attention. The record is useful only while it is maintained and checked. |
This guide explains what to record, how to build the first register and how to keep it accurate as people, systems and suppliers change.
It covers the record itself. Replacement decisions belong to hardware lifecycle planning, and licence rights and quantities to software licensing. Both rely on a register people can trust.
What Is IT Asset Management?
IT asset management is the ongoing work of knowing what technology the business uses, who is responsible for it, what it costs and what needs attention next. The register is the maintained view of that environment, not a one-off count.
Include the technology the business uses or depends on, not only what it owns or leases. Cloud services, virtual systems and important supplier dependencies may matter without appearing on a purchase invoice. A controlled set of linked records is acceptable; one living register does not need to mean one giant spreadsheet.
What counts as an IT asset?
Devices such as laptops, desktops, phones, servers, network equipment and peripherals; software and subscriptions; and cloud services and the important dependencies behind them. NCSC guidance on assets and their importance also treats information and third-party managed services as assets, with an owner for each.
Who is responsible for each asset?
Separate three roles. The business owner is accountable for the asset and its purpose, the custodian holds or uses it day to day, and the support provider maintains it. One person can hold more than one role, but recording them separately makes changes and departures easier to handle.
Is an asset register the same as an inventory?
Not quite. An inventory identifies what exists, and it can include software as well as hardware. IT asset management adds responsibility, costs, support dates and lifecycle decisions to that inventory. Tools and organisations use the terms differently, so agree what your own register covers.
Why Does IT Asset Management Matter for Your Business?
A maintained register helps you identify what needs support, who is responsible and which costs or deadlines need attention. The benefit depends on the quality of the information and on the decisions made from it.
Without one, the same questions come up at the worst moments: who has the laptop of someone who has left, whether a failing server is still under warranty, which subscription renews next month and who approved it. A register answers them from a record rather than from memory and invoices.
It also underpins security. You cannot patch, protect or recover a device nobody knows about, and NCSC asset lifecycle guidance links the asset list to patching, vendor support tracking and decommissioning.
Does a register make a business compliant?
No. A register helps identify assets and answer questions, but it does not by itself establish privacy compliance, licence compliance or insurance cover. Information privacy principle 5 requires reasonable safeguards for personal information; it does not prescribe this exact register. NCSC guidance supports inventory and ownership, but government standards are not automatically mandatory for every business.
Can a register reduce costs?
It can reveal unused capacity, duplicate subscriptions and approaching renewals. Whether a bill falls depends on approved action and the contract terms. Removing a licence from a person and reducing a purchased commitment are different actions, so check the agreement before assuming a saving.
What Should an IT Asset Register Include?
Start with the information needed to identify an asset, find the responsible person and decide what happens next. Hardware and subscriptions need different fields, but their records should link where they depend on each other.
| Record | Useful fields |
|---|---|
| Identity and scope | Asset ID, type, make and model or product, serial number or service identifier |
| Responsibility and location | Business owner, current user or custodian, support provider and physical or cloud location |
| Status and dependencies | In use, spare, missing, awaiting disposal or retired; business role and important dependencies |
| Purchase or agreement | Supplier, purchase or lease details, original cost and a reference to the agreement |
| Support dates | Warranty, operating system, firmware and vendor support dates recorded separately, with sources |
| Software commitments | Product, purchased quantity, assignment, billing frequency, term and notice deadlines |
| Verification and action | Source, last updated, last checked, unresolved gaps, next action, owner and due date |
| Retirement history | Sanitisation outcome, access removal, return or disposal details and completion date |
Use a reference to the approved vault or restricted licence record where needed. Do not copy passwords, recovery codes or sensitive activation details into a broadly shared register. Keep unknown values visible so they can be checked rather than guessed.
Why record warranty and support dates separately?
They answer different questions. Warranty coverage depends on the fault and the terms, and an expired warranty does not mean a device must be replaced. Security support comes from the operating system, firmware and vendor support dates, which are tracked on their own with a source for each and unknown values flagged.
Distinguish a vendor end-of-support date from your own planned replacement date. Deciding what to keep, repair, redeploy or replace belongs in hardware lifecycle planning.
How should software and leased equipment be recorded?
Record the product, entitlement, agreement, purchased quantity, assignments and renewal or notice dates, with a reference to restricted details rather than the keys themselves. Our software licensing service covers licence rights and quantities in more depth.
Leased equipment belongs in the register too, recorded with the agreement and return conditions. Device as a Service arrangements are a common example.
Purchase cost is not automatically current book value or replacement cost. Leave accounting valuation to your finance team or accountant.
How Do You Build and Maintain an IT Asset Register?
Build the first version from more than one source, then make updating it part of how the business buys, changes and retires technology.
Agree the scope and ownership
Choose the systems and asset types to cover, the person accountable for completeness and who maintains each part of the record.
Reconcile the starting records
Compare purchasing and subscription records with management tools, cloud services and equipment held by staff. Investigate differences rather than treating any one source as complete.
Update when things change
Include register updates in purchasing, deployment, reassignment, staff exits, supplier changes and retirement. Record the action and the person responsible.
Verify on an agreed cycle
Check records against real holdings and service administration, with critical or frequently changing assets checked more frequently. Review outstanding gaps and actions on a cycle that fits your risks.
Discovery tools help find assets, but they need reconciling with purchases, cloud administration, staff changes and physical holdings. They can miss disconnected equipment, separately purchased subscriptions and items outside their scope, so logging deployments reduces surprises without removing the need to check.
Who should update and verify the register?
Agree business accountability and technical maintenance separately. A managed IT provider can maintain agreed records as part of its work, but staff and other suppliers still need to report changes. Updating a record after a change and checking that the whole register is accurate are different tasks, and both need an owner.
How does a small business start?
Start small and controlled. List the main devices and paid subscriptions first, with the business owner, custodian and support provider for each, then add the support dates you can confirm and flag the rest as unknown. A spreadsheet or the asset features in an existing management tool is enough to begin with.
Add peripherals, network equipment and smaller subscriptions once the core records are updated as part of normal work. Buy a dedicated tool when the volume of changes or the number of sources makes manual reconciliation hard to keep up, not before. The process matters more than the product.
The register sits alongside wider IT documentation, which explains how systems connect and how they are supported. Each can reference the other without duplicating it.
What Does a Well-Maintained Register Show?
A useful register is open about its gaps. It shows what has been reconciled, what is still unconfirmed, who is responsible and which actions are due.
- Assets reconciled. Records checked against purchases, tools and real holdings
- Gaps identified. Unknown values and unconfirmed items flagged rather than guessed
- Responsibilities recorded. An owner, custodian and support provider for each asset
- Actions reviewed. Renewals and notice dates reviewed before commitments, not renewed automatically
What are the common IT asset management mistakes?
Treating the register as a one-off inventory, so it drifts out of date and people stop trusting it. Tracking hardware while missing subscriptions and cloud services. Copying passwords or activation details into a shared file. Trusting one source, such as a discovery tool, without reconciliation. And marking an asset retired before the retirement work is complete.
What Happens When an IT Asset Is Retired?
Retirement is a completed process, not a status change. Marking an asset retired does not on its own remove it from risk, insurance or contracts.
- Retain what is required. Confirm business information is kept or migrated, and that backups can still be restored
- Remove access. Remove accounts, management enrolment and dependencies as appropriate
- Sanitise and verify. Use a method suited to the media and data, then verify the result
- Record the outcome. Note return, reuse, recycling or destruction, with the date and who completed it
Sanitisation, physical destruction, recycling and lease return are different outcomes. NIST SP 800-88 Revision 2 sets out media sanitisation guidance, and our secure IT disposal service covers the disposal step. Keep the retired record, and complete any contract, insurance and financial updates separately.
Get Help Keeping Your Asset Register Current
Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide. As part of managed IT services, we can maintain agreed asset records, reconcile them with the systems we manage, flag gaps and raise support and renewal dates for review.
Your staff and other suppliers still report the changes we cannot see, and you decide what happens next with each asset.
NEXT STEP
Who updates your register when a device changes hands?
Exodesk can help maintain agreed asset records as part of managed IT support. Tell us where the records sit today and what is missing.
Or read our guide to hardware lifecycle planning.
Frequently Asked Questions
What is IT asset management?
It is the ongoing management of the devices, software and cloud services a business uses, supported by current records of responsibility, location, costs, support and status. It includes keeping those records accurate and acting on the issues they reveal.
Why is IT asset management important?
It helps a business identify what needs support, who is responsible and which costs or deadlines need attention. Better records can reduce avoidable waste and missed actions, but the benefits depend on the quality of the information and the decisions made from it.
What should an IT asset register include?
Record identity, owner, custodian, location, status, purchase or agreement details, relevant support dates, dependencies and the next action. Include the source and last-verified date. Software records also need entitlement, quantity, assignment and renewal details, while secrets belong in a separate protected repository.
What is the difference between IT asset management and IT inventory management?
Inventory identifies what exists and its relevant attributes, and it can include software as well as hardware. IT asset management uses that information to manage responsibility, costs, support, use and retirement. The terms can overlap between tools and organisations.
What is the difference between IT asset management and hardware lifecycle planning?
Asset management keeps the current record and manages changes while an asset is in use. Hardware lifecycle planning uses that information to decide whether to keep, repair, redeploy or replace equipment, then schedules the work and budget. The same records can support both.
How is IT asset management different from IT documentation?
The asset register records the technology in use and its ownership, commercial and lifecycle details. IT documentation also explains how systems connect, how they are supported and how routine work is done. Records can link to protected access information without containing the secrets themselves.
When should an IT asset register be updated?
Update affected records when assets are purchased, deployed, moved, reassigned, changed or retired, and when contracts change. Verify accuracy on a schedule suited to the risk and rate of change. Record when an item was checked and identify anything still unconfirmed.
What happens to IT assets at the end of their life?
Confirm required information is retained, remove access as appropriate and sanitise storage using a suitable method. Verify the result and record return, reuse, recycling or destruction. Keep the retired record and complete any contract, insurance and financial updates separately.
Can a small business benefit from IT asset management?
Yes. A small business can start with controlled records of its main devices and subscriptions, a named owner and updates when things change. The process matters more than buying a particular tool, and automation can be added when the records and workload justify it.
Should IT asset management include software licences?
Yes. Include the products, entitlements, quantities, assignments and commercial terms relevant to the environment. The register supports licence checks but does not establish compliance on its own, and low visible use does not prove a licence is unnecessary.
Contact us or call 0800 396 337 to talk about your IT asset register.
