The short answer
What should an IT asset inventory track?
Track desktops, laptops, servers, company-owned phones and tablets, routers, firewalls, switches, wireless access points, UPS equipment, printers, scanners, NAS or storage devices, and important monitors or peripherals. Include licensed software and SaaS subscriptions when ownership, cost, assignment, or renewal matters.
For physical assets, record an asset ID, manufacturer, model, serial number, assigned user, department, location, purchase date, vendor, warranty expiration, status, replacement target, and notes. Add hostnames, MAC addresses, IP information, operating systems, and technical relationships where those fields help support the device.
Decide which assets belong in the inventory
Inventory the technology that has business value, stores or accesses company information, requires support, carries a license, creates operational risk, or needs to be recovered when an employee leaves. A small company does not need to tag every inexpensive mouse, but it should be able to account for equipment whose loss or failure affects work.
Use categories that match how the business supports equipment. Separate user devices, servers, network infrastructure, shared office equipment, storage and backup devices, power protection, mobile equipment, and licensed services so reports remain understandable.
- Desktops, laptops, workstations, thin clients, and servers
- Company-owned tablets, phones, hotspots, and specialty mobile devices
- Firewalls, routers, switches, access points, controllers, modems, and UPS units
- Printers, scanners, multifunction devices, NAS systems, and external storage
- High-value monitors, docks, adapters, peripherals, and specialized equipment where appropriate
- Licensed software and SaaS subscriptions that require ownership, assignment, or renewal tracking
Record identity, assignment, location, purchase, and warranty fields
Give each physical asset a stable internal identifier. Manufacturer serial numbers are useful, but they may be difficult to read, may not match a vendor’s order record, and do not express the company’s own naming convention. The internal asset ID should remain attached to the record throughout the device lifecycle.
Assignment and location fields answer different questions. A laptop may belong to one employee but normally be located at a branch office; a printer may have no assigned user but serve a department; a spare device may be stored centrally and ready for deployment.
- Asset ID, category, manufacturer, model, serial number, and description
- Assigned user, department, manager, physical location, and storage location
- Purchase date, purchase price when appropriate, vendor, invoice or order reference, and ownership
- Warranty type, expiration, support entitlement, claim process, and proof-of-purchase location
- Current status, condition, notes, planned replacement date, and responsible support party
A record for laptop LT-0042 can show that it is assigned to the sales manager, normally works from the Hot Springs office, was purchased from a named vendor, is covered through a specific date, and is expected to be replaced in the next budget cycle.
Add technical information when it improves support
Technical fields should make the inventory more useful, not turn it into an unmanaged configuration database. Hostname, operating system, MAC address, IP address, device role, encryption status, management platform, and related system can speed discovery and troubleshooting for assets that participate in the network.
Use dynamic network details carefully. A fixed server address or firewall management address may belong in the record; a laptop’s temporary DHCP address usually does not. Record the stable relationship, such as the hostname, MAC address, assigned VLAN, or device-management enrollment, instead of constantly updating values that change by design.
- Hostname, domain or directory relationship, operating system, version, and device role
- MAC address, stable IP information, VLAN, switch or access-point relationship where useful
- Encryption, endpoint management, antivirus or EDR, backup, and remote-support status
- Server, storage, cloud tenant, printer queue, or application relationship
Track licensed software and SaaS subscriptions
Software assets may not have serial numbers, but they still have owners, costs, assignments, renewal dates, and risks. Record the product, vendor, business purpose, subscription tier, quantity, assigned users or department, billing owner, renewal terms, support contact, and cancellation procedure.
Do not put license keys, passwords, payment-card numbers, or MFA recovery codes in the general inventory. Reference the approved secure system where authorized staff can retrieve them.
- Application or service, vendor, tenant or account reference, and business purpose
- License model, purchased quantity, assigned quantity, department, and account owner
- Start date, renewal date, notice period, cost owner, and cancellation process
- Support entitlement, integration dependencies, data owner, and secure credential location
Track the complete asset lifecycle
Status should describe the asset’s real stage rather than simply active or inactive. A consistent lifecycle makes it possible to identify unreceived orders, equipment waiting for setup, loaners, devices under repair, unreturned employee equipment, and retired assets awaiting secure disposal.
Keep the history when equipment is reassigned or repaired. The current assignee is important, but prior assignments, repair dates, replaced parts, warranty claims, and configuration changes explain cost and reliability over time.
- Ordered: approved and purchased but not yet received
- Received: physically accepted and matched to the order
- Deployed: configured, assigned, and in service
- Reassigned: transferred with user, location, data, and condition updated
- Repaired: service event, parts, cost, vendor, outcome, and return-to-service date recorded
- Retired: removed from service with licenses, backups, and replacement relationship addressed
- Disposed: data handling, disposal method, vendor, authorization, and completion recorded
Asset inventory is not the same as depreciation records
An operational IT inventory and accounting fixed-asset records may share purchase date, vendor, price, and disposition information, but they answer different questions. Accounting records focus on financial treatment, useful life, depreciation, and reporting requirements. IT records focus on assignment, location, configuration, security, warranty, support, and service status.
Coordinate identifiers and shared fields when practical, but do not assume one system contains everything the other team needs. This guide is operational, not accounting or tax advice; the business should follow its own financial policies for capitalization and depreciation.
Quality-control review
Common omissions and mistakes
- Inventorying computers while omitting firewalls, switches, storage, printers, UPS units, and shared devices
- Using serial numbers as the only identifier and losing the internal assignment history
- Recording the assigned employee but not the department, location, manager, or status
- Tracking purchases without warranty expiration, repairs, replacement targets, or disposal
- Copying temporary DHCP addresses into the inventory as if they were permanent identifiers
- Keeping software renewals and license assignments in a separate person’s email inbox
- Marking devices retired without recording data handling, license recovery, or final disposition
Make the process repeatable
Use a consistent documentation system.
A reusable asset inventory makes receiving, assignment, support, warranty claims, budgeting, employee transitions, and disposal more consistent. Standard fields also help an MSP or consultant understand the environment without replacing the business’s accounting records.
View Small Business IT Documentation Pack