Reviewing audit support for an asset register

Review audit support by checking whether staff can compare recorded assets with a physical count, retain discrepancies and show how they were resolved. A last-audit date alone does not show what was counted or found.

Define the count

Choose one location or stockroom and preserve the expected list used for the check. Record its scope, date, counter and the identifier used to match each item. Decide how to handle an expected item that is missing, an item found in the wrong place and an item with no register record.

ServiceNow Hardware Asset Management documents scheduled audits and blind audits of stockrooms or other locations. Its process scans an asset tag, serial number or model barcode and reconciles the observation with records.

In the documented release, scheduled audits can be created in the Hardware Asset Management application and blind or unscheduled audits in the ServiceNow Agent app. Ask to see the workflow in the release and subscription proposed to your business.

Follow an exception to closure

Keep the observation separate from a later correction; otherwise another reviewer cannot tell what the count found. Decide under your own policy when a second count or supervisor review is needed.

Sortly documents activity and move reports. Its Inventory Summary shows the current state; a past point-in-time view uses the separate Inventory Snapshot feature. Some advanced reporting features, such as Custom Reports and Report Subscriptions, are available only on its Ultra, Premium and Enterprise plans. Check whether the proposed account offers a count workflow and retains the evidence your review needs.

Snipe-IT documents asset checkin and checkout. Its asset-import instructions also state that importing a “Last Audit Date” updates the date without creating an audit event, notification or log. A populated date therefore cannot, by itself, establish that a physical check occurred.

Audit Support Features Across Asset Management Tools

Audit Reporting Availability by Plan (Sortly)

Request a reviewable result

For a demonstration, have one staff member perform a fictional count and another review it. The reviewer should be able to see the expected items, observed items, exceptions, corrections, responsible people and dates.

Ask for an export that retains enough context to investigate discrepancies. If the product only produces a current list, keep a controlled count sheet and exception log alongside it.

A scan is an observation within a stated scope. A register supports a physical audit when it helps staff explain differences and repeat the count; the business still needs a counting process and someone to resolve exceptions.