An IT asset inventory is one record of every device you support: what it is, its unique ID, who has it, where it sits, and its status. Build it step by step from scope to tickets, then keep it current with event updates and location checks.
We build SherpaDesk, a helpdesk and PSA (professional services automation) a small IT team can run alone. No contract. No implementation project. No dedicated admin. The steps work in a spreadsheet or any tool.
Key takeaways
Definition
An IT asset inventory is a current list of the hardware your team supports, one record per device. Each record says what the device is, gives it a unique ID, and names its owner, user, location, and status. NIST calls system components "discrete, identifiable" IT assets.
TechTarget defines an IT asset as "any company-owned information, system or hardware used in business activities." This guide covers hardware. NIST's Cybersecurity Framework names hardware and software inventories as separate outcomes. We recommend two lists that point at each other: link each license to its device or user.
The inventory feeds IT asset management, which uses it to optimize spending; our IT Asset Management Software guide covers that practice and the tools. Our IT asset lifecycle management guide covers what happens to each device from purchase to disposal.
NIST's Cybersecurity Framework 2.0 lists "Inventories of hardware managed by the organization are maintained" as its first asset management outcome.
When a ticket says "my laptop is slow," an accurate IT asset record shows the model, warranty, and past tickets. Without one, the first reply is a question.
When people leave, the record tells you which laptop, phone, and dock to collect. One r/sysadmin member wants to know which "employee has been assigned 6 laptops in the last year that are now on Facebook market place."
One example runs through every step: Harbor Dental, an MSP client with three sites and a 46-row spreadsheet.
Give a record to anything that can store or process data. CIS lists end-user devices, including portable and mobile ones, network devices, IoT devices, and servers.
Example: Harbor Dental's scope: workstations, laptops, printers, switches, the firewall, and a NAS.
Common mistake: tagging everything on day one. One r/msp member's MSP gave a client "like 9,000 labels, and they used them and tracked them for about 3 weeks."
Pick the columns from the starter list below. NIST notes that preventing duplicate records "necessitates use of a unique identifier for each component." Use a short prefix and a number. Assign it when step 4 confirms the record, print it on the IT asset tag, and never reuse it.
Example: HD names the client, never the user or room: HD-0001 to HD-0041; the two TMP rows get theirs once confirmed.
Common mistake: using the machine name as the ID. Rename the laptop and its history splits in two.
Work inside one client or department; never match across accounts. Use one spelling per make and model. A row with an unreadable serial keeps the serial blank, gets a temporary row ID such as TMP-01, and goes on the check list. Blank serials never match automatically. Once someone confirms the device in person, it gets its HD- ID; TMP-01 stays as a note to the source row.
Example: 46 rows become 41 after five confirmed duplicates merge. Two rows are TMP rows; seven say "Unknown" for location.
Common mistake: merging on a matching serial alone. Confirm both rows are one physical device, and keep both histories and links.
Match the RMM or device-console export to the sheet by real serial numbers only. Each field takes its value from the record that wins in the table below; doubtful matches go on the check list.
Example: the export adds two laptops: 43 records. One location conflict goes on the check list.
Common mistake: treating one export as the inventory. An export shows what that source is set up to see. One r/msp member's clients want to know where devices are, "which no RMM report will tell you."
CIS asks for the "enterprise asset owner" and the "department for each asset." For an MSP, the account is the client; for internal IT, the department. The owner answers for the device; the user has it. Shared devices say "Shared"; unassigned spares leave the user blank.
Example: HD-0017, the Main Street front-desk PC, is Shared; its owner is the office manager.
Common mistake: assigning unknown devices to "IT." Nobody looks for them.
Five statuses cover most small fleets: Active (in service), Spare, Loaner, Missing, and Retired. A device in repair stays Active with an "In repair" note. The upkeep table shows who changes what. A retired device keeps its record and wipe date. With owner, user, location, and status set, test-import ten rows from one account, check them, then load the rest.
Example: HD-0009, a replaced reception PC, goes from Active to Retired with "drive wiped Oct 14."
Common mistake: deleting retired devices, and their history with them.
Walk one site at a time. Mark each device found, and add any IT asset that has no record. A device not found goes on the check list as "Not found," with an owner and a two-week deadline; after that, it's Missing.
Enter pending moves first: a count against out-of-date records can adjust the wrong thing. For remote laptops, ask the user to reply to a ticket with the tag ID, their name, where the device is, and its condition. The tag ID alone confirms possession only.
Example: at Main Street, 16 of 18 records match. One printer is in the wrong room; one laptop is Not found, and the office manager has two weeks.
Common mistake: fixing a mismatch without asking why. Investigate each error.
Every ticket about a device names its asset ID, so the IT asset record collects its repair history.
Example: HD-0031, a printer, has its third ticket this quarter: time to replace it.
Common mistake: writing "the printer" in the ticket. Harbor Dental has three.
When records disagree, this rule decides, and the latest confirmed event beats an older check. Unresolved differences stay on the check list.
| Field | Record that wins | Confirmed by |
|---|---|---|
| Serial, make, model | The device label | Reading the label during a walk |
| Machine name, last seen | The RMM or device console | The latest export or sync |
| Account | Your client or department list | The purchase record; never matched across accounts |
| Assigned user | The handover on the setup ticket | The user, in person or by ticket reply |
| Location | The latest confirmed move or check | A walk, a move ticket, or a full user reply |
| Status | The ticket that changed it | The technician who made the change |
These fields cover most of NIST's inventory specifications, such as serial number and physical location, and most of CIS's, such as machine name, owner, and department.
| Field | Example | When |
|---|---|---|
| Asset ID | HD-0023 | Required at import |
| Serial number | 5CD1234XYZ, or blank if unreadable | Required at import |
| Category | Computer | Required at import |
| Type | Laptop | Required at import |
| Make | Dell | Required at import |
| Model | Latitude 5440 | Required at import |
| Status | Active, Spare, Loaner, Missing, or Retired | Required at import |
| Account | Harbor Dental (MSP client) or a department | Required at import |
| Location | Main Street / Front office | Required at import |
| Owner | Office manager, the person accountable for it | Required at import |
| Assigned user | A named person, Shared, or blank for a Spare | Required at import |
| Machine name | HDLT-0023 | Add when you can |
| MAC address | For networked devices | Add when you can |
| Purchase date | 2026-03-02 | Add when you can |
| Cost | 1149.00 | Add when you can |
| Supplier | The reseller on the invoice | Add when you can |
| Warranty end | 2029-03-01 | Add when you can |
| Last seen by a source | 2026-10-27, from the RMM or device console | Add when you can |
| Last verified by a person | 2026-10-14, after a walk or a full user reply | Add when you can |
"Last seen by a source" confirms the device checked in, not its user, room, or status. "Last verified by a person" changes only once ID, user, location, and condition are confirmed. It schedules the next walk: the oldest site goes first.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Events update the record the same day; a monthly reconciliation catches what slipped through.
| Event | Change | Who | When |
|---|---|---|---|
| New device arrives | New record, Spare, tag on | Whoever receives it | The day it arrives |
| Device issued or reassigned | Spare to Active, user set | Technician on the setup ticket | At handover |
| User leaves | Spare, user cleared (history kept), location set to IT storage, owner stays | Technician on the offboarding ticket | The day it's collected |
| Device goes for repair and returns | Out: Active, "In repair" note, location the repair shop. Back: real location and user restored, note removed | Technician on the repair ticket | When it leaves and returns |
| Loaner issued or returned | Its own ID: Loaner, recipient, return date. On return: Spare, user cleared, location IT storage | Technician on the repair ticket | At handover and return |
| Shared device moves | New location, same owner | The owner tells IT; the technician updates it | The day it moves |
CIS asks you to review and update the inventory "bi-annually, or more frequently."
One r/sysadmin member wrote about asset databases. "They fail because no one owns drift. If updates depend on humans remembering to edit a record, it's already stale."
Store these rules with your procedures; see our Knowledge Base Software guide.
Each month, verify one site, the way a warehouse counts part of its stock until it has counted all of it.
Schools can run it by building; our IT Support For Schools guide covers the rest.
Track three numbers:
We found no neutral benchmark, so watch the trend per site.
Spot-check accuracy for one site
matched ÷ checked × 100. Your numbers stay in the browser.
How this works in SherpaDesk
It's a helpdesk and PSA a small IT team can run alone. In Asset Manager, you classify devices by Category, Type, Make, and Model, bulk-import them from an XLSX template, and add your own fields. Devices can also sync from NinjaOne or, for Chromebooks, from Google Device Manager.
Each asset gets a unique ID and is assigned to an account, a location, and a user. Statuses include active, retired, and missing, plus Loaner and Daily Loaner. An asset auditor assigned to a location verifies its assets or marks them missing. Assets link to tickets. Each record tracks work history and service costs.
Asset Manager is on High Camp: $55 per agent per month ($50 billed annually). Your first agent is free on any plan, so three technicians pay for two: $110 a month. No contract, 14 days free, no card. Schools are priced by enrollment; ask sales for a quote.
Who this isn't for
If you need network discovery scans or software license metering, use a dedicated tool. Devices reach Asset Manager by XLSX import, manual entry, or the NinjaOne and Google Device Manager syncs. We don't build RMM. We integrate with yours, and the stack stays yours.
Start with the eleven fields this guide requires at import: asset ID, serial number, category, type, make, model, status, account, location, owner, and assigned user (blank for spares). The asset ID is yours, assigned once and never reused. The starter list has examples and a TXT download.
Finish steps 3 to 6 for one account first, so every required field is set. Import about ten of its rows and check every field against the sheet. Fix the mapping, load the rest, then start the next account. See step 6.
Decide by field, not by source. The device label wins for serial and model, the RMM or console for machine name, the handover ticket for the user, and the latest confirmed move or check for location. See Which Source Wins.
Import it as "Unknown" and put it on the check list rather than guessing. The next walk at its likely site settles it. If it isn't found, it becomes "Not found" with an owner and a two-week deadline, then Missing. See step 7.
A checked sheet can work for one editor. As one r/msp member put it, "A spreadsheet with some audit cycle is better than a lot of these systems." Move when several technicians edit it, tickets name devices, or you sync from an RMM.
CIS asks for a review and update every six months or more often. With six sites or fewer, verifying one a month checks every site at least twice a year. Remote laptops need a full ticket reply (ID, user, location, condition) plus the RMM's last-seen date. See Keep It Current.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.