Skip to content
WorkStudio Help Home
Knowledge Hub

BIM Naming, Status, Revision, and Suitability Codes

Explains why naming conventions, revision rules, status, and suitability are essential to reliable BIM information management.

Open Knowledge Hub ↗

Simple stack of model and document tiles with abstract status chips.

Information only — not legal advice.

Names, status and revision codes answer different questions. A stable identifier tells you which information container you are looking at. A revision distinguishes its editions. Status or suitability tells you the purpose for which it may be used.

Keeping these meanings separate helps people avoid treating the newest file as automatically authorised for their task.

Agree a convention before the first exchange

Decide which identification fields matter, their order, permitted characters and controlled values. Typical fields may identify the project, originator, location, type, discipline and unique number. Use the applicable project standard and national provisions where adopted rather than assuming one naming pattern is universal.

Keep a short code register with descriptions and examples. Check how the convention behaves in exports, downloaded filenames and receiving systems; a rule that depends on hidden metadata may not survive an ordinary file transfer.

An illustrative identifier

For a fictional project, HBR-MEP-B01-DR-0042 might identify a services drawing for building B01. Its revision could be P03, and its suitability could be “for coordination.” These are example project values, not prescribed ISO or Romanian codes.

The identifier remains stable when the same drawing is revised. A release record identifies the revision and intended use. If a filename also carries revision and status, keep it consistent with the document title block, metadata and transmittal.

Avoid names such as final-new-approved2.pdf: they do not explain the controlling convention or which approval applies.

Revision is not authorisation

Revision P04 may be newer than P03 but still be a draft. P03 may remain the authorised issue for a particular activity until a replacement completes the required review and release process.

Do not overwrite an issued revision with changed content. Preserve the earlier issue and record what changed, why, who checked it and which recipients received the replacement. “Superseded” should remain understandable to someone who encounters a downloaded copy.

Example: coordinating while construction continues

A fictional team develops a design change in a new working revision while the site uses the current authorised issue. The coordination package clearly identifies its limited purpose. Once the change is approved through the applicable process, the issuer publishes the replacement and communicates its effect on the previous issue.

The crucial control is the connection between identity, revision, suitability and release evidence. Renaming the coordination file “construction” would not create the missing authorisation.

Check the whole package

Before release, compare identifiers and revisions across the model, drawings, schedules, issue manifest and approval record. Verify that links open the intended revision and that recipients can interpret the status without access to an internal conversation.

Use automated filename and metadata checks where appropriate, with human review of meaning and authority. A correctly formatted name does not prove technical correctness.

The UK BIM Framework guidance on the common data environment explains information workflow concepts in its implementation context. Adopt codes deliberately in your project documentation; do not present UK-specific conventions as universally required. Continue with document control and ISO 19650 in plain language.

Important information

This article provides general information and does not constitute legal advice or replace a qualified professional's assessment of your circumstances. Laws, official guidance, standards and product features can change. Check current primary sources and the requirements applicable to your jurisdiction, contract and project before making decisions. Examples illustrate the discussion; they are not official rulings or instructions for a particular case. For legal decisions, consult a qualified lawyer; for technical or other specialist matters, consult the responsible professional.

Enable JavaScript to use reading progress and usefulness ratings.