Most small IT teams know roughly where everything is - right up until they have to prove it. The auditor wants a hardware list with owners, finance wants to know why eleven laptops were bought when headcount grew by six, and a leaver’s “I returned everything” cannot be checked against anything. The gap is rarely knowledge; it is records. This guide covers how IT departments of one to five people track hardware properly without buying an enterprise ITAM suite: what to register, where devices actually go missing, and the checkout habits that make audits boring.
What you will learn
- Where small IT teams lose hardware
- What to put on the register
- You probably do not need a CMDB
- Run the loaner pool like a library
- Offboarding is where laptops disappear
- Getting started without a project plan
- FAQ
Where small IT teams lose hardware
IT hardware rarely vanishes dramatically. It drifts:
- The drawer of unknowns. Returned devices pile up unwiped and unrecorded - is that laptop spare, broken, or someone’s? Nobody knows, so it is none of them.
- Leavers and their satellites. The laptop usually comes back; the second monitor at home, the spare charger, and the dock often do not, because nobody had a list of the satellites.
- Loaners that never return. A device lent “for the trip” becomes a second machine by default, and the pool shrinks one favour at a time.
- Monitors walk. Desk moves and hybrid seating mean monitors and peripherals migrate between desks faster than any record kept by hand.
- “Temporary” is permanent. The test phone, the trade-show tablet, the machine lent to the contractor - anything issued outside the normal process is invisible to the normal process.
All five are assignment changes that never reached a record - which is why the record has to live in the handover itself.
What to put on the register
Per-device records, with serials, for everything that holds data or real value:
- Laptops and desktop computers - the core. Serial, owner, status, purchase date and price, warranty end.
- Smartphones and tablets - including the test devices and the eSIM spares, which are precisely the units that go missing.
- Monitors - cheap individually, expensive in aggregate, and the most mobile thing in the office.
- Docks, headsets, webcams - decide deliberately: track per item where value justifies it, or issue them as part of a desk kit and track the kit. Either works; “neither” is how peripheral spend doubles.
- Networking and server kit - low churn, but exactly what the auditor asks about.
- Software licences and seats - a register entry per agreement with renewal dates, the lightweight end of software asset management; cables and adapters stay consumable stock.
Warranty dates earn their place on day one: a filterable “what is still under warranty” view turns repair decisions into lookups, and a “warranty expiring” list feeds next year’s refresh budget. The fuller field-by-field treatment is in the IT asset inventory checklist.
Tip: put the QR label on the underside of laptops next to the manufacturer’s serial plate, and on the rear top-left corner of monitors - consistent placement means anyone can find the label without flipping equipment hunting for it.
You probably do not need a CMDB
Enterprise tooling conversations leap quickly to a CMDB - configuration items, dependency maps, service relationships. That machinery exists to answer “what breaks if this server goes down”, and at enterprise scale it earns its complexity. A five-person IT team’s actual questions are different:
| Question | Needs |
|---|---|
| Who has this laptop? | Asset register with assignment |
| What did we buy, when, and is it under warranty? | Purchase and warranty fields |
| What does the leaver have? | Per-person holdings view |
| Can we prove all this to an auditor? | History on every record |
| What breaks if VM-PROD-3 dies? | A CMDB - and a team large enough to maintain one |
Plain ITAM - a register, assignments, lifecycle states, history - answers the first four, and the first four are where small teams bleed money and audit hours. Choose the tool for the questions you actually have.
Run the loaner pool like a library
Loaners are the highest-churn devices in the fleet and the easiest win. Each loaner gets a label and a record; every loan is a checkout to a named person with a due date; every return is checked in with a quick condition look before the re-image. Management overhead is then a weekly glance at the overdue list and a standard nudge - no memory, no detective work. A user can also scan the label to report a fault against exactly the right device instead of “the silver one”.
Offboarding is where laptops disappear
The leaver’s last week is the single most concentrated loss event in IT. The countermeasure is a per-person holdings view: one screen listing everything assigned to the leaver - laptop, monitors, phone, dock, badge - which becomes the collection checklist HR and IT work through. Devices are checked back in as they arrive, condition noted; gear the replacement needs transfers directly with its history intact; the rest goes to storage as a recorded state, not a drawer. The end of the line should be deliberate too: wiped, sold, recycled, or donated is an IT asset disposition decision worth recording per device, since data-bearing kit needs a defensible trail. The full sequence is covered in employee offboarding and hardware recovery.
Getting started without a project plan
- Export what you have. Procurement emails, MDM lists, the old spreadsheet - merge into one starting list with serials.
- Walk the office once. Reconcile the list against physical reality, labelling devices as you go. Expect both ghosts and orphans.
- Record current assignments. Every device gets an owner or a location today - “storage” is an owner; “unknown” is a ticket.
- Switch on the habit. From now on, every issue, return, swap, and loan happens as a checkout or check-in, at the moment of handover.
- Calendar two reviews. Weekly overdue-loaners glance; quarterly reconcile of new starters, leavers, and the storage shelf.
On tooling, AMPthilly covers this scope without the enterprise suite: an asset register with serials, purchase and warranty fields and custom fields per type, CSV import to load the existing spreadsheet, printable QR labels scanned by any phone camera in the browser, checkouts with due dates, per-person holdings views, and a full audit history on every device. The free plan - 3 users, 25 assets, no card required, with SSO and MFA included - is enough to pilot the loaner pool; see pricing for fleet-sized tiers.
FAQ
How should a small IT team track laptops and hardware? One register, serials and warranty dates on every record, and every issue or return logged as a checkout at the moment of handover.
What is the difference between an asset register and a CMDB? A register answers who-has-what and lifecycle; a CMDB maps service dependencies. Small teams usually need the former.
How do you run a loaner laptop pool? Like a library: labelled devices, named checkouts with due dates, a weekly overdue glance, and check-ins before re-imaging.
How do you stop losing equipment when employees leave? A per-person holdings view becomes the collection checklist - the register remembers the second monitor so nobody has to.
Do QR asset tags work for IT equipment? Yes - consistent label placement plus a phone-camera scan identifies any device and ties fault reports to the right record.
The takeaway
Small IT teams do not need dependency maps; they need the boring questions answered instantly - who has it, what did it cost, when does the warranty end, what does the leaver still hold. A register with labels, named checkouts, and history answers all of them, makes audits a filter-and-export job, and turns offboarding from a loss event into a checklist. Start with the loaner pool, build the habit, and let the register grow outward from there.