IT asset tracking for 5-50 person teams: the practical cheat sheet

If you are starting asset tracking from a shared spreadsheet (or worse: from Slack DMs and your memory), this is the practical cheat sheet for small and medium-sized businesses. The principles work whether you are tracking 5 laptops at a 10-person startup or 500 devices at a multi-site small and medium-sized business - only the rigour scales.

The goal: a working, accurate inventory in a week, and a system the team will actually keep up to date for the next three years. Most asset-tracking projects fail not on the tool, but on the second part.

What "asset" actually means

An "IT asset" is anything you would notice if it stopped working or walked out the door. For a 30-person team, that is roughly:

Hardware: laptops, monitors, desk phones, headsets, dongles.
Software licenses: Adobe seats, JetBrains, Microsoft 365 SKUs, niche tooling.
Accessories: branded cables, USB-C hubs, label printers (used by multiple people).
Consumables: USB sticks, batteries, printer toner (one-off uses).

The mistake we see most often: trying to track everything, including a tray of pens. Pick a threshold (we suggest €100 unit value or "must be checked out to a person") and stop below it.

Design your data model first

Before opening the new tool, agree on five things with the team:

Asset tag format. Stick to one. SO-00001 is fine. laptop-marketing-19 is not - it breaks the moment marketing moves to engineering.
Categories. Aim for 6-10. Laptop, Monitor, Headset, Mobile phone, Dock, License, Accessory, Consumable. Anything more granular becomes admin overhead.
Status labels. Four states cover 90% of teams: Available, In use, In repair, Retired. If you need Loaner pool or Imaging, add it - but stop at six.
Locations. Office floors, remote, warehouse. Keep this short - "John's home" is a custom field, not a location.
Custom fields per category. Laptops need RAM, storage, OS. Monitors need diagonal and resolution. Cables do not need custom fields.

The physical labeling step nobody plans for

Plan a one-afternoon "labeling day". Stick a QR-coded asset tag on every laptop, monitor, phone and shared accessory before you start tracking. We have not yet seen a team that successfully labels assets over weeks of "I'll do it when I see them" - the project dies in the partial state.

Practical specs that work:

Sticker: 38mm × 19mm direct thermal or laser-printable polypropylene. Survives wiping with cleaning alcohol.
QR payload: a URL that resolves to a public "lost and found" page on your tracker. SimpleAMS generates these by default at /assets/scan/{tag}.
Tag number, human-readable, below the QR. So you can read it without the phone.

Decide your checkout policy

"Checkout" means assigning an asset to a person. The two policies we see work:

Open checkout: staff can check assets out to themselves from the kit room. Works for small teams with high trust. Requires an EULA acceptance step.
Mediated checkout: IT checks the asset out on behalf of the user. Works for larger or compliance-sensitive teams.

Either way, attach an acceptance step (the EULA / acceptable-use snippet) to the checkout. Most asset trackers including SimpleAMS support this - the asset cannot move out without the user accepting.

Audits: schedule them or skip them

Audits are the only way an inventory stays accurate. The two viable cadences:

Quarterly full audit: walk the floor, scan every asset. Two hours for 100 laptops.
Continuous random audit: the tracker prompts users to confirm "you still have laptop SO-00042" once a quarter via email. Less complete but no IT time.

If you do neither, your data drifts by ~10% per quarter from reality. After a year, every report needs a manual cross-check, which is when teams quietly stop using the tool.

Software licenses are easier than hardware

Licenses are forgotten until renewal day; that is the bug. To fix it:

Track seats, not just the licence. A 10-seat Adobe Creative Cloud licence with eight assignments has two free seats - your inventory should know that.
Renewal date in the system, with a 30-day-out reminder.
Assign seats to users or assets. JetBrains licences are usually per-user; Microsoft Office on a shared laptop is per-asset.

The reports that matter

Skip vanity dashboards. The reports that get used:

"What does this person have?" Used on every offboarding.
"What is overdue from this user?" The collections list.
"Devices older than four years." Refresh-cycle planning.
"Licences expiring in 60 days." Procurement.
"Total estimated value of IT assets." One number; goes in the year-end report.

If your tracker cannot answer those five questions in two clicks, it is the wrong tracker.

Common pitfalls

Over-modelling the data. 35 custom fields per laptop is a forecast of how few will be filled in. Start with 3-5 mandatory fields. Add more only when you actually need them in a report.

Letting the tracker drift from reality. If the system says a laptop is with Jane and Jane returned it three months ago, you will stop trusting anything the system says. Fix one drift fast or fix the process that caused it.

Buying software for "future scale". 30-person teams do not need an ITSM suite with a 12-week implementation. Buy the simpler tool now; outgrow it in three years; migrate then. CSV exports make that cheap.

Where to go from here

If you already have a CSV from a previous tool, follow our CSV migration guide. If you are starting from a spreadsheet, just upload it - SimpleAMS accepts a generic CSV with the same column conventions.

Or skip the setup and sign up risk-free - 14-day money-back guarantee on all paid plans, so you can validate the fit before you commit.