Drawing Revision Control: A Step-by-Step ISO 19650 Guide

In construction and engineering, building from an outdated revision is one of the single most expensive mistakes a firm can make. Miscommunication and outdated drawing versions account for over 5% to 15% of total project rework costs.

We have all seen uncontrolled file directories filled with files like Drawing_A101_Final_v2.dwg or Drawing_A101_FINAL_FOR_CONSTRUCTION_2.dwg. This "version chaos" leads to site delays, contractor disputes, and severe liability exposure.

Software tools like SharePoint, Aconex, or Autodesk Construction Cloud do not solve version chaos on their own - a enforced process does. Below is a step-by-step guide to setting up a professional, audit-proof drawing revision control workflow aligned with ISO 19650 standards.

The Foundation: Understanding ISO 19650 Information States

Before standardizing file folders or naming rules, you must define the maturity level of your drawings. Under the ISO 19650 framework, a Common Data Environment (CDE) separates information into four distinct containers:

Work in Progress (WIP): Unverified design files actively being produced. Restricted strictly to the discipline team (e.g., structural team only).
Shared: Checked and approved files released for coordination across disciplines (e.g., sharing structural models with architects to catch clashes).
Published: The official, client-approved deliverables used for procurement, tendering, and construction.
Archived: An immutable, read-only audit log of every revision, transmittal, and milestone maintained for legal records.

ISO 19650 Revision & Status Code Quick Reference

Container	Revision Format	Status Code	Description
WIP	`P01.01`	`S0`	Initial unapproved draft
Shared	`P01`	`S1 - S4`	Suitable for coordination / review
Published	`C01`	`A1 - A5`	Contractual / Accepted for construction

Step 1: Enforce an ISO 19650 Naming Convention

You cannot control revisions if filenames are changed manually across edits. An ISO-compliant naming string allows both humans and automated software systems to parse drawing data instantly.

Standardized Delimited String Structure:

[Project]-[Originator]-[Volume/System]-[Level]-[Type]-[Role]-[Number]

Uncontrolled Example: GroundFloorPlan_Structural_v2.dwg
ISO 19650 Compliant Example: PRJ01-REC-ZZ-01-DR-S-0001.dwg

The Golden Rule of Revision Control: Never change the base filename between revisions. Do not append "_v2" or "_REV A" to the file name. Versioning must be managed via metadata, CDE attributes, or title block revision fields. Appending version numbers breaks CAD Xrefs, disrupts file links, and creates duplicate file clutter.

Step 2: Eliminate Deep Folder Hierarchies

Deep, nested folder structures cause broken file paths, OneDrive sync errors, and lost files. More critically, uncontrolled folder trees lead to "folder sprawl," where team members invent custom folders with arbitrary names.

Instead of relying on deep nested folders, implement a flat, metadata-driven approach:

WIP Folder / Library: Write access restricted to authors.
Shared/Published Folder / Library: Read-only access for existing files, and write for new files. No one must be able to edit or delete.

Step 3: Implement Automated QA/QC Gatekeeping

A drawing should not move from WIP to Shared or Published without passing a strict verification gate. However, in the reality of how we work with pressing deadlines, this does happen and your CDE must be able to cope with things needing to be issued if the checker is tied up. A poor CDE would be one that doesn't consider the realities of engineering where restrictions like these will likely be bypassed, leading to issues that may never get checked even after issuing.

Author Sign-Off: Author flags the drawing as Ready for Review.
Technical QA Check: BIM manager / Lead engineer checks model geometry, layer standards, and filename compliance.
Approval & State Change: Upon approval, the file status increments (e.g., from P01.02 to P01) and moves into the Shared container automatically.

Pro Tip: Manual visual checking of title blocks and drawing revision numbers is time-consuming and error-prone. Tools like Drawing Checker automate drawing revision checking and quality control across entire drawing sets before issue.

Step 4: Maintain an Audit-Proof Issue Register

Having the correct file in your CDE is only half the battle; you must maintain a legal record showing who received which revision and when.

Your Issue Register (Transmittal Log) must record:

Drawing Number and active Revision Code (e.g., Rev P02).
Exact timestamp of transmittal.
Recipient organization and email address.
Suitability Code (e.g., S3 - Suitable for internal review and comment).

Automating Revision Control Across Your Engineering Firm

Managing revision control manually through spreadsheets and folder moving creates administrative bottlenecks as project volume scales.

By transforming your standard file system or SharePoint setup into a dedicated Common Data Environment, you can implement ISO 19650 metadata tags, generate real-time issue registers, and stop revision errors automatically.

Ready to eliminate version chaos?

Explore Environment: Drive based or SharePoint CDE Integration for AEC →

Loading...