TL;DR

IT asset tagging is one of those practices that persists because it used to be necessary. When assets sat in buildings and nothing reported its own identity, a physical label was the only way to connect a machine to a record. On a remote fleet where every device reports its serial number automatically, the label does much less work and costs more to apply.

  • The serial number is the identifier. A tag is a convenience on top.
  • Tags still help for non-reporting items: monitors, docks, peripherals.
  • Applying tags at a central point is cheap. Applying them later is not.
  • A tag that duplicates the serial adds a second thing to keep in sync.
  • Return address labels are worth more than asset tags on a remote fleet.
  • Skip tagging entirely if nobody will ever read the label.

Why IT asset tagging existed in the first place

Because the alternative was worse. A room of identical machines, no automatic inventory, and a register that needed some way to say which row described which box.

A label solved that completely. You could stand in front of a device and read its identity without turning it on.

That problem has largely gone for anything that runs a management agent. The device reports its serial, model, operating system and user on a schedule, without anybody standing in front of it.

What the label still does

Three things, and it is worth being honest that only two of them matter much.

It identifies a device that is switched off or broken. It carries ownership information for anybody who finds it. And it deters casual theft, which is a real but modest effect.

What is still worth tagging

The dividing line is simple: does the item report its own identity?

Item Reports identity Worth tagging
Laptops and desktops Yes, continuously Marginal, ownership label only
Phones and tablets Yes, if enrolled Marginal
Monitors No Yes
Docks and hubs No Yes, if they are tracked at all
Headsets and peripherals No Usually not worth tracking
Network hardware Sometimes Yes, if in an office

Monitors are the clearest case for tagging and the item most often skipped, which is backwards. They are high volume, invisible to management tooling, frequently moved, and they constitute a surprisingly large share of fleet value.

Network hardware sits in between. In an office it is worth tagging because somebody will eventually stand in front of a rack trying to work out what a device is. In a fully remote company there is usually no rack and no reason.

Peripherals are the clearest case against. If a headset is not on the register at all, tagging it records nothing. The decision to track an item class should come first, and tagging follows it.

A tag that duplicates the serial

Some schemes print a new internal code and treat it as the primary key. That creates a second identifier to keep synchronised with the first, and it breaks the moment somebody reads the serial instead.

Where tagging is worthwhile, printing the serial itself on the label, plus ownership details, avoids the problem entirely.

Apply at a central point or not at all

The economics of tagging are entirely about when it happens.

Applied at a staging point before a device ships, a tag costs seconds and the data is captured as part of a process that is already happening.

Applied afterwards, it costs a request to the employee, instructions, a posted label, and a follow-up when they do not do it. For a remote fleet, retrospective tagging programmes have a poor completion rate for entirely predictable reasons.

So the honest choice for most distributed teams is to tag everything that passes through a staging point and accept that devices already in the field will not be tagged.

Which argues for where staging happens

If devices ship directly from a supplier to an employee, there is no staging point and no opportunity to tag. That is a reasonable trade for speed, and it should be a decision rather than a discovery.

RemoAsset configures devices before they ship as part of procurement and delivery, which is the point at which labelling, enrolment and record creation all cost almost nothing.

Our note on zero touch provisioning covers the trade between staging and direct shipping.

The label worth applying instead

On a remote fleet, the most useful thing on a device is not an asset code. It is how to return it.

A label carrying the company name and a return contact does more practical work than an internal asset number, because the people who encounter a lost device have no way to use an asset code and every reason to use a return address.

The same applies at offboarding. A device with clear ownership marking is more likely to be returned by somebody uncertain about what to do with it.

  • Company name, visible without opening the machine.
  • A return contact that will still exist in two years.
  • The serial, which makes any support conversation faster.

That is a more useful label than a sequential asset number, and it costs the same to apply.

Where to put it

Somewhere visible without opening the machine, and somewhere that survives. The underside is the convention and it is also where labels get worn off by desks and bags.

Near the hinge or on the lid edge lasts longer and is readable by somebody holding the device. For monitors, the back near the stand is the only sensible location, since the bezel gets cleaned and the base gets swapped.

