What is a document numbering system?
A document numbering system is the agreed convention that gives every drawing and document on a project or asset a unique, structured identifier, so the number itself records what the document is and where it belongs.
The number is the handle everyone uses. It is stamped in the title block, listed in the drawing register, quoted on a transmittal, cited in the specification, and typed into a work order twenty years later. Together with the revision, it is the unique reference to one exact version of a document.
Also called a numbering convention · a document numbering scheme · a naming convention under ISO 19650
A structured number, read left to right.
A convention breaks the identifier into fields, each with a fixed position, a fixed length, and an agreed set of values. Read the fields in order and you know the asset, the discipline, the kind of document, and where it sits in the sequence.
Every field you add makes the number more readable and less stable. Encode only what will still be true in twenty years.
- AWAsset or project
Which asset, site, or project the document belongs to. On an estate this is the code an owner never changes.
- ELDiscipline
The engineering discipline that owns the document, for example electrical, mechanical, civil, or structural.
- DRDocument type
What kind of document it is: a drawing, a specification, a report, a schedule, or a model.
- 0140Sequence
The unique number within that group, usually zero-padded so the register sorts predictably.
- CRevision
Which iteration you hold. Some schemes append it, and others hold it as a separate field beside the number.
An intelligent, or significant, number encodes meaning in the string, so a fitter reading a print in a plant room can tell the asset, the discipline, and the document type without a system in front of them. A non-intelligent number is a plain sequence with the meaning held as metadata beside it.
The trade is readability against stability. An intelligent number becomes wrong the day a document is reclassified, a discipline is merged, or a building is renamed, and the choice then is a misleading number or a renumber. A non-intelligent number stays true for the life of the asset and tells a reader nothing on its own. Most owners land in between: a short intelligent prefix that will not change, then a plain sequence, with everything else held as searchable metadata.
The conventions most schemes are built on.
Few owners start from a blank page. A numbering convention usually draws fields from one of the published standards below, then adds whatever the asset needs. What matters is that the convention is written down, agreed, and applied by whoever books documents in.
ISO 19650 asks the project information standard to define a naming convention for every information container. The UK National Annex sets out the fields, separated by hyphens: project, originator, breakdown by function and space, form, discipline, and number.
The Australian technical drawing standard requires every sheet to carry a title block holding the drawing number, title, revision, scale, and sheet, so the number stays readable on the printed sheet as well as in the register.
Structuring principles and reference designations for industrial systems. Part 12 covers construction works and building services, and it gives a way to designate the object a document describes, which most owners tie to their asset hierarchy.
Power plant coding systems. KKS is the long-standing plant identification system, and RDS-PP succeeds it on ISO and IEC 81346 principles. Utilities and generators often number documents against these plant codes.
Classification and designation of documents for plants, systems, and equipment. It gives each kind of document a code, so the document type field in a number can follow a published table rather than local habit.
Uniclass in the UK, and OmniClass and MasterFormat in North America, classify the works and the elements a document covers. A numbering convention often borrows a field from one of them rather than inventing its own.
Where numbering goes wrong.
Numbering rarely fails during design. It fails at handover, when a contractor set numbered one way meets an owner register numbered another, and someone decides to renumber several thousand files in the last fortnight of a project.
- The contractor numbers to their scheme and the owner to theirs, and nobody settles which one wins until the handover package arrives.
- Renumbering breaks every reference that points at the old number: sheet cross-references, XREFs, specification clauses, operation and maintenance manuals, and work orders in the maintenance system.
- The old number disappears, so a search for the number written on a nameplate, a valve tag, or a ten-year-old work order returns nothing.
- The revision history stops at the renumbering, and the record of what was issued and when is lost with it.
- Numbers are edited in a spreadsheet while the files keep their old names, so the register and the drawings drift apart within a week.
Set the owner scheme in the information requirements at appointment, so documents arrive numbered correctly. Where a renumber is unavoidable, keep the old number as a legacy identifier, carry the revision history across, and issue the mapping.
Read how the record set comes together across a projectNumbering applied on the way in.
Book a document in and Lunr numbers it to your convention, reads its title block into metadata, and files it in the register, so the scheme holds without anyone policing it.
- Automatic numbering applies your register format, prefix, and sequence as each document is booked in, so numbers follow the convention without being typed by hand.
- Existing numbers are preserved on import, so a bulk migration keeps the numbers your asset already runs on.
- Title-block tags are read from the sheet into metadata, so the drawing number, revision, discipline, and sheet size come off the drawing rather than out of a keyboard.
- Version numbering increments as a document goes through workflow, and the revision is synchronised back to the title block.
- XRAY searches the text inside every drawing, scans included, so a document number written on an old sheet is still findable.
- Tag documents by asset, discipline, or location, then filter the register on those tags rather than on the number alone.
automatic numbering · title-block parsing · metadata tags · existing numbers preserved · export anytime
Questions about document numbering.
- What should a drawing number contain?
- Most conventions encode four things: the asset or project, the discipline that owns the drawing, the document type, and a sequence number. Many add a sheet number, and the revision is either appended or held as a separate field. The drawing number and the revision together form the unique reference to one exact version of a drawing, which is why a change is always made against a known revision.
- What is the difference between intelligent and non-intelligent numbering?
- An intelligent number encodes meaning in the string, so a reader can tell the asset, discipline, and document type from the number alone, even on a printed sheet with no system to hand. A non-intelligent number is a plain sequential identifier that carries no meaning, with the asset, discipline, and type held as metadata beside it. Intelligent numbers are easier to read and harder to keep true, because reclassifying a document means either a wrong number or a renumber. Non-intelligent numbers never go stale, and they depend on a register being available to interpret them.
- Does ISO 19650 define a document numbering convention?
- ISO 19650 requires that every information container carry a unique identifier under a naming convention agreed for the project, and it asks that the convention be set out in the project information standard. It does not impose one universal string on every project worldwide. In the UK, the National Annex to BS EN ISO 19650-2 publishes the field structure most projects follow, and other regions either adopt that or define their own.
- Should you renumber a contractor's drawings at handover?
- Settle the numbering before the project starts, in the information requirements, so drawings arrive numbered to the owner's scheme. If renumbering is unavoidable, keep the original number on the record as a legacy identifier so a search on the old number still finds the drawing, carry the revision history across, and issue the mapping to everyone who holds the old numbers. Renumbering quietly at handover breaks the references in specifications, manuals, and maintenance work orders that point at the old numbers.
One numbering scheme, applied on upload.
Book a walkthrough and watch Lunr number a document to your convention, read its title block into metadata, and file it in the register.
10M+ documents under management · Hosted in Australia and the US · SAML · Full audit trail · Export anytime
- entity
- Lunr Labs Pty Ltd
- location
- Melbourne AU
- workspace
- documents.lunr.app
- rev
- 2026