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
Contents
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

How many digits should our running number have?

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.

Can we encode the acquisition year into the tag number?

You can, but be aware it adds a small amount of complexity for limited benefit, since acquisition date is already recorded in the register. If you do it, keep the year strictly as a prefix that never changes, and never let it be confused with a review or audit year.

What should we do about assets we already numbered inconsistently in the past?

Decide once whether to renumber everything to a clean convention or to keep the old numbers and only apply the new convention going forward, documenting the cut-over date clearly. Renumbering is disruptive but sometimes worth it if the old scheme is badly broken; a documented cut-over is usually the pragmatic choice.

Is it a problem if our numbering has gaps?

Not inherently, gaps from disposed or cancelled assets are normal and expected, provided they are documented rather than mysterious. What matters is that no number is ever reused for a different asset once issued. Keep a short note in the register explaining why each gap exists, disposal, write-off, or a number reserved but not yet issued, so a future auditor doesn't waste time investigating what looks like a missing asset.

Should barcodes and the printed number always match exactly?

Yes, always print the human-readable number alongside the barcode or QR code and make sure they encode the same value, a mismatch defeats the purpose of a scannable identifier and will cause errors during verification. If you ever reprint a damaged tag, check the replacement encodes the same number as the original rather than the next number in sequence, since a duplicate original elsewhere in the estate is far harder to trace than a straightforward reprint done correctly.

Can two departments share one numbering series safely?

Only if a single register or coordination point issues numbers centrally; if departments issue independently without coordination, duplicate numbers are almost inevitable and very difficult to untangle once tags are already printed and fixed to assets. The safer approach for most organisations is a single point of numbering, one person or system issuing the next number regardless of department, even if department and category are still recorded as separate fields in the register.

What is wrong with encoding cost centre into the tag number?

Cost centres change more often than assets do, through reorganisations, budget restructuring or departmental mergers, and once that happens, the printed number is either wrong or needs reprinting. Keep cost centre in the register and link it via the fixed number instead.

Does a good numbering convention have to be complicated to be useful?

No, the opposite is usually true. The simplest scheme that gives you a unique, stable, fixed-width number is normally the best one; complexity should live in the register, which can be searched and filtered, not in the printed code itself.

Who should decide the final numbering convention internally?

Finance or the accounting officer responsible for the asset register should approve the final format, since they are accountable for the register's reliability, though input from IT, procurement and operational departments helps make sure the scheme works practically across the organisation.

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