QR Codes for Asset Tagging in Facilities: Do They Still Make Sense?

QR code asset tracking means putting a scannable code on a piece of equipment so anyone with a phone can pull up what the asset is and what has been done to it. It gives every asset an identity, fast and cheap. What it does not give you is tracking. The code identifies the asset and, at best, opens a form to log a request. It never chases the contractor, confirms the fix, or updates the record.

Picture a technician on a flat roof in July, scanning the sticker on an air-handling unit that quit overnight. Make, model, install date, a log with two entries from 2024. Useful for about four seconds. Then they are back on the phone, because the scan said what the unit is, not who is coming or whether the last fix held.

What is QR code asset tracking, and what does a scan actually do?

QR code asset tracking is the practice of tagging physical assets with QR codes so a technician can scan one and reach that asset's digital record. The code itself holds almost nothing. It is a pointer, usually a short URL, that resolves to an entry in your CMMS or a spreadsheet: the asset ID, its location, its make and model, any linked manuals, and whatever maintenance history someone has bothered to record.

A scan does three things, and it is worth being precise about which three. It confirms identity, so you know you are at the right unit and not the identical one beside it. It surfaces context, the manuals and past jobs, when that data exists. And it can open an intake form, so the person standing at the asset can raise a request without typing a location or an asset number.

That is genuinely useful, and it is why QR asset tags spread so fast. The friction of identifying an asset, the part that used to eat minutes at the start of every job, mostly disappears. But notice where the scan stops. It hands you information and an open form. Everything after you hit submit, the part that decides whether the asset actually gets fixed and whether anyone records it, is untouched by the code on the wall.

QR code vs RFID vs NFC for asset tagging

Before you commit to QR, it helps to see what the other tag technologies do, because the real choice is about how you read the tag, not what it costs to print. Three options dominate asset tagging: QR codes, RFID, and NFC. They split on four things that matter on a real estate: whether the reader has to see the tag, how far away it works, how many tags you can read at once, and what hardware someone has to carry.

The honest headline is that these are not competing versions of one thing. A QR code is an optical symbology, standardised as ISO/IEC 18004, which is a formal way of saying a camera has to see it, one code at a time, in reasonable light (ISO/IEC 18004:2024). RFID trades that for radio: passive UHF tags, standardised as GS1 UHF Gen2 and ISO/IEC 18000-63, read in bulk, hundreds of tags a second, at several metres, with nothing in line of sight (RAIN Alliance). NFC sits in between, a tap-to-read chip that works at roughly four centimetres or less (NFC Forum), which is why you unlock a phone with it but would never inventory a warehouse with it.

For most in-house facilities teams tagging their own plant, QR wins on cost and simplicity: any smartphone is the reader, and the tag prints on a label for pennies. RFID earns its keep when you are reading thousands of items at once, a warehouse or a stockroom, not a rooftop with a single AHU on it. NFC fits close-contact, single-asset checks where a tap beats aiming a camera. None of that changes the point of this article: whichever tag you pick, you have chosen how to identify the asset, not how to run the work.

Tagging isn't tracking: where the scan stops

Here is the claim the vendors skip: a QR code is an identity, not a workflow. Scanning tells you what the asset is and, if the tag links to an intake form, lets you open a request. That request then lands exactly where every other request lands, an inbox, a portal queue, a coordinator's to-do pile. The code did not route it, prioritise it, or assign it. It dropped a note in the same tray as the phone calls and the emails, and then its job was done.

Think about what tracking is meant to mean. You tag an asset because you want to know its state: is it working, is a job open on it, who has that job, is it fixed. A QR code answers the first question and none of the rest, because the rest are not identity questions. They are coordination questions, and coordination is manual work that happens after the scan. Somebody still has to read the request, decide it is a priority, find a contractor, chase that contractor to actually turn up, and confirm the unit runs again. The sticker does none of that.

This is the living-record problem, and it is the one that quietly defeats most tagging rollouts. The promise on the tag is instant asset status. The reality is that the record behind the tag is only as live as the last person who updated it, and updating it is manual, so it lags. You scan for the current state and get a snapshot from whenever someone last typed. A work order status query is the classic example: "where is my job on this asset?" should be instant from the scan, and in practice takes three phone calls, because the answer lives across a portal, a contractor's inbox, and someone's memory.

