Asset Tagging Best Practices: A Practitioner's Guide

Manufacturers print serial numbers in 5-point grey type on the underside of the chassis, behind the battery, or on a sticker that the first cleaning wipe takes off. That's the real argument for asset tagging, and it has nothing to do with bureaucracy: the identifier that came with the equipment is unusable for the one job you need it to do, which is telling forty-seven identical laptops apart while standing in a room holding a clipboard.

Count those forty-seven and come up three short and you have a second problem on top of the first. You know three are missing. You don't know which three, so you can't tell whether they were stolen, written off two years ago and never removed from the register, or sitting in someone's home office since the last remote-work push. Without per-unit identity, an inventory count produces a number, not information.

Asset tagging is phase 4 of the full implementation process, and it's where the digital system meets physical reality. It's also the phase where mistakes are most expensive to undo, because undoing them means walking to every asset a second time.

We build one of these systems, so treat the tooling recommendations accordingly. Material, placement, and numbering advice is vendor-neutral.

Tag technology at a glance

Prices are 2026 ballparks and move with volume, material, and whether a tag has to work on metal; treat the columns as ratios rather than quotes.

QR covers the overwhelming majority of cases, and the reason is in row two: the reader costs nothing because everyone already carries one. Every other technology on this table asks you to buy hardware before you learn anything.

Add RFID when bulk counting is the actual bottleneck: a warehouse doing weekly full counts, a hospital tracking infusion pumps across floors. Below roughly 500 assets, or when you count twice a year, the reader never pays for itself no matter how good the demo looked. We support RFID and I still say this on calls; the RFID ROI calculator will tell you faster than I can.

NFC is narrower than its marketing suggests. It earns its place where a printed label physically can't survive or can't be seen: tags under paint, assets handled with heavy gloves, equipment that gets pressure-washed. As a general upgrade to QR it's mostly a nicer gesture at a higher price per unit.

BLE is a different category altogether. It answers "where is it right now" rather than "what is this thing", and it's the only option here that doesn't need a human to do anything. It also needs gateways, and batteries that die.

Numbering: shorter and dumber than you think

The instinct is to make the ID descriptive. NYC-IT-LAP-2024-0001 tells you it's a New York IT laptop from 2024, and that feels like free information.

It isn't free. It's printed. Departments merge, offices close, equipment gets reassigned to a different team, and two years later that label is confidently wrong about three of its five fields — while the database, which could have been edited in one click, was never asked.

Use a short category prefix and a number. IT-00421. VEH-0007. Two or three letters at most, chosen from a category list that fits on one screen. The category is the only attribute stable enough to earn a place on a physical object: a laptop stays a laptop.

Everything else lives in the record, where it can change. Location, custodian, cost centre, purchase date, warranty: all of it is one edit away instead of one relabeling exercise away.

Two rules that cost nothing and save real pain later. Keep the numbering sequential per category rather than global, so you can see at a glance how many of something you own. And never reuse an ID from a retired asset: a recycled number is how a 2019 repair history ends up attached to a machine bought last spring, and untangling that costs more than the label ever saved.

Materials, and why labels fail

A label that scans perfectly the day it's printed and fails eighteen months later isn't a tagging problem. It's a materials problem, and it's the single most common reason a tagging programme quietly stops working.

Paper with a laminate overlay is fine indoors, on things that sit still: desks, monitors, meeting-room furniture. One to two years, longer if nobody handles them.

Polyester with an acrylic adhesive is the workhorse for equipment people actually touch. Laptops, tools, test gear, anything wiped down or moved between rooms. It handles moisture, mild solvents, and abrasion, and it stays put on a surface that flexes slightly.

Polycarbonate goes where there's heat or chemistry: near machinery, in plant rooms, anywhere solvents get used routinely.

Anodized aluminum plates are for the assets that outlive several label generations: outdoor structures, abrasive environments, safety-critical equipment. The image is sealed into the oxide layer rather than printed on top of it, so there's no printed surface left to wear away.

Two details that decide more outcomes than the face stock does.

Adhesive first. Low surface energy plastics, meaning the polypropylene of most tool cases and many powder-coated panels, shed standard acrylic adhesives within weeks. On plastic cases, specify an adhesive rated for LSE surfaces, or plan to relabel. Curved and textured surfaces want a conformable vinyl instead of a stiff polyester that lifts at the edges.

Print method second, and this one catches people out because it's invisible in the sample. Direct thermal printing (no ribbon, the cheap shipping-label kind) produces labels that darken and fade with heat, sunlight, and time. Six months on a sunny windowsill or a warm machine housing and there's nothing left to scan. Thermal transfer with a resin ribbon onto polyester survives solvents and abrasion. Our guide on choosing a printer for QR and barcode labels covers the models and what separates them.

Order 10–15% more labels than you have assets. Tags get damaged, applied crooked, or attached to something that turns out to be leased rather than owned, and running out mid-rollout stalls everything.

Placement

Define one location per asset type and hold everyone to it. Inconsistent placement is what turns a two-hour audit into a four-hour one, because every scan starts with a search.

