Monday – Saturday, 8:00am – 5:00pm
Nicetags SolutionsNicetags Solutions
Guides

How to design an asset numbering convention

Your asset numbering convention is the one decision in a tagging exercise that is genuinely difficult to undo, reprinting thousands of tags because the numbering scheme broke down is expensive and disruptive. Getting it right before you order a single tag saves far more time than it costs to plan properly.

Get a quote Request free samples
7 years in business500,000+ assets tagged95+ organisations
How to design an asset numbering convention, Nicetags Solutions, Nairobi

Practical guide

How to design an asset numbering convention

Your asset numbering convention is the one decision in a tagging exercise that is genuinely difficult to undo, reprinting thousands of tags because the numbering scheme broke down is expensive and disruptive. Getting it right before you order a single tag saves far more time than it costs to plan properly.

This guide sets out the principles, walks through three worked conventions for different types of organisation, and lists the specific mistakes we see most often so you can avoid them.

Detail

Principles of a good numbering convention

A number must be unique for the life of the asset and never reused, even after disposal, reuse breaks any historical record, audit trail or insurance claim that referenced the old number. It should be fixed in length, using leading zeros so every tag prints the same width. And it should be independent of anything that can change: a number should still make sense five years and three department transfers later.

Simplicity matters more than it looks like it should. A numbering scheme that a data clerk or field officer can type without checking a reference sheet will have far fewer errors than a clever scheme encoding six pieces of information into every digit.

Detail

Three worked conventions for different organisation types

  1. 1

    County government or large public entity

    CTY-DPT-CAT-00001, e.g. NBI-HLT-ICT-00230 for the 230th ICT asset tagged under the Health department in Nairobi. Department and category aid reporting; the running number itself never changes on transfer, and department/category history is tracked in the register, not re-encoded into the tag.

  2. 2

    Private company, single site

    A flat prefix and running number, e.g. NTG-00001 upward with no embedded meaning beyond the organisation prefix. Category, location and department live entirely in the register. This is the fastest to administer and the easiest to explain to staff.

  3. 3

    NGO or donor-funded project with multiple funding sources

    PRJ-FND-00001, e.g. WSH-USD-00089 for the 89th asset under a water and sanitation project funded in USD. Funding source is often reported separately to donors, so encoding it can help quick filtering, provided the fund code is stable for the life of the asset even if the specific grant later closes.

Detail

How the three conventions compare

ConventionBest forTrade-off
Department/category codedLarge, multi-department public entities needing quick visual groupingMore complex to administer; risk of stale codes if departments reorganise
Flat sequentialSingle-site private companies, simpler reporting needsNo visual grouping on the tag itself, all filtering happens in the register
Fund/project codedDonor-funded or grant-based organisationsFund codes must be chosen to remain valid even after a specific grant closes
Detail

What not to do

  • Do not embed a location or building code in the number if assets are ever relocated, the number will lie the moment it moves.
  • Do not embed a custodian's name or staff number, people leave, transfer and change roles far more often than assets do.
  • Never reuse a number after an asset is disposed of, even years later, it breaks the historical link for anyone who searches that old number.
  • Avoid overly 'meaningful' codes that pack in cost centre, year and category all at once, every one of those can go stale and force a difficult decision about whether to keep an inaccurate code or break the convention.
  • Do not vary the number of digits across the same series, inconsistent widths look unprofessional and complicate sorting and validation.
  • Do not let two departments issue numbers independently without a shared register, duplicate numbers are one of the hardest errors to untangle after the fact.
Detail

How numbering feeds the tag schedule and the register

Once your convention is fixed, it drives everything downstream: the tag schedule (the list of numbers and any variable text to be printed, sent to us for production), the physical tagging sequence on site, and the register structure itself, where the number is the primary key linking every other field, description, cost, location, custodian, depreciation, to a single physical asset.

If you already have partial numbering in place from a previous exercise, decide explicitly whether to continue that series or start a clean one, and document the decision so future audits understand why numbers may have a gap or a change in format at a particular date.

Buyer questions

Questions about how to design an asset numbering convention

Choose a fixed length that comfortably covers your expected total over the next decade or more, with leading zeros, five digits (00001 to 99999) suits most organisations. Changing digit length later is disruptive, so it is worth slightly over-provisioning rather than under-provisioning.

Need another answer? Browse the complete asset tagging FAQ.

Start a conversation

Need help applying this guidance?

Tell us what you need tagged, how many assets you have and where they are used.

Request a Quote
Get a QuoteWhatsApp