A structured approach to document and drawing management is a critical success factor for construction projects. When owners, architects, engineers, contractors, and subcontractors collaborate, all project participants must be able to identify the correct, approved, and current document version at any time.

The recommendations in this article are aligned with the principles of ISO 19650 (Information Management using BIM) and DIN SPEC 91391 (Common Data Environments for BIM Projects). Both frameworks emphasize document identification, revision management, approval workflows, traceability, and controlled information exchange.

The objective is to establish a consistent, transparent, and scalable document control process throughout the entire lifecycle of a construction project.

🎯 Purpose of a File Naming Convention

A well-designed file naming convention should immediately answer the following questions:

• ✅ Which project does the document belong to?
• ✅ Which discipline created the document?
• ✅ What type of drawing or document is it?
• ✅ Which revision is currently available?
• ✅ Is the document approved for use?

⚠️ Common Challenges Without Standards

Many construction projects start with file names such as:

GroundFloorPlan.pdf
GroundFloorPlan_New.pdf
GroundFloorPlan_Final.pdf
GroundFloorPlan_Final_v2.pdf

After only a few months it often becomes difficult to determine:

• ❌ Which version is currently valid
• ❌ Which version has been approved
• ❌ Which version was issued to contractors
• ❌ What changed between revisions

This often leads to coordination efforts, misunderstandings, construction errors, rework, project delays, and avoidable risks.

🏗️ Recommended File Naming Structure

📌 Example

🧩 Meaning of Each Segment

• Project
  PROJECT-A
• Building Part
  K1
• Level
  GF (Ground Floor)
• Discipline
  ARC = Architecture
• Drawing Type
  FP = Floor Plan
• Drawing Number
  0101
• Revision
  C
• Status
  APPROVED

🔠 Why Use Underscores (_) Instead of Hyphens (-)?

Teamsware recommends using underscores as field separators. Hyphens are frequently used inside project names, building identifiers, or document descriptions.

🚀 Benefits

• ✅ Clear field separation
• ✅ Easier automation and validation
• ✅ Better workflow integration
• ✅ Reduced interpretation errors
• ✅ Improved readability

✅ Recommended

PROJECT-A_K1_GF_ARC_FP_0101_C_APPROVED.pdf

❌ Not Recommended

PROJECT-A-K1-GF-ARC-FP-0101-C-APPROVED.pdf

🔄 Why Revision Management Is Essential

The revision identifies:

“Which technical version of the document is available?”

📝 Example

0101_A
0101_B
0101_C

The drawing number remains unchanged. Only the document content evolves over time.

• ✅ Complete revision history
• ✅ Traceability of changes
• ✅ Clear documentation of plan versions
• ✅ Auditability
• ✅ Improved project transparency

✅ Why Status Management Is Equally Important

Status answers a different question:

“May this document be used?”

🧐 Example: Under Review

PROJECT-A_K1_GF_ARC_FP_0101_C_REVIEW.pdf

Revision C – Status: Under Review

✅ Example: Approved

PROJECT-A_K1_GF_ARC_FP_0101_C_APPROVED.pdf

Revision C – Status: Approved

The revision remains identical. Only the document status changes.

📚 Typical Status Values

• PREL – Preliminary
• REVIEW – For Review
• APPROVED – Approved
• CONSTRUCTION – Approved for Construction
• AS-BUILT – Final Documentation
• ARCHIVED – Archived

🚫 The Most Common Misconception

Many project participants assume:

“The highest revision is automatically the valid drawing.”

This is not always correct.

• ✅ Revision B – APPROVED → Valid
• ❌ Revision C – PREL → Preliminary
• ❌ Revision D – REVIEW → Under Review

Although Revision D is newer, Revision B may still be the only approved version available for construction work.

Revision and status must always be considered together.

🚀 Benefits of a Standardized Naming Convention

⭐ Teamsware Recommendation

• ✅ Keep drawing numbers unchanged throughout the lifecycle.
• ✅ Manage technical changes through revisions.
• ✅ Manage usability through status codes.
• ✅ Preserve all revisions for traceability.
• ✅ Use underscores as mandatory field separators.
• ✅ Make revision and status compulsory elements of document control.

📊 Management Summary

Revision and status are not administrative overhead.

They are essential tools for professional document control.

Revision answers:
“Which version is this?”

Status answers:
“May this version be used?”

Only the combination of revision and status provides the transparency, governance, and traceability required for professional construction document management.

📚 Standards Reference

This best-practice recommendation is aligned with the principles of internationally recognized information management standards.

• ISO 19650-1
  Organization and digitization of information about buildings and civil engineering works – Concepts and principles.
• ISO 19650-2
  Information management during the project delivery phase.
• DIN SPEC 91391
  Common Data Environments (CDE) for BIM projects – Functions, modules, and information exchange.

🎯 Purpose of These Standards

• ✅ Unique document identification
• ✅ Traceable revision history
• ✅ Transparent approval processes
• ✅ Prevention of incorrect document usage
• ✅ Consistent collaboration between project participants
• ✅ Structured information management throughout the project lifecycle