IT Asset Audit Checklist: Count, Reconcile, And Sign Off

An IT asset audit is a scheduled count that checks your inventory record against what is really on desks, carts, and shelves. You set a scope and a cutoff, count one location at a time, sort every difference, fix the record, and sign off. The checklist below runs it.

We build SherpaDesk, a helpdesk and PSA (professional services automation) a small IT team can run alone. No contract. No implementation project. No dedicated admin.

What Is An IT Asset Audit?

• The inventory is the record itself. Asset audits test that record on one date.
• A fixed asset audit is the finance check of capitalized items and their depreciation. The IT count can feed it.
• A compliance "IT audit" (SOC 2, HIPAA, ISO 27001) reviews controls and policies. This page doesn't cover it.

Why An Asset Audit Matters On A Small Team

Two public asset audits show what happens when the count is missing or leaves devices out.

• IRS, 2026. Of more than 32,000 assets assigned to about 22,000 employees who left from April through July 2025, 1,308 (4 percent) showed as not returned in November 2025. After a recommended reconciliation, IRS officials said 714 had been located by April 2026; 594 worth more than $270,000 were not.
• Montgomery County Public Schools, 2025. The inspector general checked nine schools and found Chromebook records "were often not accurate and numerous devices could not be located." A count was required only at year end, and assigned Chromebooks were left out.

For equipment bought under a federal award, "the results must be reconciled with the property records at least once every two years." Equipment means tangible property with a useful life of over a year and a per-unit cost at or above your capitalization level or $10,000, whichever is lower.

The Asset Audit Checklist

Use one copy per audit; each section is explained step by step below.

IT ASSET AUDIT CHECKLIST

1. SCOPE AND CUTOFF
[ ] Name the scope: account or department, sites, rooms, device types
[ ] List what is out of scope and why
[ ] Set the cutoff date and time and the count window
[ ] Name the audit owner and who signs off

2. PREPARE (the week before)
[ ] Post every pending move, handout, return, and repair to the record
[ ] Merge only confirmed duplicates of one device, keeping history; flag
    doubtful pairs for review
[ ] Export the expected list per location: ID, serial, type, user, status
[ ] Announce the freeze: no moves or handouts from the cutoff until the
    count ends; log any move that can't wait (time, device ID, from, to)
[ ] Assign an independent counter where you can; if you count devices you
    issued or recorded, plan a second-person spot check now
[ ] Send remote users their device list to confirm or deny

3. COUNT, ONE LOCATION AT A TIME
[ ] Read the tag ID and serial from the device, not from the list
[ ] Note the user, the room, and the condition of each device
[ ] Count spares, carts, loaners, closets, and the repair shelf
[ ] Write down the serial of every device with no tag or no matching record

4. RECONCILE
[ ] Match finds across locations before calling anything not found
[ ] Search records by serial before calling a device unrecorded
[ ] Give each device one outcome, first match wins: back from Missing,
    retired still on site, belongs elsewhere, moved, matched; then
    unrecorded and not found
[ ] Flag damage separately; when a higher outcome wins, log the user or
    room change as an extra change
[ ] Give every difference an owner and a due date

5. RESOLVE
[ ] Search for each not-found device: tickets, handouts, last-seen date
[ ] Mark a device Missing only after the search deadline
[ ] Add a record for an unrecorded device only once the owner is confirmed
[ ] Send retired devices still on site to your disposal process

6. UPDATE AND SIGN OFF
[ ] Update the records and note the audit date on each change
[ ] Write the summary: expected, counted, each outcome, damage flags
[ ] Have a second person spot-check a sample of matched devices
[ ] Owner signs and dates; set the next audit date

How To Run An Asset Audit, Step By Step

Say you audit Cedar Law, an MSP client's Main Street office with 58 active devices in scope.

1. Set the scope and the cutoff

   Name the account, rooms, and device types, and what is out and why. The record freezes at the cutoff until the last location is counted: nothing moves in or out while the count runs.

   Example: untagged monitors are out. Cutoff Thursday, Oct 8, 2026, 6 p.m.; count Friday, Oct 9.

   Common mistake: auditing several clients in one pass. Keep one account per asset audit.

2. Prepare the expected list and the freeze

   Post pending moves and repairs. Merge two records only when they're confirmed as one device, keeping both histories; a doubtful pair goes on a review list. Our IT asset inventory guide covers the merge. New arrivals wait uncounted. A move that can't wait goes in an exceptions log with the time, device ID, from, and to.

   Counters shouldn't keep the records; a team of one books the second-person spot check now.

   Example: dock CL-0142 has two records with the same serial, model, and purchase invoice; merging them turns 59 active records into 58 devices.

3. Count one location at a time

   Read the tag ID and serial from the device, not the list; note user, room, and condition. Count spares, carts, closets, and the repair shelf. A device with no tag or matching record goes on the sheet with its serial; our asset tagging guide covers re-tagging.

   Why spares count: some are kept off the record on purpose. One r/k12sysadmin member says of their test spares: "These are kinda off the books, so I have them, but they're not included in official counts." Count them anyway.

4. Reconcile the count with the record

   Compare each location with its list, then match extra devices across locations: Floor 1's missing laptop may be Floor 2's unknown one. Then give each device one outcome from the table below.

5. Resolve every difference by its deadline

   Handle not-found devices with your routine rule (see the inventory guide in step 2), starting from tickets and the last-seen date in your RMM (remote monitoring and management) tool. A federal equipment loss "must be investigated." Retired devices on site go to disposal.

   Common mistake: marking devices Missing on count day. At Cedar Law, two of three turned up.

6. Update the record and sign off

   Apply each change with the audit date as its reason. Write the sign-off, run the spot check, sign, and set the next date.

What To Do With Each Difference

Each device or expected record gets one outcome, so the totals close. If a device fits two rows, the first wins; log other changes, such as a new user, in the change list.

Damage is a flag, not an outcome: open a repair ticket. Duplicate records are merged before the baseline once confirmed (step 2); a doubtful pair stays on the review list.

A Filled-In Audit Sign-Off

The asset audit sign-off is one page. Here is Cedar Law's.

Matched, moved, and not found make the 58 expected; matched, moved, unrecorded, belongs elsewhere, and retired make the 59 counted.

The spot check. The Green Book separates "handling any related assets" from recording them, and where "limited personnel" prevent that, it calls for alternative controls. We use a second-person spot check as that control.

How Often To Run Asset Audits

The table is our starting recommendation. NIST lets you set how often the inventory record is reviewed; that records check is separate from the signed physical count.

Summer Chromebook collection doesn't replace the asset audit. For remote laptops, one r/ITManagers member says: "Annually users get a form to acknowledge or deny all associated assets."

About the author

Patrick Clements Co-founder & CEO, SherpaDesk

Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.

All Articles