Hardware asset management (HAM) is the tracking of physical IT equipment such as laptops, servers, and peripherals from purchase through disposal.
Hardware asset management (HAM) is the practice of tracking an organisation’s physical IT equipment - laptops, monitors, phones, servers, peripherals - through its whole life, from purchase order to disposal. At any moment it should answer: what do we own, who has each item, where is it, what did it cost, and when does its warranty end. HAM is one half of IT asset management; the other half, software asset management, looks after licences and software entitlements rather than the machines they run on.
What HAM covers
The unit of work is the device record. For each piece of hardware, a working HAM process maintains: a unique asset ID and the manufacturer’s serial number, the model and category, the current owner and location, the status (in use, in storage, in repair, retired), purchase date and price, supplier, and warranty end date. The record collects history as the device lives its life - assignments, repairs, transfers - so that questions like “who had this laptop before it broke” have an answer.
The scope question matters as much as the fields. Laptops always make the list; the equipment that leaks is the unglamorous kit around them - printers, docks, monitors, and the networking equipment in the comms cupboard that nobody has looked at since installation.
The hardware lifecycle
HAM is usually described as a sequence of stages, each with a record-keeping moment:
- Request and purchase - the need is approved, the order placed, the cost captured.
- Receive and tag - the device gets an asset ID and label on arrival, before it disappears into use.
- Deploy and assign - the device is issued to a person, team, or location, and the record says so.
- In service - repairs, transfers between owners, and condition changes are logged as they happen.
- Refresh decision - age, repair frequency, and warranty status feed the replace-or-keep call.
- Retire and dispose - data is wiped, the device is sold, recycled, or scrapped, and the record is closed rather than deleted.
The common failure is treating step 2 as optional. Equipment that enters service untagged tends to surface again only at the next office move.
HAM vs SAM
Hardware and software asset management answer different questions about the same estate. HAM asks “where is the machine and what state is it in”; SAM asks “what are we licensed to run, and does usage match what we bought” - including whether each licence is perpetual or a subscription. They intersect constantly: issuing a laptop usually assigns software seats, and retiring one should free them. Larger estates also feed both from asset discovery scans, which find what is actually connected to the network and installed on it.
Common mistakes
- Tracking purchases, not custody. Finance knows what was bought; nobody knows who holds it now.
- A spreadsheet without an owner. Shared sheets decay because updating them is everyone’s job and therefore no one’s.
- No event discipline. If handovers, repairs, and returns are not recorded at the moment they happen, the register is a guess within six months.
- Ignoring disposal. Retired devices with company data still on them are a security problem, not a storage problem.
HAM in practice
For small and mid-size teams, working HAM is a register, labels, and a habit - every device recorded at purchase, every handover logged, every repair attached to the record. The full IT inventory then stays trustworthy without annual rebuild exercises. AMPthilly covers this pattern directly: an asset register with owner, status, warranty and purchase fields, printable QR labels that open the device record from a phone camera, checkouts and returns, and a permanent audit history per asset - with a free tier (3 users, 25 assets) to register a first batch.
Related terms
- IT Inventory - the complete record HAM keeps current
- Asset Discovery - automated scanning that finds what is on the network
- Configuration Item - the service-centric view of a component in a CMDB
- Software Entitlement - the licence rights SAM tracks alongside HAM’s hardware
- Perpetual vs Subscription License - the two licence models SAM reconciles
FAQ
What is the difference between HAM and SAM?
Hardware asset management tracks physical equipment - the laptop, its serial number, owner, warranty, and condition. Software asset management tracks licences and entitlements - what was purchased, what is installed or assigned, and whether the two match. The same machine touches both: the laptop is a hardware asset, while the operating system and applications on it are software assets. Many teams manage both in one register because the lifecycle events overlap so heavily.
What equipment does hardware asset management cover?
Anything physical the IT function buys, issues, or supports: laptops, desktops, monitors, phones, tablets, servers, networking equipment, printers, docking stations, headsets, and peripherals above your value floor. The discipline is setting that floor explicitly - tracking every cable individually is busywork, but a blanket "we don't track peripherals" is exactly how projectors and docks vanish.
Do small businesses need hardware asset management?
The trigger is not headcount but movement. The moment devices change hands regularly - new starters, leavers, repairs, shared kit - an untracked estate starts leaking equipment and warranty claims. A spreadsheet works at first; it breaks when nobody updates it at handover. The fix is less about tooling and more about a habit: every move gets recorded at the moment it happens, ideally by scanning a label rather than finding the right spreadsheet row.