How to build a QR-code asset register

A practical guide for FM and maintenance teams: what to record, how to tag site by site, QR vs barcode vs RFID, and how to keep the register alive after the survey ends.

Every FM and maintenance team has, somewhere, a spreadsheet called something like Asset List FINAL v7. It was accurate the week it was built. A QR-code asset register fixes the underlying problem: it moves the point of data entry from the office to the asset itself, so the record gets updated by the person standing in front of the kit. This guide covers what a good asset record contains, how QR compares with barcodes and RFID, and a tagging workflow that actually gets finished.

Why spreadsheets fail as asset registers

Spreadsheets fail for predictable, structural reasons — not because anyone is careless:

  • The update happens away from the asset. An engineer swaps a pump on Tuesday; the spreadsheet lives on a shared drive they open on Friday, if at all. Every hour of delay is an opportunity to forget.
  • No single version. Copies proliferate — one on the shared drive, one emailed to a contractor, one on a site laptop. Nobody can say which is current.
  • Free-text chaos. "AHU-1", "AHU 01" and "Air Handler Roof" are the same asset to a human and three assets to a filter.
  • No history. A cell overwrite destroys the previous value. You can't answer "when was this last serviced, and by whom?" from a flat sheet.
  • No link to the physical world. Standing in a plant room, there is no fast way to find the row that describes the machine in front of you. That lookup friction is why records drift.

A QR code on the asset removes the lookup friction: scan, and you're on the right record, on your phone, in the plant room.

What an asset record should contain

Keep the mandatory core small — every extra required field lowers the completion rate during tagging. A workable structure:

  • Identity: unique asset ID (the QR code's value), name/description, category or type (from a controlled list, not free text).
  • Location: site, building, floor, room or zone. Structured, so you can filter "all assets in Block B".
  • Make and model: manufacturer, model number, serial number — the details you need when ordering parts or checking recalls.
  • Dates: install date (or best estimate), warranty expiry, expected end of life.
  • Condition: a simple graded scale (e.g. 1–5) recorded at each survey, with a photo.
  • Compliance links: which statutory or planned maintenance regimes apply — LOLER, F-Gas, fixed wire testing, gas safety — and when the next inspection is due.
  • History: a running log of work done, faults, and condition changes, each entry stamped with date and person.

Photos deserve a special mention: one photo of the asset and one of its rating plate at tagging time will save hundreds of return visits over the register's life.

QR vs barcode vs RFID

QR codeBarcode (1D)RFID
Reader neededAny smartphone cameraPhone camera or laser scannerDedicated reader/antenna
Cost per tagPence (printed label)PenceTens of pence to pounds
Data capacityHigh — can encode a URL or IDLow — short ID onlyVaries; ID plus some data
Line of sightRequiredRequiredNot required — bulk reads possible
Damage toleranceGood — up to ~30% damage readable (error correction)Poor — one scratch across the bars can kill itGood, but tags can fail invisibly
Best forGeneral FM/maintenance assetsLegacy systems, retailHigh-volume stock, tool tracking

For most FM and maintenance teams, QR wins on the combination that matters: every engineer already carries a reader, tags cost pence, and error correction tolerates the abuse of a plant room. RFID earns its cost where you need bulk, no-line-of-sight reads — stocktaking thousands of items — not for a fixed-plant register. If you're migrating from an old barcode system, choose software that can read legacy barcodes alongside new QR tags rather than re-tagging everything on day one.

A tagging workflow that gets finished

Most tagging projects stall halfway. The ones that finish share a pattern:

  1. Decide the asset boundary first. Agree what counts as an asset (typically: anything maintained, inspected or valuable enough to track) and what doesn't (consumables, furniture below a threshold). Write it down; arguments mid-survey kill momentum.
  2. Pre-print tags in batches. Use durable polyester or laminated labels — plain paper fails within months in plant rooms. For harsh or outdoor environments, use anodised aluminium or riveted tags.
  3. Walk one site, one floor, one room at a time. Sweep systematically so "done" is a place, not a percentage. Tag, photograph, capture the core fields, move on — 2–4 minutes per asset is a realistic budget.
  4. Place tags consistently. Same position on the same asset type (e.g. front-left of the casing, near the rating plate), visible without dismantling anything, away from heat and abrasion.
  5. Capture minimum viable data on the walk. ID, description, location, photo. Enrich model numbers and warranty dates later from the photos — don't let perfect data collection slow the physical sweep.
  6. Close each area with a reconciliation. Compare what you tagged against any existing list; investigate assets on paper you didn't find, and vice versa.

Keeping it current: link the register to PPM

A register decays the day the survey ends unless routine work flows through it. The fix is to make the register the front door to maintenance:

  • Raise and close planned maintenance (PPM) tasks against the asset record, so every service visit touches — and silently verifies — the register.
  • Report faults by scanning the tag, so reactive work is captured against the right asset with zero lookup effort.
  • Record condition at every touch. A one-tap condition grade during a PPM visit builds a lifecycle picture for free.
  • Review exceptions monthly: assets with no activity for 12 months either don't exist any more or aren't being maintained. Both are worth knowing.

Offline capture matters more than you think

The places assets live — basements, plant rooms, risers, rural sites — are exactly the places mobile signal doesn't. If your tool needs a connection to scan and save, your engineers will fall back to memory and paper, and the register rots from the edges. Offline-first tools such as AssetIQ store scans, photos and edits on the device and sync when signal returns, so capture works in a basement plant room as well as it does in the office. Whatever software you choose, test it in your worst-signal location before rolling it out — and check you can export your full register at any time, because an asset register you can't take with you isn't really yours.

Getting started this month

Don't wait for a perfect scope. Pick one building, agree the asset boundary, print a batch of tags, and sweep it in a week. A complete register for one site teaches you more about your field workflow than a quarter of planning — and gives you a working template to roll out everywhere else.

This guide is general information, not legal, tax or compliance advice. Rules change — always check the current official guidance for your situation.

Put it into practice

AssetIQ is built for exactly this — see what it does or book a free demo.

Build a register your engineers will actually use

AssetIQ is an offline-first QR asset register — scan, capture and update in the plant room, sync when signal returns, and export your data any time.

You own your dataUK-hostedUK GDPR compliant