Your system says 240 laptops are deployed across three offices. The physical audit finds 198. That 42-device gap is the predictable result of running without a consistent process for physical inventory of IT assets. Equipment gets reassigned informally, retired without being removed from records, or deployed without ever being registered, and the system slowly drifts away from what actually sits on the floor.
The problem has become harder to manage over the last few years. Hardware is distributed across home offices, branch locations, and shared workspaces. Offboarding cycles are faster and less controlled. Compliance audits are more frequent. In that environment, the distance between records and physical reality grows quietly until an audit makes it visible.
This article covers what a physical IT asset inventory involves, why it matters in Hardware Asset Management (HAM), how the main identification methods compare, how to run a physical audit step by step, and how InvGate Asset Management supports the entire process.
Key takeaways
- A physical inventory of IT assets verifies that every asset recorded in the system exists, sits in the right location, and is assigned to the right person.
- Network discovery covers active networked devices. Physical identification methods cover non-IP assets, peripherals, and hardware in storage.
- The right identification method, whether Quick Response (QR) codes, barcodes, Radio Frequency Identification (RFID), or manual tracking, depends on asset type, audit frequency, and available hardware.
- A physical IT asset audit is the reconciliation step between the IT Asset Management (ITAM) system and physical reality, and in InvGate Asset Management every scan is checked against the expected set while the audit runs.
- InvGate Asset Management runs physical audits with QR codes and RFID readers, with barcode scanning coming soon, and records the result of each count on every asset once the audit closes.
What is a physical IT asset inventory?
A physical IT asset inventory is the process of verifying that the hardware assets recorded in your system actually exist, are located where the records say they are, and remain in the condition and state the system reports.
Three adjacent concepts often get confused with it.
- An IT asset inventory in the broad sense includes software, cloud services, and contracts.
- Network discovery detects devices that are active on the network with an IP address, which leaves out hardware in storage, peripherals without connectivity, and devices in transit.
- A Configuration Management Database (CMDB) documents relationships and dependencies between Configuration Items (CIs), without physically verifying that those items exist at a given location.
Physical inventory covers the ground all three leave open: confirming which hardware is actually present, tagged, and accounted for. That verified baseline is the foundation of HAM. Without it, every downstream decision (refresh planning, procurement, lifecycle tracking, compliance reporting) runs on data that may no longer reflect physical reality.
Why physical inventory matters in Hardware Asset Management
Most IT teams know their records are imperfect. What they often underestimate is how quickly imperfect records compound into operational and financial problems. When physical inventory runs without a consistent process, four patterns emerge reliably.
- Ghost assets are devices that appear in the system but no longer physically exist: retired equipment that was never removed from records, hardware lost during a move, or assets reallocated without an update. They inflate the asset count, distort financial reporting, and create confusion during audits.
- Unregistered assets are the mirror problem: hardware that is physically present but absent from the system, typically deployed informally or received outside the standard intake process.
- Inaccurate records also lead to bad refresh decisions, since teams purchase new hardware while usable equipment sits unseen in storage, and to compliance risk, because retiring an untracked asset leaves no documented chain of custody.
InvGate Asset Management surfaces these gaps through dashboards and Smart Tags that flag assets outside their expected assignment patterns. The underlying data those tools rely on comes from a physical inventory process, and knowing how to perform an IT asset audit is the first step to making those tools useful.
Physical inventory vs. network discovery: Why you need both
Network discovery is one of the most valuable tools in IT Asset Management. It scans the network, identifies active devices, and pulls hardware and software data automatically, giving networked endpoints, servers, and managed devices a level of visibility no manual process can match. That visibility stops at the network's edge: workstations in storage, peripherals such as monitors and docking stations, hardware in transit, and devices that only connect intermittently or through VPN all fall outside what a scan can see, along with the laptop assigned to a user who left three months ago.
Physical inventory covers that remaining ground. InvGate Asset Management combines agent-based and agentless discovery with support for non-IP assets: QR codes cover peripherals and equipment that cannot run an agent, RFID readers cover high-density areas, and physical audits compare what was scanned against what was expected. Together, the two approaches show what exists, where it is, and what state it is in.
Main methods for tracking physical IT assets
There is no single method that works for every environment. The right approach depends on the type of assets being tracked, the volume, the frequency of audits, and the infrastructure already in place, and most mature IT environments end up using more than one of these four:
- QR codes store a unique identifier linked to the asset record and can be scanned with any smartphone camera. They are the most practical entry point for a mixed fleet across several locations, as the guide on QR codes for Asset Management shows from tag generation to field scanning.
- Barcodes are one-dimensional codes that store a basic identifier, such as an asset ID or serial number. They are cheap per label and fit environments that already run barcode scanning, such as data centers with rack-mounted servers, though the tag alone reveals little without a system lookup.
- RFID reads tags by radio, without line of sight, so a single pass captures hundreds of assets. Readers and on-metal tags cost more, which is why RFID asset tracking pays off where asset volume is large and audits are frequent.
- Manual tracking records assets by serial number, asset tag, or visual inspection. It works in small, stable environments and is the first method that breaks down as the fleet grows, which places it at stage 0 of ITAM maturity.
No method wins in every environment. The decision comes down to asset type, fleet size, audit frequency, and the infrastructure already in place, and the table below summarizes the practical tradeoffs.
| Method | Implementation cost | Extra hardware needed | Works for non-IP assets | Scalability |
| QR codes | Low | No (smartphone) | Yes | High |
| Barcodes | Low | Yes (dedicated reader) | Yes | Medium |
| RFID | High | Yes (readers and tags) | Yes | Very high |
| Manual | None | No | Yes | Very low |
Practical rules for combining methods
A few practical rules apply to most IT environments. QR codes are the default entry point for a mixed fleet of endpoints and peripherals, barcodes fit where scanning infrastructure already exists, and RFID earns its cost when asset volume is large and audits are frequent. Manual tracking only works as a temporary baseline, and many teams end up combining methods by asset type.
Whatever the mix, each physical asset needs a consistent identifier that connects it to a system record. The QR code Inventory Management workflow shows how that connection operates day to day, and the IT asset tagging process defines the standards that keep identifiers consistent across the fleet.
How to run a physical IT asset audit with InvGate Asset Management
InvGate Asset Management runs the whole count inside the platform, from the inventory the audit checks against to the result recorded on each asset. The steps below follow one audit from preparation to close, with QR codes and RFID as the two scanning options.
1. Build one inventory to audit against

