How to create a document numbering system
A document numbering system gives each controlled item one stable identifier and each approved issue a separate revision, so identity never changes when content does. See a worked QueryChart workflow and the checks needed to use it.
A document numbering system gives each controlled item one stable identifier and each approved issue a separate revision, so identity never changes when content does.
The short version
- Choose the identity rule: Define a unique ID format that survives title and owner changes; document who may issue the next number.
- Separate draft and issue revisions: Mark draft iterations separately, then assign an approved revision only after the issue decision.
- Test collisions and retrieval: Try duplicate requests, withdrawn drafts and renamed documents; confirm each resolves to one register entry.
How to create a document numbering system in practice
Do not encode every team, site and policy category into one fragile number. A document ID identifies the object; a revision identifies a state of that object. Keep the ID stable when ownership or a title changes and let register metadata carry the categories.
Choose a short prefix, a sequential unique number and a published revision rule. Reserve IDs centrally, mark abandoned IDs as void, and show the ID, revision and effective date on every page and in the master register.
See where a document receives its identifier
Follow the handoff where a stable document ID and an issued revision enter the control record.
Choose the identity rule
The new draft receives an initial draft version while the underlying document identity remains stable.
Separate draft and issue revisions
Reviewer comments increment draft revisions without making any of them effective for use.
Test collisions and retrieval
Approval assigns an issued revision, updates the history register and publishes the current copy.
How it works
Choose the identity rule
Define a unique ID format that survives title and owner changes; document who may issue the next number.
Separate draft and issue revisions
Mark draft iterations separately, then assign an approved revision only after the issue decision.
Test collisions and retrieval
Try duplicate requests, withdrawn drafts and renamed documents; confirm each resolves to one register entry.
Mistakes to avoid
Overloaded identifiers
When a code embeds owners and folders, a reorganization makes it wrong. Keep identity stable and update metadata instead.
Related QueryChart feature
Open the worked workflow
Adapt the document version control example to your numbering convention and approval route.
Frequently asked questions
Should department codes appear in every number?
Only if they remain stable; keep changeable categories in register metadata.
Can an abandoned number be reused?
Avoid reuse. Mark it void so an old reference cannot silently point to a different document.
Is a revision the same as a document ID?
No. The ID names the document across its life; the revision names one approved state.