IT Asset Audits: Matching Physical Units to Records

Almost every organisation has a device asset list. Far rarer is an asset list that genuinely matches reality on the ground. That gap usually stays invisible until something forces it into view: the end of a rental contract, an external audit, or a loss incident.

This article covers how to run an audit that does not consume days, and how to keep the result accurate afterwards.

Why Records Always Drift

Devices change hands unrecorded. Employees move departments and take their unit, or hand it directly to a colleague without involving IT.

Replacement units arrive when something breaks, but the new serial number is not always updated in records. After several replacements, list and reality diverge considerably.

Employees leave without a completed return process. This is the most commonly found source of discrepancy, and the hardest to correct because the unit is already untraceable.

Devices are set aside as spares and then forgotten in a cupboard.

Preparing Before You Start

Decide first what counts as one asset unit. For laptop fleets, the serial number is the most reliable identifier because it does not change and cannot be confused.

Prepare a reference list from the source most likely to be correct. For rented units, the provider's handover record is usually more accurate than internal records that have been edited several times.

Define the audit scope. Auditing an entire fleet at once for the first time often fails because it is too large. Splitting by floor, department or location is far more likely to finish.

Running the Match

Record three things for every unit found: serial number, who holds it, and where it is. Add a brief note on physical condition where possible, since that becomes useful approaching contract end.

For large fleets, scannable labels speed the process considerably compared to typing serial numbers individually. For rented units, confirm permitted label types in advance so they do not generate cosmetic charges at return.

Match in both directions. Beyond checking whether every listed unit was found, check whether any unit found is absent from the list. This second direction is often skipped and frequently turns up something interesting.

Handling Discrepancies

Group discrepancies by type before acting.

Listed but not found. Trace the last recorded holder before concluding it is lost. Most cases end with the unit found on someone else's desk or in a storage cupboard.

Found but not listed. Usually a replacement unit that was never recorded. Add it to the list with a note on its origin.

Serial number does not match the recorded holder. Update the record and, if the pattern repeats, fix the internal handover process.

For rented units genuinely not found, report to the provider through the incident flow. The steps sit in our damaged or lost units article.

Keeping Records Accurate

An annual audit without process change simply produces the same discrepancy next year. What preserves accuracy is recording at the moment of transfer rather than periodic checking.

Fold recording into processes that already exist. Unit transfers are recorded at internal handover, and unit return becomes part of the employee exit process. The handover format sits in our rental handover article.

For rented fleets, schedule a light audit several months before the contract ends. That leaves time to trace untracked units well before collection day.

Arental clients can start this reconciliation from the client portal: every device's unit, contract, handover document and rental status is tracked in the IT asset management dashboard, so discrepancies surface sooner.

Choosing an Asset Identity That Does Not Change

Audits fail most often not because units cannot be found but because there is no way to confirm the unit found is the unit recorded.

The serial number is the only identity attached to hardware that persists across its service life. Brand and model are insufficient when ten identical units sit on the same floor.

A user name is not an asset identity. Users change, move departments and leave while their unit stays. Recording assets by user means losing the trail at every transfer.

Internal inventory numbers can serve as an additional layer, but must always link back to the serial number. For rented units, the serial number is what the provider uses, and ultimately that governs reconciliation.

For rented fleets, ensure any tagging leaves no adhesive residue. Confirm permitted label types before attaching anything to a unit.

Running an Audit Without Disrupting Work

An audit requiring users to surrender their devices will be quietly resisted and the result will be incomplete. Several approaches keep it frictionless.

Inspect at the user's desk rather than collecting units. All that is needed is reading a serial number, and that takes seconds.

Use moments that already exist: user changes, unit replacements, or periodic device checks. Attaching the audit to an existing process makes completion far more likely.

Split the audit by floor or department and finish one group before moving on. Auditing an entire office in one day almost always stalls halfway.

For users who are away, record them as not yet checked and reschedule rather than assuming presence.

Following Up Discrepancies in the Right Order

Finding a discrepancy is half the work. What determines its value is the follow-up.

For units not found, trace backwards from the last recorded holder before concluding they are lost. Most end with the unit discovered in a cupboard, on someone else's desk, or in a store room.

For units found but unrecorded, add them to the list with a note on their origin. These are usually replacement units that arrived after a failure and were never recorded.

For rented units genuinely missing, report to the provider through the incident flow rather than waiting for contract end. The steps sit in our damaged or lost units article.

Once discrepancies are handled, fix the process that caused them. An audit finding identical discrepancies next year means follow-up stopped at recording.

Frequently Asked Questions

How often should audits run?

For stable fleets, once a year is generally sufficient, plus a light audit approaching contract end. For organisations with high staff turnover, more frequent is better.

Is specialist software needed?

For small fleets, one disciplined summary file is adequate. Software benefits become apparent as unit counts and locations grow.

How do you audit units held by remote staff?

Request a photo of the serial number label along with location confirmation. It is less accurate than direct inspection but far better than relying on old records.

In Short

A useful audit is not the most exhaustive one but the one that actually finishes and gets acted upon. Start with a single department, fix the recording process, then expand.

References & Sources

CIS Control 1: Inventory and Control of Enterprise Assets (accessed 24 September 2026) places an accurate, continuously updated asset inventory as the first security control. For a device inventory that updates automatically from a management system, see the Microsoft Intune overview (accessed 24 September 2026).