An audit can only find discrepancies against a complete list, so every asset needs a record first, whatever its entry path. Devices that run the InvGate Asset Management Agent report their hardware and software data automatically, network discovery captures devices without an agent, and integrations such as Microsoft Intune, Amazon Web Services (AWS) and Microsoft Azure bring in assets that live in other platforms.
Peripherals and anything without a network address are added manually, one by one or in bulk through a CSV import. Every asset ends up in the same inventory, which becomes the expected set the physical count is checked against.
2. Tag every asset with QR, RFID, or both

Each asset needs a physical tag whose code is stored on its record, and there are three ways to get there:
- QR labels printed in-house. QR codes can be generated from the asset explorer for one asset or a full batch and printed with the label layout the team needs.
- InvGate tags with QR and RFID on one label. Tags supplied through InvGate's printing partner carry a QR code and an RFID inlay, with on-metal formats for laptops and servers, and the RFID code is calculated from the QR, so a single scan binds both identifiers to the asset. Generating those tag batches directly from the platform is coming soon.
- Existing RFID tags. Standard UHF tags from another supplier also work, with the RFID number paired to each asset as a separate step.
Before any count starts, confirm that every asset in scope carries a readable tag and replace the damaged ones. Treating tag verification as its own step keeps the scan moving once it begins.
3. Create the audit and set its scope
Create a new audit from the Audits explorer in the Assets module and choose the location it covers, since each audit targets one location. The scope can be narrowed to assets with specific tags or to a pasted list of identifiers, such as asset IDs, inventory IDs, serial numbers or hostnames, and it stays fixed until someone runs Update scope, so changes elsewhere in the inventory do not shift the count mid-audit.
Scope decisions should stay consistent across cycles so results can be compared over time. A reasonable baseline for most environments is a full audit per location each quarter, with more frequent checks for high-value or frequently moved assets.
4. Scan the location with a phone or an RFID reader
Results reach the audit through three capture methods, and they can be mixed inside the same audit:
- QR codes from a phone. The auditor scans each tag with the phone camera, one asset at a time, with no extra hardware. It fits smaller rooms, mixed fleets and assets without an RFID inlay.
- RFID with a Zebra reader. The auditor holds the trigger and walks the room while the reader captures every tagged asset in range, without line of sight. It fits storage rooms, racks and any area dense enough that finding each label would take hours.
- Manual load from the desktop. A list of identifiers is pasted into the audit, which covers teams that count another way or receive a spreadsheet from a third party.
Progress shows as found assets against expected ones, results can be submitted in batches by floor or sector, and scanning an asset twice never duplicates it. Technicians can also update an asset's location, status and notes from the phone by scanning its QR code, and barcode scanning is coming soon as a fourth option.
5. Review the results before closing

