Asset verification is the process of physically confirming that assets on the register exist, are where records say they are, and are in usable condition.
Asset verification is the process of physically confirming that the assets on your register exist, are where the records say they are, are held by the person the records name, and are in usable condition. It is the ground-truth check behind every claim a register makes - the difference between “the system says we have forty laptops” and “we have forty laptops”. Regular verification is what makes a fixed asset audit uneventful and is the working core of audit readiness.
What verification checks
For each asset in scope, verification answers five questions:
- Existence - is there a real item behind this record?
- Identity - is it the same item, confirmed by tag ID and serial number, not just the same model?
- Location - is it where the register says?
- Custody - does the person recorded as holding it actually have it?
- Condition - is it usable, or quietly broken in a cupboard?
The identity check is the one most often skipped and most often regretted. Two identical printers are interchangeable until one is under warranty and the other is not.
A verification procedure that works
Pull the register list for the scope - a site, a department, a category. Go to each item, scan or read its tag, and confirm serial, location, custodian, and condition against the record. Log every exception as found: missing, moved, reassigned, damaged, or present-but-untagged. For remote staff, verification can be a photo of the device with its tag and serial visible, requested and filed against the record. Finish with a signed summary - who verified what, when, and what was found - and pass the exceptions on for investigation rather than fixing records mid-walk.
For fixed infrastructure such as racked servers and networking equipment, verification is less about whether the item moved and more about whether it is still the device the record describes - hardware gets swapped during incidents far more often than registers get updated.
How often to verify
Annual full verification is the usual floor, with risk deciding what gets checked more often: items that are portable, valuable, or frequently reassigned deserve a quarterly or rolling rotation. Event-driven verification catches the rest - at offboarding, after an office move, after a burglary, and before audits. Information security frameworks push in the same direction: ISO 27001 expects an accurate, maintained inventory of assets, and verification is how that inventory stays defensible rather than aspirational. Having someone other than the register’s owner perform the checks keeps the exercise honest - a small but real piece of internal controls.
Verification vs counting vs reconciliation
The three are easy to blur. A physical inventory count starts from the floor and asks “what is here?”. Verification starts from the register and asks “does each record have a real, correctly-described item behind it?”. Reconciliation takes the differences either exercise finds and resolves them in the records. In a small estate they collapse into one walk-through; in a large one they are distinct steps with different owners.
Verification in practice
The slow, error-prone part is matching items to records, which is why tagging pays for itself at verification time. With AMPthilly, scanning the QR label on an asset with a normal phone camera opens its profile in the browser, so the verifier can confirm owner, status, and serial against the physical item on the spot - no app install, no typing IDs into a spreadsheet.
Related terms
- Fixed Asset Audit - the formal review verification prepares you for
- Audit Readiness - keeping records inspection-ready all year
- Internal Controls - the separations that keep verification independent
- Segregation of Duties - why the record-keeper should not verify their own records
- ISO 27001 Asset Management - the infosec standard that expects a maintained asset inventory