Never put a tag on a removable part. Battery covers, access panels, and caddies get swapped between units during repairs, and when they do, the identity moves with the wrong piece of metal.

Photograph the intended placement for each asset type once and give that sheet to whoever is doing the tagging. It's faster than explaining, and it removes the judgment calls that produce inconsistency.

What goes on the tag besides the code

The code, the ID in plain human-readable text, and a contact route.

The plain text matters more than people expect. Phones die, cameras fail, a new hire hasn't been given access yet, the code gets scratched. A readable IT-00421 keeps the asset identifiable with a pen and paper.

[QR CODE]
Asset ID: IT-00421
Found this? (555) 123-4567

A "found asset" URL is worth setting up if equipment leaves the building regularly. Point the code at a page that says what the item is, who to tell, and gives one tap to report it — no login, no app. The reason it works is friction: someone who finds a laptop in a meeting room will scan a code, and won't hunt through a directory for the right IT contact.

What doesn't belong on the label: serial numbers, purchase cost, and employee names. The serial is the field a thief benefits from, the cost is an invitation, and names go stale every time someone changes role.

Making the data survive contact with people

Tagging is a one-time exercise. Keeping the register true is not, and these are the practices that decide whether the effort holds.

Tag at intake, not later. Every new asset gets its label before it's deployed, while it's still in a box in one place. Assets tagged "later" are the ones that never get tagged; they go straight to a desk and disappear into normal use.

Photograph each asset when you tag it. Wide shot, close-up of the tag, existing damage. Name the file with the asset ID rather than IMG_4532.jpg. Thirty seconds each, and it settles disputes about condition and ownership that are otherwise unresolvable months later — the ones that turn into insurance arguments.

Assign a person, not a room. Every asset needs a custodian through a check-in/check-out process. Behaviour changes measurably when equipment is assigned to a named individual rather than "the department", and offboarding becomes a checklist item instead of an archaeology project.

Audit the tagging while it's happening. Have someone spot-check a sample as the work proceeds: correct location, firmly adhered, photo captured, fields filled, code scans. Fixing ten labels now beats re-tagging five hundred in six months.

Then audit the tags themselves, quarterly. Scan a 5% sample and record how many read first time. We work to 95% as healthy and 90% as the line where a re-tagging batch is due — our working numbers, not an industry standard. If you want something objective, ISO/IEC 15415 grades 2D symbol print quality from A to F, and codes grading below C are the ones that start failing in poor light and on worn labels. This is asset audit applied to the labels rather than the inventory, and it's the check almost nobody runs.

Have a process for untagged equipment. People will find things. Label it TEMP- with a date, photograph it, ask around, and set a deadline after which it's either catalogued properly or written off. Inherited equipment from acquisitions and gear from closed offices are the usual sources.

Set up a physical staging area for broken and retired assets. One room, one status in the system. Without it, dead equipment lingers in closets in an ambiguous state, and nobody can tell what's awaiting repair from what's awaiting disposal.

Rolling checks beat annual ones. Twenty percent of the estate each month, by building or floor, spreads the work and catches problems while they're still traceable — cycle counting logic applied to fixed assets. High-value equipment deserves monthly spot checks; furniture is fine annually. The audit strategy playbook covers building that rhythm properly.

A rollout plan that survives contact with a calendar

This timeline assumes 200–500 assets. Scale it with the table underneath.

Two scheduling details that aren't in any vendor's plan. Tag in the morning, when equipment is at workstations rather than in meeting rooms; an afternoon session turns into a hunt. And build in buffer, because you will fall behind — the tagging itself is fast, but every twentieth asset raises a question that takes ten minutes to answer.

The pilot is the part to protect when the schedule slips. Two to three weeks of tagging fifty things surfaces what planning can't: that the labels don't stick to that particular plastic, that there's no signal in the back storeroom, that the location hierarchy is one level too deep. How to run a pilot program covers scoping and what to measure.

A pilot needs somewhere to put the records, and at fifty assets that shouldn't cost anything or require a decision you can't reverse. Ours is free for 50 with no card, and everything exports to CSV or JSON if you take the data elsewhere afterwards — which is worth checking with any vendor before you tag anything, not after.

Where tagging programmes go wrong

Tagging before choosing the system. The numbering scheme depends on what the software can do with it, and relabeling because the ID format was wrong is the most avoidable rework in this whole process.

Buying the cheapest labels for a harsh environment. Saving a couple of hundred dollars on stock that fails in three months costs several times that in relabeling, and it costs trust in the data during the months when scans quietly stop working.

A scanning workflow that requires a desktop. If someone has to walk back to a computer, the scan doesn't happen and the record goes stale. Phone-first or it doesn't get used.

Too many steps. Beyond about three taps, adoption falls off a cliff. Ask for the scan and the person; every additional mandatory field is a small tax on every future scan, and the fields nobody needs are the ones that get filled with garbage.

No named owner. "Everyone is responsible for assets" reliably produces nobody being responsible.

