An IT asset inventory should include, for every physical device: an asset tag, serial number, make and model, exact location down to rack and U position, owner, purchase and cost details, warranty or lease dates, a flag for whether it holds data, its current status, and a dated record of every custody change.
Those fields sound obvious, and most inventories have some of them. The trouble is the ones that are missing or stale when you need them, usually during an audit, a move, or a disposal. This guide sets out the full field list for a hardware asset inventory, the foundation of CIS Control 1, why each one earns its place, and an example value for each.
Why Do the Inventory Fields Matter?
The fields decide which questions the inventory can answer. A list of serial numbers tells you what you own. It cannot tell you where a device is, who pays for it, whether it can be retired, or whether it is safe to put on a truck.
Each field should exist because someone needs to act on it. If nobody uses a field, it will not be kept current, and a stale field is worse than a missing one because people trust it. Start with the fields below, then add only what your own processes require. The same list works for a small IT equipment inventory in a branch office or a large data center estate.
The Core Fields, With Example Values
This table works as a hardware inventory template and an example of a complete record. The examples are made up, but the formats are typical.
| Field | Why it matters | Example value |
|---|---|---|
| Asset tag | Your own permanent, unique identifier | A-004817 |
| Serial number | Manufacturer identity for support and disposal certificates | 7XK2P93 |
| Manufacturer and model | Specs, weight, power, and support coverage | 2U rack server, model X-200 |
| Asset type | Groups devices for reporting and planning | Server |
| Site | Which building the device is in | Main campus, DC2 |
| Room or cage | Narrows the search inside the site | Hall B, Cage 14 |
| Rack and U position | Exact physical location | Rack B14-07, U22-23 |
| Owning department | Who approves changes and pays | Finance Systems |
| Technical contact | Who answers questions about the device | Named person or team |
| Purchase order and date | Proof of purchase, audit trail | PO-2024-1183, 2024-03-12 |
| Cost and ownership type | Owned, leased, or financed | Leased |
| Lease or contract end | Return or renewal deadline | 2027-03-31 |
| Warranty or support end | Repair entitlement and refresh timing | 2027-03-11 |
| Data-bearing flag | Whether the device holds drives or storage media | Yes, 8 drives |
| Status | In use, in storage, in transit, retired | In use |
| Custody history | Dated record of who held it and where | Received 2024-03-20, dock, signed |
Some teams also track power draw, weight, network ports, and the drive serial numbers inside each device. Those are worth adding if you plan moves or rack layouts from the inventory.
Identity and Location Fields
Tag, serial, make and model
The asset tag is the anchor. It should be your own number, never reused, and not encoded with location or department, because those change. The asset tagging and labeling standards guide covers tag materials, placement, and identifier schemes.
Record the manufacturer's serial number as well. It is what the manufacturer needs for support, and it is what a certificate of destruction or recycling will list. Record make and model in a consistent format so you can filter on them.
Site, room, rack, and U
Location should be precise enough that someone who has never been in the building can walk to the device. "Data center" is not a location. "Hall B, rack B14-07, U22-23" is.
Rack and U position are the fields most often left blank, and they matter most during a move. Planners use them to build move groups, rack elevations, and labeling plans. A site survey before a relocation will often find devices in places the records do not show, so expect a reconciliation step.
Ownership, Financial, and Warranty Fields
Ownership tells you who decides. If a device has no owning department, nobody can approve retiring it, and it tends to stay powered on for years.
Financial fields include the purchase order, purchase date, cost, and whether the device is owned or leased. Lease end dates are deadlines. Leased equipment usually has to be returned complete, in working order, and on time, so the inventory should flag what is coming due well in advance.
Warranty and support end dates drive refresh planning and tell you whether a failed part will be replaced under contract. Track them per device, not per purchase, because devices bought together often have different coverage.
What Is the Data-Bearing Flag For?
The data-bearing flag records whether a device contains drives or other storage media, so you know which assets need extra controls when they move or leave. It is one of the most important fields in a hardware asset inventory and one of the least often present.
For devices with storage, note how many drives and, ideally, their serial numbers. Drives get swapped, and a disposal certificate, such as the certificate of sanitization described in NIST SP 800-88, is only useful if the serials on it match your records. What happens to the data on those drives is your own IT team's decision. The inventory's job is to make sure no data-bearing device is treated like a keyboard or a patch cable.
Status and Custody History
Status should use a short, fixed list: on order, received, in storage, in use, in transit, awaiting disposal, disposed. Free-text statuses cannot be counted.
Custody history is the dated record of each handoff: who had the device, where, and who signed. It is what lets you prove where an asset was on a given day. During moves, a formal chain of custody record with signatures at each transfer gives you a dated, signed entry for every device that moved.
How Do You Keep the Inventory Accurate?
By checking it against the floor and updating it at every change. An inventory is only as good as its last physical check. Records drift every time someone moves a server without updating the location, or swaps a drive without noting it.
Build updates into the events that change things: receiving, installs, moves, repairs, and disposal. Then walk the floor on a schedule and compare what you find against what the records say, using the approach in reconciling a CMDB against physical inventory. The IT asset inventory guide covers how to run those counts and how to resolve what does not match.
The best time to fix the field list is before a move or an audit, not during one. Pull a sample of twenty devices, check every field against the physical hardware, and you will know quickly which fields your team can trust.