How to Run a Device Inventory Audit Across a School District

When it's time to audit your district's devices, the question is pretty simple: can you account for every device the district owns?

That question matters more than you might expect. The New York State Comptroller audited 20 school districts and found that 17 couldn't locate every IT asset selected for testing. Auditors couldn't find more than 100 sampled assets, including 81 Chromebooks, and about 4,800 inventory records had no location or assigned employee.

The same issues are showing up in recent audits. In 2025, Roslyn had at least 400 active devices without a serial or tag number. In October 2026, Palmyra-Macedon was cited for records missing serial numbers, locations, assigned users, purchase information, and disposal dates.

The auditors' recommendation was straightforward: keep complete records and conduct a full physical inventory every year. CIS Control 1 also recommends reviewing and updating asset inventories at least twice a year.

You can start with the information your district already has. Bring together the records you use today, look for anything that doesn't match, and use current device information to decide which devices need a closer check.

1. Start With the Records Your District Already Has

Before anyone walks through classrooms or storage rooms checking devices, bring your inventory system and purchase records together. Add any repair or loaner pool lists that individual schools keep, too. You'll be looking for mismatched records so you know where to focus the physical check.

The Comptroller's checklist is a useful starting point: make, model, serial number, assignee, physical location, and purchase details. Its statewide audit found about 4,400 records with missing or duplicate serial numbers, so that's one field worth checking early.

Device records need to stay current as equipment moves around. NIST's Cybersecurity Framework 2.0 also says inventories should be updated when devices move or change hands, so check that each record still reflects the device's current assignment and location.

Start with the issues that are easiest to spot: devices listed in purchase records but nowhere else, duplicate serial numbers, and records with no assignee. Keep in mind that if a device was never added to the district's management system, it may also be missing from Senturo.

This is where Senturo can help bring device information together. If your district connects Microsoft Intune, Jamf Pro, Google Admin Console, or Cisco Meraki, our MDM integrations import managed devices and keep their information in sync. Incident IQ works differently: it maintains its own asset records and adds Senturo action links to them. That integration syncs nightly, so new assets receive those links during the next sync.

‍2. Use the Dashboard to Find the Records That Need Attention

Once your main lists are reasonably close, use our dashboard to see which devices deserve attention first.

Use Assignment Status to see which devices are assigned or unassigned, and Management Status to see which are managed or unmanaged. Label Status tells you whether a device has a label, while Fleet Info breaks the fleet down by platform, make, model, and operating system.

Compare those dashboard totals with your purchase records. If the numbers for a model or platform don't match, you've got a specific set of records to investigate instead of going through every device one by one.

Security Status is another place to look. Senturo's At-risk count includes devices that haven't been activated, are marked Missing, or haven't connected to our servers in the past seven days. A device could still be in storage or out for repair, so check with the school before changing its record.

If your district already organizes devices by school or program, work through one group at a time. It's easier to get a clear answer from each school when the follow-up list is manageable.

3. Match the Record to the Right Device

When records don't match, start with the serial number. A regular search on the Devices page checks the device name, serial number, and asset ID. If you want to search specifically by serial number, use the serial: search keyword to narrow it down.

Once you've found the device, check its Users tab and compare the login history with the assignee. The last logged-in user shows the account that most recently signed in, which may differ from the assignee when a device is shared or loaned out.

Login history can give you a clue about who used a device, but it can't confirm who has it right now. If the last user and the assignee don't match, check with the school before updating the record.

‍

‍

4. Use Location and Network History to Decide Where to Ask Next

Once you've confirmed the right device record, location and network information can help you decide where to follow up next.

For example, this search finds devices in the Lincoln Elementary group that last reported the Jefferson-Staff Wi-Fi network:

group:"Lincoln Elementary" wifi:"Jefferson-Staff"

Both search terms need to match. Put a colon directly after each search keyword, with no space, and use quotation marks around values containing spaces.

A Wi-Fi name can point you toward the right place to ask, but it can't tell you where a device is today. Treat location history the same way and always check the timestamp before relying on an older record.

You can also download a device's location history from its record in Senturo. Our current retention policy keeps location records for 180 days by default, and custom plans are available. When a device goes offline, it stops sending new locations, so you'll see its last-known information until it reconnects.

‍

‍

5. Save the Answer While You Have It

Once a school confirms what's going on with a device, add a short note to its record while the details are fresh. Include where it is or why it isn't available, along with who confirmed that information.

Those notes are easy to find again. Use the note: search keyword, for example, note:repair to find devices with that word in their notes.

If a device has changed hands, update the system your district uses as its official record. When that system is one of our supported MDM integrations, those changes continue syncing into Senturo.

6. Finish With the Devices That Still Need a Physical Check

By now, you should have a more focused list for the physical check. Look at purchased devices that never appeared in the management system, devices that have been offline for a long time, and records where the assignee or location still hasn't been confirmed.

The New York State Comptroller recommends conducting a complete physical inventory every year and comparing what you find with the district's records. CIS Control 1 also recommends reviewing and updating the asset inventory at least twice a year. Your district may have its own scheduling requirements, so make sure you're checking the records against the devices themselves.

If a tracked device is confirmed missing and it's online, Missing Mode gives you its live location. If it's offline, use its last-known information and continue following up with the school.

‍

‍

Frequently Asked Questions

Which device management tools work alongside Senturo?

Senturo works alongside Microsoft Intune, Jamf Pro, Google Admin Console, Cisco Meraki, and Incident IQ. The MDM integrations import managed devices into Senturo. Incident IQ keeps its own asset records, with Senturo action links available on those asset pages.

Do Incident IQ users need a Senturo account?

No. An administrator can grant someone access using their email address and choose which Senturo actions that person can use from Incident IQ.

Can we update many device records at once?

Yes. Our CSV Data Import matches devices by serial number or UUID and lets you update device names, tags, notes, groups, and assignee information. It can add or update values, but existing tags and notes need to be cleared directly in the Senturo interface.

What happens if a device is offline during an audit?

An offline device can't send a new location, but you can still refer to its last-known information and location history. Check again once it reconnects.

Can we audit a mixed-device fleet?

Yes. Senturo supports Windows, macOS, ChromeOS, iOS/iPadOS, and Android, although available device information and actions may vary by platform.