Equipment and asset tags

The tag outlives the manual. Twice.

Asset tags, placards, the sticker inside the panel: installed once, in the field, for the life of the machine. What they point at changes every year, and the person scanning is standing in front of the thing.

The worked example

One tag, every year of the machine's life.

The sticker says go.yourbrand.com/pump-4. Where it points is a schedule, a few rules, and a record.

Business hours, wherever it's scannedThe current manual and the service deskHours on the scanner's own clock, because the machine shipped worldwide.

After hoursThe emergency lineA rule that crosses midnight, in the scanner's zone, not yours.

Manual revision 4 shipsChange the destination onceEvery tag on every unit follows. Nobody goes into the field with a label printer.

A service bulletin for one batchA rule for that print runUnits tagged in the 2025 run see the bulletin; the 2026 run doesn't.

The support site is downA hold page with the phone numberChecked every five minutes; fails over on its own and switches back when the site answers.

OtherwiseThe fallbackWhere a scan lands if nothing above applies. It can't be blank, because the tag can't be recalled.

What changes for you

Three things you stop doing.

Sending someone out with labels

The manual moved, the contractor changed, the number's different: change the destination, not the tag.

Printing tags after the fact

Reserve a block of codes before the units exist, print them with the batch, and assign destinations as each unit ships. The print run is a thing you can pause or point somewhere on its own.

Answering "what did that tag say last March?"

The record of what each code answered, with when and why, is kept for the life of the code and exportable with a checksum. Liability likes a record.

Ten thousand units

Your domain, your namespace, your record.

Print under a hostname you own. If we ever go away you repoint one DNS record and every tag in the field keeps working, and the whole workspace downloads as a file any web server can serve. An agent or your service system can drive it over the API: a nightly job that points every tag at the current revision and the on-call contact is a few lines.

Want the scan itself to be the event, "this extinguisher was inspected," with nothing to build? That's next; write to hello@linkshift.co and tell us what you'd tag.