What Is an IT Inventory?

An IT inventory is a complete, current record of every hardware and software asset an organisation owns or pays for - what each item is, who holds it, where it sits, and what state it is in. On the hardware side that means the laptops, monitors, servers, phones, and peripherals in circulation; on the software side, the licences and subscriptions the company is entitled to use, including each software entitlement and how many seats of it are actually assigned.

What to record for hardware

For each physical item, a useful inventory captures: a unique asset ID, the category and model, the manufacturer’s serial number, the current owner or location, the status (in use, in storage, in repair, retired), purchase date and price, supplier, and warranty end date. Condition notes and attached documents - receipts, manuals - earn their keep the first time a warranty claim or insurance question comes up.

Set a value floor explicitly. Below it, items are counted as categories (“14 docking stations”) rather than tracked individually. Without a stated floor, teams drift into either tracking every cable or tracking nothing smaller than a laptop - and the second drift is how projectors and docks disappear.

What to record for software

Software entries need different fields: the product and vendor, the licence model - perpetual or subscription - the number of seats owned versus assigned, the renewal or expiry date, the annual cost, and an owner responsible for the renewal decision. For seat-based products, per-user licensing makes the owned-versus-assigned gap the key number: unassigned seats are money leaking quietly, and over-assignment is a compliance problem waiting for a vendor audit.

Building the first inventory

The first pass is physical: walk the office, open the cupboards, and record what actually exists rather than what purchasing history says should exist. Tag items as you count them so the second pass never has to re-identify anything. A spreadsheet or CSV is fine as the capture format - the goal of day one is completeness, not tooling. For the software half, the billing trail (invoices, card statements, admin consoles) is usually a more honest source than memory.

Larger or messier networks add an automated pass: asset discovery scans find the devices and installed software currently connected, which catches things the walk-around missed. Discovery complements the count rather than replacing it - it cannot see the spare kit in storage or anything off the network.

Keeping it accurate

An inventory decays at the speed of unrecorded events. The pattern that holds up is update-on-event: issuing, returning, repairing, and retiring a device each touch the record at the moment they happen, ideally triggered by scanning a label rather than remembering to find a row later. A periodic verification - walking a sample of the estate and reconciling it against the record - then confirms accuracy instead of restoring it.

An IT inventory in practice

The teams whose inventories survive contact with reality tend to share three habits: one system of record rather than three competing spreadsheets, labels on everything above the value floor, and handovers that are logged as they happen. AMPthilly is built around exactly this shape - one register for physical equipment, licences, and consumables, CSV import for the day-one spreadsheet, and printable QR labels so a phone-camera scan opens the right record at every handover.

Related terms

• Asset Discovery - automated scanning that finds what is connected to the network
• Configuration Item - the CMDB view of components that support an IT service
• Software Entitlement - the usage rights a licence purchase actually grants
• Perpetual vs Subscription License - the two licence models in the software half of the inventory
• Per-User Licensing - seat-based licensing where owned-versus-assigned is the number to watch