How an Asset Tagging Programme Runs
A tagging programme has four stages, and the order is not negotiable.
- Agree the numbering convention. What the numbers look like, who issues them and how a replacement tag is handled.
- Survey and capture. Walk the estate, decide where each tag goes and record what is physically there.
- Fix the tags. Apply the label, plate or RFID tag chosen for each area.
- Reconcile. Match every captured asset to a register row, and every register row to an asset.
Programmes that buy tags first nearly always renumber later, because the printed stock encodes a decision nobody had made. Capture comes before fixing because an asset cannot sensibly be tagged before it has been described; the walk-round establishes what exists, in what condition and in whose custody. Fixing is the fastest stage and the one most people budget for as though it were the whole job. Reconciliation is where the value is, because it finds the rows with nothing behind them, the assets nobody recorded and the locations that were wrong.
In short, that is how asset tagging is done: settle the numbering rule, walk the estate and record each asset, fix the tags, then reconcile the register. Tags can be bought pre-printed in the number blocks your convention issues, which suits a one-time programme, or printed in-house on a thermal transfer printer, which suits a business that adds assets every month. Either way the numbers come from your own list, and the tag material is chosen for the conditions each asset works in.
Designing the Numbering Convention
The convention is settled before anything is purchased, and inside a programme three decisions settle it. The first is what, if anything, the number encodes. Location, class and a running sequence are the usual candidates, and only the sequence is safe: location changes when the asset moves, and class changes when the accounting policy is revised, so encoding either turns a permanent identifier into a temporary one.
The second is the physical constraint. The number has to fit the smallest tag in use, stay readable after wear, be spoken over a phone without confusion between similar characters, and ideally carry a check digit so a mistyped number is caught when it is entered rather than at the next count. The third is ownership: one person or function issues numbers from one list, so two sites never fix the same number on different assets.
Decide now what happens when a tag wears out or falls off: the replacement carries the same number, and the old number is never reissued to another asset. Writing that rule down before the first tag is fixed saves a long argument later.
Choosing Where the Tag Goes
Tag placement is decided by walking the estate, not at a desk, because the constraints are physical. The survey is also where the tag type is settled area by area, and where the numbers of tags, plates and special tags needed are counted before anything is ordered.
- Surface. A flat, clean, non-porous patch large enough for the code; machines with none need an engraved plate or a bracket.
Check - Heat. Motor housings and hot zones defeat most adhesives; place the tag away from them or rivet a plate.
Check - Washdown and abrasion. Where water, hands, trolleys or brushes pass, specify a sealed or overlaminated tag, or move it.
Check - Line of sight. An optical tag must be readable from where a counter can stand, without moving the asset or fetching a ladder.
Check - No visible spot at all. Agree an alternative in advance: an internal identifier with a photograph, a plate on the nearest fixed structure, or an RFID tag.
Decide
Pick one consistent position per asset type, such as the top right of the front face, so a counter knows where to look on every similar machine. Record the position for awkward assets on the capture sheet; the next verifier will thank you for it.
Capture and First Reconciliation
Capture happens as each tag goes on and records more than the number. Location, custodian and condition are noted for every asset at that moment, because the team is already standing in front of it and no later exercise will have the same access. Condition matters most: it is the field that raises the impairment question, and it cannot be judged from a desk. The columns these details land in are laid out in the asset tagging format in Excel.
Matching to the existing register runs alongside the tagging rather than at the end. Each captured asset is looked up and one of three outcomes recorded:
Matched
Found cleanly against one rowDescription, class and location agree; the tag number is written into the row.
Matched after review
Found only after resolving an unclear descriptionNote what was ambiguous, so the description can be rewritten and the next count does not stumble on it.
Not found
No row for the asset on the floorRecord everything observable, a photograph and what the custodian knows of where it came from, then check purchase records: it may have been expensed, transferred in, or bought and never capitalised.
Doing this daily means a systematic problem, such as a whole department recorded under the wrong site, is caught on the second day instead of the last. The opposite outcome, a register row whose asset never turns up, is listed separately and searched for before anybody concludes it is gone.
How the capture is recorded matters less than that it is recorded once, at the asset. A scanner or phone app that reads the new tag and fills in the row avoids retyping; paper sheets work for a small estate if they are entered the same evening and the sheet is kept as the source record. Either way, a photograph of the asset with its tag in place settles most later disputes about which machine a row describes. Before the team leaves an area, somebody checks that every asset in it is either tagged or on the exception list, so nothing is left in between.
Evidence the Programme Produces
A tagging programme produces three records, and the value of the exercise lies in all three rather than in the tags themselves.
What the programme hands over
Each record answers a different question a reviewer will ask.
Coverage
- Share of assets carrying a readable tag tied to a row
- Shown by asset class and by site, not as one figure
Exceptions
- Assets that could not be tagged
- The reason against each: unreachable, no surface, hostile conditions, disputed ownership
Reconciled register
- Rows with no asset, identified and valued
- Assets with no row, identified and described
- Locations and custodians corrected
A single estate-wide coverage figure hides the sites where coverage failed; broken down by class and site it becomes something to act on. An exception with a stated reason is a decision waiting to be taken; one without a reason is unfinished work. The reconciled register, not the tag count, is what a verifier looks at first, as the fixed asset verification checklist shows.
Keeping the Register True After Tagging
A tagged register decays at the speed of unrecorded movement, so the routine after the programme matters more than the programme did.
- Tie every move to its approval. The register is updated by whoever authorises a transfer between locations, departments or custodians, as part of the approval itself.
- Close every disposal in the register. Sale, scrapping or write-off carries its approval and document reference into the row; this is the event that otherwise leaves rows with nothing behind them.
- Tag new assets at receipt. The number is issued when the asset is capitalised, not at the next annual count.
- Inspect harsh areas on a schedule. Areas flagged at the survey are checked for worn tags, which are replaced with the same number.
Bring in an independent team where a verification is due, where the estate has moved sites, or where nobody can say when the register was last reconciled. Tags are only as useful as the reconciliation behind them, and an asset tagging engagement runs all four stages and hands back the reconciled register.
