In this guide
How an Asset Tagging Programme Runs
A tagging programme runs in four stages, and the order is not negotiable: agree the numbering convention, capture what is physically there, apply the tags, then reconcile the captured population back to the register. Programmes that buy tags first almost always renumber later, because the convention was never settled and the printed stock encodes a decision nobody had made. Capture comes before application because you cannot sensibly tag an asset you have not described; the walk-round establishes what exists, in what condition and in whose custody. Application is the fastest stage and the one most people budget for as though it were the whole job. Reconciliation is where the value is: register lines with no asset behind them, assets on the floor with no register line, and lines whose location or custodian was wrong. What comes out at the end is a register in which every line has a number and every number has an asset.
Designing the Numbering Convention
The convention is settled before anything is purchased, and three questions decide it. What, if anything, the code encodes: location, class and sequence are the usual candidates, and only the last of them is safe. Location changes when the asset moves and class changes when the accounting policy is revised, so both convert a permanent identifier into a temporary one. A code that encodes nothing but position in a sequence never needs reissuing. Why intelligent numbering ages badly is worth stating plainly rather than as a preference. Every encoded attribute is a prediction that the attribute will not change, and over the ten or fifteen years an asset register spans, sites are consolidated, departments renamed and classes reorganised. Each of those events turns part of the code into a false statement, and the remedy is always either an inaccurate register or a renumbering exercise. Length, check digits and human readability are the practical constraints. The code has to fit on the smallest tag, be readable after wear, be speakable over a telephone without ambiguity, and ideally carry a check digit so a transcription error is caught at entry rather than at the next count.
Choosing Where the Tag Goes
Tag placement is decided by walking the estate rather than at a desk, because the constraints are physical. Surface is the first: the label needs a flat, clean, non-porous area large enough for the code, and machines that offer none require an alternative such as an engraved plate or a tag on a bracket. Heat rules out large parts of many machines, since adhesives fail well below the temperatures a motor housing or a hot zone reaches. Wash-down environments destroy paper and lift labels at the edges, so they need a sealed substrate and often a protective overlaminate. Abrasion decides the rest: a label where hands, trolleys or brushes pass will wear regardless of specification. Line of sight matters wherever an optical tag is used, and the position has to be readable from where a counter can stand without moving the asset or bringing a ladder, which frequently rules out the tidiest location. Assets that cannot carry a visible tag need a documented alternative agreed in advance: an internal identifier recorded with a photograph, a plate on the nearest fixed structure with the relationship recorded, or a bulk-readable tag where line of sight is impossible.
Capture and First Reconciliation
Capture happens at the moment of tagging and records more than the number. Location, custodian and condition are recorded for each asset as the label goes on, because the team is already standing in front of it and no later exercise will have the same access. Condition in particular is worth capturing then, since it is the field that triggers the impairment question and it cannot be reconstructed from a desk. Matching to the existing register follows immediately rather than at the end of the programme. Each captured asset is looked for in the register, and the three outcomes are recorded separately: matched cleanly, matched only after resolving an ambiguous description, or not found at all. Doing this as the work proceeds means a systematic problem, such as a whole department recorded under a different site, is caught on the second day rather than the last. Assets with no register line are the population the programme exists to surface. Each is recorded with everything observable, a photograph and whatever the custodian can say about where it came from, and it is then investigated against purchase records, since most turn out to have been expensed rather than never bought.
Evidence the Programme Produces
A tagging programme produces three artefacts, and the value of the exercise is in all three rather than in the tags themselves. The first is the coverage rate broken down by asset class and by site, which states what proportion of the estate now carries a readable identifier tied to a register line. Reported as one estate-wide figure it conceals the sites where coverage failed; reported by class and site it becomes actionable. The second is the exception list of assets that could not be tagged, with the reason recorded against each: assets in continuous operation that could not be reached, assets whose surface will not hold an adhesive, assets in environments that destroy labels, and assets whose ownership was disputed on the day. An exception with a stated reason is a decision waiting to be taken; an exception with no reason is simply unfinished work. The third is the reconciled register handed back at the end, in which register lines with no asset and assets with no register line have both been identified and quantified. That reconciliation, rather than the tag count, is what an auditor examines first.
Keeping the Register True After Tagging
A tagged register decays at the speed of unrecorded movement, so the discipline that follows the programme matters more than the programme did. Every movement between locations, departments or custodians has to update the register at the time it happens, and the practical way to achieve that is to make the register entry part of whoever authorises the move rather than a separate task somebody remembers later. Disposal needs the same treatment, because it is the event that generates ghost assets and the one with no document naturally forcing itself into the ledger. A re-tagging cycle handles wear. Labels degrade at a rate the environment sets, so areas identified as harsh at the original survey are inspected on a schedule and worn tags are replaced with the same number, never a new one. An independent team is worth bringing in where a verification is due, where the estate has moved sites, or where nobody can say when the register was last reconciled, since asset tags are only as useful as the reconciliation standing behind them.
