Productivity & Best Practices 3 min readORG-F30

Engineering Document Numbering: A Naming Convention That Survives Revisions

Share

A document number should identify an information object without embedding every attribute that may change. A durable convention separates stable identity from metadata such as title, status, revision, language, format and file name.

The short answer

Define the information scope and owner, then choose the minimum stable segments needed for uniqueness and retrieval—such as organization or project, plant/system context, information kind and sequence. Keep revision and lifecycle status in separate controlled fields rather than inside the permanent number. Specify allowed characters, length, separators, leading zeros, reserved values, assignment authority and duplicate prevention. Test the scheme against multilingual titles, supplier documents, bulk imports, supersession and future expansion before migration.

  • Identity remains stable when title, status, file format or revision changes.
  • Every encoded segment has one governed meaning.
  • A central assignment process prevents duplicates and reuse.
  • The visible file name is not the complete metadata record.
Stable identity is deliberately smaller than the complete document description.
Text-free engineering document identifier model separating stable number from title, revision, status, language and file format

Stable identity is deliberately smaller than the complete document description.

Decision guide

ElementKeep in stable number?Reason
Project/system codeSometimesUseful only if the object never moves across that boundary
Information kindOftenSupports classification when governed and stable
Revision/statusNoChanges through the lifecycle
Title/language/formatNoHuman-facing and mutable metadata

A practical workflow

  1. 01

    Inventory current schemes, collisions, business needs and legacy obligations.

  2. 02

    Define the object being identified and its metadata model.

  3. 03

    Design segments, code lists, sequence allocation and validation rules.

  4. 04

    Pilot representative documents, suppliers, languages, revisions and imports.

  5. 05

    Approve governance, migration map, aliases and exception process.

Governance prevents duplicate, reused and ambiguous identifiers.
Text-free numbering governance flow covering request, validation, allocation, release, retirement and legacy mapping

Governance prevents duplicate, reused and ambiguous identifiers.

Evidence and acceptance

Keep the numbering policy, scope, data dictionary, code owners, segment syntax, examples and counterexamples, sequence allocation log, reserved and retired values, duplicate checks, validation rules, legacy mapping, supplier rules, exception approvals, migration results and periodic governance review.

Common mistakes

  • Encoding title, status and revision into one long identifier.
  • Reusing a cancelled number for a different object.
  • Allowing every supplier to interpret segments differently.
  • Using folder path as document identity.
  • Migrating without a permanent legacy cross-reference.

Responsibility boundary

Primary sources

Technical claims and product boundaries were checked against these primary sources. Fact-checked

  1. IEC 81355-1:2024 — Classification and designation of informationInternational Electrotechnical Commission
  2. IEC 82045-1:2001 — Document management principles and methodsInternational Electrotechnical Commission

Frequently asked questions

Should revision appear in the document number?

Usually no. Treat revision as controlled metadata so identity persists across revisions.

Can the file name equal the document number?

It can include it, but file name, title, format and revision remain separate metadata.

How are supplier numbers handled?

Preserve supplier identity and map it to the project-controlled identifier without overwriting either.

Does AutoNexit assign numbers automatically?

It can store and validate configured records, but the organization remains responsible for its scheme and authority.

Related articles