While the audit is open, its summary shows Assets in scope, Found, Pending and Others. Expected assets that have not been scanned stay Pending, scanned assets that exist in the inventory but belong to another location or were left out by the filters appear as Extra, and scanned identifiers that match no record appear as Unknown.
Those results map to the problems this article has already covered: ghost assets end up Missing, unregistered assets show up as Unknown, and mislocated assets appear as Extra where they were found. Each one needs a different response, so the detail view keeps them in separate tabs.
6. Close the audit and correct the records
Closing the audit turns every Pending asset into Missing and writes the audit name, date, location and result on each expected asset, which gives every device a dated record of when it was last physically verified. Closing cannot be undone, so review the Others group first and flag Missing assets for investigation before removing anything, since a device may be in transit, checked out or stored off-site.
From there, corrections become bulk work: filter the asset explorer by audit result, send Extra results to the explorer to fix their location, and export the Unknown list to register those devices. Pasting a list of up to 500 identifiers also finds every matching asset in one search, which helps confirm a delivery at receiving or update the devices that came back from a checkout period.
7. Document the results and watch for drift between audits
Audit results export to CSV or XLSX, with total assets scanned, discrepancies by category and open items, and that report becomes the baseline for the next cycle and the evidence trail for compliance. The documentation standards in HAM audit preparation extend this step for formal compliance requirements, and a broader hardware audit adds discovery data, Health Rules and reporting on top of the physical count.
Between cycles, Smart Tags group assets by any criteria the team defines, and automation rules send alerts when an asset falls outside its expected pattern, such as a device assigned to a user who has left. The next audit then starts from a much smaller list of open questions, and the full feature set is covered in physical audits in InvGate Asset Management.
Coming soon: the QR Menu Portal
A QR Menu Portal will let anyone who scans a tagged asset reach a public page to report a found device or a problem, which can open a ticket in InvGate Service Management, and optionally see the asset's details. No InvGate Asset Management account will be required to use it.
Conclusion
A physical inventory of IT assets is what keeps the records behind every refresh plan, procurement decision and compliance report tied to what actually sits on the floor. QR codes give any team a zero-hardware starting point, RFID turns dense locations into a single walk, and a consistent audit cycle keeps the distance between the two numbers from growing again.
The audit itself is only as useful as the record it updates, which is why running it inside the same platform that holds the inventory matters. Start a 30-day free trial of InvGate Asset Management or talk to Sales to see how it fits your environment.