🐒Monkey AssetsAsset register
Practical guide

How to build an IT asset register that stays accurate

A spreadsheet works until it doesn't — until people can't find the file, edit the wrong row, or lose the serial you needed. Here's how to build a register that scales, tag by tag, without the data-entry slog.

The fields worth tracking from day one

A register is only as useful as the questions it can answer — who holds this laptop, is it under warranty, where did it go. Start lean with the fields below, plus a free-text notes column for the things that don't fit.

  • Identity A unique asset tag, the type, the make and model, and the serial — enough to tell one black laptop from forty others.
  • Ownership Who holds it and which site or team it belongs to, so a missing device always has a name against it.
  • Status and notes In use, in storage, being repaired, retired — the field that stops you buying kit you already own — plus notes for the rest.
  • Purchase and warranty Purchase date, cost and warranty expiry, so renewals and write-offs never ambush you.

Tag every asset so anyone can find it

A register no one can connect to the physical thing in front of them drifts out of date fast. A QR tag on the device closes that gap — scan it, see its whole history.

  • One tag, one asset Give every asset a permanent code the moment it's created, not months later when you get around to it.
  • Print and stick Run die-cut labels on a Brother QL roll or an A4 sheet straight from the register, then apply them as gear arrives.
  • Scan with any phone No app, no scanner gun — any phone camera opens the asset's record, so audits and handovers take seconds.
  • Design the scheme, not just the sticker A short, consistent code — a site or type prefix plus a number — reads at a glance and never clashes with an old label.

Populate it in an afternoon, not a month

The reason most registers die is data entry — hundreds of rows typed by hand. Skip it. There are three fast ways to fill a register, and nothing stops you mixing all three.

  • Photograph your gear Snap a device or its label and AI reads the make, model and serial and fills the form for you.
  • Let PCs report themselves A bundled desktop uploader reads a Windows or Mac machine's full specs and serial and files it as an asset.
  • Import from Microsoft 365 Pull devices from Intune or Entra and people from your directory, so half the register is there before you start.
  • Meet in the middle Bring across what you already have, then enrich each row with a photo and a QR tag.

Keep it accurate after day one

A register is a living record, not a stocktake you do once. The trick is making the true version the easy version — updates that happen as the work happens.

  • Log movements as they happen Record every handover, transfer and retirement, so 'where is it' always has a current answer.
  • Keep an audit trail Track who changed what and when, so a mistake is a lookup rather than an argument.
  • Use transfer agreements Hand a device over against a signed record, so responsibility is clear if it later goes missing.
  • Don't let it fork One register, one source of truth — the moment there are two spreadsheets, both are wrong.

Common questions

Can't I just use a spreadsheet?

For your first dozen assets, a spreadsheet is fine. It stops scaling when several people edit it at once, when you need a history of who changed what, and when you want to connect a row to the physical device in front of you. That's when duplicates, stale rows and lost serials creep in — and a purpose-built register handles all three without you policing it.

What fields should an IT asset register include?

At a minimum: a unique tag, asset type, make and model, serial number, owner, site, status, and purchase and warranty dates, plus a notes field. Those let you answer who has what, where it is, whether it's covered, and when to replace it. Start lean and add custom fields only once you feel their absence.

Should I tag assets with barcodes or QR codes?

QR codes are the easier choice for most teams. They hold more than a barcode, scan reliably at odd angles, and read with any phone camera — no dedicated scanner to buy or maintain. Print them on durable labels and apply them as assets arrive.

How often should I audit the register?

A light quarterly check suits most organisations, with a fuller review once a year. If every movement is logged as it happens and each asset carries a QR tag, an audit becomes a walk-around with a phone rather than a week of reconciliation.

Is there a free IT asset register template?

Yes. Monkey Assets has a free tier that gives you a working register — not just a blank spreadsheet — with QR tags, AI photo intake and the core fields already set up. You can start with 30 assets at no cost and no card required.

Keep reading

Start your register free

Monkey Assets does everything on this page — QR tags, AI photo intake, Microsoft 365 import — and the free tier covers your first 30 assets with no card required.