Most of the hardware an MSP answers for sits in somebody else’s building. Client firewalls live in client comms cupboards, managed laptops live in employees’ homes, and the loaner pool leaves your office at exactly the wrong moments. This guide covers how small MSP and IT provider teams keep client hardware, loaners, and bench spares under control - without making the tracking a second job.
What you will learn
- Why client hardware drifts out of sight
- What an MSP should track
- One register, many clients
- Loaners, spares, and the bench
- Getting started without a discovery project
- FAQ
Why client hardware drifts out of sight
In-house IT teams lose track of equipment; MSPs lose track faster, for structural reasons:
- Distance. Most client sites see you monthly or quarterly; between visits, hardware is moved and reshuffled by people who do not report to you.
- Tickets record work, not custody. The PSA proves you replaced a switch in March - not where the old switch went, or who still holds the loaner from that night’s outage.
- Emergencies skip process. The laptop that went out at 7pm during an incident is documented, if at all, in a chat thread that scrolls away by Friday.
- The bench drains silently. Spares get consumed mid-job, and nobody owns noticing the empty shelf.
- Clients buy their own kit. Devices you never procured appear on the network - classic shadow IT - and you are expected to support them anyway.
The pattern repeats: custody changes hands, and the change never reaches a record.
What an MSP should track
Track per item anything you would have to answer for in a renewal conversation or a dispute:
- Client core infrastructure - servers, firewalls, switches, and access points (networking equipment), plus managed printers. These carry serials, warranty end dates, and configuration documents.
- Managed end-user kit - laptops, monitors, docking stations, and headsets at clients where you own the device lifecycle.
- Your loaner pool - the laptops and spare phones that leave during incidents. Highest churn, weakest paper trail, and entirely your money.
- Bench spares - drives, memory, PSUs, cables. Track these as stock with reorder points, not per item; a register of individually numbered SATA cables is a register nobody updates.
| Asset group | Who owns it | Assign it to | What matters on the record |
|---|---|---|---|
| Client infrastructure | The client | The client site | Serial, warranty end, config documents |
| Managed end-user devices | The client | The employee using it | Current user, condition, refresh date |
| Loaner pool | You | The borrower, with a due date | Return date and condition photos |
| Bench spares | You | A stock location | Quantity left and the reorder point |
One register, many clients
A spreadsheet per client feels tidy and fails quietly - each file goes stale at its own rate. One register with hard separation works better:
- Every asset carries its client and site, so a single filter answers “everything at this client” for a renewal or an audit.
- Your property never shares an ambiguous shelf with client property. A loaner stays flagged as yours even while it sits at a client for a month.
- Warranty conversations become an export: filter a client’s fleet by warranty end date and next quarter’s refresh proposal writes most of itself. (An IT asset inventory checklist settles which fields to keep.)
- When a contract ends, the list of assets assigned to that client is the handover document. When one of their employees leaves, hardware recovery starts from the register rather than from anyone’s memory.
Loaners, spares, and the bench
The loaner pool deserves more ceremony than it usually gets:
- Check out every loaner to a named borrower with a due date, even mid-outage. If it takes longer than a scan and ten seconds, engineers will route around it.
- Review the overdue list weekly. A loaner two weeks late is a phone call; six months late, it is a write-off.
- Run spares on reorder points. Decrement when consumed, let deliveries update the count, and the empty shelf stops being a mid-outage surprise.
Tip: photograph a loaner at handout and again at return. The pair of photos settles every “that crack was already there” conversation before it starts.
Getting started without a discovery project
You do not need to inventory every client before this pays off. Sequence it:
- Start with what is yours. Label and register the loaner pool and the bench in one afternoon - the part with the worst current record.
- Add one client at the next scheduled visit. Walk the site, record serials, photograph and label as you go.
- Import the rest from paperwork you already have. Procurement spreadsheets and supplier invoices get most of the fleet on the register via CSV import.
- Make scanning the habit. Nothing leaves the bench, and nothing changes hands on site, without a scan.
AMPthilly fits this shape of work. Departments and roles keep each client’s world separate, and the Client role lets a customer contact sign in and see only their own assets. Printable QR labels scan with a normal phone camera in the browser - no app for the engineer on site - and every checkout, transfer, and repair ticket lands in an exportable audit history. The free plan covers 3 users and 25 assets, no card required - enough to run the loaner pool; see pricing for the rest.
FAQ
How do MSPs keep track of client hardware? One register where every asset carries its client, site, serial, and warranty end date - with custody changes recorded as checkouts and transfers by scanning a label.
Should an MSP keep one asset register for all clients? One system with hard separation inside it. Per-client spreadsheets go stale at different rates; one register filtered by client stays reviewable.
How do you track loaner laptops as an MSP? Like library books: a named borrower, a due date, condition photographed both ways, overdue list reviewed weekly.
What should be on a client hardware record? Serial, model, client and site, current user, purchase date, supplier, warranty end, and any configuration documents worth keeping.
How does an MSP prove a device was returned or replaced? With the asset’s custody history. Tickets prove the work; the asset record proves where the hardware went.
The takeaway
An MSP’s register must keep other people’s property, your property, and the grey zone between them cleanly separated across buildings you rarely visit. Assign every asset to a client and site, run the loaner pool like a lending library, keep spares on reorder points, and make the scan the moment of record - with AMPthilly or anything else - and “where is that device” becomes a filter, not an investigation.