Then there is the void nobody scans into: verification. In our interviews with multi-site FM leaders, most requesters never go back to confirm the work was actually done, and most contractor engineers skip the full record-keeping process. So the request the scan raised gets marked resolved by whoever closed the ticket, not by anyone who checked. A QR code cannot verify a fix. It can show you a status field that reads complete, which is a claim, not a fact.

If you're a managing agent running maintenance across a portfolio: this gets worse at scale, not better. A tag on every unit across dozens of buildings looks like visibility, but a scan in block twelve still dead-ends into the same central inbox. Now you have hundreds of dead-ended scans a month, each one a request nobody is chasing and a record nobody is verifying. Tags multiply the front doors; they do not add anyone behind them.

Can you actually track maintenance history with a QR code?

Yes and no, and the gap between the two is where the disappointment lives. A QR code can link to a maintenance history. Whether that history is worth reading is a separate question, and it comes down to whether humans logged the work in the first place.

Scan the tag on that rooftop AHU and you might see two entries from 2024. That does not mean the unit was serviced twice in two years. It means two jobs got logged. The filter change nobody recorded, the emergency call-out a contractor handled without touching your system, the made-safe temporary fix that never got its follow-up, none of that is on the tag, because none of it reached the record the tag points to. The scan shows a history that is complete only to the extent that people kept it current.

And people, reliably, do not. Engineers log time after the fact, so a two-hour job shows as a two-minute note. Contractors run their own paperwork and skip yours. This is not a software failure, it is a behaviour problem, and it is exactly why estates running excellent CMMS platforms still cannot answer a basic question like whether to repair or replace an asset. The data is thin because keeping it complete is unpaid manual work, and the QR code did nothing to change that. A tag that links to a hollow record just lets you reach the hollowness faster.

So do QR codes still make sense?

Yes, with your eyes open. QR asset tags are a cheap, sensible way to solve identification, and identification is a real problem worth solving. The mistake is expecting the tag to solve tracking, because the two are different jobs and only one of them is printed on a sticker.

A QR rollout is worth it when:

• There is a system behind the tag that someone actually maintains, so the scan reaches a live record and not a graveyard.
• The value you want is faster, cleaner intake: walk up, scan, raise a request without typing an asset number.
• You have already sorted out who coordinates and verifies the work each scan raises.

A QR rollout is theatre when:

• You are hoping the tags fix a coordination or data problem the tags do not touch.
• Nobody owns the record behind the code, so every scan surfaces stale or empty history.
• The plan stops at sticking a code on everything, with no answer for what happens after someone scans it.

The tag is the start of the journey, not the whole of it. If everything downstream of the scan still runs on someone chasing it by hand, the code just gives that someone a faster way to start the chase.

What picks up after the scan

Everything above is true whether or not you ever change a tool. Tagging identifies the asset; something still has to run the work the scan raises. That something is coordination, and it is exactly the part that gets skipped when a coordinator is buried, which is why tagged estates so often still feel untracked.

At Heyfixit we put AI agents on the work that starts after the scan. When a request comes in, however it comes in, the agents triage it, dispatch it to the right contractor, chase that contractor for acknowledgment and a real arrival, verify the fix against the job's own evidence rather than a ticked box, and write the confirmed result back to the asset's record. The scan opens the request; the agents carry it through to a verified, recorded close, so the history behind the QR code is complete because it was captured as the work happened, not typed up later if anyone remembered. That is the difference between verified completion and claimed completion, and between an asset log that can inform a repair-or-replace call and one that just looks tidy.

Here is the honest boundary. Heyfixit is not an asset-tag, RFID, IoT, or condition-monitoring product; it does not read your tags or track assets by sensor, and it is not a CMMS replacement. It is a coordination layer that sits on top of the CMMS you already run and takes over the manual middle between statuses. Judgment stays human: the agents assemble, chase, verify, and recommend, but a person still makes the calls that matter. If your assets are tagged and the work still dead-ends, that gap is the whole point. See how AI agents run the coordination after the scan.

If you want to go deeper, the same logic runs through why facilities management is entering its self-driving era and how AI agents work across the facilities lifecycle.

Vishak C Prakash

Co-Founder & CEO

Vishak spent six years as a digital transformation consultant to facilities management and real estate operators across the UK, Middle East, Canada, and Australia — working with teams at CBRE, Siemens UK, British Land, and Brookfield. He now runs Heyfixit, building AI agents for facilities management.

LinkedIn