Use a label stock rated for the surface. A paper label on a warm aluminium laptop lasts months, and a tag that falls off has cost the application time and bought nothing, which is the worst outcome of the three available.

The decision table

Tagging effort should follow what your tooling cannot see.

Situation Scale Setup Primary pain Recommended starting point
Office fleet, assets stay put Any On-site Finding things Traditional tagging still works
Remote fleet, all enrolled Any Managed endpoints Little Ownership label only, skip asset codes
Lots of monitors and docks 50 to 200 Peripherals tracked Invisible to tooling Tag peripherals, not laptops
Direct-ship from supplier Any No staging point No chance to tag Ask the supplier to label and record
Audit requires tags Any External requirement Policy, not practicality Tag at staging, document coverage honestly

Row five is worth handling directly. If an external requirement specifies tagging, meet it at the staging point and state the coverage honestly rather than claiming a completeness that a remote fleet cannot deliver.

The record matters more than the label

Whatever you decide about labels, the thing that determines whether asset management works is the record and what updates it.

A perfectly tagged fleet with no disposal trigger drifts exactly as fast as an untagged one. The label helps you identify a device in front of you. It does nothing about the devices that quietly left.

the NIST Cybersecurity Framework places knowing what you have at the foundation of everything else, and the practical version of that on a remote fleet is enrolment coverage rather than label coverage.

Where to spend the effort instead

If there is a budget for an asset tagging programme, consider whether the same money spent on enrolment coverage and a working recovery process would buy more. For most distributed teams it would, by a wide margin.

Recovery in particular is where the register loses accuracy fastest, because an uncollected device is a row that can never be closed honestly. Collection from former employees closes those rows, and no amount of labelling will.

Our piece on IT asset management implementation covers that sequencing, and ISO 55001 on asset management systems describes the wider frame for teams that need one.

RemoAsset configures, labels and records devices before they ship, which is when it costs almost nothing. More at PeopleOpsHQ.

Frequently asked questions

Is IT asset tagging still necessary?

Less than it was, for anything that runs a management agent. The practice exists because assets once sat in buildings and nothing reported its own identity, so a physical label was the only link between a machine and a record. A laptop that reports its serial, model and user on a schedule has already solved that. The label still helps when a device is switched off, broken or found by a stranger.

What should we tag and what should we skip?

Tag what cannot report its own identity. Monitors are the clearest case and the most often skipped, which is backwards given they are high volume, invisible to management tooling and a significant share of fleet value. Docks and network hardware follow. Laptops and enrolled phones need an ownership label at most. Peripherals usually should not be tracked at all, and tagging something you do not track records nothing.

Should the asset tag use its own numbering scheme?

Preferably not. Printing a new internal code creates a second identifier to keep synchronised with the serial number, and it breaks the first time somebody reads the serial instead. Where a label is worthwhile, putting the serial itself on it alongside ownership details avoids the reconciliation problem entirely and makes support conversations faster as a side effect.

When should tags be applied?

At a staging point before the device ships, where it costs seconds inside a process already happening. Applied afterwards it costs a request to the employee, posted labels, instructions and chasing, and retrospective tagging programmes on remote fleets have poor completion rates for predictable reasons. The honest position is to tag what passes through staging and accept that existing field devices will not be.

What if devices ship directly from the supplier?

Then there is no staging point and no opportunity to tag, which is a reasonable trade for speed as long as it is a decision rather than something discovered later. Some suppliers will label and record on your behalf as part of configuration, which restores the option. Otherwise plan around the absence rather than running a retrospective programme that will not complete.

What is more useful than an asset code on a label?

A return route. The company name and a contact that will still exist in two years does more practical work than an internal asset number, because anybody who finds a lost device has no way to use the code and every reason to use the address. The same applies at offboarding, where clear ownership marking makes return more likely from somebody unsure what to do.

Should we fund an asset tagging programme?

Compare it against spending the same money on enrolment coverage and a working recovery process, because for most distributed teams those buy considerably more. A perfectly tagged fleet with no disposal trigger drifts exactly as fast as an untagged one. The label helps you identify a device in front of you and does nothing about the devices that quietly left, which is where the real inaccuracy comes from.