What do you write on an asset tag?
An identifier behind an address you control, and nothing else. Everything about an asset changes over its life: its location, its owner, its status, its value. A tag written once cannot follow any of that, and revisiting every tag is not a plan.
An identifier, nothing more
A short address on your own domain, ending in an identifier unique to that asset. That is the whole content.
Reading it gives a technician a page, and gives your system a certain answer about which asset was touched.
Where the chip mirrors its own identifier, even that is written identically across the whole batch, and assignment happens in your system when the tag is applied.
Everything else about the asset lives where it can be edited by someone at a desk rather than by someone with a ladder.
What people write instead
The asset description, which changes when equipment is reconfigured.
The location, which changes the first time anything is moved and is wrong for the rest of the tag's life.
The owning department, which changes at every reorganisation.
Service dates, which are wrong the moment the next service happens.
Each of these is written because it seems useful offline, and each becomes a lie that a technician will eventually trust.
Why the address matters
The identifier is only useful if something resolves it, and that something must still exist in ten years.
An address on your own domain survives a change of software, a change of supplier and a change of hosting. An address on a vendor's platform does not.
Asset tags outlive the systems that created them, routinely. Equipment is tagged once and inspected for a decade.
So the domain is the durable part of the design, and it is chosen once at the beginning by someone who may not realise they are choosing it.
The offline exception
Where technicians work with no coverage and need something without a system, a small amount of stable text alongside the address is defensible.
Stable means genuinely unchanging: an asset number, a model, a manufacture date. Not a location, not a status, not a next service date.
It costs memory and it costs a longer read, so keep it to what is genuinely needed when nothing else is reachable.
And print the same information on the tag face, which serves a technician with a flat phone and costs nothing.
Frequently asked questions
Should the location be on the tag?
No. It is wrong the first time anything moves, and a wrong label is worse than none because people trust it.
Can I write the service history?
It changes at every service, so it belongs in the system. A tag written once cannot follow a history.
What if there is no coverage in the plant?
Add a small amount of genuinely stable text, such as an asset number and a model. Keep changeable facts off the tag.
Why does the domain matter so much?
Because asset tags outlive the systems that created them. An address you own still resolves after a change of software or supplier.