Waiting for a complete plan. A register covering the 200 assets that actually move is worth more than a perfect scheme covering nothing. Tag the expensive things and the mobile things first, adjust the convention as you learn, and accept that the first version won't be the final one.

Industry notes

IT and tech. Hardware plus licences; QR on everything, with the tagging record syncing to the ITAM or CMDB rather than living separately. Remote and BYOD hardware wants labels that peel cleanly when kit comes back.

Manufacturing. RFID where counts happen in bulk, NFC on machines with maintenance histories worth reading at the machine, and tags placed away from vibration and grease. Ties directly into preventive maintenance scheduling.

Healthcare. Sterilisation cycles destroy ordinary labels, calibration records have to be attached to the asset, and equipment moves between floors constantly. Materials matter more here than anywhere else.

Logistics. GPS on vehicles, RFID at dock doors, QR on everything smaller.

Education. High volume, high turnover, low budget. QR with strict issue-and-return control, because the loss pattern is almost entirely at handover.

What it costs and what it returns

Rough orders of magnitude for 500 assets on QR, not quotes: a few hundred dollars of labels, with the spread driven almost entirely by material (paper versus polyester versus metal plates); software somewhere in the hundreds to low thousands a year at that scale, depending on how many people need logins; and one to two working weeks of someone's time to run the rollout. That last figure is the one people underestimate, and it's mostly walking.

The returns are harder to pin down honestly, because most of them are avoided costs. Fewer duplicate purchases of equipment that already exists somewhere. Audits measured in days rather than weeks. Fewer write-offs of assets that were merely misplaced. Whether that adds up to a payback in four months or fourteen depends entirely on how bad the starting point was, and anyone quoting you a precise figure hasn't seen your storeroom.

Where spreadsheets stop working

Up to about 50 assets with one person maintaining the file, a spreadsheet genuinely works, and our asset tracking in spreadsheets guide covers doing it properly.

It breaks on two things, neither of which is the row count. Concurrent editing, where two people update two copies and nobody notices for weeks. And the handoff, because nobody opens a spreadsheet at the moment they hand a drill to a colleague — which is precisely the moment the record needs to change.

A real system adds movement history, depreciation, maintenance scheduling, and reporting that finance will accept. It also adds the thing tags exist for: scanning as the update mechanism, so the record changes at the moment custody does. If you're at that point, the implementation checklist breaks the move into tasks, and the data migration playbook covers cleaning what you've got before it goes in.

Frequently asked questions

What are asset tagging best practices?

Core best practices: choose tag technology that fits your environment (QR for most, RFID for high-volume), design stable asset IDs that resolve to a database record, use durable materials (polyester or metal), place tags consistently per asset type, write the conventions down in one page for staff, and run quarterly audits to catch degraded tags before they break your data.

Should I use QR codes or RFID for asset tagging?

QR codes for the overwhelming majority of organisations, cheap (cents per tag), scannable by any smartphone, high data density. RFID when you need bulk scanning (hundreds of tags per second) or hands-free audits at doorways, costs $1–$5 per tag plus reader infrastructure. Many teams use both (QR on every asset, RFID on high-value).

How should I number assets when tagging?

Short, sequential, and close to meaningless: a two or three letter category prefix plus a number, like IT-00421. Don't encode department, building, or purchase year, those change within a couple of years while the printed label doesn't. Keep numbering sequential per category, and never reuse an ID from a retired asset.

What material should asset tags be made of?

Laminated polyester for most indoor environments (offices, warehouses). Polycarbonate for high-heat or chemical exposure. Metal plates with etched codes for outdoor, abrasive, or safety-critical assets. Paper labels fail within months on anything that moves, avoid them for tracked assets.

Are there IT asset tagging best practices that differ from physical assets?

IT assets need additional data capture: MAC address, serial number, OS version, assigned user. Tags should survive display screens (avoid front placement on laptops), and IT tagging usually syncs with the ITAM/CMDB system automatically. For BYOD or remote hardware, use soft labels that peel cleanly without residue when assets return.

Where should I place an asset tag on equipment?

Define a standard location per asset type and enforce it. Laptops, top-right palm rest or bottom case. Desktop monitors, bottom-right bezel. Machinery, front-right panel at eye level. Vehicles, door jamb or dashboard. Consistent placement cuts audit time in half and reduces missed scans. Document the convention in one page; train it once.

Start with fifty

Fifty assets is the right size for a first batch. Enough to hit the real problems — the plastic that rejects adhesive, the storeroom with no signal, the category list that turns out to be missing something — and small enough to redo if the convention was wrong.

Pick the fifty that go missing most often rather than the fifty nearest your desk. Order labels rated for where they'll actually live. Tag, scan each one immediately to confirm it resolves, and run real check-outs for a fortnight before extending to anything else.

UNIO24 is free for 50 assets with QR and NFC support, iOS and Android apps, and no card required, which is deliberately enough to get through that first batch and decide honestly. The QR code asset tracking guide covers the scanning side in more depth. Start free whenever the labels arrive.