New to this? You're in the right place. This post doesn't assume you know what a "fleet" is, or what IT does when they say they're "running an audit" on company laptops. If a word needs explaining, it's explained right where it shows up.
The problem this kind of software solves
Picture a company with thirty laptops. Some are with people who started last year, some with people who left last month and never gave theirs back. One is still running an old version of its operating system. Nobody has a single up-to-date list of which laptop belongs to whom, which ones are actually being used, and which ones need attention.
A "device audit" is just a regular, organized check of that list — is each laptop accounted for, is it in reasonably good shape, does it still belong to someone who works there. Doing this by memory or a stale spreadsheet is how a laptop quietly disappears for a year before anyone notices.
The three words you'll see everywhere
- A fleet is simply the whole collection of company devices — every laptop, however many there are. Not a boat term here, just "all of them, as a group."
- A queue is a list. Nothing more complicated than that — think of it as a named to-do list, like "Devices" or "Things to look into."
- A finding is one specific thing the audit noticed — "this laptop hasn't checked in for a while" or "this one's still on an old operating system." One finding, one entry, one thing to look at.
That's most of the vocabulary already. Everything else below is a variation on those three ideas.
What an audit actually looks at — and what it doesn't
Here's the part worth being direct about, because "audit" can sound like surveillance: a device audit looks at the machine, not the person using it. It checks things like: is this laptop still checking in, what operating system version is it running, is it assigned to someone who still works here. It does not look at browsing history, files, messages, or anything about what someone actually does on the computer day to day.
Think of it like a car's regular safety inspection. The inspector checks the brakes and the tires — not what music you play on your drive, not where you've been. Same idea here: the audit is about the hardware and its basic status, nothing else.
What actually happens when something looks off
A routine check runs — daily or weekly, whichever the team has set up. If everything looks normal, nothing happens; the laptop just gets confirmed as fine. If something looks off — say, a laptop hasn't checked in for a long stretch — that becomes a finding: one tracked entry saying what's wrong, so it doesn't just get forgotten.
From there, a person on the IT team works through it using a playbook — a short checklist for that specific kind of problem, so the steps are the same every time instead of being reinvented from memory. Nothing here reaches out and fixes the laptop by itself. A human decides what to do; the checklist just makes sure the right questions get asked in the right order.
What you'd actually see, in a project
If you opened a project built from an "IT Device Audit" starting template, you'd find three separate lists (queues), each doing one job:
| What you'd see | What it's for, in plain words |
|---|---|
| A device list | One entry per laptop — who it's assigned to, what it's running, when it last checked in |
| A findings list | One entry per thing the audit noticed that needs a look |
| An audit-runs list | One entry per check that ran — daily or weekly — so there's a record that the check actually happened |
Two screens (called dashboards) show the big picture at a glance: overall device health, and how the audit work itself is going — what's still open, what's been resolved.
What this isn't (yet)
An honest note, because overselling doesn't help anyone: this template doesn't come with a live connection to your actual laptops built in. Out of the box, it's the lists, the checklists, and the screens described above, filled with clearly-labeled example data so you can see the shape of it. Connecting it to real devices — so it can see actual laptops instead of examples — is a separate step someone on IT does deliberately, not something that happens automatically the moment you import it.
Ready for the deeper version?
Everything above describes the shape of the IT Device Audit template built into OpenTechnologyApp. If you want the real technical detail — the exact automations, every field, what the dashboards actually show — the full version is here: IT Device Audit: A Fleet Audit System as a One-Click Project Template.
If this was your first time reading about device audits, you now know enough to follow that post — and enough to tell whether this kind of tool would actually help your team.